On the approval detail page, the "Approval Content" area displays the current approval content instance name, approval operation content, field changes, detail-object changes, and related information. When the default display cannot meet business requirements, you can enhance this area through the approval detail plugin.

Typical scenarios include:

• Customize the display of the instance name, operation description, field change block, or detail-object change block after rendering
• Add a custom display area below flow information or task information after rendering
• Mount a custom component on mobile before rendering to replace or extend the approval content card area
• Trigger linked actions such as "view edit records" or "view detail-object change records"

Applicable Scenarios

Use this when the approval content area needs a custom layout, supplementary descriptions, or display content strongly related to business data.

Applicable Pages

• Approval content area on the approval detail page

When To Enhance The Approval Content Area

• You need to change how modules such as the approval content title, operation information, field changes, or detail-object changes are displayed
• You need to append business-related custom actions or prompts below flow information or task information
• On mobile, you need to inject a custom component before content rendering, including approval cards on object detail pages
• You need to post-process the content after rendering based on getContentData or control parameters

Development Approach

1. Distinguish the Web "after render" entry point from the mobile "before render" entry point to avoid incorrect capability assumptions.
2. Register the event or Hook in the approval detail plugin, and customize the area through the api or return structure described in the reference documentation.
3. After publishing, verify behavior in live flows with different objects and different detail-object data volumes.

Development Flow

1. Confirm the client and timing

   • Web: after the content area is rendered (approval.content.render.after)
   • Mobile: before the content area is rendered (flow.approval.detail.approval.content.render.before)

2. Create an approval detail plugin

   Create an Approval Detail plugin in the admin console. Choose Web or mobile based on the target client, and align with the Web approval detail plugin documentation or mobile approval detail plugin documentation.

3. Select the event or Hook and implement the logic

   Web: Register the approval.content.render.after event in the plugin apply method, and use the api methods provided by the documentation, such as getContentData, setTitle, setFieldChange, setFlowCustomArea, and setTaskCustomArea.

   Mobile: Register the flow.approval.detail.approval.content.render.before Hook, and configure parameters such as customComponent (use the spelling in the reference documentation) and objectDetailCardEnable.

4. Debug and verify

   • Cover branches with and without detail objects, multiple field changes, and button-triggered configuration forms
   • Check data retrieval, style customization, and return values against the reference documentation

5. Publish and go live

   After development is complete, publish the plugin, enable it in the corresponding approval detail scenario, and verify the approval content area display on real flow tasks.

Recommended Entry Points

Web

• approval.content.render.after - after approval content is rendered

Mobile

• flow.approval.detail.approval.content.render.before - before approval content is rendered

Next Steps

• Approval opinion enhancement: Approval Opinion Enhancement
• Distinguish components and plugins: see the Component Guide and Plugin Guide