Grouped actions not fully triggering if confirmation selection is false

[wheaties]

I have a Grouped action with three other actions within it.  My app is a project management app, and when a project is marked complete, it initiates the Grouped action (see below). 

• Mark Project Complete (changes status of this row to Complete)
• Send Review link to Agent (adds a new record to a Review table)
• Send Review link to Client (adds a new record to a Review table)

First action triggers fine, however the second and third actions both have Confirmation pop-ups enabled, allowing the user to decide to trigger them or not.  If the user confirms, all actions execute as planned. 

The issue is if the user selects cancel on the confirmation pop-up for the second action which results in the third action not triggering. In essence, when the second trigger is deemed FALSE, it stops any remaining actions to trigger. My goal is to ensure the third action always initiates even if the second action is not triggered (by user choice). I need the confirmation pop-ups to remain in place for both actions.

Any suggestions are appreciated.

[Steve]

Rather than invoking the second directly, use an action of type Data: execute an action on a set of rows to execute the second action. Leave the confirmation on the second action itself. I believe this indirect call will insulate the grouped action from the user skipping the second action.

[wheaties · Accepted solution]

Steve - This worked like a charm, exactly what I needed.  Didn't know you could insulate actions like this, very handy to know.  Thank you!

[Suvrutt_Gurjar]

Please try below workaround if you wish:

1. Please add a real column of enum type called say [Agent_Client] in the "Locations" table with 3 Enum Options

Agent , Client and Both

2. Add an INPUT() function action called say " Select Agent or Client or Both" on the "Locations" table with an expression something like below that sets the [Agent_Client] column.

This action's INPUT() expression can be something like INPUT( "Agent_Client" , "Agent")

3. In the existing actions that you have already created, please add the following expressions in the "only if this condition is true" setting

     A)  Create Review Record( Agent) action

        OR(  [Agent_Client]= "Agent", [Agent_Client]="Both")

    B)  Create Review Record( Client) action

             OR(  [Agent_Client]= "Client", [Agent_Client]="Both")

    Remove the confirmation required on these actions.

4. Now the order of your group action can be something like 

   Change Project Status to Completed

    Select Agent or Client or Both

     Create Review Record( Agent)

     Create Review Record( Client)

With this arrangement , the user will need to select the desired enum options and either or both of the actions  "Create Review Record( Agent)" and "Create Review Record( Client)" will fire based on the user's enum selection.

The GIFs below show two selections in a test app. When one record is selected to be added you can see two actions invoke ( One for input action and one for adding a record)

When the user selects two records to be added , it invokes there actions in the GIF below  ( One for input action and two for adding two records)

[wheaties]

@Suvrutt_Gurjar - Thank you for detailing all this out.  I am gaining more experience with the INPUT() functionality and plan to use this in other areas of my app.  For this particular problem, Steve's solution ended up working great with minimal adjustments to my framework.  Your way undoubtedly would have also worked, but would have required much more restructuring and rebuilding than needed currently.  I like the user experience with your recommendations more, and can see myself taking this route at a later date.  Your time in thinking this through and detailing it out will not go wasted!

[Suvrutt_Gurjar]

Got it. Thank you for the update.

Yes, Steve's solution is easier to implement.