How to make Approval form Read only

If your form should always be read only, then just find all the places in your form that use a variable to determine whether it is read only or not and make the value always true. If you need more help, I'd suggest pasting your full expression here so we can make more specific recommendations.

Hi,

I am referring this code https://docs.appian.com/suite/help/21.2/SAIL_Tutorial.html. I need other way of making my form conditional not the way it is mentioned in this tutorial.

Thanks

Faisal

faisalf0003 said:

I need other way of making my form conditional not the way it is mentioned in this tutorial.

I'm sorry, I don't understand what this means. Can you provide more context? What do you want to change? What have you tried? What does your code look like? If you always want it to be read only, then why do you need your form to be conditional at all?

I have a requirement that the same form should be in a read only Format when it goes to approval stage, let us say HR approval. The second form will additionally show a radio buttons to approve or reject and cancel button will be absent in the approval form.

I do not want to use two forms and also I do not want to go by the logic mentioned in the tutorial.

I need help if you could tell me the other way of doing this.

Thanks

Faisal

Ok thanks for the context! I think the easiest way to do this is to include a rule input for ri!readOnly. Then, in all the places in the form that you want to alternate between editable and read only, just use this variable (similar to how that docs page uses local!readOnly). Then, the key to using this in your process is to hard-code the value within each user input task to the appropriate value. So for instance, your approval form wouldn't even be mapped to an activity class parameter in the process; instead, you directly set the value for your readOnly variable to true.

If you want to see other ways of setting up conditionally read only forms, I'd also suggest using the "Create from CDT" builder that is visible when you first create a new interface.

Ok thanks for the context! I think the easiest way to do this is to include a rule input for ri!readOnly. Then, in all the places in the form that you want to alternate between editable and read only, just use this variable (similar to how that docs page uses local!readOnly). Then, the key to using this in your process is to hard-code the value within each user input task to the appropriate value. So for instance, your approval form wouldn't even be mapped to an activity class parameter in the process; instead, you directly set the value for your readOnly variable to true.

If you want to see other ways of setting up conditionally read only forms, I'd also suggest using the "Create from CDT" builder that is visible when you first create a new interface.

Thank you Peter.. I will try builder.

One more thing!  I want to understand what does the line [local!readOnly: ri!step = "APPROVAL" ] returns in the tutorial https://docs.appian.com/suite/help/21.2/SAIL_Tutorial.html ? This local value assignment I could not understand.

'ri!step = "APPROVAL"' evaluates to TRUE if the value of ri!step is "APPROVAL", and FALSE otherwise.  This sets "local!readOnly" to whatever value is the result of the evaluation.

Thank you Mike