Awesome Process: This serves as the name of the process definition, providing a clear identifier for the workflow.
This section displays both the version branch name and the current state of the published version. It offers insights into the active development state of the workflow.
When selected, this icon opens up additional options to enhance visibility and control over the various process definitions and their branches.
To commit alterations to the workflow, you can employ this designated action found within the version menu. Triggering the submission action prompts the appearance of a modal window, inviting you to provide a commit message for context.
This reassuring notification indicates that any modifications made to the workflow have been automatically saved, eliminating the need for manual user intervention. It ensures the safety of your work.
Utilize this icon to switch the current work mode from "Edit mode" to "Readonly." It empowers you to control the accessibility and editing permissions for the workflow.
The Misconfigurations Warnings represent a proactive alert system that ensures process configurations align with selected platforms. Dynamic platform-specific settings provide users with alerts guiding optimal navigation and UI design, integrated into the frontend interface to empower informed decision-making and enhance process configuration.
In the Node details tab, you can set the configuration details for a node.
When the connection with the database fails
when the connection with [Redis](../../../platform-overview/frameworks-and-standards/event-driven-architecture-frameworks/intro-to-redis) fails
| | Definition | Misconfigurations: process def name, subprocess parent process id value, start node condition missing. | | Node | When an outgoing node can’t be found (missing sequence etc). | | Gateway Evaluation |When the token can’t pass a gateway for any reason, possible causes:
Displayed when expiryTime
field is defined within the process definition. To set up an expiryTime
function, follow these steps
Client Name:
Client ID:
Item | Description | Price |
---|---|---|
This is displayed if it is a preferred client. They are eligible for special discounts!
This is displayed if the client has specific requests. Please review them carefully.
This is displayed if the client has an active contract with us.
By default all process data is reset when the process renderer component gets destroyed. Setting this to true will keep process data even if the viewport gets destroyed
| boolean | false | false | - | | isDraft | When true allows starting a process in draft state. \*Note that isDraft = true requires that processName be the **id** (number) of the process and NOT the name. | boolean | false | false | - | | legacyHttpVersion | Set this to `true` only for HTTP versions \< 2 in order for SSE to work properly. Can be omitted otherwise. | boolean | false | false | - | #### Data and actions Custom components will be hydrated with data through the \$data input observable which must be defined in the custom component class. ```typescript @Component({ selector: 'my-custom-component', templateUrl: './custom-component.component.html', styleUrls: ['./custom-component.component.scss'], }) export class CustomComponentComponent { @Input() data$: Observable