06/03/2026 8:50 am
Topic starter
Community
Connect with us and enhance your M-Files experience using Extension Kit for M-Files. Here is how to get started.
Notifications
Clear all
0
Hello everyone
We would find it very helpful if all modules in Extension Kit supported the ability to use a property setter after a rule has completed successfully.
With the Orchestrator, rules simply run in sequence. In scenarios where a task continues in the background, this is difficult to handle cleanly. For example, when merging multiple PDFs, the job runs in the background, and the simplest solution would be to set a property once the rule has finished successfully, for example through an on-success action.
This would provide a reliable way to confirm that the process has been completed and allow the next steps to continue with certainty.
The delay options in the Orchestrator are not really a practical solution for this kind of scenario. There are workarounds, but none of them are as clean or effective as having a property setter available directly after successful rule execution.
We believe this would make many workflows more robust, transparent, and easier to manage.
Is this feature already planned, or can it be expected in an upcoming release?
Kind regards
Jeremias
IMCT AG
1 Answer
1
17/03/2026 10:31 am
Hi Jeremias,
Even though we’ve already discussed this topic through other channels, I’ll share a summary here in case others have the same question.
Property setter functionality has already been introduced in several commonly used modules where it adds clear value. This is especially true for modules that execute actions without directly modifying the processed object’s properties, where it can otherwise be difficult to confirm whether the rule has completed successfully. Examples of such modules include HTTP, Word Writer, Object Operations, and similar ones.
For Document Processing, each action automatically writes an entry to the PD Version label, which can be used to track whether the rule execution was successful. You can use this as a workaround until property setter support is added.
We’re continuing to expand property setter support across additional modules over time, based on demand and prioritization.
Best regards,
Nika
