You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Introduction

Run Process enables one to start a process instance from the UI.

If you would like to start a process instance by using an existing form record, add the additional parameter "recordId" to the menu itself and specify the record ID to this parameter.


Process Version

New Process Instance will start based on the latest process version of the current published App version.

Run Process Properties

Configure Run Process

Figure 1: Run Process Properties

NameDescription
Custom ID

Item link slug. Optional field.

Unique field

Value defined here must be unique to the rest of the UI Menus as the first matching name will be called upon.

LabelMenu label. Mandatory field.
ProcessProcess to start. Mandatory field.
Run process without confirmation screen?If checked, user will be prompted before proceeding to start the process instance.
Show in popup dialog?If checked, user will be presented a popup dialog to run the process instance.
Submit Button LabelLabel to be displayed on the submit button.

Redirection

Figure 2: Run Process Properties - Redirection

NameDescription
Message shown after process startedMessage shown after process started in text.
Action to Perform After Form Saved
  • Redirection
  • Reload Page
URL redirect after process startedWhen the user clicks on "Complete" or "Save As Draft" form button, Joget will redirect to this URL value if the activity/form is the first activity in the  process flow.

Redirect Target on Form Submission

  • Top Window
  • Parent Window
  • Current Window
Field ID for URL Redirect Value PassoverField ID of one of the form element in the preceding form to retrieve the value from.
Field Value Passover Method
  • Append to URL
  • As URL Request Parameter
Request Parameter NameParameter name to be added to the URL redirect.

Advanced

Figure 3: Run Process Properties - Advanced

NameDescription
UI Key NameIf defined, the corresponding form element defined here will be populated with the UI key value.


Performance & Offline

Figure 4: Performance & Offline

Cache Settings

Name

Description

Scope

Caching options are:

  • None: No caching.
  • Application: Cache content by application where all users will see the same content.
  • User: Cache by username.
Duration (s)Duration in seconds to cache content, defaults to 20 seconds if applicable.

Read more at Performance Improvement with UI Caching.

PWA Offline Settings

Note: PWA Offline support is dependent on the theme used.

Name

Description

Enable cache for offline supportEnable caching for offline support, usually set for use on mobile browsers.

Read Progressive Web Application (PWA) for more information.






  • No labels