Release Notes - 2019.09.11

Improvements to Data Pipeline Processing

Data Ingestion Bugs Fixed

We have improved the responsiveness of the One Model application by optimizing the use of the user’s web browser cache by only downloading application assets that have changed since the user last logged on, or the last product release. (ref 2340)

In this release One Model has added additional strength to our security infrastructure by adding a new default user session timeout window of 30 minutes.  This means that after a user logs into One Model, if they are inactive for 30 minutes then their session with the One Model application will be ended and they will have to log-in again.  We also removed the 'remember me' feature on the login page to further tighten security. (ref 2700 & 2564)

Customers that require specific column delimiters for downstream integrations can now configure the delimiters for One Model Data Destination exports. This can support text between one and three characters. The  "," (comma) remains the default delimiter for One Model Data Destination exports. (2666)

Enhance LEAD/LAG functions to allow the ability to look ahead or behind a variable length using an integer column in addition to the existing static integer value.  (ref 2498)

In this release we delivered a number of improvements to processing resiliency using multiple techniques including improved retry logic in the case of errors. One of these features is the addition of a new configuration setting specific for the Workday API connector that includes the ability to set the planned regular maintenance window for Workday. This will allow the connector to automatically resume if there are errors in data transmission during this time.  (ref 2187, 2582, 2673, 2190)

Added support for columns using the Double data type when extracting data using the Redshift Data Source.  (ref 2325)

Fixed an issue where the Workday API was returning an unexpected result for the Applicants endpoint. (ref 2693)

Added the ability for users to manually cancel API runs from the API Runs page. (ref 2498)