This shows you the differences between two versions of the page.

Link to this comparison view

action type - application role [2016/09/14 14:19] (current)
Line 1: Line 1:
 +====== What role is the application in? ======
 +Applications can be in a [[Application Lifecycle Management#​Application Roles|"​Development",​ "​Testing"​ or "​Production"​ role]]. You may want an action to run only in certain application roles. This evaluation will pass if this application is in the specified role and will fail if the application is in a different role.
 +===== Explanation =====
 +Evaluations have two [[Automation Trigger|automation triggers]] associated with them : Then and Else.  Actions under the "​Then"​ automation trigger execute when the evaluation passes, and actions under the "​Else"​ automation execute when the evaluations fails.
 +{{ ::​action_evaluation_drop.png?​direct |}}
 +Application role evaluations are used to execute a set of actions if an application is in a particular role, and another set of actions if it isn't.
 +Example: Suppose an application sends a lot of email as various [[Record|records]] are moved through [[Workflow|workflow]]. ​ If the builder wants to make sure these emails are only sent when the application is in testing, or production, to avoid sending a lot of spurious emails while testing feature development in build, they could accomplish this by wrapping the [[Action Type - Emails|email send]] actions in application role evaluations so these actions only run in the appropriate mode.
 +===== Settings =====
 +==== Select application role ====
 +Select the application role you wish to evaluate for.
 +{{ ::​action_applicationrole_choices.png?​direct |}}
 +==== Describe this action ====
 +Useful as a comment, this description will overwrite the automatically generated description in the [[Action Manager|Action Manager]].
action type - application role.txt ยท Last modified: 2016/09/14 14:19 (external edit)
Copyright WorkXpress, 2019