Navigation in Platform

Modified on Wed, 6 Apr, 2022 at 12:34 PM

Every “page” of the web navigation includes a unique URL, including every view, chart, report, etc. This enables the web browser [back] and [forward] buttons to work as intended, so they can be utilized to move back and forth through the user navigation thread. URLs can also be shared to other ShotFlow users, and the user who opens the link will see the exact same page (assuming both users have permission to the page). View URLs will include simple, List, and Advanced search results (with some exceptions as noted below). Note that sidebars and modals are not considered “pages,” and do not have a corresponding URL. 


The Back browser button will incrementally step backwards; whereas the Back button will likely behave differently. 


Example Scenario: 

Navigating to the Shots table, then view record, then edit record

Each click of the Back browser button would move one step backwards in the process: From edit record, to view record, to Shots view

Choosing the Back button would go back to the Shots view from edit record (skipping the view record step).



Some Exceptions: 

1. URLs are limited by characters (browser dependent)

Examples: Possible limitations with Nested Navigation; List search with hundreds of values; temporary searches that include one hundred fields


2. Right pane not included

Examples: 


Non-executed list searches (empty or input values but never click search to execute)




Confirmation of Record Deletion



Using an action button





3. Modals are not included 

Examples: 


+ related records modal




Non-executed advanced searches (empty or input values but never click search to execute)




Historical views for logged fields



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article