Sanction Check#
See also the following ChangeLogs#
27.4.646.0 - 2026-02-25#
Hotfix
- Assistet Setup after first installation marked as "done" (#16973, SACH-91)
Assistet Setup after first installation marked as "done". This erros was fixed if you run the assistet setup for the app the first time there is no message that the setup was already done.
Change
- Fields in Sanction Check Setup to setup how to block customer or vendor via workflow (#16997, SACH-92)
To increase flexibility in how a customer or supplier is blocked within the workflow, we have implemented this functionality in the setup using two dedicated fields.
27.4.638.0 - 2026-02-20#
Change
- General performance and stability improvements.
27.4.635.0 - 2026-02-19#
Change
- Interface for alternative providers (#16118, SACH-69)
The app has been restructured technically, making it easier to integrate new providers. - Permission Extension to stop breaking Standard AI Agents for Sanction Check (#16809, SACH-90)
In order to not break standard ai agents like Sales Order Agent in conjunction with installed Sanction Check, we extended the standard permissionsets. - Interface Provicer for BEO (#16952, SACH-74)
A new provider is now available: the Sanction Check verification offered by BEO.
27.2.531.0 - 2026-01-07#
Hotfix
- Request Page in Batch Force Check Entities (#16522, SACH-80)
The Request Page for the report 'Batch Force Check Entities' automatically reset when added to the job queue. This issue has been fixed.
27.0.488.0 - 2025-10-20#
Hotfix
- Error while Posting Service Credit Note (#15876, SACH-72)
Three new events have been added to allow sanction checks to be skipped when the document type is unknown.