Requirements
A device running iOS release: 15.0 or higher
- Access to at least one ShotFlow Brand or Studio app, including the Access Mobile Application permission in the user's role
- For updating Sample Locations using the [Track] function, users must log in via a ShotFlow Studio app configured with Areas and Locations
NOTE: THE ABOVE IS A NEW REQUIREMENT FOR THIS RELEASE THAT SHOULD BE CONFIGURED PRIOR TO USERS UPGRADING TO THIS RELEASE. LEGACY APPS WITHOUT AREAS AND LOCATIONS CONFIGURED WILL NO LONGER BE SUPPORTED FOR MOBILE SAMPLE TRACKING STARTING WITH THIS RELEASE.
Installation Procedure
1. Access the ShotFlow Samples & Styling mobile app on the App Store
2. Download and install to your iOS device, or update your app if already installed.
What’s New?
- Revamped Track workflow with support for Studio Locations
- Area and Location display when listing Samples
Lists of Samples are now grouped under the Studio Area and Location, displayed at the top of each list. Samples lacking an Area and/or Location are listed together at the bottom.
- Major Upgrades to Groupings functionality
- A new Similar Groupings screen enables searching for existing Groupings, and by default shows Groupings that contain the same Product Children as the scanned items. This screen enables users to determine if their intent is to update a Grouping that already exists, or to create a new one. The default filtering is to show existing Groupings with the same Product Children that were scanned in the prior step. Groupings displayed by default may have additional items that were not scanned, or the items may be in a different sort order, but all scanned items are included. The user can change the search/filtering at the top of the screen to find other existing records that may be the intended Grouping to update. Selecting an existing Grouping will update it with changes based on what was scanned in the prior step.
- On the Similar Groupings screen, a [+New] Grouping button enables one-tap skipping to the [New Grouping] screen. If the user wants to create a new Grouping without searching for an existing one with similar items, the user can tap the [+New] button to skip to the New Grouping screen.
- The Similar Groupings screen is auto-skipped if there are no existing Groupings in the brand app with the same Product Children. The Product Children related to the scanned Samples are compared to the Product Children related to all existing Groupings in the brand app, and if no existing Groupings are related to those Product Children, the Similar Groupings screen is no longer displayed to the user, the workflow moves directly to the New Grouping screen.
- Creating a new Grouping now displays all required fields for the Groupings table plus "Reference Image." Prior releases displayed Name, Description and Styling Notes fields, but not all Brands want the same fields to be available when creating a Grouping. Now the mobile app will utilize all required fields for the Brand's Groupings table, enabling each brand to configure the specific fields to be available on mobile when creating a new Grouping. The Reference Image field will always be shown regardless of whether it is marked as "Required" for the Brand Groupings table.
- When updating a Grouping, a new confirmation screen lists Products to be added and removed from the Grouping. This screen enables confirmation of changes to an Grouping from its prior related Product Children, based on the updates being made from the mobile app. For example, a Grouping that previously had item 1111, 2222 and 3333 is being updated based on scanning items 1111, 4444, and 5555. This screen will list added items as 4444 and 5555, and removed items are 2222 and 3333.
- Groupings created via the Style Out function are auto-set as Type = "Style Out". This will help brands distinguish Groupings that are official "Looks" from Groupings that exist as a Style Out of a hero Product Child.
What Did We Fix?
- Squashed some bugs!
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