The forthcoming "Super" Views update enhances the functionality and configurability of Views. This will reduce "forced" navigation by enabling more work to be completed on an individual view, ultimately reducing the number of views needed per user role. It adds user-selectable favorites to improve access to the most commonly used views for each user.
This update changes navigation to access ShotFlow Views. There are also navigation changes for configuring Table elements (Forms, Labels, Fields, etc.) for Admin users (which is addressed in this article).
This release has NO functional impact on the following aspects of ShotFlow:
- Appearance of current Views (all settings, columns, actions, etc. remain identical after deployment)
- Roles
- Permissions
- System Access
- Dashboards
- Charts
- Reports
- Calendars
- ShotFlow Capture
- ShotFlow Samples & Styling Mobile App
- Automations
- Data Ingest
- Table Relationships
This article discusses two broad approaches to preparing for to the new Views deployment currently scheduled for early 2022:
"MVP" Approach
Goals
- minimal disruption for users and system admins
- minimal training and support effort at deployment point
Configuration changes required by client System Admins
- None
User Training required (by client System Admins, and/or ShotFlow Training team)
Users that access ShotFlow via web browser will experience a navigation change when accessing Views that must be communicated in order to continue to use the tool with no disruption to the workflow process:
Accessing Views
Users currently access Views via the following process:
- User selects Tables in the left nav
- User sees a list of tables. Select the table where the View is located
- User sees the default table View for their role
- To navigate to other Views that are also associated with the current table, user opens the menu and then selects a different View. To navigate to Views that are associated with a different table, go to step 2
Once the new Views are deployed, users will access Views via the following process:
- User selects Views in the left nav.
- User sees all the Views available for their role. The Views displayed at the top will be that user's "Favorites." At initial deploy, these are the default table views for user's existing role, which have been auto-flagged as "Favorites" automatically during the Views deploy process. Once the user is accessing the tool, they can manage these Favorites themselves without impacting other users.
- User selects the desired View
- To navigate to other Views, select the Back button (go to step 2)
Note that in both current state and post-deploy, accessing key views requires 2 mouse clicks.
Each View will have identical columns, create record and action button(s), saved filtering, pagination, default sort and related settings, and so will be essentially identical in appearance and functionality to current state. The only minor exception is Views with a saved search/filter: the visual indicator will change appearance and will not be removable when interacting with the View.
"Touch It Once" Approach
Goals
- improve user experiences over current state by aligning configuration changes with this update
- leverage this opportunity to improve views and/or roles for better outcomes
Configuration changes recommended for client System Admins
- Update configuration of existing Views to reduce excess navigation, filtering/searching and process steps by utilizing new View features
- Removal of unused/redundant Views through configuration activity in prior step
- Possible adjustment of default Views and accessible Views by role, as appropriate
User Training required (by client System Admins, and/or ShotFlow Training team)
- For Views that are altered, consolidated, or otherwise updated per Configuration changes... (above), users need to be clear on which View(s) are being used for which steps in their workflow. Note this can be clarified using the Description field in each View, which is visible to the user when browsing Views in the new UI:
- Users that access ShotFlow via web browser will experience a navigation change that must be communicated in order to continue to use the tool with no disruption to the workflow process:
Accessing Updated Views
Users currently access Views via the following process:
- User selects Tables in the left nav
- User sees a list of tables. Select the table where the View is located
- User sees the default table View for their role
- To navigate to other Views that are also associated with the current table, user opens the menu and then selects a different View. To navigate to Views that are associated with a different table, go to step 2
Once the new Views are deployed, users will access Views via the following process:
- User selects Views in the left nav.
- User sees all the Views available for their role. The Views displayed at the top will be that user's "Favorites." At initial deploy, these are the default table views for user's existing role, which have been auto-flagged as "Favorites" automatically during the Views deploy process. Once the user is accessing the tool, they can manage these Favorites themselves without impacting other users.
- User selects the desired View
- To navigate to other Views, select the Back button (go to step 2)
Note that in both current state and post-deploy, accessing key views requires 2 mouse clicks.
Each View that has not been expressly modified by a client user post-launch will have identical columns, create record and action button(s), saved filtering, pagination, default sort and related settings, and so will be essentially identical in appearance and functionality to current state. The only minor exception is Views with a saved search/filter: the visual indicator will change appearance and will not be removable when interacting with the View.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article