add

You can use the add command to add scheduling items to the database.

Overview

You can add new items and items similar to existing ones. If an item already exists, you are asked whether to replace the item or not. You must specify the file location before the file name, if the file is not located where you run the command. You can use the unlock option, if the item is locked by any other user. The add command checks for loop dependencies in a workflow. There is a loop dependency in a workflow, if TASK1 follows TASK2 and TASK2 follows TASK1.

You must have add access to add an item to the database. If the item already exists and locked by any other user, then you must have modify and unlock access to the item.

Syntax and command line options

You must provide at least one scheduling or security item with the command to perform the action. You need to use the ;unlock parameter, if the item already exists and it is locked by the same user and session.
ocli model add|a filename [;unlock] [;password[=key]]

filename: You must specify the name of the file that contains the item definition.

unlock

You must add the parameter if the item you want to edit is locked by the same user and session.

v2.1.6+;password[=key]

You can use this option to provide the decryption key for files that contain {aes-user}, AES:, or ENCRYPT: encrypted password fields. The Orchestration CLI auto-detects the prefix in the file and applies the appropriate decryption method. For files that use only the {aes} prefix, no option is required. The key is resolved in the following order of precedence:
  1. The WA_EXPORT_PWD environment variable.
  2. The key value provided inline with ;password=key.
  3. An interactive prompt, if neither of the above is set.
The key must be 8–64 characters.

Examples

  1. Run the following command to add tasks from taskspend:
    ocli model add tasksspend
  2. Run the following command to add workflows from skedon:
    ocli model add skedon
  3. v2.1.6+Run the following command to add user definitions from the file users_export.txt, decrypting {aes-user} password fields using the key stored in the WA_EXPORT_PWD environment variable:
    export WA_EXPORT_PWD="mySecretKey123"
ocli model add users_export.txt