How do Creating work object status with PEGA platform tools ?

      PEGA Work Object status Creation

To change the Pega work object status creation (also known as a case) in PRPC, you typically need to use either the user interface provided by the PEGA platform or implement logic in the form of data transformations or activities.

Changing PEGA Work Object Status Creation via the User Interface.

      PEGA Work Object status Creation
PEGA Work Object status Creation

 

1. Log in to PEGA:

Use your credentials to log in to the PEGA environment.

2. Navigate to the Case Manager Portal:

This is usually the portal where you manage cases.

3. Find the case:

Use the search functionality or navigate through your work list or dashboard to locate the specific work object (case) you want to change the status for.

4. Open the case:

Click on the case ID to open a detailed view of the case.

5. Change the status:

Depending on your configuration and permissions, you might have a dropdown or button to change the status. This can usually be found in the case details or actions section.

Select the new status from the available options.

6.Save/Submit Changes:

After selecting the new status, ensure you save or submit the changes to apply the new status.

Changing Work Object Status in Pega Programmatically

Using Data Transforms

1. Open/Create Data Transform:
  • Navigate to Records > Technical > Data Transform.
  • Create a new data transform or open an existing one where you want to set the status.
2. Set the Status Property:

Add a step in the Data Transform to set the status.

Example

Set.pyStatusWork = “Resolved-Completed”

3. Save and Apply the Data Transform:

Save the data transform and ensure it is invoked at the appropriate point in your case lifecycle.

Using Activities

1.Open/Create Activity:

  • Navigate to Records > Technical > Activity.
  • Create a new activity or open an existing one where you want to set the status.
2. Set the Status Property:

Add a step using the Property-Set method to set the status.

Example:

Property-Set
Step Page: Primary
.pyStatusWork = “Resolved-Completed”

3. Save and apply the activity:

Save the activity and call it from the relevant step in your case workflow.

Example: Setting Status in a Flow Action

1. Open the Flow Action:

Navigate to the flow action that handles the transition for which you want to change the status.

2. Add a data transform or activity:

In the flow action, configure it to call the data transform or activity that sets the status.

3. Implement the status change:
1. If using a data transform:

Apply Data Transform: <Your Data Transform Name>

2. If using an activity:

Call Activity: <Your Activity Name>

Best Practices

1.Validation Rules:

Ensure that status changes are validated to prevent invalid transitions.

2.Role-Based Access Control:

Restrict the ability to change statuses based on user roles and permissions to ensure only authorized users can make certain changes.

3.Consistent Status Values:

Use consistent and meaningful status values across the application for clarity.

4.Document the workflow:

Document the statuses and their transitions within your case lifecycle to maintain clarity and ease of understanding for all team members.

5.Testing:

Thoroughly test status changes in a development or staging environment before deploying to production to ensure they work as intended.

OOTB Properties and their prefixes.

pxCreateDateTime: It holds the data and time value when the case is created.

pxCreatedDateTime: It holds the operator ID of the Work object creator.

pxUpdateOperator: It holds the operator ID of the last update operator.

pyID: It holds a work object.

The pzInsKey in PEGA holds the primary key of an instance, which can be a case, work object, or any other instance within the PEGA platform. This key is unique for each instance and is used to identify and retrieve specific instances from the PEGA database.

Understanding px, py, and ps prefixes:

Prefix                                               Meaning

Px             identifies properties that are special, meaning that the values cannot be input by the user  on an HTML form.

py            Properties with names that start with py are not special, meaning that values can be input by users on an HTML form.

pz           Properties with names that start with pz support internal system processing. Users cannot directly manipulate pz properties.

Your application may examine these values, but do not set them. The meaning of values may change with new product releases.

Understanding pzinsKey:

pzinsKey is the primary key column of all tables in the PRPC rule base.

Any time we create a new instance, PRPC generates a pzInsKey value.

 PASH

CustomerDetailsSec — version 1

CustomerDetailsSec — version 2

PASH-Pashon

CustomerDetailsSec
      PEGA Work Object status Creation
PEGA Work Object status Creation

Rule-HTML-Section PASHCustomerDetailsSecTimeStamp

Rule-HTML-Section PASH-PASHONCUSTOMERDETAILSSECTIMESTAMP

If we want to know the pzInskey of any rule, as developers,.

Open Rule -> Go to Actions -> View XML -> Find Pzinskey.

Conclusion

By following these steps, you can effectively manage and change the pega work object status creation   in PRPC, ensuring smooth case handling and workflow transitions.

More topics on technology click here

 

Leave a Comment