Integrate enterprise approval workflows
Use DAM as the source of truth for business objects and states, and the enterprise approval platform as the workflow orchestrator. Connect them through an extension service or event adapter.
Typical workflow
- A user submits a standard, asset, or catalog publication request in DAM. Save its snapshot and request ID.
- Send applicant, object IDs, change summary, risk level, and callback address to the approval platform.
- Verify callback signatures, process decisions idempotently, and invoke DAM publication, rejection, or withdrawal.
- Read back DAM state, revision, and audit records for portal display.
Objects and states
| Object | Request content | Action after approval |
|---|---|---|
| Standard | Code, name, type, definition, revision, values | Publish standard or revision |
| Asset | Catalog, object, owner, classification, description | Publish or change ownership |
| Catalog/report | Location, scope, fields, visibility | Publish catalog or report |
Store workflow and DAM states separately. Suggested adapter states are DRAFT, SUBMITTED, APPROVING, APPROVED, PUBLISHING, PUBLISHED, REJECTED, and FAILED. Approval permits transition to PUBLISHING; only confirmed DAM success permits PUBLISHED.
Interface design
Retain a complete snapshot or change patch. Callbacks should contain requestId, objectType, objectId, version, decision, operator, and timestamp. Use requestId + version for adapter idempotency. After signature verification, log reception and update asynchronously. Do not write directly to DAM databases. Close publication only after DAM confirms success.
Verify deployment-specific publication paths, permissions, and enums against Swagger and UI operations. See standards and assets.