This function displays a process instance on its own page.
On the Process Instance page, select a process from the table, then click “View > Render”. The rendered instance will show its execution path relative to the workflow design.

A rendered execution is shown below. Notice the instance name, status, and test mode information at the top. Click the navigation icon to render the process definition on a new page. Use the column filter to show or hide columns in the table. The table displays the “created on” and “updated on” dates, the user who created it, the instance state, and priority. The instance image shows workflow progress from the “Start” step. Use the “pan” feature to quickly navigate the image. Click the icon to toggle the “pan” feature on or off.

Mouse over the process steps to view the tooltip information: "step type, elapsed time in milliseconds, and execution ID".

View the instance's task list by selecting the “Items > Tasks” menu option. The tasks appear in the table below. Use the “Search” text box to filter the list.

The IsAcknowledged and AcknowledgedOn columns are included by selecting the Column list icon, as shown below.

The critical path for a process instance.
Users can view the execution's critical path for a process instance based on the process definition's configuration. The critical path represents the longest path through the process instance's execution.
On the Process Instance page, select a process from the table, then click “View > Render”. The process instance will open on a new page. Then, select “View > Instance Critical Path”.

The critical path is highlighted in red, as shown below.

Select “ON” for Display Dates to show the plan’s start and end dates.

The “Instance Critical Path” shows the longest path the process instance follows.
Note: The critical path calculation for definitions and instances relies on the time zone for steps such as milestones and waitForDatetime. When the time zone calculation is null (i.e., when getDate and getUTCDate differ), the calculation uses the UTC date as the current date for all steps.
Export - XML
This function exports the process instance to an XML file.
On the Render Instance page, select “Export > XML”. The process instance XML file is generated and downloaded to the local folder.

The instance XML file content is included here for reference.

Export - Task Files
This function exports the task file attachments of a process instance to a ZIP file.
In this example, the process instance has a completed Task.

The Task has a few file attachments uploaded by the User.

On the Render Instance page, select “Export > Task Files”. The task file attachments for this process instance are retrieved from the file system (or the DMS File Storage Folder) and exported to the local folder as a ZIP file. An alert notification appears with "No files" if the task contains no file attachments. Note: The DMS File Storage Folder is configured in the “Start” process step.

Items - Documents.
Based on the configuration of the process steps, the workflow definition creates tasks and form tasks, runs subworkflows and dynamic subworkflows, and generates documents to be stored in the DMS folders through its process instances.
The DMS File Storage Folder and its contents, generated by the process instance, are removed when the process instance is “reset, removed, or archived” via the UI.
In this example, the process instance has a completed Task. The Task has a few file attachments uploaded by the User. On the Tasks page, click the Task's “clock” icon to view the Task's history. The file attachments are listed in the table below.

Select the Process Instance and render to view. On the Render Instance page, click “Items > Document”. The process instance navigates to the DMS folder in the new page.

The DMS folder is automatically created by the Process Instance, as configured in the “Start” process step. The folder contains “Tasks, Generated Documents, and Forms” as sub-folders, as the workflow generated these artifacts.

Click to expand “Tasks” and its subfolder. The task file attachments are listed in the table below.

Click to expand “Generated Documents” and its subfolder. The documents generated by the process are listed in the table below.

Click to expand or collapse to view the Document folder path as shown in the image below.

Tasks in the render instance.
This function shows the task information for the process instance.
On the Process Instance page, select the process from the table, then click “View > Render”. The process instance opens on a new page. Next, select “Items > Tasks”.

The tasks are listed in the table below. Select a task from the list, then click the "Resend Email Notification" button to resend the email notification.

Click the Clock icon to view the task history. The information appears in the pop-up window below.

Use the “Search” feature to find the task. To view tasks, click the “Instance” tree to expand or collapse it. Click the status link to view sleeping or closed tasks. This “Search-and-view-selective” task is an Admin feature.

Instance hierarchy.
This function helps you navigate between parent and child instances in a tree view.
On the Process Instance page, select the instance in the table, then click “View > Instance Hierarchy”. The parent and child instances are displayed in a tree view, as shown in the example below. Click the node to open the instance in a new page.

Navigate to Error and the Wait steps.
This function navigates to the Wait and Error steps in the process instance.
On the Process Instance page, select the process from the table, then click “View > Render”. The process instance will open on a new page. Then, choose “Items > Waiting Steps”.

A pop-up window appears with URL links to navigate to the specific waiting step.

On the Process Instance page, select the process from the table, then click “Items > Error Steps”.

A pop-up window appears with URL links to navigate to all errors and to a specific error step. Click the link to view that error step, and the instance page will jump to it.

Click the status hyperlink to view all errors, including the step and system logs, as shown below.

The instance errors are shown below.

Users in the render instance.
This function displays the users involved in the process instance.
On the Process Instance page, select the process from the table, then click “View > Render”. The process instance will open on a new page. Next, select the “Items > Users” menu option.

The “involved users” and “historical users” are listed below.

The user is involved in process instances.
The Process Instances page shows the instances the user has started, as well as cases where the user has completed or received tasks. It is available in the new "Involved" tab.

Logs in the render instance.
This function shows the log details specified for each step in the definition.
On the Process Instance page, select the process from the table, then click “View > Render”. The process instance opens on a new page. Next, select the “Items > Log Messages” menu option.

The Log Messages are shown in the table below.

Note: In the process step, go to the Logging tab and configure the workflow to enable logging, as shown.

Business data in the render instance.
This function displays all linked business data used during execution.
On the Process Instance page, select the process from the table, then click “View > Render”. The process instance will open on a new page. Next, select “Items > Business Data”.

The business data (if any) is presented in the table below.

Queues in the render instance.
This function displays all queues involved in the selected instance.
On the Process Instance page, select the process from the table, then click “View > Render”. The process instance will open on a new page. Next, select the “Items > Queues” menu option.

The queue information is shown in the table below.

Engine Alerts.
This function displays the engine alerts recorded during execution.
On the Process Instance page, select the process from the table, then click “View > Render”. The process instance opens on a new page. Next, select “Items > Engine Alerts”.

The “Engine Alerts” information is presented in the table below. The render instance displays a pie chart of engine alerts.

History in the render instance.
This function shows the history details of the rendered process instance.
On the Process Instance page, select the process in the table, then click “View > Render”. The process instance opens on a new page. Next, select “Items > History” from the menu.

The historical information is shown in the table below. Use the tabs to view “Events, Runtime Info, Task Reminders, Engine Alerts, and Error Details” for the process instance.

The information on the Events tab is presented in the table below.

The information in the Runtime tab is shown in the table below.

The information in the Task Reminders tab is presented in the table below.

The information in the Engine Alerts tab is shown in the table below.

The information in the Errors tab is shown in the table below.

Statistics in the render instance.
This function displays statistics on steps, steps by execution, the elapsed time for each step, and the elapsed time for each engine alert in the rendered process instance.
On the Process Instance page, select the process in the table, then click “View > Render”. The process instance will open on a new page. Next, select “Statistics > Step”.

The step-by-step statistical information is shown in the table below.

The table below presents step-by-step execution statistics.

The elapsed time for each step is shown in the table below.

The table below shows the elapsed time by engine alert statistics.

Execution view in render instance.
On the Process Instance page, select the process from the table, then click “View > Render”. The process instance opens on a new page. Next, select “View > Execution View”.

The process instance execution view appears on the new page below. Observe the process flow along the execution path.

Use the “Select Steps” drop-down menu to select two or more steps, then click the “Generate Image” button.

The application renders a new process instance execution view between the two process steps, as shown below. This concise view should help understand the execution of an extensive process in segments.

Start-End execution in the render instance.
This function displays the process instance between the “Start” and “End” steps based on the user's selection. This concise view helps understand the execution of a complex process in segments.
On the Process Instance page, select the process from the table, then click “View > Render”. The process instance will be displayed on a new page. Next, select the “View > Start End”.

Select a starting step from the dropdown list.

Select an end step from the dropdown menu, then click the “Generate Image” button.

The execution path between these two workflow steps is shown in the image below.

Select steps to exclude from the render instance view.
This function displays the process instance without the selected steps. This clear view helps understand how a complex process executes in stages.
On the Process Instance page, select the process from the table, then click “View > Render”. The process instance will open on a new page. Then select “View > Start End” execution.
This feature hides steps from the render instance view, helping you focus only on the selected steps.
Click the “Select Steps to Exclude” drop-down menu, check the boxes for the steps you want to exclude, then click "Generate Page."

The process instance will be re-rendered without the selected steps.

Task Heat Map view in render instance.
This function creates a heat map of process instance tasks for the rendered instance. The heat map visually shows the process's behavior, its most frequently used parts, and where errors occur.
On the Process Instance page, select the process from the table, then click “View > Render”. The process instance opens on a new page. Next, select “View > Task Heat Map View”. The task heat map for completed steps appears on the same page.

The heat map of completed steps is shown below.

You can watch this video to learn more.