¶ Storage Domain
The Storage domain in Fuse governs the management, referencing, and runtime injection of content resources — such as files, blobs, URLs, and dynamically generated outputs — across workflows, orchestration steps, and domains.
Storage is treated as an active, governed content layer that supports secure file handling, runtime resource attachment, and dynamic content lifecycle management.
Storage in Fuse manages:
- Physical file resources (documents, attachments, assets)
- Blob storage objects tied to workflows, approvals, or orchestration outputs
- URL resources referencing internal or external content
- Runtime-injected artifacts (e.g., PDFs, downloads, task outputs)
- Access-scoped resource usage based on token context and domain policies
- Metadata tagging, versioning, and retention policies for content
Storage enables content to flow securely and compliantly through workflows, UI panels, AI interactions, and messaging systems.
- Resource Registry and Catalogs — Manage categorized resources across domains and workflows
- Scoped Resource Access — Enforce runtime visibility based on identity, token, role, and workflow state
- Dynamic Resource Injection — Attach files or blobs during approvals, tasks, or orchestration steps
- Storage Abstraction — Handle local file systems, cloud storage, or federated storage systems seamlessly
- Caching and Version Control — Manage resource lifecycles, update tracking, and runtime versions
- Secure Attachments — Encrypt and control file access based on security scopes and policies
- External Storage Integration — Connect to external blob providers (AWS S3, Azure Blob, Google Cloud Storage) through storage connectors
Layer |
Storage Role |
Integration |
Normalize inbound files, documents, or storage events from external systems |
Automation |
Inject generated files or artifacts into downstream workflow steps |
Orchestration |
Attach or reference content resources during approvals, user tasks, and AI processing |
Interoperability |
Govern storage usage and access through runtime policies, token scopes, and auditing |
Storage transforms content into governed, orchestrated assets inside Fuse’s domain-driven model.
- A refund approval task dynamically attaches jurisdiction-specific document templates for reviewers to download and verify.
- A scheduled orchestration exports a compliance report PDF and injects it into a regulated user’s workspace inbox.
- A resource injection step selects a URL resource dynamically based on runtime context, role, and current environment.
¶ Extending the Storage Domain
You can extend this domain using:
- Workflow Domain — Attach content during flow steps, approvals, and human tasks
- UI Domain — Render resources inside panels, dashboards, and user interfaces
- Visibility Domain — Audit and trace resource access and usage across orchestrations
- Glossary — Learn about resource injection, scoped attachments, and secure storage orchestration