You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
... 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.
The text was updated successfully, but these errors were encountered:
... 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.
The text was updated successfully, but these errors were encountered: