20 - Adding Action Security and Submission criteria

📖 Task Introduction

In our notional scenario, you could have one analyst performing the triage and assignment of alerts while the assignee performs the Actions. This would have implications for your other Actions validations, but let’s at least build in that assumption into your Function-backed one. For this Action to be taken, the user must be the assignee listed on the object.

An expandable image of these steps can be found at the bottom of the task.

🔨 Task Instructions

1. Click Security & Submission Criteria from the menu on the left.

   • By default, the criteria you designated (i.e., the submitting user must be you) on Action creation appears. Click the x to the right of that criteria to start from a blank slate.

2. Click the underlined word condition to ➕ Add a condition.

3. In the Select condition template panel on the right, choose Based on current user.

   • Remember that we want the logic to stipulate that the user’s ID must match the assignee property on the flight alert in question.

4. Click user id from the list of values.

5. Click the is operator.

6. Click the Parameter button in the Select a value section on the next screen — we want to compare the user's ID with a property on the flight alert.

7. Click the Alert parameter.

8. Choose the Assignee property from the list.

9. Enter the following failure message at the bottom of the panel: Only the alert assignee can apply vouchers.

   

10. Save your Action to the Ontology.