Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Creating automation scripts

For every action that you want to perform in an external system (target) by using BMC Release Process Management, you must create an automation script. Once you have your automation scripts ready, you can use them in various steps of a request and then run the request.

Before you create an automation script, ensure that you configured an integration server.

You can create new automation categories to sort your automation scripts. Also, you can use one of your existing scripts with a Template type as a template for creating new scripts.

Starting with BMC Release Process Management version 4.6, you can change the status for your automation scripts. For more information, see Using status of objects.

Note

 All new and imported automation scripts have the Draft status set by default.

To create an automation script

  1. Go to Environment > Automation.
  2. Click Create Automation on the right pane.
  3. From the To use as list, select Automation.
  4. In the Choose Automation Category list, select one of the automation categories.
  5. From the Apply template list, select an option that you want to use as a base for creating your script. 

  6. In the Script integration server list, select that integration server that you want to use for connecting with the external system.

    Notes

    • When you select a server from the list, the details related to that integration server are automatically added to the script body.
    • You cannot add an integration server if the script body is empty.
    • A general script that you do not plan to use for performing some actions in a particular target external system does not require an integration server.
  7. In the Script Name box, specify a unique name for the script.
  8. In the Description box, specify a short description regarding the purpose of the script.
  9. In the Script body area, specify the Ruby script that runs in a step.
     The script body is the core of an automation script. The action that you want to perform and how you want to execute it depends on how you design the arguments and the logic in the script body. For more information about designing the script body, see Designing-the-script-body-of-an-automation-script.
  10. In the Script type list, select one of the following options as appropriate:
    1. Template — Select this option if you want to save this script as a template for future use.
    2. System — Select this option if you want to save this script as a base script that can be only viewed or copied but not modified by anyone apart from the Administrator.
    3. User — Select this option if you want to save this script as a normal script for your personal use and available for viewing, copying, and modifying. 
  11. Click Add script to save the script or click cancel to exit without saving any changes.
  12. (Optional) Change the imported automation script status to the state other than Draft if you want to make the script available for other users.

Related topics

Creating-resource-automation-scripts

Integrating with various external systems

Mapping-properties

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*