Hello all,
So I have a process, where the stakeholder wants to handle a feature more restrictively.
So before starting a process prompt a new question. ( I already have an interface working fine, but with the new requirements should I create a new one with the questions ?)
What you would like to amend? ( I already have an interface working fine, but with the new requirements should I create a new one with the questions ?)
Distribution Fee amount only (->only Distribution Fee should be editable)
-> process works the same as before, BUT once approved and processed by Documentation the task does NOT go back to other team in the end anymore
KID, Target Market, Cost&Charges only (->only these fields should be editable)
-> process works the same as before, BUT once approved and processed by Documentation the task does NOT go back to the other team in the end anymore
Others (might include the above ones) (all editable)-> normal process
Discussion posts and replies are publicly visible
It is a bit hard to follow.What is your question exactly in one sentence?
So In the process that I have I want to add like a message that could prompt and give the user the ability to choose between 3 different options regarding an amendment that is required. Normal process gives the user the right to edit all of the fields from the form. I want to add two new options where only some fields could be editable
Option one : only distribution fee amendable.
Option two.
Here we have the process
I am sorry but I am still figuring out the exact requirement here. Could you please confirm if you want to add multiple options to restrict certain fields in the form?
An absolut guess by my side: it seems that you are looking a condition for the "readonly" parameter in your SAIl components.Example-> a!textField( label, instructions, required, readOnly, disabled, value, validations, saveInto, refreshAfter, validationGroup, requiredMessage, align, labelPosition, placeholder, helpTooltip, masked, accessibilityText, showWhen, inputPurpose, characterLimit, showCharacterCount )
Read-only
readOnly
Boolean
Determines if the field should display as not editable. Default: false
https://docs.appian.com/suite/help/21.4/Text_Component.htmlSo the moment your condition is true, its not editable any more. If you click on a element with a link function (linkfield,card, richtext...), a value changes and its becoming editablel or read only depending on the current state.-> but i didn't get the issue regarding "going back" in the process?
correct, sorry couldn't explain in a better way.
in this case you can use readonly parameter of those fields to conditionally make then editable or readonly.
how should I then give the choice between 3 options ?
You can have 3 variables to store boolean values and then based on these values you can configure your readOnly parameters.