Custom Button

• Support to create custom buttons on objects, and you can set button display conditions, pre-verification, content to be filled in after clicking the button, and post-action.
• A maximum of 20 custom buttons can be set. If you want to increase the number of custom buttons, you need to purchase a resource pack for the number of custom buttons. Each resource pack contains 5 custom buttons, and you can purchase a maximum of 5 resource packs.

1. New Custom Button

• Button Type:

  • Business Button: used to operate data or do tripartite system data synchronization, etc.

  • UI Button: Jump to the interface, you can jump to custom components, custom pages or third-party pages, and you can fill in the interface information when you create a new edit page

• Button Position: that is, which page the button should be placed on.

  • The button position can be placed on the details page, single operation on the list page, batch operation on the list page, general operation on the list page, single operation on the related list page, new page, edit page

• Display Condition: What condition is met to display the button.

• Data Locked Status: After checking, the custom button will also be displayed in the data locked status

• If there is an operation to change the current data in the custom button execution action, it is recommended not to enable this setting (risky)

  • The relationship between this configuration and the button display condition is and

• What needs to be entered after clicking the button: configurable fields under the object or adding new fields (added new fields are only used when the button is clicked).

• There are three types of operations after the button is clicked: pre-verification, execution action, and after execution action is successful.

• Pre-verification: Custom functions can be executed.

  • Pre-verification is the data verification before the button action is executed. For example: when saving a sales order, check whether there is inventory, if the check is passed, continue to execute the save action, and if the check fails, the operation will be interrupted.
  • Pre-verification only supports business buttons
  • Pre-verification is to verify after entering the parameters

• Execution Actions: you can configure field changes and execute custom functions.

  • Field Changes

    • When the changed value of the field does not conform to the rules or an exception occurs, the field will not be changed.

      E.g:

      1. When the required field is changed to empty, the field will not be changed.

      2. When field A is changed to field B divided by field C (C value = 0), then field A will not be changed.

      3. The integer field A supports a maximum of 14 bits. If the calculation result exceeds 14 bits and cannot be assigned, the field A will not be changed.

      4. When there is some logic abnormality in the field, the field A will not be changed, and the CRM administrator will be notified to change the calculation formula.

• Custom Functions

  - Only one custom function can be set for one button.
  

  • After the action is executed successfully: CRM reminders and emails can be sent.

  • Who can use it: Set role function permissions.

2. Operations of Custom Button

• Disable: After the button is disabled, the page corresponding to the object will not be displayed.
• Delete: Disabled buttons can be deleted.