Disposition Rule Computed Date Is Not Calculated as Expected.
(Doc ID 2066756.1)
Last updated on JANUARY 06, 2023
Applies to:
Oracle WebCenter Content: Records - Version 11.1.1.8.0 and laterInformation in this document applies to any platform.
Goal
In Webcenter Content:Records, the disposition rule computed date value is being calculated from the start of the defined period, instead of the start date defined in disposition rule.
Example:
Disposition Rule states: After <someaction> Wait For <some period> Then Delete All Revisions
After Cutoff Wait for 3 months
If cutoff date = 10/15/15 then the expected cutoff is 01/15/16
However, the following is occurring:
If cutoff date = 10/15/15 then the computed date is showing as 02/01/16 (it is starting from day one of the following month, rather than on day the item was cutoff)
Note:
If the period is Month - the computed date is starting calculation from Day one of the next month
If the period is Year - the computed date is starting calculation from Day one of the next Calendar Year
If the period is Fiscal Year - the computed date is starting calculation from Day one of the next Fiscal Year
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| References |