Skip to main content

Asset Management Integrations

Integration classification

ContextClassificationEvidence-backed boundary
Identity and tenantClaims/header contextSupplies actor and tenant scope; service accepts authenticated context but endpoints are not authorization-required.
EmployeeIdentifier-onlyUser/labor references are stored; existence and ownership are not synchronously verified.
Gateway/UIGateway composition and frontendCompatibility workspace/assets routes serve existing UI; dashboards also request direct inventory.
DocumentSynchronousContent is stored/downloaded by Document Service; Asset keeps references.
WorkflowOptional synchronous plus callbackNew requests may start approval; managed requests await terminal callback.
NotificationAsynchronousLifecycle outbox events are recognized by Notification Service.
MessagingAsynchronousTransactional outbox and hosted relay publish six lifecycle event types.
Exit clearanceSynchronous readOpen-assets and clearance-status projections support an external exit/HR gate.
ReportingFrontend-only derivationOperations metrics are computed from list/workspace rows.
Procurement, payroll, financeNot implementedNo source-backed calls, identifiers, or events.

Source References

  • microservices/src/asset-service/Program.cs
  • microservices/src/asset-service/Application/WorkflowIntegration.cs
  • microservices/src/asset-service/Infrastructure/AssetDocumentGateway.cs