• • In the approval workflow scenario, enhance the interaction and presentation related to "pre-add-signing" (such as the default pre-add-signing mode of the pre-add-signing pop-up window, etc.). * *

Typical scenarios include:

• After the web-side pop-up window is rendered, specify that parallel/serial modes are selected by default
• The mobile terminal sets the default signature mode in the pre-add-signing scenario

Applicable scenarios

Applicable to display and behavior customization such as "default signature mode" in the front pop-up window; specific parameters are subject to the reference manual.

# Applicable Pages

• Pre-sign pop-up

# When is it appropriate to add signatures before strengthening

If you encounter any of these needs, it's usually a good idea to prioritize your enhancement:

• The default selection mode needs to be signed before adjustment (setDefaultSequence, etc., see the reference manual)

# Development Ideas

The pre-add-signature enhancement can usually be broken down into three steps:

1. Make it clear whether you want to enhance the web or mobile
2. Select the appropriate Extended Event/Hook
3. Access the extension point in the plugin and verify the behavior

DEVELOPMENT WORKFLOW

1. Identify scenarios and access points

• Web: before pop-up rendering * * after * * (approval.preAddSign.render.after)
• Mobile: Approval action execution * * before * * (flow.approval.action.before), you can set the default signature mode in the previous signature scenario

2. Create approval details plugin

Create a * * Approval Details * * type plugin in the background (Web/Mobile according to the actual terminal selection), and align it with the Web Approval Details Plugin Description ] or Mobile Approval Details Plugin Description ] documents.

3. Select events or hooks and write logic

• • Web-side * *: Register the event approval.preAddSign.render.after in the plugin apply, use the api method provided in the document (such as setDefaultSequence) within the callback.
• • Mobile * *: Register Hook flow.approval.action.before, use pluginContext.setDefaultSequence(true) to set the default signature mode (true means concurrent, false means concurrent).

4. Joint Coordination and Validation

• Web-side: pop-up window opens multiple times before coordination, paths such as switching modes, etc.
• Mobile terminal: sign-off operation before joint adjustment, display effect of different sign-off modes

5. Launch and go-live

After the development is completed, the plug-in is released, enabled in the corresponding approval detail scenario, and the path is signed before returning to the real process task.

# Recommended entrance

Next

• Consent Enhancement (postscript)
• Distinguish between components and plug-ins: View the Components Guide vs. Plug-ins Guide