Create and Activate a RAM Trigger

Creating a RAM Trigger

Page Contents
  1. Create a RAM Trigger
  2. Activate a RAM Trigger
  3. Edit a RAM Trigger
  4. View Trigger Versions
  5. Inactivate a RAM Trigger
  6. Delete a RAM Trigger
  7. Delete Previous Trigger Versions
Relevant eLearning
Configure Rules Automation Manager Triggers
Create a RAM Trigger
See Common RAM Examples, for examples of RAMs that can be created.
  1. To create a RAM trigger, in Workbench, select Tools > Automation Manager > Admin.
    The Tools Automation Manager Admin menu
  2. To add a RAM trigger, select Actions > Add new trigger.
    Selecting Add new trigger
  3. Name the RAM trigger. Enter a name that easily identifies the purpose of the trigger.
  4. Select Select trigger type > RAM Trigger.
  5. A red alert message displays. Select I agree.
  6. Select Save and Continue.
    The alert trigger message
  7. Select the Trigger Mechanisms by using the pull-down menu.
    Trigger Mechanisms
    • Trigger Mechanism can be considered as a Category that defines what triggers the RAM to run. RAM can be triggered to run when HR statuses are updated, or actions are performed on forms or reqs.
    • After one or more rules are created for the trigger, the Trigger Mechanism cannot be modified. To modify the trigger mechanism, all existing rules must be deleted first.
    • See Trigger Mechanisms for more information on the Trigger Mechanisms available.
  8. Select the Trigger Event by using the List icon.
    • The Trigger Event is defined by the selection of the Trigger Mechanism. The event is the specific occurrence that dictates what causes the trigger to run. After one, or more, rules are created for the trigger, the Trigger Event cannot be modified. To modify the trigger mechanism, all existing rules must be deleted.
    • Only one RAM trigger is allowed per HR status and per Form when the same combination of Delay Mechanism and Trigger Delay are not used. Different scenarios based on a single HR status, or form, must be handled within the rule.
      The select trigger event section.
  9. Select the Timing Mechanisms, and Trigger Timing by using the pull-down menus.
    The Timing Mechanism options
  10. Select the Trigger Context.
    • The Trigger Context extends the scope of the trigger. After one or more rules are created for a trigger, the Trigger Context cannot be modified. To modify the Trigger Context, all rules must be deleted.
    • There are four Trigger Context options. See Trigger Contexts for more information.
  11. After the Trigger Mechanisms, Trigger Events, Timing Mechanisms, Trigger Timing and Trigger context have been configured, select Save.
  12. Select Add Rule. Rules allow for different logic to run in each rule, producing a different set of actions and results.
  13. Name the rule, and select Save & Continue.
    Entering the rule name
    • Existing configured rules are displayed by row in the Defined Rules section. Configure the rule’s Condition(s) and Action(s).
    • Do not add more than 50 rules or actions to any trigger. Doing so has the potential to cause performance problems, and cause the trigger to be automatically disabled.
    • For more information on Conditions, see Conditions.
    • When creating Conditions a Category must be selected. For more information see Category Reference.
    • For more information on Actions, see Actions and Action Types
    • If a rule runs an EXIT action, such as an HR Status update, the entire trigger exits, and no additional rules run.
    • Rules are run in the sequence on the screen. Depending on the logic that is needed within the trigger, the sequencing might or might not be important. However, in most cases the order is important to produce the business logic that is wanted within the trigger. To change the order in which the rules run, use the arrows to move the rules up or down in the sequence.
  14. Select Save.
    Entering the rules conditions and actions
  15. After a condition is saved, it displays in the Existing Conditions section of the rule screen. To edit the existing condition, select Edit for the specific condition. To delete the existing condition, select Delete for the specific condition.
    The Existing Conditions section.
  16. After an action is saved, it is added to the Existing Actions section. To edit the existing action, Select Edit for the specific action. To delete the existing action, select Delete.
    The Existing actions window.
  17. Add Additional Rules if needed.
    • Rules are run in the sequence on the screen. Depending on the logic that is needed within the trigger, the sequencing might or might not be important. However, in most cases the order is important to produce the business logic that is wanted within the trigger. To change the order in which the rules run, select the arrows to arrange the rule sequence.
      Sequencing Rules.
  18. Select Save after all rules are added and sequenced.
    Saving rules
  19. Select Edit to edit a rule, or select Delete to delete the rule. To view a rule select the hyperlinked rule name. The RAM is available in Draft status.
Activate a RAM Trigger
  • By default, RAM triggers are placed in a draft status during initial creation. This allows configuration to occur periodically before testing. RAM triggers are also placed in draft after selecting edit on an active trigger. These triggers can be activated after all changes are completed.
  • Power Users can create RAM triggers in both Staging and Production environments, but can only activate them in Staging. To activate a Production RAM trigger, contact your IBM representative.
  • Reactivated triggers are treated as if this is the first time the trigger has been made active. All trigger events that occur during the time the trigger is inactive, are not held until the trigger is actived.
To activate a draft trigger,
  1. Select Draft or Inactive depending on whether the trigger is in draft or an inactve state.
  2. Select the trigger and select Activate trigger.
  3. After it is activated, the trigger is live.
Activate Trigger.
To activate multiple triggers at the same time,
  1. Select Draft
  2. Select Bulk activate RAM triggers.
  3. In the window that opens, select the triggers to activate, and select Activate.
The activate trigger.
Edit a RAM Trigger
  • When Edit Trigger is selected a notification appears. The notification recommends one of the options for the trigger that varies depending on whether the trigger uses versioning or not. Make the selection carefully as this affects how the RAM trigger functions moving forward.
    • Create new version and apply changes to new reqs:
      • Selecting this option applies the changes to reqs opened after the change was made active. This allows all candidates within a req to follow the same trigger logic. While saving the changes in the new version, a different trigger name must be specified. It is recommended to append version names such as v2 or v3 to the name. After versioning is activated, only one trigger is seen under this new name.
      • After versioning is selected on a trigger, all additional changes use versioning as well.
      • To disable versioning for a RAM trigger, select Delete previous trigger versions.
    • Make changes to existing version and apply changes across all reqs:
      • Does not create versioning for RAM triggers.
      • Selecting this option makes the change immediately, upon activation, across all reqs. The new trigger logic takes effect immediately, and a mixture of trigger logic for candidates within a req might be seen.
  • After edits are finished, the trigger must be activated.
  • If the trigger is in draft status, all trigger events are held until the trigger is made active again, up to 2 weeks. After the trigger is activated, the events that occurred during the time the trigger was in draft status are processed. After 2 weeks, any events during the draft period are ignored.
  • Do not leave triggers for a long time in draft mode in the Production environment since all testing must be completed in staging.
  1. To edit a trigger, select Tools > Automation Manager > Admin
  2. select the trigger and select Edit trigger.
  3. Edit the trigger as needed.
Edit Trigger.
View Trigger Versions
To view the versions of a trigger, select the trigger and select View trigger details.
View Trigger details.
The Version name.
Inactivate a RAM Trigger
  • It is recommended to inactivate triggers rather than delete triggers.
  • When a trigger is inactivated, triggering events are no longer processed or held.
  • Only active triggers can be moved to the inactivate status. To inactivate a trigger in draft status, the trigger must first be activated.
  • If an HR status, or form, is selected for a trigger that is inactive, it is not available for selection as a trigger event.
  • See RAM FAQs for more information on inactivating RAM Triggers.
To inactivate a trigger,
  1. Select Tools > Automation Manager > Admin.
  2. Select the trigger, and select Inactivate trigger.
Inactivate Trigger.
Delete a RAM Trigger
  • If a trigger was created in error, or is no longer needed, it can be deleted.
  • It is recommended to inactivate triggers rather than deleting. This option is available only for triggers in Draft status.
  1. To delete an active trigger, select Tools > Automation Manager > Admin.
  2. select the trigger and select Edit trigger.
  3. Select Draft.
  4. Select the trigger, and select Delete trigger.
Delete Trigger.
Delete Previous Trigger Versions
  • This option is available for triggers in Active and Inactive statuses.
  • Any new trigger events use the configuration as defined in the most recent trigger version.
  • When the triggers are edited the next time, the user is presented with the option to use versioning or continue without using versioning.
  • For Active triggers, no events are missed when the delete versioning is processed.
  1. To Delete Previous Trigger Versions, select Tools > Automation Manager > Admin.
  2. Select the trigger and select Delete previous trigger versions.
The delete trigger confirmation message.
Email WatsonTalentTraining@us.ibm.com if you have a suggestion for improvement, or encounter an issue on this documentation. Include the product and page title in your email.