NOE And Expired Content Issues With Updating Expiration Date
Last updated on MAY 30, 2017
Applies to:Oracle Universal Content Management - Version: 7.5.0 to 7.5.2 - Release: Stellent to Stellent
Information in this document applies to any platform.
Product: Content Server
The Notification Of Expiration component will not work if using a custom field instead of dOutDate. In this case it was attempted to work around not being able to have expired content, but needing notifications sent every 6 months.
Content can be "unexpired" by updating the expiration date in Repository Manager. When this was attempted the error "Error updating content item. Unable to update the content item information for '036955'. Unable to execute service method 'doSubService'. (System Error: helper.HelperService.getCurrentErrorMsg()Ljava/lang/string;)" occurred
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms