GetNextWorkObjectActivity change in Parameter "skipCopyToPrimary"
Hello.
I had a requirement to enable Get Next when the a User finishes a case. So I activated the Get Next Work in the Flow Action in the section "Back-to-back processing configuration". When no cases are available a Message was displayed in the top of the Page, this in Pega 7.2. After an Upgrade to Pega 7.4 this message stopped showing.
After check I realised that the Activity Get Next Work Object has a step that is executed when no cases are available, this calls the SetPageErrors Activity by passing a Parameter called "skipCopyToPrimary" defaulted to false in Pega 7.2, but in Pega 7.4 it is defaulted to true, that's why the message is not showed.
I was wondering why this parameter changed in Pega 7.4. I hope you can help.
Thanks beforehand.
***Edited by Moderator Marissa to update platform capability tags; update SR details****
Thank you for all your support. We raised a ticket to get support, we got a good solution for this.
Thank you so much for all your help.
Hi @GilbertoB1298,
So glad to hear that you received a resolution. Could you share your SR ID with us so that we may share the resolution?
Thanks!
Sure this is the SR Number: SR-D2811. My lead did this request, I can share the implemented solution here if needed. This was kind of mistake from our side.
Thanks @GilbertoB1298,
I have updated your post with the SR ID. I'd love for you to share your resolution! Someone else may have the same issue and it'd be great to help them out! Once you've posted it, you can click the Correct Answer link to mark it as the resolution.
Thanks!
Here the solution:
We were expecting to see the errors on top of the Page, this was working before the param was set to true in Pega 7.4 Version, we did not realize that that we already had available in the Clipboard a property with the right Message for "No Assigments Available" (.pyConfirmationNote).
The OOTB Section pyConfirmMessage has a section with this Property (.pyConfirmationNote), and as we had customized the Harness Confirm, just we needed to include a section similar as the one in pyConfirmMessage. In our business requirements the Confirm Harness just will be displayed when no cases are available when the Get Next Operation is called. We are calling this in all the scenarios where a case is closed, so the user always gets a new case after finish one. Because of this, we did not add any validation to display this Section, so every time the user finishes a case and there are no more cases to work on, the Confirm harness will be displayed with the message "No cases Available".
As you know this Property has the default Value "Thank you for your input", so if your business requirements require you to display this Confirm Harness in other situations, you will have to validate when to show this section containing the message ("No Cases Available").
Hello
As far as i remember, this change has been incorporated in order to address a use case which was missed in the earlier releases.
UjjwalaP what you think.