Add flow type to the execution response #982
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
wso2/product-is#25509
This pull request introduces support for handling and exposing the flow type in the flow execution API. The main changes include adding the
flowTypeproperty to the flow execution response model, ensuring it is included in API responses and error DTOs, and updating related utility methods and OpenAPI documentation.Flow Execution Response Model Updates
flowTypeproperty to theFlowExecutionResponseclass, including its getter/setter, builder method, and validation annotations. Updatedequals,hashCode, andtoStringmethods to account forflowType. [1] [2] [3] [4]flowTypeproperty in the response object.Error Handling Enhancements
FlowExecutionErrorDTOclass extendingErrorDTO, with aflowTypeproperty for error responses.Utils.javato includeflowTypewhen constructing error DTOs and API error responses, and propagatedflowTypefrom exceptions. [1] [2] [3] [4] [5]API Documentation
flow-execution.yaml) to requireflowTypein the flow execution response schema and documented its purpose.