Any modification of a retention tag sets the retention tag age to 1 day. Not sure if this is intended or modifiable behavior but its dangerous.
To go a step further its not updating the database values. So its setting all of them to 1 day when a change is made.
This is what appears to be happening. When a retention policy was modified it would set the default retention limit to 1 day, and write that to the database. Then all of the retention tags were updated per the database. So even after I had modified all of the retention tags manually on the back end any modification was applying the database values, which were incorrect.
SolidCP version 1.4.2
Confirmed. Able to reproduce.
Add new tag age limit for retention set to 365. Sets default value to 1.
Modify an existing tag and it sets the agelimit for retention to 1 even if the value was previously set.
And thus modifies the retention policy on the exchange server.
I will check this one out later this week, sounds like it’s passing a default value when it’s empty.
This has been fixed on the latest code. It will be included in the next release.
We normally aim to release a stable version once every 3 months, however sometimes this has been pushed for 1-2 months in addition due to instable codes which prevented a stable release.
- Views717 times
- Answers8 answers