v5.0-v5.1.1

Migration considerations from Q-flow 5.0

SQL Server database version

Starting from this version, SQL Server 2012 or higher is required to install and work with Qflow databases.

Script tasks that uses dates

Now, when having time zone per instance, you should use the “GetCalendarDateUTC” method (returns the time in UTC) in cases where date type data is used, so that the task is successfully executed. However, pre-existing methods will return the dates in the server’s time. For more information, see the scripting interface manual.

Changes in date type data

The format with which dates are stored has been updated (now it is stored as DateTimeOffset). Therefore, if you have custom elements that access them, such as database access or components that access the value in a non-standard way, they should be updated.

Default time zone

For those dates which come from previous versions, the time zone will be assumed to be the current one of the server. If the database used is Oracle, dates will always be stored in the server’s time zone.

Note

The current version is the last in which Oracle will be supported.