Discussion
2
Replies
559
Views
Posted: February 18, 2016
Last activity: May 19, 2016
Closed
Party ID error after Creating and Editing Flows exercise
After implementing the Exercise Solution (downloaded from Pega Academy) for Case Design > Creating and Editing Flows, when I create an Onboarding case, I get an error "Party ID:This field may not be blank" on the "SETUP ORIENTATION SCHEDULE" screen.
I have no idea why this happens since the exercise did not have us do anything with that screen. Any ideas how to resolve this? I cannot work through to the solution since the exercise makes changes to steps that occur later in the case lifecycle.
Thanks,
Phil
Moderation Team has archived post,
Close popover
This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Discussion, please write a new Discussion.
Posted: 4 years ago
For future reference, this issue has a workaround- when creating a new OnBoarding case, make sure to enter an email address for the candidate. Otherwise you will run into the error "Party ID:This field may not be blank"
Work Parties can be added automatically to a case via the pyCaseManagementDefault Work Parties rule if "VOE" (visible on entry) is checked.
Regardless how your problem Work Party is being added, it is missing critical information such as a unique "Party ID".
Take a look at the parameters to the Work-.addWorkObjectParty Activity.
"PartyRole" is passed in. "Party ID" is generated. "Party ID" is the same as "PartyRole" for singular WorkParties.
For repeatable parties, ["_" + <nth repeat>] "will be appended to "PartyRole" to form the value of "Party ID".
Either there is an attempt to reference a .pyWorkParty() property without supplying the "Party ID" subscript or the subscript is assumed but there is no corresponding Data-Party property.
Whenever you submit a Flow Action, the Data-Party.Validate Activity will be called. This Activity verifies that every PartyRole used is defined in the pyCaseManagementDefault Work Parties rule.
Have you traced to identify where this error occurs?