A property setter after the rule has run would be excellent as a trigger for subsequent rules. This is needed to ensure that the job has been fully executed and only then do subsequent processes begin. We are aware that orchestration should be used for this, but this is often not useful, because we lose the filter options that we have with the trigger object entered status, for example.

In the case of creating documents using templates and then converting them into a PDF, this configuration would be necessary. For example, if you use a trigger to execute the object creation and then want to create a PDF from the native format, you can use the workflow and thus ensure that the conversion via workflow only runs when the rule has finished running. The current problem is that the conversion takes place earlier than the rule has been completed. PDF Conversion is not useful, because the document will rendered not as we wished.

This would also make the configuration faster as you would not have to use the orchestration for an ordered sequence.

In our view, this would make the Extension Kit even more flexible and powerful.