• • In the Approval Detail page, the "Approval content" area is used to display the name of the approval content instance, the content of the approval operation, field changes, changes from the object, etc. This area can be enhanced with the Approval Details plugin when the default display fails to meet business demands. * *

Typical scenarios include:

• After rendering, customize the instance name, action description, field/change the presentation of the block from the object
• Mount custom components on mobile before rendering to replace or expand the approved content card area
• Need to trigger linkage behavior such as "View edit history" "View change history from object"

Applicable scenarios

Applicable to "customized layout, supplementary explanation, or display strongly related to business data required for approval of content area";

# Applicable Pages

• Approval content area in the Approval Detail page

# When is it appropriate to do an approval content area enhancement

• Need to override the presentation of modules such as approval content titles, action information, field changes, changes from object, etc.
• Custom components need to be injected on the mobile side before the content is rendered (including scenarios such as object details page approval cards)
• Requires secondary processing based on getContentData/control parameters after content rendering is completed

# Development Ideas

1. Differentiate between Web "after rendering" and mobile "before rendering" access points to avoid mixing capability assumptions
2. Register the event/hook in the approval details plugin and complete the customization using api or return structure according to the reference manual
3. After publishing, verify the performance of different objects and different amounts of data from objects in the online process

DEVELOPMENT WORKFLOW

1. Clarify the terminal and timing

• Web: After content area rendering * * * (approval.content.render.after)
• Mobile: content area rendering * * before * * (flow.approval.detail.approval.content.render.before)

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.content.render.after in the plugin apply, use the api method provided in the document (such as getContentData, setTitle, setFieldChange, etc.) within the callback.
• • Mobile * *: Register Hook flow.approval.detail.approval.content.render.before, configure customComponent (document spelling is subject to reference manual) and objectDetailCardEnable and other parameters.

4. Joint Coordination and Validation

• Override branches with/without from objects, multi-field changes, button-triggered configuration forms, etc.
• Check data acquisition, style customization and return values against the reference manual

5. Launch and go-live

After the development is completed, the plug-in is released, enabled in the corresponding approval detail scenario, and returned to the approval content area for display on the real process tasks.

# Recommended entrance

Next

• Enhanced Approval Comments: Enhanced Approval Comments
• Distinguish between components and plug-ins: View the Components Guide vs. Plug-ins Guide