-
Notifications
You must be signed in to change notification settings - Fork 26
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
Add metadata to data being sent to API endpoint in JSON dump registration backend #5012
Comments
Add reference number to metadata |
Discussed with JVS and they agree with the suggestion made by you @viktorvanwijk |
Also add form version |
10 tasks
viktorvanwijk
added a commit
that referenced
this issue
Jan 30, 2025
viktorvanwijk
added a commit
that referenced
this issue
Jan 30, 2025
Also add support for an extra static variables registry in generate_json_schema
viktorvanwijk
added a commit
that referenced
this issue
Jan 30, 2025
viktorvanwijk
added a commit
that referenced
this issue
Jan 30, 2025
If there is no authentication, the value can be an empty string
viktorvanwijk
added a commit
that referenced
this issue
Jan 30, 2025
viktorvanwijk
added a commit
that referenced
this issue
Jan 30, 2025
Also add support for an extra static variables registry in generate_json_schema
viktorvanwijk
added a commit
that referenced
this issue
Jan 30, 2025
viktorvanwijk
added a commit
that referenced
this issue
Jan 30, 2025
If there is no authentication, the value can be an empty string
viktorvanwijk
added a commit
that referenced
this issue
Feb 4, 2025
If there is no content (in case of an HTTP 204 response for example), converting the response to json results in an error, so we just return an empty string
viktorvanwijk
added a commit
that referenced
this issue
Feb 4, 2025
* Improve UX by introducing a (collapsed) fieldset which contains a table of fixed variables, and a variable selection box to add additional variables. * Fix imports * Add TODO: currently, this is tricky because the form registration options are saved before the (user defined) form variables are persisted. If this field is limited to static/registration variables, however, it will be possible as they are defined in the code. At this point in time, though, not sure how strict we should make this.
viktorvanwijk
added a commit
that referenced
this issue
Feb 5, 2025
Also add support for an extra static variables registry in generate_json_schema
viktorvanwijk
added a commit
that referenced
this issue
Feb 5, 2025
If there is no authentication, the value can be an empty string
viktorvanwijk
added a commit
that referenced
this issue
Feb 5, 2025
If there is no content (in case of an HTTP 204 response for example), converting the response to json results in an error, so we just return an empty string
viktorvanwijk
added a commit
that referenced
this issue
Feb 5, 2025
* Improve UX by introducing a (collapsed) fieldset which contains a table of fixed variables, and a variable selection box to add additional variables. * Fix imports * Add TODO: currently, this is tricky because the form registration options are saved before the (user defined) form variables are persisted. If this field is limited to static/registration variables, however, it will be possible as they are defined in the code. At this point in time, though, not sure how strict we should make this. * Fix help texts of JSON dump option fields. They are sentences that should end with a period
viktorvanwijk
added a commit
that referenced
this issue
Feb 5, 2025
viktorvanwijk
added a commit
that referenced
this issue
Feb 5, 2025
viktorvanwijk
added a commit
that referenced
this issue
Feb 5, 2025
Also add support for an extra static variables registry in generate_json_schema
viktorvanwijk
added a commit
that referenced
this issue
Feb 5, 2025
If there is no authentication, the value can be an empty string
viktorvanwijk
added a commit
that referenced
this issue
Feb 5, 2025
If there is no content (in case of an HTTP 204 response for example), converting the response to json results in an error, so we just return an empty string
viktorvanwijk
added a commit
that referenced
this issue
Feb 5, 2025
* Improve UX by introducing a (collapsed) fieldset which contains a table of fixed variables, and a variable selection box to add additional variables. * Fix imports * Add TODO: currently, this is tricky because the form registration options are saved before the (user defined) form variables are persisted. If this field is limited to static/registration variables, however, it will be possible as they are defined in the code. At this point in time, though, not sure how strict we should make this. * Fix help texts of JSON dump option fields. They are sentences that should end with a period
viktorvanwijk
added a commit
that referenced
this issue
Feb 5, 2025
viktorvanwijk
added a commit
that referenced
this issue
Feb 5, 2025
* Improve UX by introducing a (collapsed) fieldset which contains a table of fixed variables, and a variable selection box to add additional variables. * Fix imports * Add TODO: currently, this is tricky because the form registration options are saved before the (user defined) form variables are persisted. If this field is limited to static/registration variables, however, it will be possible as they are defined in the code. At this point in time, though, not sure how strict we should make this. * Fix help texts of JSON dump option fields. They are sentences that should end with a period
viktorvanwijk
added a commit
that referenced
this issue
Feb 5, 2025
viktorvanwijk
added a commit
that referenced
this issue
Feb 5, 2025
* Improve UX by introducing a (collapsed) fieldset which contains a table of fixed variables, and a variable selection box to add additional variables. * Fix imports * Add TODO: currently, this is tricky because the form registration options are saved before the (user defined) form variables are persisted. If this field is limited to static/registration variables, however, it will be possible as they are defined in the code. At this point in time, though, not sure how strict we should make this. * Fix help texts of JSON dump option fields. They are sentences that should end with a period
viktorvanwijk
added a commit
that referenced
this issue
Feb 5, 2025
viktorvanwijk
added a commit
that referenced
this issue
Feb 5, 2025
viktorvanwijk
added a commit
that referenced
this issue
Feb 5, 2025
Also add support for an extra static variables registry in generate_json_schema
viktorvanwijk
added a commit
that referenced
this issue
Feb 5, 2025
If there is no authentication, the value can be an empty string
viktorvanwijk
added a commit
that referenced
this issue
Feb 5, 2025
If there is no content (in case of an HTTP 204 response for example), converting the response to json results in an error, so we just return an empty string
viktorvanwijk
added a commit
that referenced
this issue
Feb 5, 2025
* Improve UX by introducing a (collapsed) fieldset which contains a table of fixed variables, and a variable selection box to add additional variables. * Fix imports * Add TODO: currently, this is tricky because the form registration options are saved before the (user defined) form variables are persisted. If this field is limited to static/registration variables, however, it will be possible as they are defined in the code. At this point in time, though, not sure how strict we should make this. * Fix help texts of JSON dump option fields. They are sentences that should end with a period
viktorvanwijk
added a commit
that referenced
this issue
Feb 5, 2025
sergei-maertens
pushed a commit
that referenced
this issue
Feb 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Follow-up of #4908
Suggestion is to add metadata to the data being sent. In the JSON dump configuration options, any variable (component, user-defined, or static) can be selected to add to this metadata, with several pre-selected variables such as:
Example
An example form with the following configuration:
firstName
andlastName
attachment
Should lead to a JSON object being sent with the shape:
The text was updated successfully, but these errors were encountered: