To implement automation triggers, you must first write trigger scripts or executables and have the appropriate powers, such as those included in the built-in Manage Policies and Automation Triggers role.
To successfully implement a custom trigger, you must write a script that runs during a specific operation (administrative task). You can specify whether DRA applies the trigger before (pre-task) or after (post-task) an operation runs. In the trigger script, you can define error messages to display whenever the trigger fails. You can also specify a default error message through the Create Automation Trigger Wizard.
For more information about writing custom triggers, viewing a list of Administration operations, or using argument arrays, see the SDK.
NOTE:
Before associating the custom automation trigger with an assistant administrator and an ActiveView, first ensure that the assistant administrator is assigned to that ActiveView.
If the path of the custom trigger script or executable contains spaces, specify quotation marks (") around the path.
Currently, if the UserSetInfo operation is used for a script automation trigger and a user attribute is changed (executing the trigger), the changed attribute is not proliferated across the enterprise until after a Find Now operation is run on the user object.
When implementing a trigger for specific ActiveViews, or in other words, triggers with a limited scope, GetInfo operations need to also include the properties operation for that object type. For example, when triggering on the UserGetInfo operation, the UserProperties operation also needs to be added in the trigger operations list.
To implement an automation trigger:
Write a trigger script or executable file.
Log on to a DRA client computer with an account that is assigned the built-in Manage Policies and Automation Triggers role in the managed domain.
Start the Delegation and Configuration console.
Connect to a primary Administration server.
Use File Replication to upload the trigger file to the DRA primary and secondary servers.
The folder path must already exist on all DRA servers in the managed domain. This path, including the file, will be used in the Do file path of the Automation Trigger wizard.
In the left pane, expand Policy and Automation Management.
Click Automation Triggers.
On the Tasks menu, click New Trigger.
On each wizard window, specify the appropriate values, and then click Next. For example, you can associate this new trigger with a specific ActiveView, allowing DRA to apply this trigger when assistant administrators manage objects included by that ActiveView.
Review the summary, and then click Finish.
IMPORTANT:If you have more than one ActiveView configured for a trigger by adding a comma between ActiveViews, those ActiveViews get bifurcated in the trigger when upgrading to a new version of DRA and the trigger will not execute. In order for the operation to execute after upgrade, the trigger will need to be reconfigured or a new trigger will need to be created.