Question
Data Retention - DX API
The Assignment refresh API with a PUT method allows us to trigger a targeted refresh on any of UI controls via the API. If my refresh executes a DT which sets values on the case, they are propagated back to the consuming system only if those fields are the screen. (This is because the response of the API is simply a json representation of the screen).
If my refresh had triggered a change on a case property which doesn’t have any reference on the section, how to propagate them back to the consumer. This is required to perform a follow-up POST on the assignment to trigger a case submission.
Thanks in advance,
Ratan Balaji.
Accepted Solution
Areteans Technology Solutions
AU
@Saikat_ChakraborttyThanks for the reply. This sounds more like a workaround than a solution. I could find a specific section of property mapping in 8.5 called "DX API Attributes" that allows one to set up Key-value pairs from controls on a section. This is something one can leverage to send out "customAttributes" to the consuming system which are not a part of the UI.
Accepted Solution
Areteans Technology Solutions
AU
@Saikat_ChakraborttyThanks for the reply. This sounds more like a workaround than a solution. I could find a specific section of property mapping in 8.5 called "DX API Attributes" that allows one to set up Key-value pairs from controls on a section. This is something one can leverage to send out "customAttributes" to the consuming system which are not a part of the UI.
Pegasystems Inc.
IN
@Ratan : The purpose of the custom attribute in the control is to supliment the control with more data. Please check if you change anything, does it get posted to the server once you submit the assignment.
Saikat