Discussion
1
Replies
297
Views
Posted: July 11, 2015
Last activity: August 3, 2015
Closed
Problem adding specifications to assignment & its flow action
In the lesson, "Adding Business Use cases to a Process," it appears as though something isn't working correctly in the exercise system. The description fields for the assignment and the flow action appear to be mapped, and making changes to the flow action specification does not create a new specification for the action.
Here is what I did:
- Opened Candidate case in the Case Designer and clicked "Configure Process Detail" under the Collect Information stage to open it.
- Selected the "Personal Info" step.
- Scrolled down to the Specification region and entered the information as instructed.
- Scrolled up and clicked Save.
- Clicked "View Action Specification" under "Collect Personal Info" action in the "Actions" region.
- Looked for the blank field, as instructed, but instead, I saw the same information I had just entered into the Specification region of the assignment step.
- Sat there, confused for a second, and then replaced the information with what was instructed.
- Clicked OK, and then Save.
- Scrolled down to the Specification region to see if the original text had been retained, and it had not. It was replaced with what I entered on the flow action.
- Opened the Application Overview and looked for the specifications I had just created. Only one existed - that of the Personal Info assignment. The CollectPersonalInfo flow action specification is missing.
Dear Cheri,
It appears that the Flow Action has the specification errorenously linked to the Flow specification! What you can do to rectify the above is to go to the Flow Action specification (screenshot on step 5 above), click on the "View action specification" and click the "Specification Actions" (screenshot on step 6 above). Then select the "Remove from step" option.
After that, you should be able to create a new Flow Action specification. Ensure the name of the specification is different, i.e. not "Personal Info", otherwise you will reuse the same specification again.
Regards,
Teng Hao Chua
Pega Academy Support Team