Create System Actions

To create a system action for a process

  1. Select Processes from the Data Administration menu.

    The Available Processes page appears.

  2. Click the process name for which you want to create a system action.

    The Process Definition: Properties page appears.

  3. Open the step you want to edit.

    The Process Definition: Step Details page appears.

  4. Click New in the Actions section.

    The Select Action Type page appears.

  5. Select System Action and click Next.
  6. On the Create System Action page, enter an action name, ID, and notification details.
  7. In the System Action section, click the Object drop-down and select an object.
  8. Click the Action drop-down and select a system action for the selected object. Accordingly, select the desired action parameters. The choices that appear depend upon the action you selected. For example, for the Resource object, if you select the Set Booking Manager system action, then you must also specify which booking manager. Or, if you select the Lock Selected Attributes system action, then you must also select which attributes to lock.
  9. Click Submit.

    The Process Definition: Step Details page appears.

    You can create another action in the same step by clicking New.

Create a Run Job

To set the system action that will run a scheduled job

  1. Select Processes from the Data Administration menu.

    The Available Processes page appears.

  2. Click the process name for which you want to create a run job.

    The Process Definition: Properties page appears.

  3. Open the step you want to edit.

    The Process Definition: Step Details page appears.

  4. Click New in the Actions section.

    The Select Action Type page appears.

  5. Select Run Job and click Next.
  6. On the Select Job page, select a job type and click Next.

    The Set Job Properties page appears.

  7. Complete the following information:
    1. Enter the action name, ID, and notification details.
    2. (Optional) At Job Name, enter a new name for the job.
    3. At Completion Mode, select the check box to mark the step complete when the job completes (synchronous), or when the job starts (asynchronous).
    4. If the Parameters section displays, enter any parameters required for the job. The parameters that display, if any, depend upon the job you selected.
    5. In the Notify section, click the Browse icon and select the resource or group who should receive notifications about the job.
    6. In the Sharing section, click the Browse icon and select the resource or group with whom you want to share this job.
  8. Click Submit.

    The Process Definition: Step Details page appears.

    You can create another action in the same step by clicking New.

Create Subprocesses

To set the system action that will run an existing subprocess that is valid and active

  1. Select Processes from the Data Administration menu.

    The Available Processes page appears.

  2. Click the process name for which you want to create subprocesses.

    The Process Definition: Properties page appears.

  3. Open the step you want to edit.

    The Process Definition: Step Details page appears.

  4. Click New in the Actions section.

    The Select Action Type page appears.

  5. Select Subprocess and click Next.
  6. On the Subprocess page, complete the following information:
    1. Enter the action name, ID, and notification details.
    2. At Subprocess, browse and select a subprocess from a list of available processes.

      The Select Subprocess page lists all validated and active processes whose primary objects and their partitions match the objects and partitions of the master process. The Initiating Object field is automatically populated. The selected object is used at runtime to initiate the subprocess.

    3. At Subprocess Object Key, enter an ID for the subprocess so it can be used as a reference when building conditions.
    4. Select subprocess completion mode. A subprocess can be run in the following modes:
      • Synchronous. After the subprocess is invoked, the master process is paused till the subprocess completes. You cannot terminate a synchronous subprocess because terminating the subprocess intervenes with the master process.
      • Asynchronous. The subprocess runs asynchronously with the master process, but may join the master process at a future step or action. The subprocess' state is visible to the master process. The master process does not complete until the asynchronous subprocess completes. You cannot terminate an asynchronous subprocess because terminating the subprocess intervenes with the master process.
      • Independent. The subprocess runs independently from the master process. After a subprocess is invoked from a step action, its state is not visible to the master process. You can set the mode of a subprocess to independent if the execution of the subprocess will not intervene with its master process. The master process can complete even if the independent subprocess is still running. You can terminate an independent subprocess because terminating the subprocess does not affect the master process and vice-versa.
  7. Click Submit.

    The Process Definition: Step Details page appears.

    Note: You can create another action in the same step by clicking New.