From 28c0eea8cb0e1016e751a2e28d0b09006751c58b Mon Sep 17 00:00:00 2001 From: Arthur Schiwon Date: Fri, 21 Aug 2020 17:36:01 +0200 Subject: fix possible leaking scope in Flow - a configured flow can be brought into consideration, despite its event was not fired - it could either run through - or run into a RuntimeException and killing processing of valid flows Signed-off-by: Arthur Schiwon --- lib/public/WorkflowEngine/IRuleMatcher.php | 10 ++++++++++ 1 file changed, 10 insertions(+) (limited to 'lib/public/WorkflowEngine') diff --git a/lib/public/WorkflowEngine/IRuleMatcher.php b/lib/public/WorkflowEngine/IRuleMatcher.php index cb52001a1a2..47ab3a25c3a 100644 --- a/lib/public/WorkflowEngine/IRuleMatcher.php +++ b/lib/public/WorkflowEngine/IRuleMatcher.php @@ -78,4 +78,14 @@ interface IRuleMatcher extends IFileCheck { * @since 18.0.0 */ public function getEntity(): IEntity; + + /** + * this method can be called once to set the event name that is currently + * being processed. The workflow engine takes care of this usually, only an + * IComplexOperation might want to make use of it. + * + * @throws RuntimeException + * @since 20.0.0 + */ + public function setEventName(string $eventName): void; } -- cgit v1.2.3