Tracker should support a pre-submit hook.
Before artifacts are really submitted, a business check should be possible.
In case the business logic results in a successful code, the artifact can be created/updated.
Otherwise the code should be represented to the user via a meaningful message.
Via this mechanism certain business rules can be defined which are checked before the artifact is really created or updated.
by: Hans T. | over a year ago | Trackers
Comments
From an industry standard use perspective, webhooks are for publishing events – sending notifications of the occurrence of an event to all 3rd party systems that have subscribed to that event meeting certain criteria, and are non-blocking (i.e. not serial calls). They are meant for other systems to listen for events happening in the source system and to respond as necessary. It is critical that they are not blocking calls for the integrity of the source system.
This use case(s) is much more serial in nature, and is intended to modify the internal behavior of the system, which may not be an appropriate use of webhook-based event publishing. Any thoughts?
What kind of other business logic solution can we expect as customer without adaptations in the TeamForge application?
Tracker pre-submit webhooks are supported from TeamForge 20.0