Skip to content
This repository has been archived by the owner on Nov 17, 2023. It is now read-only.

Add Support For BPMN User Tasks #139

Closed
hhund opened this issue Oct 27, 2020 · 2 comments · Fixed by #369, #380, #389, #390 or #391
Closed

Add Support For BPMN User Tasks #139

hhund opened this issue Oct 27, 2020 · 2 comments · Fixed by #369, #380, #389, #390 or #391
Assignees
Labels
enhancement New feature or request ready for release Issue is fixed and merged into develop, ready for next release
Milestone

Comments

@hhund
Copy link
Member

hhund commented Oct 27, 2020

To support BPMN user tasks better, we should add support for OAuth2 / OpenID Connect authentication and use Task resources with recipient Practitioner or PractitionerRole.

This way we could implement simple BPMN user tasks, by having a user change the status from requested to completed to continue the process. If we need the user to communicate outcome back to the BPE we would use output parameters.

@wetret
Copy link
Member

wetret commented Jun 3, 2022

We should evaluate if Questionnaire and QuestionnaireResponse resources are not a better fit than Task resources. The recipient could be matched by the subject and the process could continue as soon as the QuestionnaireResponse status changes from in-progress to completed.

@wetret wetret self-assigned this Jun 3, 2022
@wetret wetret linked a pull request Aug 31, 2022 that will close this issue
@hhund hhund added this to the v0.8.0 milestone Sep 12, 2022
@hhund hhund added the ready for release Issue is fixed and merged into develop, ready for next release label Oct 11, 2022
This was referenced Oct 11, 2022
@hhund hhund linked a pull request Oct 16, 2022 that will close this issue
@hhund
Copy link
Member Author

hhund commented Oct 17, 2022

Reopening to change some details of the implementation in the 0.9.0 release.

@hhund hhund reopened this Oct 17, 2022
@hhund hhund added this to the v0.9.0 milestone Oct 17, 2022
@hhund hhund removed the ready for release Issue is fixed and merged into develop, ready for next release label Oct 17, 2022
@hhund hhund linked a pull request Oct 17, 2022 that will close this issue
@hhund hhund added the ready for release Issue is fixed and merged into develop, ready for next release label Oct 17, 2022
@hhund hhund mentioned this issue Oct 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request ready for release Issue is fixed and merged into develop, ready for next release
Projects
None yet
2 participants