Hi @Em_Hallett ,
There is no direct solution available to setup up capping number of claims submitted per month. However, you can do following workaround.
Note - this solution will only allow monthly one claim. Monthly two claims will not work.
1. Add report start date and report end date field on expense report header form and mark it as required fields.
Now, Create 1st audit rule with below conditions. Add start date and end date for each month separated with OR operator.
Note - This audit rule needs to be updated on yearly basis to make this validation work.
2. Create 2nd audit rule using 'dates overlap another report' = Yes.
This will check if current expense reports start date and end date is overlapping with any existing previously submitted expense report or not. If multiple reports found for the same start date and end date then system will throw error message.
Hi @Em_Hallett ,
There is no direct solution available to setup up capping number of claims submitted per month. However, you can do following workaround.
Note - this solution will only allow monthly one claim. Monthly two claims will not work.
1. Add report start date and report end date field on expense report header form and mark it as required fields.
Now, Create 1st audit rule with below conditions. Add start date and end date for each month separated with OR operator.
Note - This audit rule needs to be updated on yearly basis to make this validation work.
2. Create 2nd audit rule using 'dates overlap another report' = Yes.
This will check if current expense reports start date and end date is overlapping with any existing previously submitted expense report or not. If multiple reports found for the same start date and end date then system will throw error message.
Hi @faye ,
No, "Equal" will look for exact start date and end date. There is no direct way to check "between" start date and end date.
If you want to check it then conditions needs to be written in following way:
Example, lets say you want to check whether report contains any date in between April 2025 month or not? If no, then trigger hard stop msg. Then this is how conditions can be written.
However, you cannot do this for all 12 months bcz here each month date condition will affect another month condition and exception msg will not get resolved.
If you want to specifically ensure that for each month start date and end date should be correctly entered by the user then you need to consider separate field to capture month and based on the selected month we can force user to select the correct start date and end date for that month with the help of audit rule.
Audit rule conditions which are given in my previous response that is assuming user will enter start date and end date of that month and if they try to create another report for the same month then restrict.
