Record permission recalculation
I have a manual RP with a condition to allow update on records.
This RP was not working successfully and after some chat with the support we disabled/enabled all of our RP and it was working again. We also verified that this RP was after the other fields in calculation order.
My problem is that after some time, this RP is back to being a problem. What could cause an RP to recalculate ?
Does anyone had similar issues using RP with date conditions (field Date next 45 days) ?
Just a FYI...
I read in the Help several Archer versions long ago where a formula that calls the Today() or Now() functions are always calculated regardless of the Always or As Needed setting. When a formula contains either of these, this enables the 'Scheduled Recalculation' option for the application. We both know it all depends on the business need on how the scheduled recalculation needs to be set. There is a possibility there could be a bug for the version in question.
Jonathan, if you see find that the scheduled recalc does not update the RP field, my suggestion is to delete the current rules and simply re-add them back in. If that does not work, you may want to look at breaking down the process and follow the tracks. Good Luck.
Hello everyone, we are working on the same infrastructure as the one Jonathan was working on when he created this ticket.
The problem is that this RP and the related rule are working perfectly fine for new records, the only issue is that the rule did not changed the RP for some old records, that have been created at some time.
We had noticed that a simple recalculation of a record that shows the problem triggers the rule and the RP is applied, so it "solves" the problem for this record at that time.
But if the record goes on in its lifecyle (expiring, validity extension...) and comes back in the step where the rule should trigger, it still not triggers until we recalculate the record.
We also noticed that each time a field value is changed in a record, it triggers a recalculation of this particualar record.
So, with the Support we set up 2 months ago a workaround based on a datafeed that changes the value of a flag field on all records that match the conditions of the RP rule.
So this is effectively working but it is not a solution, just a workaround.
The Support engineer told us that he believe that, one time, a RP has been disabled in the application and re-enabled later, and that records created during this period must have a permanent issue in the RP model and this is not fixable.
Could someone confirm or invalidate this hypothesis?
We would like to know if there could be a way to really/permanently solve this issue without relying on a datafeed workaround.
Thanks in advance for any opinion on that problem.
It would be simple to confirm your hypothesis. Just create a new RP field that has never been inactivated with the exact same conditions and test the access.
My understanding is that RP field behaves like calculated field hence they need the record to be recalculated to be evaluated. You then need to trigger recalcuation which is what you do with your datafeed.
This is a solution not just a workaround that you implemented
Hello Jonathan !
Thanks for your reply, I will test that as soon as I have time to do so and note that you consider the datafeed as a decent solution