• • Secondary action buttons for custom process layout/form pages. * *

Description

On the process layout or form page, you can customize the name, invisibility, and order of secondary action buttons (such as submit, cancel, etc.).

# Example of a typical scenario

• • • Scenario 1 * *: Modify the submit button copy
      For example: replace "Submit" with "Confirm Submission"
• • • Scenario 2 * *: Hide unwanted buttons
      Ex: Hide the "Save Draft" button under certain business scenarios
• • • Scene 3 * *: Adjust button order
      Example: Put "Cancel" button before "Submit"

Applicable Scenario

• Action buttons that require granular control over the form page
• Need to dynamically adjust button presentation based on business status
• Button styles that need to be unified across multiple forms

# Applicable Pages

• Business Flow Edit Form Page

# Development Ideas

Enhancements can often be broken down into three steps:

1. • • Identify which link to enhance * *

• Identify buttons that need to be modified, hidden or reordered

2. • • Select the appropriate extension event/hook * *

• Mobile: flow.edit.form.render.before
• Web: bpm.process.render.before

3. • • Access the extension point in the plugin and verify the behavior * *

• Call the api.customFormButtons(fn) method (web) or call the api.updateBottomBtnList() method (mobile)
• The label, action, hidden, etc. of the incoming callback function processing button

DEVELOPMENT WORKFLOW

1. • • Define button modification requirements * *

• Identify buttons that need to be modified, hidden or reordered

2. • • Write button custom logic * *

• Logic customization according to special needs

3. • • Configure the plugin * *

• Select the corresponding plugin in the custom plugin configuration

# Recommended entrance

Caution

1. • • Input parameter description * *: The button array in the callback function does not contain a "cancel" action button
2. • • Return value requirements * *: The returned button configuration must be customized based on the button entered in the parameter
3. • • Visibility controls * *: If a button does not exist in the return array, it will be hidden
4. • • Sequence control * *: The order of the buttons in the return array determines the display order of the buttons