These basic actions constitute the most common or standard actions performed during a process and are specific to Process Manager. They provide the capability of integrating with other applications, systems, services, and so on.
System actions are described below.
This action enables you to define a task and assign it to one or more users or groups. You can also configure when the task should be completed. The task can represent any type of work to be performed. When the action occurs in the course of a process, an e-mail is sent to the designated participants. Any user assigned to perform the task is provided controls to mark the task as completed or not completed.
This action enables you to implement system-initiated decisions based on predefined conditions that you configure. When the action occurs in the course of a process, the system evaluates the conditions and acts accordingly based on whether the results are true or false.
This action enables you to define a JavaScript command to be executed by the system. When a workflow encounters a request to execute a JavaScript command, it locates the script by reading the path defined in two separate configuration files (listed below) on the Process Manager server. The complete path to the script must be provided in both of these configuration files in order for the script to be able to run.
After defining the path (or at any time the path is changed), it is necessary to restart the LANDesk Process Manager Scheduler service.
When the action occurs in the course of a process, the specified JavaScript command is executed.
This action enables you to define a program file to be executed by the system. When a workflow encounters a request to execute a program, it locates the executable by reading the path defined in two separate configuration files (listed below) on the Process Manager server. The complete path to the executable must be provided in both of these configuration files in order for the program to be able to run.
After defining the path (or at any time the path is changed), it is necessary to restart the LANDesk Process Manager Scheduler service.
When the action occurs in the course of a process, the specified program is initiated.
This action enables you to define a SQL command to be executed by the system. When the action occurs in the course of a process, the specified SQL command is executed.
This action enables you to define a VB script command to be executed by the system. When a workflow encounters a request to execute a VB script command, it locates the script by reading the path defined in two separate configuration files (listed below) on the Process Manager server. The complete path to the script must be provided in both of these configuration files in order for the script to be able to run.
After defining the path (or at any time the path is changed), it is necessary to restart the LANDesk Process Manager Scheduler service.
When the action occurs in the course of a process, the specified VB script is executed.
This action enables you to assign one or more users or groups to act as an approval authority. You can also configure when the approval should be completed. When the action occurs in the course of a process, an e-mail is sent to the designated participants. Any user assigned to perform the approval is provided with controls to mark the task as approve, deny, or approve with conditions. These same controls are also provided in the Web Application. If several users are assigned the task, the first person to respond determines the result for the group.
This action enables you to modify a get approval action and mark it as approved or denied in order to allow the process to continue. Normally, the get approval action is modified if it doesn't get approved or denied in the Get approval action in the process. Typically, this action is attached to a timer action. When the modify approvals action occurs in the course of a process, it assigns a value for any approval not yet completed. You determine whether the approvals are changed to approved or denied.
This action enables you to modify an Assign manual task action; it marks the manual task as not completed and allows the process to continue. Typically, this action is attached to a timer action. Normally, the Assign manual task action gets modified if it doesn't get marked as completed or not completed in the manner for which it was designed in the process. When the Modify manual tasks action occurs in the course of a process, it assigns a Not completed value for any manual task not yet completed.
This action enables you to modify a Request information action, which marks it as not completed and allows the process to continue. Typically, this action is attached to a timer action. Normally, the request information action gets modified if it doesn't get marked as form completed or form not completed in the manner for which it was designed in the process. When the Modify request information action occurs in the course of a process, it assigns a Form not completed value for any form not yet completed.
While you are in the process of creating a workflow, you may not be certain of all the elements, conditions, dependencies, and so on, that would need to be included in order to finalize the workflow. For this purpose, you can insert a placeholder as a reminder that another action may need to be included at that position in the process. The placeholder is meant to be temporary, and should be deleted once the workflow is considered complete. If it is not removed, it will generate an exception when the workflow is executed.
This action enables you specify a web form that you can have recipients fill out in order to acquire certain information. When the action occurs in the course of a process, an e-mail is sent to the recipients, informing them of the information request. They click a link provided in an e-mail, which launches a browser. They can either agree or decline to fill out the form. If they agree, the form opens so they can fill it out. The recipients then submit the information and the action is marked as Form completed. If they decline, the action is marked as Form not completed.
Note: In order for users to fill out InfoPathforms, InfoPath must be installed on the machine.
This action enables you to create a preformatted e-mail. You can designate the e-mail recipients and the messaging to be used. When the action occurs in the course of a process, an e-mail is generated with the predefined content and sent to the designated recipients.
This action enables you to specify a date and time value, which determines when the subsequent action in a process will occur. You can use the current date and time, a proposed date and time, or any other date/time field that you set up. The proposed date is required if you want the action to occur at a specified time. You can configure the number of days, hours, and minutes until the action occurs. The number of days can be according to the work week (five-day) or full week (seven-day) schedule. You can also configure the action to occur a certain amount of time before or after the action occurs.
This action enables you to change the state of the workflow instance to canceled, closed, open, pending, or reopened. When the action occurs in the course of a process, the status of the entire workflow is determined by the designated state.
This action enables you to define a Web service to use in order to communicate with another application. You select a particular method on the Web service. Some methods contain input parameters, output parameters, or both. The input parameters come from Process Manager fields or fixed values that you can specify. The output fields come from Web service fields that you can specify. When the action occurs in the course of a process, the specified Web service enables the interchange of data between Process Manager and the target application.
This action does not support asynchronous exchanges, so any data transfer occurs at that instance. Complex types such as arrays or structures are not supported. Only simple types such as integers, dates, strings, and floats are supported.
Note: In order to incorporate more complex Web services into your workflows, you need to write your own wrapper Web service. The Web Service can be called by Process Manager, which would then construct the complex arguments and pass them to the real Web service. For more information, contact customer support.