In Decisions 4.1 there is a change to use of DateTime fields. Must the WSDLs be recreated for an upgrade to 4.1?
book
Article ID: KB0079488
calendar_today
Updated On:
Products
Versions
TIBCO iProcess Decisions Server
4.1
Description
In Decisions 4.1 there is a change to use of DateTime fields as follows: Returning a Date Only value will not validate against an xsd:dateTime (same for Time Only sub-type, also). What this means is that for backward compatibility, a DateTime data type without a sub-type is equivalent to the earlier Date data-type in pre-4.1 versions of Decisions. However, the response message may not validate against the XSD/WSDL. It is our recommendation that after upgrading to Decisions 4.1, the integrator specifies explicitly all the DateTime subtypes. Only then is the response message guaranteed to validate against the XSD/WSDL.
Issue/Introduction
In Decisions 4.1 there is a change to use of DateTime fields. Must the WSDLs be recreated for an upgrade to 4.1?
Environment
o TIBCO iProcess Decisions Server 4.1.x
o TIBCO iProcess Decisions Studio 4.1.x
o All Platforms
Resolution
If all the data types for your attribute are of type 'DateTime' and granted that the client also has 'xsd:dateTime' for the same attribute in the WSDL file you do not need to change your WSDL or regenerate the vocabulary.
You need to only worry if you start using the sub-types: 'Date Only' and 'Time Only'. The Subtype 'Full DateTime' is the same as xsd:dateTime which is the same as if you didn’t select a subtype in 4.x. If you do select one of the other sub-types then you should regenerate or create a new WSDL using the 'Deployment Console'. The new WSDL will then have the following entries for 'Date only' and 'Time Only' respectively: 'xsd:date' and 'xsd:time'