Error messages propagated to case when Data page loads gets removed
I have a data page ( source can either be connect or report definition) .
I have a property which refers to this data page. This property is used as a grid source and the grid is used in a section.
Now when the section loads-- section refers to grid-- grid refers to property-- property refers to data page.
Data page tries to load data -- Fails---Sets errors ( either I use Post load or response data transform to handle this) . As expected this error gets propagated to my case (pyWorkPage).
However this error on page does not stop the user from progressing the case/flow because the set error is cleared off by the activity ( Work-.FinishAssignment 4th step) when the user submits the flow action with errors.
The only way to handle this error and stop user from progressing in the flow is by checking for some property ( say pyErrorPage in the data page ) in post activity of flow action and then setting the message again. But this is not ideal because I may refer the data page in multiple places and the data page may be loaded again and I have to do the error handling all over again.
Is there any way of handling all errors originating from data page load in the data page itself rather than having to use post activity in my case?
Message was edited by: Lochan to add Category
**Moderation Team has archived post**
I have a data page ( source can either be connect or report definition) .
I have a property which refers to this data page. This property is used as a grid source and the grid is used in a section.
Now when the section loads-- section refers to grid-- grid refers to property-- property refers to data page.
Data page tries to load data -- Fails---Sets errors ( either I use Post load or response data transform to handle this) . As expected this error gets propagated to my case (pyWorkPage).
However this error on page does not stop the user from progressing the case/flow because the set error is cleared off by the activity ( Work-.FinishAssignment 4th step) when the user submits the flow action with errors.
The only way to handle this error and stop user from progressing in the flow is by checking for some property ( say pyErrorPage in the data page ) in post activity of flow action and then setting the message again. But this is not ideal because I may refer the data page in multiple places and the data page may be loaded again and I have to do the error handling all over again.
Is there any way of handling all errors originating from data page load in the data page itself rather than having to use post activity in my case?
Message was edited by: Lochan to add Category
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Pegasystems Inc.
IN
Hi
Do you think these two article can help :
https://docs-previous.pega.com/data-source-error-handling-data-pages
https://docs-previous.pega.com/invocation-error-handling-data-pages
Amadeus
DE
Hi,
Yes this article is nice.
However this part of this article--
"
Preventing case processing from continuing when the data page has an invocation error |
Case processing already has built-in validation that prevents users from continuing when the case has errors. To make use of this, use an auto-populated property embedded within the case instead of referencing the data page directly. |
This does not work. Even if i use auto populated property, the error gets removed.
Regards
Bopanna
Pegasystems Inc.
IN
Hi,
Thank you for posting your query in the PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write a Post button that’s available on the top right pane of this page. Once created, please reply back here with the URL of the new post.
You may also refer this discussion link as a reference in the new thread.