Question
IECISA
ES
Last activity: 4 May 2018 12:33 EDT
Pega web mashup included but ...
Hi I sucessfuly included a bew mashup of a proces in Liferey portal . The problem is that once the user fills the first form it gest to the success page in pega .
Is there a way to tell web mashup just to post first Form and then redirect to the unfilled form or just stay there and launch a sucess or error message?
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
IECISA
ES
Example Load before post:
IECISA
ES
Example load after post
Capgemini
IN
Hi,
Try below steps
1. customize your Confirm Harness to show your customize success or error message
2. The next assignment should be routed to different operator
Can you try above steps and let me know?
Thanks,
Dibyakanti
-
PRAVEEN KUMAR SEETHARAMAN
IECISA
ES
Hi There is a HarnessConfirm template that belongs to Pega Process commander . Do you mean that ?
Is it possible to circumstance it for pega web mashup . In fact we are using a custom operator id to avoid doing login in the web mashup.
Can you be a little more explicit about how to do the version of the confirm harness ?
Thanks and sorry for the delay .
IECISA
ES
Just to clarify , the web mashup defines data-pega-action-param-parameters=\'{\"UserIdentifier\":\"LiferayUser.DemoBlue\" ....
IECISA
ES
Hi . Any guidelines to do Save as the correct confirm Harness and have a circumstance for , sample with pyRequest and Userid value ?
Capgemini
IN
Sorry for my late response.
If you are using static Operator ID when setting up the Web Mashup then it'll be best to circumstance the COnfirm harness. If it's dynamic one then you've to use different design approach. Guideline to circumstance is given below:
Just open your flow and go to process tab and open Confirm Harness from "If an assignment is not being performed" area. On the top right portion of Save button circumstance it using Property (generally pyUserIdentifier).
Above solution is best if you are using static operator ID and that Operator is only used for Mashup purpose.
IECISA
ES
Thank you and no problem for the delay . The 2nd of May is free day and we didnt work . Let me do a test to verify this .
IECISA
ES
I managed to do what you sugessted . I created a Circumstanced rule by pyUserIdentifier but it did not make any change .
Isnt it pxRequestor.pyUserIdentifier ?
See screenshots attached.
Capgemini
IN
please try with pxRequestor.pyUserIdentifier once and let me know.