Skip to content
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.

Sign up for GitHub

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

Jump to bottom

All registration/update/confirm workflows should use only one Participant.create call #19

Open
bjendres opened this issue Feb 22, 2022 · 4 comments
Open

All registration/update/confirm workflows should use only one Participant.create call #19

bjendres opened this issue Feb 22, 2022 · 4 comments
Labels
enhancement New feature or request
Milestone
1.3

Comments

@bjendres
Copy link
Member

For example, if you accept/confirm an invitation with some fields to fill out, you will currently (1.0-beta8) trigger two Participant.create calls: one for the status change, one for the storage of the registration data.

This is not ideal, and can get other processes relying on the Participant triggers to operate in trouble. For example the EventCommunication extension might send two emails for the same process.
@bjendres bjendres added the enhancement New feature or request label Feb 22, 2022
@bjendres bjendres added this to the 1.1 milestone Feb 22, 2022
@bjendres bjendres mentioned this issue Feb 22, 2022
Closed
@jensschuppe jensschuppe removed the enhancement New feature or request label Oct 17, 2023
@jensschuppe jensschuppe modified the milestones: 1.1, 1.2 Oct 17, 2023
@jensschuppe jensschuppe added the enhancement New feature or request label Oct 17, 2023
@jensschuppe
Copy link
Contributor

@bjendres I guess that's still relevant after #19 has already been fixed …?

@bjendres
Copy link
Member Author

bjendres commented Dec 4, 2023

@bjendres I guess that's still relevant after #19 has already been fixed …?

I'm not sure I understand

@jensschuppe
Copy link
Contributor

Sorry, this should read

after #20 has already been fixed

@jensschuppe jensschuppe modified the milestones: 1.2, 1.3 Mar 25, 2024
@jensschuppe
Copy link
Contributor

Moving to 1.3 as 1.2 is already in beta.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
1.3
Development

No branches or pull requests
2 participants
@bjendres @jensschuppe