Out Parameters from Data Transform to HTML are blank
Hi,
Greetings. Hope you are all doing well! I am on Pega 8.7.1, i am trying to use ShowHelpStream to populate the guidance for Flow actions, i am calling a Data Transform from the HTML.
I am able to set the parameters within the Data Transform and i can see these but as soon as the DT ends and control reaches the Stream rule, i cannot see the parameters.
I have seen an article from 6 years https://support.pega.com/question/data-transform-not-setting-output-parameters which says this will be addressed in future releases,
Can someone please confirm if the issue i am seeing is still there?
***Edited by Moderator Marije to add Capability tags**
Accepted Solution
Updated: 1 Jul 2022 11:20 EDT
Pegasystems Inc.
GB
@KOMARINA I checked the article you mention. I also found other internal documentation which informs me that this fallback is expected because the way out parameter are handled which then may not be used in future interactions. We fallback for 'out' parameters with non-literals like .pyPage or .pyProperty or Param.PageParamType etc
"Data transforms does not support pass current parameter page" (BUG-484360) was fixed in Pega 8.4
As of 8.4. we use an updated pzShowModelParamsModal to show the checkbox if the value starts with 'param.'
The product should now issue a warning letting folks know that they should use alternatives.
As you've seen there is no option from the UI to pass current parameter Page from a flow. Hence, in the context of the Data transform, a new parameter page is created and the parameter page values that are set here are not sent back to the flow.
Supporting this required major changes in generated java as well as UI changes providing a checkbox to pass current parameter page.
As of 8.4. we updated pzShowModelParamsModal to show the checkbox if the value starts with 'param.' Also product was updated with a severe warning recommending using a different method of calling DT
@KOMARINA I checked the article you mention. I also found other internal documentation which informs me that this fallback is expected because the way out parameter are handled which then may not be used in future interactions. We fallback for 'out' parameters with non-literals like .pyPage or .pyProperty or Param.PageParamType etc
"Data transforms does not support pass current parameter page" (BUG-484360) was fixed in Pega 8.4
As of 8.4. we use an updated pzShowModelParamsModal to show the checkbox if the value starts with 'param.'
The product should now issue a warning letting folks know that they should use alternatives.
As you've seen there is no option from the UI to pass current parameter Page from a flow. Hence, in the context of the Data transform, a new parameter page is created and the parameter page values that are set here are not sent back to the flow.
Supporting this required major changes in generated java as well as UI changes providing a checkbox to pass current parameter page.
As of 8.4. we updated pzShowModelParamsModal to show the checkbox if the value starts with 'param.' Also product was updated with a severe warning recommending using a different method of calling DT
Workarounds: 1.Use Set properties to set Param Page values instead of a data transform. 2. Use properties on the primary page in the data transform and set values on them. Later , these properties can be used in the utility activity.
Accenture
GB
@MarijeSchillern Thank you, I am aware of Work Around 2, but what is this about Work Around 1? How do i use Set Properties from HTML instead of calling a Data Transform?