|Maintenance Notice - PDF Generation|
|Dynamic PDF generation for web-based content is temporarily unavailable. This maintenance affects dynamic PDF files that are generated from either the HTML-based page or manual that you are viewing. Links that normally allow this functionality have been hidden, and will reappear as soon as the feature is restored.
Set Conversation Expiration
Context Services includes granular expiration capabilities for conversations. You can configure expiration dates by type of conversation identified in the service_type attribute of a service instance, instead of instancing purge scenarios.
The conversation data remains valid from the date where you start or update the associated service, till its expiration date. At expiration, the conversation data (all its service, states, and tasks) is removed from the database.
More about the Expiration Option
You can configure the expiration date in the Context Service application or in the Business Attributes mapped with services (see below). The expiration attribute must match the following formatting:
expiration = <integer><letter>
- <integer> specifies the time period
- <letter> is one of the following period type:
- s: seconds
- m: minutes
- h: hours
- d: days
- w: weeks (7 days)
- M: months (30 days)
- y: years (365 days)
For example, setting expiration=2w means that data inserted or updated using the Context Services API will last 2 weeks.