The approval workflow to-do page can be extended from two dimensions: list page and card page (Web only). When the default behavior does not meet business requirements, mount Web events or mobile Hooks in the approval to-do plugin to enhance it.

Typical scenarios include:

• Web: Get the object ApiName after the list or card is rendered, and customize button styles or behavior for batch approver changes, batch approvals, and similar actions
• Mobile: Customize buttons and labels in each area of the to-do list, or intercept before batch operations and card button clicks

Applicable scenarios

The mapping between list-level capabilities and mobile Hooks is described in "Recommended Entry Points" below. Cards (Web) are based on flowTodo.approval.card.render.after. Mobile Hooks are mostly named by list page area. For customization related to single-row display, check the list Hooks and reference manual together. Specific parameters are subject to the reference manual.

Applicable Pages

• Approval workflow to-do page (Web / mobile)

When should I use approval workflow to-do feature enhancements?

If you encounter any of the following requirements, the capabilities on this page are usually a good fit:

• You need to control batch button display or style based on object or filter conditions
• Mobile needs to adjust labels and buttons in the top-right, bottom, or batch operation areas of the list
• Mobile needs to insert validation or custom prompts before batch operations or button clicks
• Web: You need to customize batch-related capabilities by task after the list or card is rendered

Development Approach

Approval workflow to-do feature enhancements can usually be understood in three steps:

1. Identify the terminal (Web / mobile) and access point (after list rendering, after card rendering, before each button is rendered, or before a click)
2. Register the event or Hook in the approval to-do plugin, then modify data or return values in the callback according to the reference manual
3. Release the plugin and jointly debug/verify paths such as filters and batch operations on the to-do list/card paths

Development Workflow

1. Read the Web approval to-do plugin description and mobile approval to-do plugin description.

2. Create a to-do-related JS plugin in the admin console. The plugin type is subject to the actual admin options.

3. Register Web events or mobile Hooks according to the "Recommended Entry Points" below and implement the business logic.

4. Joint debugging: switch objects, list/card views, filters, batch operations, batch operation paths, and button interception paths.

5. Release the plugin and configure it in the process/to-do advanced configuration.

Recommended Entry Points

Web

• flowTodo.approval.list.render.after - After the approval to-do list is rendered
• flowTodo.approval.card.render.after - After the approval to-do card is rendered

Mobile

• flow.remind.list.right.top.btn.render.before - Before the top-right button of the to-do list is rendered
• flow.remind.list.batch.btn.render.before - Before the bottom action button of the to-do list is rendered
• flow.remind.list.batch.option.click.before - Before a batch operation button is clicked
• flow.remind.list.batch.option.render.before - Before a batch operation button is rendered

Next Steps

• Business Flow To-Do Feature Enhancements