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

Add column(s) for zaak/document identificatie in Ladybug overview table #247

Closed
MLenterman opened this issue Jan 3, 2024 · 0 comments · Fixed by #251
Closed

Add column(s) for zaak/document identificatie in Ladybug overview table #247

MLenterman opened this issue Jan 3, 2024 · 0 comments · Fixed by #251
Labels
feature New feature or request

Comments

@MLenterman
Copy link
Collaborator

... so that it is easier to find all related messages for a certain zaak/document.

All SOAP-actions will always contain a zaak and/or document identifier either in the input message or the return message. Most of the time its either a zaak identifier OR a document identifier, but very few actions will contain both. For example voegZaakdocumentToe will contain the identifier of the document that is being added, but document is added to a zaak, so the zaak identificatie is also present there. In this case both identifiers are equally useful to see in the Ladybug overview table.

A solution could be to create separate columns for zaak and document identifiers. This will require a bit more space in the overview and most of the time there will be space wasted, because its almost always zaak OR document indentifier. An alternative could be to combine them in a single column and figure out a good way to show both identifiers for those exceptions.

Ladybug table customization is configured in src/resources/springIbisTestToolCustom.xml.

Between different SOAP-actions, the identifier is sometimes in a different place in the request/response.

@MLenterman MLenterman added the feature New feature or request label Jan 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant