Authorizing System-Automated Tasks
When you create tasks or Task Types for System-Automated tasks, for security purposes, you specify a user account under which the task is run. To preserve security, you may require authorization to perform the task if any of these conditions occurs:
-
If you add a System-Automated task with an alternate runtime user known as the RunAs ID to a schedule, from a template or by manually adding the task
-
When you set a schedule to Open status, the system automatically issues a request for authorization if it has not been completed.
-
If the parameters of a task are modified by a user other than the Assignee (or task owner if the owner is also the Assignee), the authorization is reset to unauthorized and must be obtained by entering a password. For System-Automated tasks, if a user other than the specified or default Run As user modifies the parameters, the task is reset to unauthorized.
Authorization ensures that the user performing the System-Automated task has security privileges for the application and data for which the task runs. An administrator who knows the credentials of the runtime user can perform the authorization or issue a request to the user to obtain authorization.
When the System-Automated task is scheduled to run, if authorization is not provided, the task is not run, and its status changes to Needs Attention. If an owner or Assignee edits the task, the task details indicate that authorization is required. In this case, only the RunAs ID can authorize the task.
A user who receives a request for authorization can access the Authorization dialog box from a link in the email or by logging on to the application.
To authorize a task: