Question
Cap Gemini
DE
Last activity: 12 Jun 2024 10:46 EDT
Custom parameter prompting appears read-only
Hi all,
We are implementing a flow, which can be added from App Studio. This flow runs a custom integration. So the citizen developers can pick this flow as a smart shape.
We have implemented a custom Flow Action, so that when citizen developers select this flow, they can configured it, using this Flow Action.
Now, when we select this Flow, the Flow Action appears as Read-only. I tried and force all controls (using a template with Cosmos) to be editable but still all fields appear as read-only.
The section appears at first editable, but then refreshes and then goes read-only (both on Dev Studio and App Studio).
We did not set privileges neither on the Flow, neither on the Flow Action. When we trace it, no errors. Nothing on the logs either.
I followed the steps described in this link: https://docs-previous.pega.com/process/how-create-custom-smart-shape#create-section-and-flow.
The Flow Action has a Post Data Transform, to set the flow parameters from the properties on the Flow Action / Section (as described in the link above).
Accepted Solution
Updated: 24 Jun 2024 10:04 EDT
Cap Gemini
DE
@Priyanka Boga I was configuring, forcing it to be Editable, still it did not work. But once i removed it and added it again, it miraculously became editable :)
Thanks for the reply!
Cap Gemini
DE
@Filipe Lopes I don't know what happened, but I tried to remove the smart shape, and add it again, and then it was editable.
Pegasystems Inc.
IN
@Filipe Lopes - If the section layouts Edit options is auto then based upon the harness or parent section edit options settings the read only condition will flow. Some where for this parent section layer or harness rule layer the read only conditions are set that is why the behavior is not consistent.
Thank you.
Accepted Solution
Updated: 24 Jun 2024 10:04 EDT
Cap Gemini
DE
@Priyanka Boga I was configuring, forcing it to be Editable, still it did not work. But once i removed it and added it again, it miraculously became editable :)
Thanks for the reply!
Pegasystems Inc.
IN
@Filipe Lopes - Probably the rule cache had some older or corrupted changes.
Thank you.