TechTuts

 Follow & Subscribe to this blog. A detailed End to End Project Explanation with each step will be posted in the 4th week of Jan 25. So be connected.   PEGA Project Implementation  steps involved are: - Requirements gathering  - Analysis - Prepare Test Case Documents - New  ( Scratch) -Existing Application ( Proposed Functionalities) - What are the Current Functionality &  What will be the Future Functionality. Prepare the Test Case Documents. Share these documents with TechLeads & BA (Business Analyst) - BA will Prepare the Requirements - BA will have complete idea about application functionality ( End users also have Functional knowledge) - BA will identify No of Requirements  ( 10), Duration ( 3 Months) , Decide the Release date. ( When the code will move to the Live Server) Methodology: Water Fall Methodology: (Present not using) - Requirements - No Deadlines ( Dead Lines can be extended) - Status Calls, but specific process to set...

  ✪       Below are the objects (components) involved in Admin part: Operator ID, Access Group, Application, RuleSet Name, RuleSet Version, Organization, Division & Unit 1.       Organization hierarchy: ⮚       Pega supports a three-level organizational hierarchy as: Just a logical structure ⮚       Go through the Organization features ( Access Groups or Rulesets and global level Calendar ) ⮚       Usually – Division or Unit may be geographical location or department. Your wish 2.       RuleSet hierarchy: ⮚       RuleSet a set of related rules in it & provides Packaging (for deployment), Versioning and access control ☞       RuleSet is like folder structure (like container ) in windows ⮚       RuleSet Name contains multiple v...