Discussion
IN
Last activity: 24 Aug 2015 3:20 EDT
Pega Migration Rules and OOTB Concepts
Hello Everybody,
I have the following doubts in mind for a long time. Any help on this would be pretty much appreciated.
1) What is OOTB(Out of the Box) in Pega and is this concept physically accessible or it is same as all the services provided by Pega?
2) Can you please let me know the detailed process of Migration( listing all the possible meanings for migration in pega)? In detail meaning a clear explaination of what it is done and how it is achieved?
Thanks in advance!!
Virtusa Corp.
US
Hi Prasannna,
For your Query 1:-
1) OOTB means for any functionality you require for example creating a case instead of writing your own activity you can use Work-Cover-.Add or AddWork activity using the Process API.
2) if you want to generate ID use OOTB Work-.GenerateID activity
3) UI rules you have Perform,New, Review,Confirm etc. harness you can direclty use them without any modification until you want see some application specific data.
Query2:-
1) You can create product rule using wizard DesignerStudio--> Application -->Distribution-->Package you need to select the related rules for this application etc.
2) approach using DesignerStudio-->Applicatino-->Distribution-->Export you can either export by Ruleset version or by patch or using the product created above