Hi,
Set the scope of the business rule to Entity is the correct answer.
When the scope is set to Entity, business rule is executed on server side.
To elaborate more, Business Rules execute on-change of a field, there is no on-save event available for the Business Rule.
However, to run a Business Rule on save, we can set it's scope to Entity.
This way, Business Rule do not run on-change of a field's value, rather it executes on server side save operation (however this is till pre-save, you can throw validation errors so the data is not saved).
You can test this as following:
- Add a form level Business Rule (click on the Business Rules on the Form header, do not add a business rule on a Field Properties).
- Add a condition (any).
- Add an Action on true path of the condition.
- Set the scope to the current or all forms.
- Activate the BR and test your scenario, it should not work.
- Then deactivate the BR and set it's scope to Entity.
- Activate and test the scenario, it should work.
In short, adding a condition on Modified on is not necessary, you can add any condition as per your requirement, but scope should be Entity in order to execute on save.
I hope this answers your query, feel free to discuss if you have doubts.
Best,
Wahaj
(if it helps, mark it verified)
