Structured run records
Capture the fields that matter for troubleshooting and reporting.
Data Logger component
Use Data Logger when the business needs visibility into what moved through a workflow.
Write selected workflow data to a datasource for troubleshooting, reporting, and audit workflows.
What this component unlocks
Data Logger gives teams a purpose-built way to capture execution data without turning every flow into custom logging code. It is useful for audit, reporting, QA, and operational diagnostics in customer-owned environments.
Capture the fields that matter for troubleshooting and reporting.
Preserve selected input and output values alongside workflow execution history.
Feed downstream reporting, dashboards, or support workflows.
Use cases
These examples show how this component can become part of production workflows across customer-owned systems and environments.
Use Data Logger as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
Use Data Logger as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
Use Data Logger as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
Use Data Logger as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
Use Data Logger as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
Use Data Logger as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
Configuration surface
The exact fields can vary by deployment and product version, but each page gives customers a clear view of the component's intended role.
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Implementation notes
Components should be easy for builders to configure and easy for operators to understand after the workflow is live.
This component detail page is a CXFabric website template and can be expanded as formal documentation grows.
Log only the data needed.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Mask or exclude sensitive values.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Agree on retention and destination before deployment.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Workflow patterns
These are concept patterns that can be adapted to a customer's systems, policies, credentials, and deployment model.
Start with an event, use Data Logger, then route the result to CRM, ticketing, or a customer-owned system.
Add validation, human approval, and logging around the component before downstream actions execute.
Deploy the component inside a customer-owned environment with credentials and logs governed by the customer.
Combine the component with packaged connectors or custom APIs when the process needs reusable system logic.
Component planning
We can scope the workflow, component configuration, credentials, deployment model, and handoff path before buildout begins.