Hi All
I would like to show a button of โApprove Inspectionโ to the user all the time.
In order to approve such inspection some details should be populated first.
Letโs assume these details are Inspection Date and Signature for example.
If the user presses the button while these are not provided, an error should appear and indicate that one or more of these details are missing.
Is there a simple way to implement this?
I tried using the Action option while setting a condition for โOnly if this condition is trueโ.
But this means that the button will show only when everything is done perfectly by the user.
If not, he wonโt see the button at all and then the user might wonder on the reason he canโt see that button, without the app giving him any clue on the reason.
You might be able to do something like below to guide the users (step-by-step):
Some of the action is just to show a kind of guidance steps and the validity is being arranged as such so that it will only shown if the condition is true.
For the button Detail-is-blank:
Do-This: Grouped: Execute a sequence of Actions
Action: NONE
Behaviour:
And only show the actual action after all of the predecessors are completed.
Thank you so much for this trick.
I went with a slightly different approach inspired by your reply as many fields are needed for some actions to be allowed. I donโt want to create an action for each missing field.
So for each action, I simply created a โparallelโ action that will show up when the original action is not allowed (kind of inverted condition).
Like you did, the Do this is set to โGrouped: execute a sequence of actionโ but Actions is empty => nothing happens except showing the confirmation message.
The confirmation message on them will explain why they are not possible.
I named the action for example: โAccept not allowedโ.
The only problem is that the confirmation message still shows shows 2 options which are โNoโ and โAccept not allowedโ. both of these two options are a bit misleadingโฆ But I guess we can live with it.
If anyone has a better approach, please suggest
User | Count |
---|---|
43 | |
28 | |
24 | |
24 | |
13 |