Process Assistants Overview
Concepts and Terminology
Quick Start Guide
Exploring the Process Apps Store
Building Process Apps from Scratch
What's New
Current Version

Flow Builder
Human Task
Script Task
Connect to Data Table
Connect to API
Call a Subflow
Form Creation
Form Components
Form Actions
Self-Service Portal

General Settings
Members and Roles
Bot Permissions
Import & Export
Change Logs
Delete App

Creating a Process App
Creating a Process App
Importing and Exporting a Process App
Sharing a Process App with Co-Developers
Configuring a Process App
Defining a Digital Form
Defining a Flow for a Process App
Defining Triggers for a Process App
Using Stencil to Define a Logic for a Process App
Using Events for a Process App
Adding Access Controls to a Digital Form
Calling a Subflow from Process App
Deploying a Process App
Configuring Channels to a Process App
Publishing a Process App
Analyzing a Process App
Stimulating a Process Instance
Creating and Publishing a Process App
Viewing a Process App Errors
Viewing Change Logs Made to Process App Definition
Creating or Restoring a Version of Process App
Adding Bot Permissions to let Bot Trigger the Process App

Assistant Admin Console
Administration Dashboard
User Management
Add Users
Manage Groups
Assistant Management
Assistant Management
Invite Users
Send Bulk Invites
Import User Data
Synchronize Users from AD
Security & Compliance
Using Single-Sign On
Security Settings
Cloud Connector
  1. Home
  2. Docs
  3. Process Apps
  4. Publish


End users can interact with a process app only when it is published. The Publish option allows you to make your Process App available to your end-users. 

Process App Status

Process application goes through different stages before it is used by an end-user. It follows the life cycle as shown below:  

  • In Development – The process app configuration is in progress but has yet to define all the required configurations.
  • Awaiting ApprovalThe Process Owner has published the process application thus initiating a request to the admin, but the admin is yet to approve the publishing request.
  • Approval Queue:
    • Approved – The admin has approved the process application publish request and is ready to use. The status of the process application automatically turns into a published state.
    • Rejected – The admin has rejected the publish request. An email is sent to the developer with comments from the admin.
  • Published – The Process App is live and available for end-users to use.

Publish a Process App

To publish a process app, follow the below steps:

  1. Open the process app you want to publish.
  2. Click Publish on the top-right.
  3. On the Publish window, you can find the below components with configurations:
    • Triggers
    • Flow
  4. If the process app is published for the first time, the system enables all the above components to be published, and you can select/clear the components. Once the process app is published, and if there are any changes made post publishing, components updated after publishing the latest version are enabled for selection, and the rest of the sections remain in the disabled state. At least one trigger and channel are mandatory to publish a process app.
  5. Select the Visibility option from Public (visible to anyone with the link), or Private (restricted to specific user groups and users in the system).Note: Selecting Visibility is mandatory where Public is selected by default. Once published, the visibility settings cannot be modified.
  6. Under the Additional Comments section, enter relevant comments for publishing.
  7. Click Publish.

Dynamic Error Console

You can view all the errors categorized by step on the Flow Designer error console in the property panel. You will see the errors if the mandatory fields are not entered.

If errors exist, the Publish button is disabled on the Publish page which prevents the user from publishing the node.

The following message appears on the screen.

To view the error details, follow the steps below:

1. Click the Fix Issues link.
2. This will navigate to the Property panel where the error warning(s) are displayed.
3. The number of errors against each step is displayed and the node for which unresolved errors are present are highlighted.
4. Click the error on the error console to view the steps and all the errors within the steps including the step name, step type, and relational inferences.
5. Navigate through the errors by clicking the caret icon at the top.

6. Resolve the errors by clicking the issue and fixing them in the respective node and property panel.