Skip to main content

Custom Action

Feature Overview​

Custom buttons allow you to set the actions when clicking a record or clicking a custom button, and there are 2 types:

  • When clicking a record

    Clicking a record can open the record detail page, or open the link saved in the field, or without any actions.

  • When clicking a custom button

    • Single data source: When a button is clicked in a record, it is possible to have a pop-up window for the operator to fill in the specified fields, or to execute a workflow after clicking the button.

    • Multiple data sources: Check multiple records in the grid view and click the button, it gets the checked multiple data and executes the workflow once.

Actions after clicking a record​

  • Open the detail page of the record.

  • Open the link. If there is a text field saving a link, you can open this link directly when you click the record.

  • None. No actions after clicking.

Introduction to Custom Button​

Entrance to Set Custom Button​

Custom actions can be set in both worksheets and views.

  • Set Custom Action in Worksheet

  • Set Custom Action in View

Buttons created in the view are automatically synchronized to the worksheet; on the button management page in the worksheet, you can set in which views the buttons are available.

Example 1 : Fill in a specified field after clicking the button​

When there are too many fields in a form, you can fill in the fields with a button, which saves time by quickly focusing on the target fields.

Example: In the "Intern" view, add a "Pass" button, so that the operator can click the button to fill in the time and status.

Button Configuration

1. Set the button name​

There is no character limit for a button name. 4 characters or less is recommended.

2. Set the icon and description​

A button description tells what the button does, and the description appears when the operator mouses over the button.

3. Set actions​

After clicking the button, you can set whether to execute the workflow, or to have a pop-up window to fill in the fields in the form.

Actually, you can also set a third action, that is to execute the workflow after filling in the fields

In this example, it is set to fill in the field, that is, to fill in the pass date after clicking the button.

4. If to fill in a field​

  • Object: whether to fill in the fields in the current record, or to fill in the fields in the associated record (must be a single association).

  • Content: Fill in fields or create a new associated record.

There are four possible cases:

  1. Fill in the specified fields in the current record. You can set default values, such as dynamic default values for member and date fields (the filler or the filling date).

  2. Create a new associated record for the current record.

    After clicking the button, there is a pop-up window for creating the associated record.

  3. Fill in the fields in the associated record with the current record.

    After clicking the button, there is a pop-up window showing the fields in the associated record. For example, a contact is associated with a company record, and in the contact record, clicking the button can open a pop-up window to edit the fields in the company record.

  4. Add a new associated record for the associated record with the current record.

Configuration of the filled field​

You can set the properties of the fields displayed in the popup, read-only, editable, or required, etc.

You can also set the default value of the field, fixed default value, or dynamic value.

If you are filling in the fields in the associated record, the default values can be set to the field values in the current record.

5. Secondary validation and notes​

You can set a second confirmation required after clicking the button to remind the operator what to do next, whether to continue or not, and you can also add a note.

Effect: The user can edit the content of the field only after clicking the button and making a secondary confirmation.

Notes Template​

You can preset frequently used comments as note templates. If unchecked, it allows users to input freely.

Template:

Get the fills through a workflow​

The filled-in notes can be obtained in the workflow, as shown below.

6. Verify login password​

If checked, the user needs to enter the login password to continue the operation.

7. Enable the button​

  • [Always]: The button is always available.

  • [Conditional]: The button is available only when the set conditions are met, otherwise the button is grey and unavailable.

For example, the [Pass] button is only available on the intern page.

8. Hide the button​

The button cannot be clicked if the conditions are not met. If you need to hide it, you can check [Hide buttons that are not available] in the view.

9. Effect​

Example 2. Execute the workflow after clicking the button​

For example, in the "Intern" view, add the "Pass" button and click it to trigger the workflow to automatically update the employee's status to "Regular" and the date to be updated to the current date.

1. Set the button name/description​

To distinguish it from the button in Example 1, the button is named [Pass 2] here.

2. Execute the workflow​

When executing a workflow, you need to determine whether the data source for the workflow is a single record or multiple records.

In this example, clicking the [Pass] button is for a specific employee, so it is a single record.

Scenarios for multiple records:

  • Dispatch List: select multiple to-be-dispatched list details to generate a single dispatch order.

  • Purchase List: Select multiple records in the to-be-purchased list, click the button to execute the workflow to generate a purchase order, and associate the currently selected records with the purchase order.

3. Other settings​

Details about secondary confirmation, verifying login password, enabling buttons, icons and colors, etc., are as described in Example 1.

4. Configure the workflow​

Click the button to open the workflow configuration page, modify the status and date fields with the [Update Records] node.

5. Publish the workflow​

After the configuration is complete, publish the workflow,

6. Test​

Open an intern record and click the button to check if the field contents will be automatically modified.

Example 3: Selecting multiple records and execute the workflow once​

Scenario 1: Check multiple detail items to be reimbursed to automatically generate a reimbursement order.

Scenario 2: In ERP, check multiple orders to merge and generate a delivery order.

Scenario 3: In manufacturing, check multiple orders to merge and generate a production planner.

Take Scenario 1 as an example.

1. Add the button for batch actions​

Here it involves multiple data processing, so you need to add a button for batch actions.

2. Select multiple records as data source​

Select multiple records as data source so that the workflow will be triggered once after clicking the button. The trigger node is the multiple records that are checked.

3. Configure the workflow​

  • Add reimbursement request

    Select the trigger node for [Reimbursement Details].

  • After adding a new reimbursement request, it automatically opens the reimbursement details page through the [Interface Push] node and completes it.

Effect:

How to get the trigger of a button-triggered workflow

Select [System] - [Trigger].

Actions on the record detail page/Actions for batch operations​

You can set whether or not the button is available on the record details page and for batch operations.

  • Record details page

    The button is available when you click a record and open the record details page. It is also available when one record is checked in the list.

  • Batch operations

    You can set whether the button is available when you batch check multiple records in the grid view.

As configured in the figure below, the [Pass] button is available on the details page and for batch operations, and the [Leave] button is only available on the details page.

Effect:

Have questions about this article？ Send us feedback