Question
Endeavour Energy
AU
Last activity: 8 May 2024 20:18 EDT
Sample implementation for "Enrollment/Add a Task to a TODO list" design pattern
By theory the below design pattern matches our business requirement, I am looking for sample implementation for this design pattern.
"Enrollment/Add a Task to a TODO list" design pattern.
Our requirement is to process list of dynamically created recommendations to be processed via assignments and each tasks items will have its own lifecycle with SLA.
Accepted Solution
Updated: 8 May 2024 20:18 EDT
Pegasystems Inc.
GB
@Balamurugan Balakrishnan if there are no suggestions on this forum I would suggest that you contact our Pega consulting services for your requirements.
Pegasystems Inc.
GB
@Balamurugan Balakrishnan please clarify your question.
In Pega, you can implement this design pattern using Case Types and Assignments.
- Create a parent Case Type for the TODO list. This will represent the entire list of tasks.
- For each task in the TODO list, create a child Case Type. This will represent an individual task. You can dynamically create instances of this Case Type as needed.
- In the child Case Type, use Assignments to represent the different stages of the task's lifecycle. You can add an Assignment for each place in the task's lifecycle that requires human judgment or input.
- For each Assignment, you can set a Service-Level Agreement (SLA) to ensure that the task is completed within a certain timeframe.
- You can use the routing options in the Assignment to assign the task to a specific user or group of users.
- As each task is completed, you can update the status of the parent Case to reflect the progress of the TODO list.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
Assignment shapes in Processes
@Balamurugan Balakrishnan please clarify your question.
In Pega, you can implement this design pattern using Case Types and Assignments.
- Create a parent Case Type for the TODO list. This will represent the entire list of tasks.
- For each task in the TODO list, create a child Case Type. This will represent an individual task. You can dynamically create instances of this Case Type as needed.
- In the child Case Type, use Assignments to represent the different stages of the task's lifecycle. You can add an Assignment for each place in the task's lifecycle that requires human judgment or input.
- For each Assignment, you can set a Service-Level Agreement (SLA) to ensure that the task is completed within a certain timeframe.
- You can use the routing options in the Assignment to assign the task to a specific user or group of users.
- As each task is completed, you can update the status of the parent Case to reflect the progress of the TODO list.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
Assignment shapes in Processes
Glossary: A > Glossary for Assignment:
Updated: 29 Apr 2024 2:34 EDT
Endeavour Energy
AU
@MarijeSchillern , Thanks for the reply.
I am looking for an option without case type, todo lists are generated by AI and they are dynamic. We don't know the number of items to be processed.
we have constrain with number of cases in our landscape. Looking for some option with data instances but supports assignment and SLA.
Accepted Solution
Updated: 8 May 2024 20:18 EDT
Pegasystems Inc.
GB
@Balamurugan Balakrishnan if there are no suggestions on this forum I would suggest that you contact our Pega consulting services for your requirements.