Solved
Issues with my Pega Community Lab
Good afternoon,
Now that my Pega Community Lab is working (after the AWS East 1 outage was resolved), I am running some tests and have encountered some unusual behavior.
For example:
- The routing of an Approval Process is not working properly. Instead of routing the Case to the specific user indicated in the Approval Step configuration, it routes it to the user [email protected].
- Related to this same Approval Process, the pyNote field is not updated in the Case when the Case is Rejected, checking in the Clipboard that the pyNote field on the pyWorkPage page is empty.
I would like to know if there is any limitation in this type of Lab or if it is necessary to activate any option to obtain the expected and desired behavior.
Thank you very much in advance.
Best regards
Accepted Solution
Posted: 16 hours ago
Updated: 16 hours ago
Updated: 24 Oct 2025 8:26 EDT
Upen Go Soluciones SLU
Upen Go Soluciones SLU
ES
I have resolved the two unusual behaviors.
- In the case of Routing, I verified that it was not working correctly because the Operator did not have the “Operator is available to receive work” checkbox activated. When I activated it, the Routing began to work correctly.
- Regarding the behavior of pyNote, I was able to verify that the Approval subprocess was responsible for passing the information from the pyNote field to Pulse and reinitializing the pyNote property so that it could be used again.
I hope this investigation helps others with the same issue.