Adding conditional action sequences
1. Adding conditional action sequences
2. DEMO script
Welcome back. Let's wrap up our chapter on actions by learning how to add conditional and branching logic to action sequences. Let's imagine that at Oakmark Bank, any approved loan application for $200K or greater requires a second review by the VP of lending. We want to flag any loans meeting this criteria for additional review by the VP. Let’s start building. We’ll begin by creating a column in our loan applications table where we can capture that a record has been flagged for VP review. We’ll configure a new column as a checkbox and call it ‘Needs VP approval’. When an application is approved by a loan officer for $200K or more, an action sequence will automatically check the box. For this demo, we’ve already added a control to the app controls page, capturing the dollar amount of the loan being reviewed, and we’ve added an action to our input table to pass the dollar amount of the loan that is clicked to this control. We’ll leverage this control parameter to set up conditional action sequences. Currently, there is one action sequence that always triggers when an officer clicks the modal’s ‘Approve’ button. The approval status and comments are immediately added back in the loan applications table, control values are cleared and the modal is closed. We’ll duplicate this action sequence, and configure one of the copies to execute when the loan value is $200K or more, and the other to execute when it is not. Entire action sequences can be duplicated with the three dot menu next to ‘Action sequence’. Clicking the three dots again, we can add a condition to the action sequence. We’ll use a custom formula to specify the condition that the control ID [loan value] is less than 200K. Now this entire action sequence will only execute under that condition. Moving to the second action sequence we’ll set up the opposite condition, for when [loan value] is greater than or equal to 200K. This action sequence will need an additional step to check the box in the VP review column. We’ll add a new effect, set it to ‘Update input table row’, and point to the linked input table. We’ll point to the VP review column for updates. Because this is a checkbox column type, we set the toggle to the position we’d like to set it to when this condition is met, which is the ‘True’ position. Stepping back, we now see two action sequences with conditions. Each will only execute if its given condition is met. Let’s test it out. Back in the applications table, let’s approve a loan for over $200K. Right away, we see that the action sequence logic is holding, and this application received a check in the VP review column. Testing with a small loan approval, we see that the box was not checked.3. Let's practice!
We’ve just learned how to add conditions to action sequences to create branching workbook logic. In the next exercises, you’ll practice adding conditional actions to your loan officer promotion app.Create Your Free Account
or
By continuing, you accept our Terms of Use, our Privacy Policy and that your data is stored in the USA.