- Introduction
- Getting Started
- Managing Automation Packs
- Performing advanced console tasks
- Authoring Processes
- Authoring Categories
- Advanced Authoring
- Monitoring Operations
- Performing Basic Console Tasks
- Performing Administrative Actions
- Working with Events and Triggers
- Using Adapters
- Using the PowerShell Snap-in CLI
- Managing High Availability and Resiliency
Advanced Authoring Concepts
Cisco Process Orchestrator provides integrations with various technologies. Although it supports numerous types of integrations, at the core Process Orchestrator provides the individual steps that make up the workflows in processes; these are called activities . For example, Process Orchestrator provides:
- A set of String activities that you can use to manipulate string text and characters.
- A set of Table activities that you can use to modify the format for existing defined table variables. The available table variables can be defined as either a global or process variable.
- A Set Variable activity that you can use to place a collection of bits in a Process Orchestrator number.
- Knowledge base articles provide information to help understand the results of an activity, including a summary of what has occurred, the possible cause of the result, and suggested actions to take to resolve issues with an activity.
- Modifying a process does not automatically modify an activity. Activity definitions are included in a process workflow and the activity properties must be modified separately from the process properties.
- Activities can only be modified in the Process Editor. With the appropriate rights from the Operations view, the Process Editor is launched when accessing the process properties.
- When user rights are restricted, the Process Viewer is launched with the properties displaying a display-only view after determining that the user cannot edit the activity.
The following topics describe these activities:
- Using String Activities
- Using Table Activities
- Using Core Activities
- Authoring Knowledge Base Articles
For instructions about inserting a variable in an activity, see Inserting Reference Variables.
Using String Activities
You can use String activities to search, replace, and modify string content in the objects within Process Orchestrator. For example, you can:
Using Table Activities
You can use Table activities to modify the format for existing defined table variables.
Note Any boolean and numeric values that are used by the Table activities in the product are not localized. Numbers use [ . ] for the decimal format regardless of the regional and language options. Boolean values for substitutable boolean must be true or false regardless of the installed language.
Read Table from Text
Read a comma-separated value (CSV) string variable and convert the text into a table with a specified set of columns.
Populate columns from first record in source text—Check this check box to use the first row data from the source text as table columns in the output result.
By enabling this check box, the Columns to read field is hidden.
When you enable this check box for existing activities with data in Columns to read field. All existing data in columns in read is deleted.
File type—The source text can be delimited by Tab, Semicolon, Comma, Space, and Other (enter the required delimiter).
For example, if the Populate columns from first record in source text is checked & File type is delimited by Comma:
"Georgetown","Williamson","TX"
\"Georgetown\",\"Williamson\",\"TX\"
Georgetown,Taylor,LibertyHill,Williamson,TX
"Georgetown,Taylor,LibertyHill",Williamson,TX
The following example explains how you can include multiple strings in a single column using double quotes (Last row) and you can use slash (\) to include double quotes along with the string (Third row).
The fourth row displays only the first three strings being considered as City, County, and State as we have three columns only.
Read Table from XML
Read an XML snippet and convert it into a table with a specified set of columns.
Populate columns from xml—Check this check box to use xml elements from the source xml as table columns in the output result.
By enabling this check box, the Columns to read field is hidden.
When you enable this check box for existing activities with data in Columns to read field. All existing data in columns in read is deleted.
This produces a table with two columns (name, age), with three rows.
Read Table from JSON
Read an JSON and convert it into a table with a specified set of columns.
JSON Path: Enter the JSON path to be used as columns.
Populate columns from JSON—Check this check box to use JSON elements from the source JSON as table columns in the output result.
By enabling this check box, the Columns to read field is hidden.
When you enable this check box for existing activities with data in Columns to read field. All existing data in columns in read is deleted. For example:
This produces a table with author as column name, with four rows containing author names. For example:
Join Tables
Join two tables with same schema’s or with different schema’s such as table from text, table from xml etc. and convert it into a table with a specified set of columns.
- Table1—Select table 1 by clicking the reference tool.
- Table2—Select table 2 by clicking the reference tool.
- Join Type—Select type of join from the drop–down list:
– Inner—Displays all records that match the condition in both the tables, and records in both the tables that do not match are not reported.
– Left Outer—Displays all the rows from the left table in conjunction with the matching rows from the right table. If there are no columns matching in the right table, it returns NULL values.
– Right Outer—Displays all the rows from the right table in conjunction with the matching rows from the left table. If there are no columns matching in the left table, it returns NULL values.
– Union—Displays matched and unmatched from both tables.
- On Condition—Select on condition for the table 1 and table 2 columns either by clicking the reference tool icon or by entering the column name manually in case of table from XML.
Note This mandatory field will be read only, if the selected join type is Union.
- Results Column—You can Select All or Unselect All or select the columns from the results column as needed.
- Number of rows—Click All rows or At most radio button by entering the appropriate number of rows.
This produces a table with two tables combined by selected join type and on condition entered for table1 and table 2 column.
Using Core Activities
Core activities are a set of items that span applications. For example, use the following activities to:
Calculate a new date/time value based on a specified base date/time and adjustments. |
|
Convert the date and time into a string text format. For example: |
|
Check whether a process event occurred within a certain amount of time of another problem (see Creating Correlate Event Activities). |
|
Generate an automation summary including data selected activities in a process. To generate the data output, choose the activity, then specify the section in the automation summary in which to output the data. An automation summary is a collection of data summarizing the objects included in the process and the data retrieved by the processing of the of the objects. The share path specified in the Core Functions Adapter properties will be used when viewing the automation summary reports. |
|
Among other use cases supported by this activity, you can find targets whose properties have certain values. |
|
Define the configuration properties to be used to insert one event into Process Orchestrator Reporting Database. |
|
Define the performance metric properties to be published into the Process Orchestrator Reporting Database and the Windows Management Instrumentation (WMI) provider. The metrics are published under the root\TEO name space through the WMI class, TEO_PerformanceMetric . |
|
XPath queries navigate through XML documents and search through the document nodes. Use the XPath Query dialog box to enter the XPath properties to query from the source XML code. |
|
Apply an XSLT transformation to a specific XML text. XSLT transformation can transform XML into plain text, HTML, or other XML. |
Adding an XPath Namespace Definition
An XML namespace provides a way to avoid element and attribute name conflicts within an XML document. An XML namespace is uniquely identified by a Uniform Resource Identifier (URI) and is assigned a prefix (unique to the XML document) used for its element and attribute names.
Step 1 In the Process Editor, choose Toolbox > Core Activities > XPath Query , then drag and drop the activity onto the Workflow pane.
Step 2 Choose the XPath Query tab, then choose Namespaces > New .
Step 3 In the XPath Namespace Definition dialog, enter the prefix and URI for the new namespace, then click OK .
XPath Example Syntax
The following expressions can be used when selecting nodes in a path expression.
XPath Query Example
The following is an example of source XML.
The following example path expressions and related results are based on the preceding source XML.
For additional examples, see http://www.w3schools.com/xpath/xpath_syntax.asp .
XPath Query Example 2
In the following example, the elements prefixed with xdc are associated with a namespace whose name is http://www.xml.com/books , while those prefixed with h are associated with a namespace whose name is http://msdn.microsoft.com/en-us/library/ms950779.aspx .
For additional examples, see http://msdn.microsoft.com/en-us/library/ms950779.aspx .
Authoring Knowledge Base Articles
Knowledge base articles provide information to help understand the results of an activity, including a summary of what has occurred, the possible cause of the result, and suggested actions to take to resolve issues with an activity. Knowledge base articles can make automation summaries more usable, explaining how to use the information that is surfaced.
Knowledge base articles are referenced by specific activities and can be viewed in the following locations in Process Orchestrator:
- Operations Workspace—When viewing activity instance properties, you can view the display-only properties of the associated knowledge base articles by selecting the Knowledge Base tab.
- Process Editor—You can reference a knowledge base article to an activity when defining the activity properties in the Process Editor.
- Automation Summary—All referenced knowledge base articles will display on the automation summary.
The Definitions > Knowledge Base view displays the available knowledge base articles that can be assigned to a process activity or to a trigger. When Knowledge Base Articles is selected in the Navigation pane, the defined knowledge base articles display in the Results pane.
Process Orchestrator ships with predefined knowledge base articles, or you can create your own knowledge base articles to associate with activities in the process.
To create a knowledge base article:
Step 1 Choose Definitions > Knowledge Base , right-click and choose New > Knowledge Base .
Step 2 On the Knowledge Base property pages, define the properties, including:
- Summary—A concise description of the issue.
- Possible cause—An explanation of the condition that may be causing the issue. If necessary, enter multiple possible causes so that all possibilities are investigated.
- Possible resolution—List of actions that can be performed to attempt to resolve the issue.
- Related information—Additional information that may be relevant to the issue.
Step 3 Click OK to close the dialog box.
Feedback