Connect with us and enhance your M-Files experience using Unitfly Toolkit for M-Files. Here’s how to get started.
Hello everyone,
I find the default configuration with "Trigger on target change = Yes" to be very risky. Wouldn't it make more sense to change it to "No" instead?
Best regards,
Steve
@steve-hagenbring I can see why this could be risky, but we can't change the default values as that would potentially change the current behavior of existing Property Operations rules in the Extension Kit.
Would it not be possible to run a job during the installation of the next release that writes the correct configuration into the JSON from the old default values in the module?
We are well aware that the rules need to be configured carefully. However, it has already happened twice that we ended up creating a loop.
It's not possible, as the default values are not in the JSON, so they can't be remapped...
So, you came to the end of the page. This means you are passionate about technology as we are.
WATCH THE WEBINAR