This LANDesk Process Integration Module provides structured integration of LANDesk Process Manager with FrontRange HEAT. This tight integration enables the systems to cooperatively communicate with one another, exchange data, and execute tasks. Process Manager enables you to implement HEAT autotasks into processes. Autotasks are defined actions or functions that are performed within HEAT, such as updating records, creating logs, and sending messages. By incorporating these autotasks into processes, the processes can be partially or fully automated to perform the designated tasks.
The integration module also enables you to leverage your existing investments and extend their capabilities by actively involving them in process management.
Process Manager's 30-day trial period includes the integration module for HEAT. At the conclusion of the trial period, you can make the integration permanent by purchasing a product license. See "Product licenses".
You need to complete the following steps to deploy and take advantage of the HEAT integration.
In order for HEAT autotasks to be available in Process Manager, you need to configure HEAT with the necessary requirements. You need to create a container (folder) named Workflow in the autotask manager of HEAT's call logging tool. Once the container has been created, you add the autotasks supported by Process Manager into the container. Autotasks can be actions or functions.
Process Manager supports the following HEAT actions:
Process Manager supports the following HEAT functions:
Once you have created the Workflow container in HEAT and inserted the supported autotasks, the next step is to create an database listener to start your HEAT workflows. The database listener monitors the HEAT database and when the listened-for event occurs, initiates the designated workflow.
For instructions on creating a database listener, see "Event Listeners" in Process Designer Help.
The final step is to use Process Designer to create workflows to take advantage of the HEAT autotask integration. As with all other workflows, you drag and drop the HEAT autotask action onto the canvas and then configure the corresponding attributes.
For details on creating and running workflows, see "Setting up a workflow" in Process Designer Help.
Once you have built the workflow process and saved it, you are ready to start the database listener. This will cause Process Manager to monitor the HEAT database and initiate processes when the predefined conditions are met.
Note: Whenever a change is made to a form in HEAT, you need to close HEAT and log in again in order to update the catalog file. If you attempt to use a form that has been changed without updating the catalog file, the autotask will fail. Any processes configured to use the autotask will also fail.