Page Comparison

Overview

Action buttons take common RIB CX  form actions and convert them into a Single Click. This makes for a speedy and simple process when managing Workflows.

Action buttons are shown on:

• Preview Email notifications. These can be clicked without needing to login to the project to progress the Workflow. The buttons are compatible on desktop emails as well as emails received via your mobile phone.
• Dashboards. They can trigger a form based on trigger configuration.

Types of Action Buttons

Buttons

These are simply buttons that can be added to the toolbar of an RIB CX form. They can be configured to be visible based on some pre-conditions.

When they are clicked, they can be configured to trigger some post actions.

Project Administrators can create action buttons for any new form type they create.

Select

Select Action buttons work in conjunction with a mapping Select field. It allows you to pick a value from a drop down that auto updates the RIB CX form addressing based on the mapping user field used in the configuration.

They are only displayed in a special type of List that can be accessed via a Dashboard.

Bulk Assign Select Status Action

You can also bulk assign a select status action button.

1. To assign a mapped user field value via the action button tick the forms you wish to bulk update.

2. Then select the Bulk Assign option.

3. Select the user field you wish to update and assign a value to it.

4. Click next.

5. This will update the forms you selected with the value you assigned to the mapped user field.

Basic Configuration

1. To add an action button go to the Form type you wish to add it to.

2. Edit the status config.

3. Then click on Add Action.

4. From here you can select the type of Action Control it is (Button or Select).

5. Give it a title.

6. Give it a Colour.

7. Give it an Icon.

8. And also set permissions. This will define who can see this Action buttons.

Configuration Pre-Conditions

Pre-conditions define when the Control appears. 

1. By default the first option will be the Status criteria.

2. From there you can define user field values that must be matched for the button to appear.

Additional Pre-Condition Options on Contract Admin forms

On CA forms you can configure Pre Conditions based on additional CA options.

Matches Assessment

"Matches Assessment" allows the status action button configuration of CA forms.

When configured, you can use it to hide/show buttons based on whether the assessment amount of a variation is equal to the total of the variation

If the amount is the same the system will dynamically update the list of status action buttons and display them when changing the assessment amount on a variation.

Currency and Number Field Criteria 

Currency and Number fields have been added to the status action button criteria list.

You can configure the same field more than once to support configuring numbers between two others.

"Between" Values for Contracts Admin Criteria

Configuring "in-between" values for Contracts Admin forms.

In between values allow you to configure for example:  An amount between two values eg: 25,000 < Amount < 50,000.

This has been implemented by enabling the user to select the same criteria twice when configuring the pre conditions

This is supported for all CA fields

Automatic Progression for Action Buttons

Automatically progress an action button after waiting a specific number of days in that status.

You can turn on this option under post conditions in action buttons and configure the number of days the form should wait in the specific status before progressing the form. This helps get around any bottlenecks where a workflow may be stuck due to non-action

Configuring Post Conditions 

Post conditions define what happens when the Control is clicked or selected. It has the options to 1. Change Status, 2. Change Action, 3. Change Info and 4. Change Due Date

Change Status : 

1. Change the status to something else.

2. And also Change the Document Addressing based on the options shown below.

Author

Returns the form back to the author of the form.

Contact User Field

1. Select Contact user field in the post Actions area

2. Pick the contact user field you wish to use.

Mapping User Fields

The action person can be set by using the configured mapping user field. 

Prerequisites - You must have an action button configured for the first status of the form

You must have this button configured to update the action based on a mapping user field.

When creating a new form of this type the action area will be greyed.

You can still set the info users as required.

When creating the new form you simply set the mapping user field value and click on the action button.

This will submit the form and automatically update the action person on the form based on the mapping user field configuration

Update available Action Buttons based on user field selections in real time

You can configure one or more user field criteria against another user field, in order to customise which action buttons should appear when user selects it.

A good use case is where you configure a mapped user field against an action button. When that user is selected the action button will appear in real time on the form.

This functionality enables users with dynamic action buttons that automatically update based on their selections. It ensures seamless task management and enhanced productivity. By automatically refreshing action buttons based on specific field selections, users experience an interface tailored to their immediate needs.

Step 1: In the form, make sure  you have a 'Select' user field where user can select a contact. Toggle on 'Mapping user field' . 

In this example we're using an RFI form and adding a user field with description 'Response Required By'

Step 2 : Add mapped user contacts in options of this user field : 

Step 3 : Once user field is configured, go to 'General' tab in the form → Click Status → Status List → Action button you'd like to configure against this user field

Step 4: Configure button's If/then logic by using 'Condition' and 'Action'  

In this example, we're sayin, if condition is that form is in draft stage and 'Response Required By' Select Option is 'QA Team' 

then action should be to Change Status to Quality Team, and Change Action of Mapping User field to 'Response Required By'

That completes the configuration! 

As a user: When you go to that example RFI form and select 'QA Team' it will show 'Quality Team' button underneath straight away in real time

Change Status to Return

Returns the form to the previous Action person

To find out who was the previous action person, the system looks at history or comments to see who was the previous action person.

If there is no history or comments by a different previous collaborator then the system keeps the current status

In the example below for a Defect form : 

Usman creates a document on 14th Feb (Status 1: For Review)

Barry receives the form from Usman to action ( Status 2: Ready to inspect)

When Barry presses the 'Fail' action button, form returns back to the previous status (Status 1: For Review)

Change Action to Return

When an action button is configured change action user to Return, the system will return the document to the previous action person.

If multiple action persons are allowed, then it can allow For example : 

Lets say Bob, John and Jane are the action persons. 

Then status is changed for Bill to action. Lets call this Status 1 (Lets assume Status 1 has Action = Return)

When you press the Action button from Status 1, it will return the form for Bob, John and Jane to action

User(s)

You can configure status action buttons to directly change addressing without requiring a mapping field.

When User(s) is selected you can configure a group, a user or multiple users.

Requires Comment Option

With this option turned on you can force a user to enter a comment prior to clicking on the Status Action button.

This applies to the Response Window

Comments Required can also be used when responding to email.

On Dashboards, there will be a pop up alerting you that a comment is required :

Change Info User

You can also configure an action button to update the info user of a form. 

You can update the info using

• Contact user field
• Mapping user field
• Or a specific user

Change Due Date

Similar to the above you can also configure the action button to update the due date of a form and move it forward by however many days as desired

History Log for Action Button Changes

Changes to Action buttons are logged and can be viewed via the history button on the action button.

Re-ordering / Re-organizing buttons

You have the ability to drag and drop to reorder action buttons. The new order will be automatically saved and reflected on those forms : 

Info

Skip Workflow Step (SKIP) In the VLA form, if you are using the 'Skip Workflow Step (SKIP)' workflow, do not use it in a status action button. Image RemovedSkip Workflow only works on Classic form workflows. It is not supported for Modern form workflows, therefore if used it will continue to the next step and will not skip any steps.  An error will appear in the history of the form.  The Skip workflow button means skip the current status, and go to the next status step in order. And then find the applicable button of the same name and trigger that instead. Skip Workflow Step (SKIP) is only applicable to Classic Form workflows. Therefore it is not supported for action buttons (which is a Modern Form function). Due to that, if you calibrate it with a mapped field, you will get an error. If you leave the mapping field empty in this case it should all work as expected.the workflow.  Image Added