Creating a case in App Studio, I create a step that is saving data to a data object. It is a "Collect Information" step, configured with a field of the "Data reference"/"Data relationship" type, pointing to a data object. This data object is saved in the Pega database.
In App Studio I set the "Optionally save to the following objects" to the correct data object.
When I test this construct I get the following error:
The Flow Action post-processing savable data pages/auto populate properties failed: Failed to save auto populated property 'TestData' : Required parameters for Data page D_TestSavablemissing
It seems that the pyGUID is empty when it is submitting the form. The pyGUID on the savable datapage is required.
To fix this behavior, I can make the pyGUID optional on the savable data page. And it will work that way.
Question is: is this the correct way? It does not seem low code, to alter the requiredness of the property in Dev Studio. Shouldn't the pyGUID parameter be optional by default?
***Edited by Moderator Marije to add Capability tags***
In the mission exercise of "Data and Integration Beginner" (so at least it is not advanced ;) ), I found the following note:
Note: Pega uses pyGUID as a primary key and automatically generates a value for pyGUID. In this use case, you can enterany pyGUID parameter value, such as "newcustomer" for the Customer data object. The system will automatically generate a unique value and replace "newcustomer."
Based on the note, I adjusted the page property to make the pyGUID hold a string. That works, also when leaving the field as required on the data page.