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

Try Corticon Now

Decision Service versioning and effective dating

Corticon Server can execute Decision Services according to the preferred version or the date of the request.
This chapter describes how the Version and Effective/Expiration Date parameters, when set, are processed by the Corticon Server during Decision Service invocation. Assigning Version and Effective/Expiration Dates to a Ruleflow is described in the topic Ruleflow versioning and effective dating
In this section: 
* Deploying Decision Services with identical Decision Service names
* Invoking a Decision Service by version number
* Invoking a Decision Service by date
* Summary of major version and effective timestamp behavior