PEGA PRPC contents: PEGA is useful to develop software for concepts like BPM (Business Process Management) and CRM (Customer Relationship Management). This is used to improve the services & products for customer engagement and digital process automation in order to enhance the business. PEGA makes things very easy for the customer as the software is simple and straight forward. PEGA is useful in large organizations and industries as well as small scale businesses also. Advantages in Pega Technology • Business Friendly Toolkit • Pega Application Maintenance is much Easier Compared to Salesforce • Once Designed Deploy anywhere • Quick Developments • BPM Provides the Case life cycle Management • It won’t require any coding • It doesn’t Require any Conventional Programming Comparison between Salesforce and Pega:- Pega Platform is most popular with enterprise software users while Salesforce is preferred by reviewers from midsize companies. Who can learn:- 1. Bachelor's degree in Software Engineering or Computer Science. 2. Proven work experience as a Pega Developer. 3. Advanced knowledge of Pega PRPC 5. ... 4. Familiarity with J2EE, XML, Java, JSP, and EJB. 5. Familiarity with Scrum and Agile methodology. • Any graduate or fresher’s, who wish to start an exciting career in Pega development. • Experienced professionals like developers/Testers/Business Analyst/Managers who wish to switch to Pega. • Freelancers doing own development/testing having sound knowledge in Java concepts, J2EE, XML, Java, JSP and EJB Pega Devloper responsibilities:- • o As a PEGA Developer you must be able to develop enterprise level applications. o Good knowledge about Agile and Scrum Methodology o Strong experience and knowledge about OOPS concepts o Technologies such J2EE, JSP,EJB,Xml and Java o Must be Well-versed in PRPC (Pega Rules Process commander ) o Must have knowledge and experience in working with Agile Methodology o Ability to work with SCRUM/Pega Smart o SOAP, PL/SQL are important and having knowledge of Oracle is a plus o Ability to code and it is good when you are proficient in these following languages like Java, Jquery, Angular JS etc o Its good to know these tools Visio, UML and Excel. o Knowing Web Technologies such as HTML, XML, must be strong in JavaScript, XHTML, CSS is a plus These are the following Job responsibilities to become a PEGA developer Disadvantages in Pega Technology  BPM tool is Expensive little tool  Development and maintenance is cost  Don’t go small scale industries for the license  It’s a little complex at starting Advantages in Salesforce technology  Using Salesforce there is low risk  Salesforce has good Customer care service  It has a good brand name around the world  It is one of the most popular CMRs  No need to purchase any software and hardware systems for Running the applications  Salesforce Technology gives more analytics to expand the Campaign effectively  Salesforce technology Updates automatically Disadvantages of salesforce technology  More Tool Kits can be used for Customization  In the process of Automation, users can lose their personal touch  The cost is more for redesign the application  No service agreement for the standard contract 15 calsses: 1. PegaPRPc installation 2. Operator creation 3. New Application creation 4. Implementation an Framework Layer 5. Ruleset definition 6. Org, Div and unit creation 7. Admin and author operator for new application 8. Operator security 9. Case life cycle creation 10. Stages and Process creation 11. Flow creation 12. Assignments connector and flow action 13. Section and Other UI component 14. Validations, Post and Pre Activity and Data transform creation 15. Manager portal 16. Access group creation 17. Access role 18. Work basket creation 19. Work group creation 20. Circumstance rules 21. Report def creation and joins, sub reports 22. Email configuration 23. Data type creation 24. SOAP intereation R u ok with below Content and is it similar to your study? BPM Overview, Project Implementation Methodology, Class Structures & Hierarchy • Introduction to BPM • Introduction to PRPC • Smart BPM • Build for change • Application Documents • DCO • Application Express • PRPC frameworks • Class structure in PRPC • ECS • Inheritance • Class groups Data Modeling • Define PRPC classes • Data branch • Property Types and Modes – Single and page properties Process Flow – Flow & Flow Actions, SLA • Different flow shapes and their purpose • Usage • Creation • Flow Actions • SLA – Creation, Usage User Interface • Properties display and validation • Layouts • Harness • Sections • Style Branding • Decision Rules • Creation of different decision rules, usage inflows and activities. Declarative rules • Forward chaining • RDE • Declare constraints • Declare triggers • OnChange Case Management • Workflow • Units of work • Work status • Locking • Design correspondence • Send correspondence PRPC Database Concepts • Role of PegaRules DB • A link between rules and DB • Basic tables • Exposing column properties Activities • Definition • Configuration • Steps • Parameters • Security • Common methods Integration with external systems • SOA • HTTP • SOAP • WSDL • Connectors & Services • Listeners • Connect SQL Rule Management & Security • Rule • Ruleset • Ruleset version • Rule resolution algorithm • Operator ID • Access group • Access role • Privilege Performance, PRPC Guardrails & Topics revision • Clipboard • Alerts • Pre-flight • PAL • DB trace • Tracer • SMA • 10 guardrails • Iterative approach • Class structure • Build for change • Design intent driven process • Security and object.