Passing property value from Non-Autogenerated-HTML section
Hi,
I created a section which contains two buttons using HTML under HTML tab. On clicking those buttons i want a value to be updated to a property and move forward through the flow. I used the below code.
<input type="submit" value="Approve" id="Ap" onclick="<pega:reference name=".propertyName" mode="input"/>"></input> <input type="submit" value="Reject" id="rj" onclick="<pega:reference name=".propertyName" mode="input"/></input>
I got the below output:
Here i am getting "> near my approve button. so i didn't use this for reject button, as you can see in the above code. However both the buttons work fine. On clicking, those values are being passed to the clipboard and flow is working fine.
Is this the correct way to do this?
Is there any other way to pass value to a property on click of a button using HTML or JS?
Pegasystems Inc.
IN
would running a Data transform to apply the value for property followed by OOTB finish assignment works? so that we can refer to auto generated section only?
please share your thoughts/comments...Thank you!
IBM INDIA PVT LTD
IN
Yeah. By using Data transform we can achieve this. Since i am trying to practice HTML part in Pega for my own satisfaction, will we be able to call a Data Transform inside a HTML or a JSP tag. Or is there any other way to pass a value to a property from HTML or JS
Pegasystems Inc.
US
Is your Section being used by a Flow Action or a Harness?
In a Flow Action you can check the "Hide the default action section buttons" checkbox in the Actions tab.
At the bottom of your section you would add your own OOTB, auto-generated buttons.
For the button that corresponds to the Flow Action + Section you are in, use the "Finish Assignment" Click Action.
To show an "Other Action" as a button, use the "Perform Action" Click Action.
You rarely need to write custom HTML and should try your best to avoid doing so.
For a basic approval screen such as the one you showed, there is an "Approval" Case Design step type in 7.1. You configure the step telling it where to route, for example to the Manager, and optionally name the stage to change to on Approval and similarly for a Rejection..