-
Notifications
You must be signed in to change notification settings - Fork 6
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
feat(zeebe): support Job Corrections in complete command fixes #347 #348
base: alpha
Are you sure you want to change the base?
Conversation
const res1 = await job.completeWithJobResult({ | ||
variables: {}, | ||
result: { | ||
denied: true, | ||
}, |
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.
💭 Given the test case (the process has a service task for which this job worker code will run) this code may eventually break.
Job result is at this time only meant to be used for User Task Listeners.
For now, we allow regular job completions with a job result ignoring the result. However, in the future we may add validations against it.
🔧 As a more durable test case, please consider a Camunda User Task
with a completing
task listener. You can then try to complete the user task, which creates a job that you can activate and complete with a job result.
// * `assignee` - reset by providing an empty String | ||
// * `dueDate` - reset by providing an empty String | ||
// * `followUpDate` - reset by providing an empty String | ||
// * `candidateGroups` - reset by providing an empty list | ||
// * `candidateUsers` - reset by providing an empty list |
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.
🔧 The language in this documentation was changed for clarity. Would be good to take along in this sdk as well: reset
has become clear
for the Job Result corrections
// * `assignee` - reset by providing an empty String | |
// * `dueDate` - reset by providing an empty String | |
// * `followUpDate` - reset by providing an empty String | |
// * `candidateGroups` - reset by providing an empty list | |
// * `candidateUsers` - reset by providing an empty list | |
// * `assignee` - clear by providing an empty String | |
// * `dueDate` - clear by providing an empty String | |
// * `followUpDate` - clear by providing an empty String | |
// * `candidateGroups` - clear by providing an empty list | |
// * `candidateUsers` - clear by providing an empty list |
Description of the change
[Describe your changes here]
Type of change
Checklist
alpha
branchFurther comments
[If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...]