-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BPM Abstraction #5
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this change cause the BPM engine to rely on the abstraction layer to fulfill the core BPM features? Are there any suggestions to overcome the mentioned performance implications?
We are not planning to change any core BPM engine features, abstraction layer is only on the rest layer. We will parse the default BPM request/response and provide request/response as in the API Spec designed (link in rfc), then make our web and api to work with these API spec. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me
tags: [] | ||
responses: {} | ||
operationId: get-process-instance-id-instances | ||
/filters/tasks: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
endpoint has modified to /task-filters
in the current implementation.
For better readability : https://github.com/sumesh-aot/forms-flow-ai-rfcs/blob/bpm/rfcs/bpm_abstraction.md