Application types in Pega
- Application Profiler - for B.A. non technical persons, to build visio diagram.
- Application Accelerator - Developer
- Application express - Infront application for demo
Steps:
- Choose - (reusable) framework and Implementation.
- Give objective of the application
- Give Organisation name: BOA (name of organization layer)
- Give class name 'Leave'
- Give various Data type names (table name) - new table 'leaveBal'
- Your choice where you want to build the table whether in (organization enterprise org layer -) framework layer or implementation layer
Review:
Organisation layer.
- work class (business layer)
- Data class (for all data tables)
- Integration class
(..We didn't give division layer)
Framework layer
- Work class (business layer)
- Data class (for all data tables)
- Integration class
- Implementation layer
- Work class (business layer)
- Data class (for all data tables)
- Integration class
User
- Access group
- Access Role (Admin, manager, user)
- Work Groups (group emails hold all email in particular group)
- Work Baskets
Complete the wizard, Create the application - 4 users with passwords created for the application.
- The application will be loaded.
- You can view operator details by clicking the top right corner,
- You can can change profile details, update the password.
- You can open rules - your application built on Pega rule.
Cases -> Leave
Records (only data) -> Oraganisation -> Operator id
Records -> Security -> Access group
Records -> Application -> id
App (explorer)-> find your class, and Rules
BOA Timeoff Work - class and child as below,
- BOA. - Organisation layer classes
- BOA-Data - Organisation data class
- BOA.FW. - framework layer classes
- BOA-FW-Data - framework layer data classes
- BOA-TimeOff - Implementation layer classes
- BOA-TimeOff-Data - Implementation data layer classes
Data (explorer)-> LeaveBal (table you can see)
If you choose BOA.TimeOff-Work -> you will see below
Case (explorer) -> you can see various type of cases of your application
Define the stage first
A stage is a collection of business processes. Stages represent show where a case is at any time during its process
Lifecycle - from creation to resolution. for example, a purchase request case can have these stages in this
Sequences.
1. Request
2. Vendor addition
3. Quote
4. Approval
5. Procurement
6. Closes
Case -> lifecycle -> add stages -> group a flow
1. Apply leave (Leave application stage), You can give SLA (Service Level Agreement)
2. Approvals
3. Notification
You can alternate stage by Actions -> Configure alternate stages
1. Rejected Notification (when approval rejected)
Done
No comments:
Post a Comment