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.

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

[GENERAL]: signals for completed registrations #152

Open
StevenHosper opened this issue Dec 4, 2024 · 0 comments
Open

[GENERAL]: signals for completed registrations #152

StevenHosper opened this issue Dec 4, 2024 · 0 comments
Assignees

Comments

@StevenHosper
Copy link
Collaborator

Currently, completed registrations are not translated to visible items within the overview.
This can cause quite some confusion.

The cause is as follows: new registrations result in an upload_task. Upon completion, no registrations are made within gmw/gmws gmw/monitoringtubes gmn/gmns or anything.

As a result, the query for the user-interface won't include the new registrations.

Within the signals.py file, we are able to create an action that would post to these endpoints once on the following conditions:

  1. the registration type is 'registration'
  2. the sourcedocument type is in: [GMW-Construction, GLD-StartRegistration, GMN-StartRegistration, FRD-StartRegistration].
  3. the status is completed.
  4. a BRO-ID is available.

If all of these are met, a post request can be completed.

Eventually new registrations should result in updates, but this is quite complicated.

@StevenHosper StevenHosper self-assigned this Dec 4, 2024
@StevenHosper StevenHosper changed the title [General]: signals for completed registrations [GENERAL]: signals for completed registrations Dec 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant