Once you've installed and configured Workflow Solution it's time to start making your work flow. Read on for information about how to customize components or use pre-packaged workflows.
Altiris Component Generators
There are four component generators available with Altiris Workflow Solution: ASDK, Task, Report, and Resource. Each component generator is an Integration project, created through Workflow Designer, which builds or rebuilds Altiris components available by corresponding to its named counterpart. Example: the Task generator builds Task oriented components.
Any modifications to the ASDK methods or web services, Resources, Reports, or Tasks on the Notification Server need to be reflected within the components for any workflow using this functionality. Example: If a new task instance is created in Notification Server, the new component will not be available to a workflow until the Task Generator is built or rebuilt.
- Resource Generator - The Resource Generator is run during installation and gathers all resources available on Notification Server. A resource is usually a tangible item, like a computer, telephone, or printer, and has data and associations to other resources on Notification Server. Resources are managed in Notification Server, and any components generated will need to be regenerated in order to reflect changes from Notification Server.
- Task Generator - The Task Generator is run after installation by the workflow developer and gathers all tasks available on Notification Server. A task is a series of actions taken on a resource or a collection of resources. Tasks are managed in Notification Server, and like resources, any component generated will need to be regenerated in order to reflect changes from Notification Server.
- Report Generator - The Report Generator is run after installation by the workflow developer and gathers all reports available in Notification Server. For every report available, one component is created. Each report component represents a SQL query that retrieves and stores structured data back in a collection within a workflow.
- ASDK Generator - The ASDK Generator is run after installation by the workflow developer and creates components out of ASDK method calls. ASDK methods change less frequently than task and resources change on the Notification Server. However, like other components, any changes to an ASDK method contained within a component requires the components to be regenerated.
About Creating a Workflow
After Altiris Workflow Solution has been set up for the first time, a new workflow can be created.
About Workflow Components
A workflow uses special components with the ability to pause execution until a person interacts with a requested task. Workflow components have parameters to control the behavior of delivering a task, setting conditions on how to deliver and how long to wait, and how to deal with a task that has been waiting for a response for too long. Within a workflow component, there is an imbedded model, which is essentially a model with components configured to present a workflow interface and react to the input. Special components have been created for the Altiris platform for Altiris specific interactions; however, general workflow components are also contained within Workflow Solution.
The general workflow components contain components for interaction, components to manage tasks, and components to pause execution in case of task timeout.
Testing a project
To test a project
- If the project is fully valid, click the Bug icon located on the Icon toolbar to run your program.
- Double-click on the blue underlined Execute link, located on the left of the Running... window, to begin running the project. During testing, the project generates output to use for debugging. A project in debug is automatically labeled MyService.asmx.
- If required, the Input Values window appears. Enter any data to continue testing.
In order for a project to successfully execute, any input data required must be provided, unless set to Null Allowed.
After the project is running, if any problems are encountered, an exception is thrown. If the project is valid, it executes properly, and displays the project's output.
As the project functionality executes, within the Model tab of the Running... window, the entire project is highlighted. The yellow highlighting indicates the project has executed the highlighted component or connection. If a project returned an error (an exception), the arrow stops at the component which "threw" the exception (caused the error). This is the point to begin debugging.
Debugging a Project
At the point of failure, an exception is shown in a dialog box.
The error report displays a stack trace, which shows the list of error messages provided by different steps of the execution process. Each error displays the cause, the error location, and the point where the component failed
.
To debug the project
- Read the feedback from an execution attempt and decipher the location of the first error being thrown.
- Attempt to locate the source of the problem within your project and test.
After a program is executed without exception, a feedback session is created. The feedback session describes the execution of your project.
Publishing a Workflow
Workflow Designer uses a Plug-in for publishing a workflow to the Altiris Platform. When the workflow is ready to be deployed, dependent on project type, the deployment wizard allows different types of deployments. Forms projects can be published as a dialogWorkflowItem, ItemAction, or CatalogItem (SmartTask included). Workflow and Decision Only projects can be deployed as a ServiceWorkflowItem. For each deployment type, the wizard presents the Altiris options and asks for related information.
There are two wizards for publishing a workflow: Form Start Workflow and Non Form Start.
Form Start Workflow projects options:
- Deploy as a Service Catalog Item.
- Deploy as a Collection item to Help Desk.
- Deploy as a Dialog Item Action (must have one array data variable that is of type unique id to capture and identify the item guid in the process).
Non Form Start project options:
- Deploy as a service workflow item.
- Deploy as task.
- Deploy as an Item action (must have one array data variable that is of type unique id to capture and identify the item guid in the process).
To publish a Service Workflow Item
- Click the Deployment icon in the toolbox.
- From the Project Deployment dialog box, select the Notification Server for deployment, and click OK.
- From the Application Properties Editor, verify the properties are set up correctly, and click Save.
These properties come directly from the Deployment settings in Project Properties.
- From the Deployment dialog box, click Yes.
- From the AskServiceData dialog box, enter the details and click OK to publish the project.
After the project has been published, a Success dialog box appears stating the Service Workflow Task was added to the Altiris Console.
- On the Altiris Console, select Configuration > Configuration > Solutions Settings > Workflow and verify that the Service Workflow Item was successfully published. The newly added item should appear in the list of Workflow.
Workflow Packs
As part of Altiris Workflow Solution, Workflow Packs are available for use as customizable, pre-packaged workflows, or as a template that can be cloned and edited for further customization. The level of interaction with Workflow Packs is dependent upon the license acquired for the Workflow Packs.
In addition to pre-configured Workflow Packs, custom workflows can be developed using Workflow Designer.
Chapter 2: Installing and Configuring Altiris Workflow Solution 6.0
Chapter 4: Altiris Workflow Designer