skip to main content
Corticon Server: Integration & Deployment Guide : Decision Service versioning and effective dating : Invoking a Decision Service by date

Try Corticon Now

Invoking a Decision Service by date

When multiple Major versions of a Decision Service also contain different Effective and Expiration Dates, we can also instruct Corticon Server to execute a particular Decision Service according to a date specified in the request message. This specified date is called the Decision Service Effective Timestamp.
How Corticon Server decides which Decision Service to execute based on the Decision Service Effective Timestamp value involves a bit more logic than the Major Version number. Let's use a graphical representation of the three Decision Service Effective and Expiration Date values to first understand how they relate.
Figure 319. DS Effective and Expiration Date Timeline
As illustrated, our three deployed Decision Services have Effective and Expiration dates that overlap in several date ranges:  Version 1 and Version 2 overlap from July 1, 2013 through December 31, 2013. And Version 3 overlaps with both 1 and 2 in July-August 2013. To understand how Corticon Server resolves these overlaps, we will invoke Corticon Server with a few scenarios.
* Modifying the sample Rulesheets and Ruleflows
* Specifying Decision Service effective timestamp in a SOAP request message
* Specifying effective timestamp in a Java API call
* Specifying both major version and effective timestamp
* Default behavior with no timestamp