General
The Configurable PreProcessing Workflow in the Fusion Manage Module enables customization of how data is collected and prepared before entering the standard processing workflows. This feature extends the default behavior by allowing dynamic data enrichment, multi-source data collection, and flexible logic handling.
This article describes how to enable and configure the configurable PreProcessing Workflow and explains its structure and behavior.
For general module behavior, see: [CROSS-REFERENCE: Fusion Manage Source Module V2]
Purpose
By default, the Fusion Manage Module includes a static PreProcessing Workflow that supports standard use cases. However, some scenarios require additional flexibility, such as:
- Collecting data from multiple Fusion Manage workspaces
- Enriching items with data from external systems
- Extending metadata beyond default mappings
The configurable PreProcessing Workflow allows these scenarios to be implemented without requiring custom module extensions.
Enabling the PreProcessing Workflow
The configurable PreProcessing Workflow is disabled by default.
To enable it:
- Open Integrator Server
- Navigate to Workflow
- Select Settings
- Click Enable Preprocessing (green button)
Once enabled:
- PreProcessing Workflow configuration becomes available
- Default PreProcessing Workflows can be created
The default generated workflows replicate the behavior of the built-in static workflow.
Workflow Structure
The PreProcessing configuration follows the same structure as standard processing workflows and consists of:
- Transaction PreProcess Workflow
- Article PreProcess Workflow
- Structure PreProcess Workflow
- Document PreProcess Workflow
Each workflow type is responsible for preparing a specific part of the transaction.
Transaction PreProcess Workflow
The Transaction PreProcess Workflow defines which transaction modes are handled.
It acts as the entry point and routes processing to:
- Article workflows
- Structure workflows
- Document workflows
Configuration is based on the transaction’s modes property.
Article PreProcess Workflow
The Article PreProcess Workflow prepares item (article) data.
Default Behavior
- Retrieves item data from Fusion Manage
- Matches items using a predefined field
- Compares Fusion Manage data with source properties
- Sets article status based on existence
Configuration
The Get Item action can be configured to:
- Use a different workspace
- Compare against different fields
Extensibility
The workflow can be extended to:
- Retrieve additional metadata from Fusion Manage
- Fetch data from external systems
- Append data to the Article object
Structure PreProcess Workflow
The Structure PreProcess Workflow handles BOM (Bill of Materials) data and relationships.
Complexity
This workflow includes more advanced logic due to:
- Parent-child relationships
- Root vs. component distinctions
- Items existing only in Fusion Manage or only in the source system
Default Behavior
- Evaluates structure hierarchy
- Retrieves BOM data from Fusion Manage
- Processes each BOM instance
Key Action: Get Item BOM
- Retrieves BOM instances for the current structure item
- Executes a looped sub-workflow for each BOM instance
Extensibility
- Additional data can be retrieved from Fusion Manage or external systems
- BOM processing logic can be extended
Important Considerations
Changes to this workflow must be made carefully. Incorrect modifications may:
- Break BOM retrieval
- Affect status assignment
- Impact downstream processing workflows
Document PreProcess Workflow
The Document PreProcess Workflow prepares document-related data.
Default Behavior
- Retrieves item data from Fusion Manage
- Populates the DocumentArticle object
- Loads existing attachments from Fusion Manage
Differences from Article Workflow
- Includes attachment handling
- Focuses on document-specific data
Extensibility
- Additional metadata can be added
- External data sources can be integrated
Best Practices
- Start with the default generated workflow and modify incrementally
- Validate changes in Structure workflows carefully
- Ensure field mappings are consistent with Fusion Manage configuration
- Avoid breaking status logic used in downstream workflows
- Use external data enrichment only where necessary to limit complexity