• • Customize the action buttons on the Business Flow task card. * *

Description

Before the task card buttons are rendered, customize the exposed buttons, more buttons, and buttons in the abnormal state, including button name, order, and invisible controls.

# Example of a typical scenario

• • • Scenario 1 * *: Approval node custom consent/reject button
      Example: Change the text of the "Agree" button to "Pass and send notification"
• • • Scenario 2 * *: hide button based on approver
      Ex: Hide all action buttons when the current user is not a approver
• • • Scenario 3 * *: Exception Task Special Button Handling
      Example: Display two custom buttons "Retry" and "Ignore" in an abnormal state

Applicable Scenario

• Requires fine-grained control over the presentation and interaction of card-level buttons
• Button presentation in different task types or statuses that need to be handled
• The button needs to be hidden according to the user's permissions

# Applicable Pages

• Object Details Page - Task Card Area

# Development Ideas

Enhancements can often be broken down into three steps:

1. • • Identify which link to enhance * *

• Determine if you want to modify the button copy, adjust the button order, or control the button to be invisible
• Identify the types of buttons that need to be customized (exposed/more/abnormal)

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

• Mobile: flow.bpm.detailcard.item.bottombtn.render.before
• Web: bpm.detailCard.render.before

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

• Get button data under the current task
• Filter and modify target buttons based on taskId, state, etc.

DEVELOPMENT WORKFLOW

1. • • Determine button range * *

• Identify the types of buttons that need to be customized (exposed/more/abnormal)
• Specific fields explicitly modified

2. • • Select an event * *

• Mobile: flow.bpm.detailcard.item.bottombtn.render.before
• Web: bpm.detailCard.render.before

3. • • Write custom logic * *

• Logic customization according to special needs

4. • • Configuration to Process * *

• Select the corresponding plugin in the custom plugin configuration

# Recommended entrance

Caution

1. • • Do not add new buttons * *: You can only delete, change, or change the data on the original buttons
2. • • Keep the data structure intact * *: The original data structure must be kept intact
3. • • Permissions * *: The final appearance of the button may also be affected by permissions and task status