Creating and modifying nodes for trees using the builder.
Walk through the sources to make sure that they still make sense
XXX indicates an element to create or modify, possibly a link to set
Task trees are created by adding and modifying nodes and connectors.
Nodes are representations of handlers customized (in most cases) for the specific tree. There are System Controls that are the basic operations included with every installation (Wait Nodes, Joins, Junctions, etc) and other handlers added specifically to your installation of Kinetic Task (System Retrieve, Incident Create, VM start/stop, etc).
Add Node to Tree
New trees begin with only a Start node (there are no end nodes). All available handlers are listed in Categories. Click on a Category to expose the handlers. Click on a handler and drag to the desired position on the builder (nodes can be moved at any time).
Basic Node Options
All nodes share the following properties:
- Delete (x). Click the X on the upper left to delete the node. Deleting a node also deletes all attached connectors.
- Information (i). Click the "i" on the upper right to see the details of the node. You can also double click in the body of the node.
- Connector Creator. Click the triangle and drag a connector to another node on the tree. You cannot create a connector that doesn't connect at both ends (must connect to another node).
- Label. "friendly" name for the node. Set on the details presentation.
A node that is solid orange is deferred. More on that later in the article. A dashed border around the node means that it is not configured correctly.
- Label. The initial label is the same as the node id including the integer identifier (underscore integer added to the end of the id to make the id unique. ex: _42).
- Defers. Check box to indicate that the task is deferred. XXX reference to deferred actions/connectors
- Visible. Check box to have the task shown on a console. Optional.
- Parameters. Enter or reference values for use by the task handler.
- Messages. Information about the task that can be displayed on related consoles. If the node is deferred separate message fields are available for Creat, Update, and Complete. If the node is not deferred only Complete is available.
- Id. Unique identifier for this node on the current tree. Read Only.
- Save and Cancel. Buttons that perform the Save and Cancel actions.
Parameters allow you to input both dynamic and static data. Asterisk indicates a required field.
Each parameter has a label and an input field. Hold your cursor over the label for help text.
For static data, type directly into the input field.
Dynamic data can be referenced from multiple sources. Click on the edit pencil to the right of the input field to open the edit dialog for the parameter (see below for sources).
Static and Dynamic data can be combined and formatted as needed depending on the destination of values.
Along the top are logical operators and helper options for creating qualifications.
Clicking on Pre-defined Values brings up a menu of possible values. Depending on the Source, different groups of values are displayed.
Sources determine what details are available under Pre-defined values. If the tree is not bound to a certain source the following groups are available:
Source Information. Configuration information about the tree.
- Source Group.
- Source ID.
- Source Name.
System. Information that is provided to the trigger.
- Execution Id.
- Trigger message.
Task Results. Results from other nodes.
Current Sources that provide bindings include Kinetic Request, Kinetic Survey, and Kinetic Task. With the correct naming structure, of the Source Group (Service Catalog > Service Item or Survey Category > Survey Template), the following additional groups of parameters are available:
Answers. List of the questions from a service item (Binding by Source Group). (ex: <%=@answers['User ID']%>)
Application Config Values. (ex: <%=@appconfig['Default Web Server']%>)
- Default Web Server
- Mid-tier Web Server
Dataset. Values from the dataset attached to the service item specified in the binding. (ex: <%=@dataset['Attribute 1']%>)
Service Item Details. Configuration information from the service item. (ex: <%=@template['Description']%>)
- Allow Anonymous
- Data Set
- Anonymous URL
- Display Name
- Message Template
- Message Template Id
- Service Category Id
- Service Category Name