Process Engine supports representation of dates beyond January 2038 in user-defined fields of type Time—a 64-bit field. For compatibility with existing systems, Process Engine also supports the 32-bit time as type Time32 (deprecated).
If you are using queues, rosters, or event logs with exposed time files specified in previous systems and you intend to use 64-bit time fields in your applications, you should configure or change exposed time fields to type Time to avoid exceptions or unexpected behavior that can occur if a 64-bit time value is written to a 32-bit field.
NOTE If a work object is dispatched to a queue that exposes a 32-bit field and the value is 64-bit, an error will occur and the work object is moved to the malfunction map.
For event logs, to change an existing exposed field from type Time32 (deprecated) to type Time, you need to delete the 32-bit field and then add the field as Time. In this case, any existing values in the 32-bit field will be lost.
NOTE If Process Engine tries to add a record to a log table where the date is too big to fit into the exposed 32-bit field:
When you upgrade an existing system to version 4.0.3, the upgrade of the VWWobTimeOut table in the database (to handle the conversion of 32 bit to 64 bit) will be handled automatically the first time you logon—access the database. You might notice a very short delay.
Limitation of the createQuery() method, regarding subscripts for query substitution for filter strings: If a user has a filter on a 32-bit time field, the value bound to the bind variable in the query using that filter must be a value that can fit in 32-bits, otherwise the query won't return the expected result – for example: "my32bitColumn < :a", will not work correctly if bound to a date value like "11/11/2099", It will work fine if you bind it to a value like "11/11/2037". This only affects time substitution variables.
All time system fields (F_StartTime, F_CreateTime, and so on) still have the 32-bit field value.