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 and moving Locations to a new Area, users must log in via a ShotFlow Studio app configured with Areas and Locations
NOTE: LEGACY APPS WITHOUT AREAS AND LOCATIONS CONFIGURED ARE NO LONGER SUPPORTED FOR MOBILE SAMPLE TRACKING. PLEASE CONTACT SUPPORT@SHOTFLOW.COM TO REQUEST STUDIO APP AREAS & LOCATIONS CONFIG IN ORDER TO UTILIZE THE LATEST MOBILE TRACKING FEATURES. 


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?

  • Home Screen Buttons are Tied to Role Mobile Visuals - Only buttons that the user's  has permissions to access. Note this change could result in users losing access to certain home page functionality (missing buttons) if Role Mobile Visuals are not properly configured.

  • Style Out Required Fields - Configure your mobile Style Out settings to include required fields, such as Reference Image and/or Styling Notes. Requiring user input during the the Style Out flow ensures compliance with your brand Style Out rules, and can trigger further automations, sync product data, and optimize on-set productivity. This is configurable via Capture Module Forms in the brand app (refer to How Do I Enable These New Features, below).

  • Edit/Add/Remove Style Out Products - Edit, add, or remove products from a Style Out through the mobile app interface. This was formerly done through via web browser in most brand workflows (refer to Creating/Updating a Style Out, below).

  • New Samples View by Shot List or Request - With this release, a new button on the home page enables viewing samples related a Shot List or Request. This is a totally new mobile workflow for passing work from the producing process to the Merch Team. Your ShotFlow planning workflow will need to be modified to fully leverage this new feature, including some field modifications (this feature is currently configured to only display Shot Lists with a Status of ‘Needs Samples Pulled' and Requests with a Status of 'Samples Available'). Please reach out to your Technical Account Manager (TAM) to discuss configuring this exciting new mobile workflow to make sample prep at scale a breeze!

What's Changed?

  • Redesign the Style Out user experience flow plus an updated look and feel to a simpler design.

  • Removed support for searching via Area ID's when scanning samples.

  • Ongoing bug fixes and improvements.

How Do I Enable These New Features? (Client Admins only)

Setting up Forms for Style Outs

Since Style Outs are specialized Groupings, you’ll be creating forms for the Grouping table on platform. Log into Platform and select the desired brand application. Navigate to the Capture Module header and select Forms:

Select the ‘Create’ button at the top right or centre of the screen (depending on if there are existing forms). Select the ‘Groupings’ table followed by the type of form, either ‘Create’ for Style Out creation, or ‘Edit’ for updating an existing Style Out. It is recommended you create a form for both ‘Create’ and ‘Edit’ to cater for both scenarios on mobile.

After selecting ‘Create Form’ you can drag fields from the left pane to the right pane to include them in the mobile workflow when creating or editing a Style Out:


Any field tagged with a “Required” label must be completed by the user in order to complete the Style Out process.

Creating/Updating a Style Out (mobile users)

Once logged in into the desired studio and brand applications, select the ‘Scan Samples’ button and proceed to scan sample barcodes that have a related product. You will know that a product is related to the sample if you see a tag icon next to the scanned sample:

Once you have scanned all the relevant samples to the Style Out, tap ‘Done’ and navigate to the ‘Style Out’ button. Select your ‘hero’ product you want to Style Out:


If there are existing Style Outs for the same products you have scanned, they will be displayed on the next screen. Tap an existing Style Out will utilize the the ‘Edit’ form for ‘Groupings’.

For the rest of this example, we will be ignoring the existing Style Outs to show creating a new Style Out by tapping the ‘New’ button on the top navigation bar:


All the fields the ‘Create’ form for ‘Groupings’ will appear on this screen for the user to complete. Required fields will display a red asterisk next to their name (unless it is a toggle, in which case the default value is off):

Tap ‘Create’ to move to the next stage of the Style Out. You will see a success screen if everything has been created successfully, or an error screen stating what went wrong during the process:

Tap ‘Next’ to enable adjusting the current products related to the Style Out:

Once you’re happy with the current products for the Style Out, tap ‘Next’ to finalize the products and see a success screen if everything succeeded:

Tap ‘Next’ to select the Type of Shots that are related to the ‘hero’ product that you are styling for, such as On-Figure or Flats (note the choices available are dependent on the brand app configuration). Selecting a Type will link all shots for the hero product that are not Completed or Canceled to this Style Out. This step is optional, tap ‘Close’ at the top left, or swipe the view downwards to dismiss the view.


You have successfully created a Style Out and linked products/shots to it!


Note that a similar approach can be followed for updating an existing Style Out, that process will utilize the fields designated in the CM Groupings table ‘Edit’ form.


If no ‘Edit’ or ‘Create’ form exists for ‘Groupings’ the mobile user will see a “No Fields” screen (example below) which still allows proceeding to the next part of the workflow. However the Style Out process will fail if there are required fields for your ‘Groupings’ table that are not added to the Create/Edit Forms (the mobile app cannot determine what value(s) to utilize):