Export to PDD
Timeline provides a convenient way to export a task description to Process Definition Document (PDD). This document outlines the task and its properties in a comprehensible and illustrative way. Get familiar with the systems involved in the process and the presence of decision points affecting performance. Use Task schema as a flexible tool for visualization to clear out and unify the actual processes and prepare the basis for creating automation solutions for the business.
For example, explore the most repeatable task with low complexity. This indicates with high probability that users spend a lot of time performing simple steps. Customize a schema to see the most representative workflow and export PDD. This document will explain the direction for optimization development.
How to generate PDD
- Select a task in the Automation candidates table.
- Choose Task schema in the drop-down list of analysis types.
- Prepare the schema for export (each point is optional):
- Mark optional nodes.
This feature grays out nodes in the document and adds the corresponding text to the file.
To do this, select an application or a form on the schema and toggle on Application is optional/Form is optional in the properties pane. - Add objects to the Ad hoc list.
This option does not display such nodes in PDD but keeps them as a part of the task. Ad hoc objects can be applications and forms that cannot be automated or exceptions from the main work process.
To do this, select an application or a form on the schema and click in the left pane. - Add Comments for nodes and transitions.
- Configure the schema view for export: expand and collapse necessary nodes and adjust transitions display.
Note. The minimum level available for export is a form level. - Click Export task and select PDF or Microsoft Word format to save the document on your computer.
For setting descriptions, see Task Schema Customization Options.
PDD content
PDD provides concentrated information about a task. It includes general information about the task definition, nodes' settings, and necessary details marked with comments. The exported document contains:
- Picture with a preconfigured schema view where nodes are marked with numbers for easier identification.
- Task definition description.
- Lists of used applications and forms within them.
Each point of the list can be marked as optional and may have a comment. - Lists of subtasks, if the task includes any.
Each point of the list can be marked as optional and may have a comment. - Section with transition comments, where start and end points, and text are specified.
- Section with special transitions, such as copy-paste, if the task includes any.
Usage example
You may need to create a document for an automation team as a basis for further development. For this, you need to create a task definition and cut logs into instances. Create a schema for the task and make the needed preparations in Task schema:
- Review applications and forms.
- Mark nodes as Ad hoc if they can be skipped or are not essential for the PDD representation. These nodes will be removed from the schema.
- Mark nodes as optional to gray them on the schema. This allows you to identify those nodes, the presence of which in the task may depend on some factors.
- Add comments for nodes and transitions.
- Configure schema view and export task.
As a result, you will get a PDF or Microsoft Word document with a guideline for future automation.
05.09.2024 16:23:54