Depends On
Requires support for the proposed Extensible Activity Output Converters capability within Elsa Core.
Summary
If output converter support is introduced in Elsa Core, workflow designers should be able to configure output conversions directly within Elsa Studio when binding activity outputs to workflow variables.
Problem
Currently, activity outputs can be bound to variables, but there is no way to optionally transform the output value during the binding process.
This means workflow authors must either:
- Use custom activities.
- Add transformation steps.
- Handle conversion logic manually later in the workflow.
Proposed Enhancement
Extend the Output configuration experience to support optional converter selection.
Conceptual example:
Output:
Result
|
+--> Variable: QueryResults
+--> Converter: DataSetToRecordCollection
Desired Behaviour
When converter support is available:
- Converter selection should remain optional.
- Existing workflows should continue functioning unchanged.
- Available converters should be discoverable from registered converter providers.
- Converter configuration should integrate naturally into the existing Output experience.
Additional Notes
While investigating this feature, it appears that the Output tab may not currently expose the same extensibility mechanisms used elsewhere through Field Extensions.
If output converter support is approved, this may provide a good opportunity to introduce an extension point for output binding configuration.
Depends On
Requires support for the proposed Extensible Activity Output Converters capability within Elsa Core.
Summary
If output converter support is introduced in Elsa Core, workflow designers should be able to configure output conversions directly within Elsa Studio when binding activity outputs to workflow variables.
Problem
Currently, activity outputs can be bound to variables, but there is no way to optionally transform the output value during the binding process.
This means workflow authors must either:
Proposed Enhancement
Extend the Output configuration experience to support optional converter selection.
Conceptual example:
Desired Behaviour
When converter support is available:
Additional Notes
While investigating this feature, it appears that the Output tab may not currently expose the same extensibility mechanisms used elsewhere through Field Extensions.
If output converter support is approved, this may provide a good opportunity to introduce an extension point for output binding configuration.