Use a Display Page step in a ReadiNow Process when you want to show a form or record to a user—for viewing, editing, or data input—without automatically creating or updating a record.
Display Page Properties
| Property | Description |
|---|---|
Name | The name of the block that will appear on the process builder screen. |
Description | Helpful description as to what is the purpose of the step. |
Run Condition | The condition by which the Step will run. For example if a button named ‘Approve’ was clicked in from a different block then the step will be run. |
| Wait for Next Task | A property that controls whether the user leaves the Process screen after completion of the task. When selected to off, a process user who is in the process runner completing a task, upon completion of the task, and if they have no other tasks to complete at this time, will be told they are finished and will leave the process runner and be redirected to the record page the work related to. When selected to on, the user will be left on the Process runner upon completion of their task even if they have no further tasks to complete at this time in the Process, and see a waiting modal until it is determined there is a task for them, or the Process ends. |
Configuration | |
Page Type | Choose between displaying the page in a Long form or a Multistep form. |
Page | Select the form page to present to the user. |
Select open form mode |
|
Step Inputs | |
Entity Resource (page name) |
In other words, Entity Resource links the step input to a valid object instance that the page will work with at runtime, aligning it with the process context and data structure. |
Assign task | |
Step assigned to Person | The person to whom the Step is assigned. If no value is specified then ownership of the step goes to the initiating person (who started the process). |
Step status | |
Initial Status | Sets the status value at the start of the step. As the step progresses and is executed then the next status to be adopted will be from the “Status” property below. |
Action buttons | |
Button text | Defines the label that appears on an action button to be displayed during that step. |
Button style |
|
Status | Set the status value after the step is completed. |
Action Dialog | A modal form that appears when a configured action button is clicked in the Process Runner. It can be of two types: Information or Confirmation. |
| Disable logic | Optional expressions that control whether the step’s action button is enabled. If any expression returns a message, the button is disabled and the message appears as a tooltip. All conditions must return null for the button to be enabled.Tooltip shown: Status must be Approved Considerations
|
Action Dialog Properties
Action Dialogs are configured within the Step Action properties in the Process Builder. You can select the dialog type, style (e.g., Default, Info, Success, Warning, Danger), and other properties like button text and inputs. When configured, these dialogs help guide user interaction and ensure confirmation before performing critical actions.
Below: The configuration screen of an Action Dialog
Below: Action Dialog screen result when run by the user
| Property | Description |
|---|---|
Type |
|
Style | Choose between Default, Danger, Warning, Success or Info to show a relevant icon for the style. |
Title | The title you want to appear at the top of the dialog box/screen |
Text expression | The full text that you want to show the users and explain what the purpose of the dialog box is or what to do next. |
Primary button text | The text here becomes the label on the primary button such as “Cancel”, “Complete”, “Decline” etc… |
Inputs | |
Name | The variable name |
Type | Select from a list of RN field types such as Multiline String, String, Date, Date/Time, Decimal, Number, Time, Yes/No, Choice Field, Choice Field List, Record, Record List. |
Mandatory | Indicate whether the field is mandatory for the user or not. |
Delete (icon) | Removes the field. |
+ New Input | Adds a new field. |
Note: The inputs section allows you to create variables of different data types and present them on the action dialog so that users can return back required information and user input.