@ArnaudLM I know the overlapping date condition can be added to prevent submission. In the Audit Rule condition builder, there is I believe you would then just add a condition that designates the correct policy this would apply to.
Now, if you have more than one policy a user can select, you would need to make a second audit rule with the same overlapping date condition, but would then add a condition for the second policy.
I think this would work.
I always, and I cannot stress this enough, ALWAYS test new audit rules with test users first before activating them for your real users.
The rule would look like what is in the screenshot below. The policy in the example, is just a policy we have in our training site. Give this a try and let me know if it works.
Hi @KevinD , exact! I am trying to prevent the employee from creating two reports, in the same month, that both use the same policy.
My audit rule triggers on the "report save" event and includes only one condition :
As a result, when the employee creates two reports whom start date and end date values in the report header overlap, the rule triggers, regardless the policy.
Now, if you add the policy condition in the rule:
the rule is still not relevant. Indeed, let's assume the employee hasn't created any report yet. If he first creates a report with policy A in January 2021, then creates a report with policy "Travel and Expense Policy" in January 2021, the rule will trigger, although the reports don't use the same policy.
As a result, the dates overlap another report condition seems not to reach the requirement.
Question: is there a workaround?
Thank you very much for your dedication.
Arnaud
