We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Add method getWorkflowInstance and getWorkflowInstances
getWorkflowInstance
getWorkflowInstances
In Camunda BPM you can query instances through REST API (https://docs.camunda.org/manual/7.9/reference/rest/process-instance/get/ and https://docs.camunda.org/manual/7.9/reference/rest/process-instance/get-query/), we should do it with Zeebe as well through Elasticsearch exporter (by default)
In Elasticsearch, we have zeebe-record-workflow-instance index. We should query this index.
zeebe-record-workflow-instance
Providing feature parity between Camunda BPM and Zeebe in order to make the transition easier.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
🚀 Feature Proposal
Add method
getWorkflowInstance
andgetWorkflowInstances
Motivation
In Camunda BPM you can query instances through REST API (https://docs.camunda.org/manual/7.9/reference/rest/process-instance/get/ and https://docs.camunda.org/manual/7.9/reference/rest/process-instance/get-query/), we should do it with Zeebe as well through Elasticsearch exporter (by default)
Example
In Elasticsearch, we have
zeebe-record-workflow-instance
index. We should query this index.Pitch
Providing feature parity between Camunda BPM and Zeebe in order to make the transition easier.
The text was updated successfully, but these errors were encountered: