What's New?

In an effort to continue making access to TrackVia resources as easy as possible on mobile, this release is the first of a series of releases to update our support for 'deep links' when utilizing the Android app, setting the stage for universal links and new types of notifications. 

What's a `deep link`?

A deep link is a specific type of link formatted to direct a user to a specific location within a mobile app installed on their device, rather than the generic dashboard landing page or sign-in page. 

Differences from normal URLs

Deep link URLs are formatted differently than regular URLs. For example, while a link to a Form to add a new record might look like https://go.trackvia.com/#/apps/1/tables/8/records/new/form/9 in your browser, a properly formatted deep link would be: com.trackvia://apps/1/tables/8/records/new/form/9

In a future release we will be adding additional support for regularly formatted links to quickly get users into the app. For now, any instances, integrations, or use-cases where you're leveraging deep links will work as expected, per the fixes below:

What's Fixed?

• Previously, if a user was filling out a Form or working in a Flow, toggled away from TrackVia, and then clicked a deep link (from an email or other app) to take them back to TrackVia, their in-progress work was not saved. We have fixed this and users will always be presented with the appropriate "Save" or "Exit Workflow?" modal. 
• If a user does not have access to a resource but clicks on a deep link attempting to take them there, they will be presented with the appropriate 'Insufficient Permissions' error, instead of simply being presented with an app spinner. 
• Previously, if a user clicked on a deep link while the TrackVia app was closed, they would simply be taken to the login screen of the app. Now deep links to will allow the user to get to the target Form, Record, View, or Flow as expected. 
• Previously, if a deep link did not specify the exact Form to open, links to specific records would not open as expected. Now, the app will open the appropriate Form based on the View ID specified in the link.
• We resolved an issue with Flows not initiating as expected in some scenarios where a user had newly installed the app and not yet accessed any Views. 

Android v4.8.0