Release Notes: Capture 2.1.4 (No longer supported)

Upgrade Procedure

1. Download ShotFlow capture 2.1.4 from Box.com
2. Extract the files from the ZIP archive
3. Drag any older ShotFlow capture releases to the trash
4. Launch ShotFlow capture 2.1.4 and log in

What’s New?

• Show Style Guide as an overlay in Capture One. For ShotFlow brand apps with the Style Guides module enabled and a related Style Guide available for a Shot (a [picture] icon is displayed for that Shot in the List View), connecting the Shot to Capture One sets the overlay to the first Style Guide image, and the overlay’s Show property will be turned on automatically so that the overlay is visible. This feature is toggled on or off by the Admin / Set C1 Overlay to Style Guide menu option.
• Syncing behavior changes. Reading and writing syncing intervals with the cloud server are now configurable in the brand app, and "instant" write of every change to a Shot has been eliminated in favor of a timed interval write sync. This will improve performance of both ShotFlow capture and related brand app(s) during heavy production work, particularly with fast tethered shooting. Consequently, local changes to Shots (e.g. Status, capture count, locally added Notes, etc.) will be cached during the write sync interval, which could result in the loss of those changes if a capture station is shut down or put to sleep prior to a write sync. Quitting ShotFlow capture or signing out from a Set by selecting ShotFlow Capture / Sign Out will trigger a write sync to ensure all data is updated to the cloud, so it is best practice for on-Set teams to always Sign Out or Quit ShotFlow capture prior to shutting down or putting a capture station to sleep, in order to ensure all local data has been written to the cloud. 
• New permissions-related informational and warning dialogs. Apple continues to add additional permissions controls to each new O/S release, which can impact whether ShotFlow capture can perform all its functions. Prior ShotFlow capture releases did not provide explicit warnings to the user in many of these scenarios, either displaying a more generic error message, or recording the error in logging without displaying a dialog to the user. This could potentially result in metadata not being tagged correctly due to disk/folder permissions, issues with installing XMP panels, etc. Note that this release does not change ShotFlow capture behavior related to permissions, it just adds these new dialogs to ensure that a local user is aware of permissions issues immediately and can assess whether the issue is critical for their workflow (potentially requiring local Security & Privacy changes) or can be ignored.
• Eliminate checking Shot List Capture - Subfolder - Create (Y/N) field when shooting tethered. Prior releases checked the Capture - Subfolder - Create (Y/N) field for True or False, and if True, utilized the Capture - Subfolder - Naming Format field to determine capture subfolder naming. New behavior is to ignore the Capture - Subfolder - Create (Y/N) field (which can now be removed from brand apps) and only check the Capture - Subfolder - Naming Format field. If that field is blank, no subfolders will be generated. If there is a value, it will be processed to create subfolders. Drag and Drop already worked this way, now tethered shooting does as well.

What Did We Fix?

• Active/Inactive status for Talent resources were invading other Shot List(s) related to the same Set. They are staying where they belong now.
• Cloning a Shot was not cloning relationship(s) to Requests. Now any existing Request relationships will be inherited by the cloned Shot.
• Local changes to multiple Product Parent fields were not syncing correctly if one of the fields was invalid. Now only the invalid field will be ignored when syncing the data.
• Product List field in XMP was not populating. Now all Product Children in a Grouping should be listed using the delimiter defined in the brand app 
• Drag and Drop failed to create a subfolder after a local data wipe. Should do as it's told now.
• "No file found" dialog displayed for temporary files. Dialog has been kindly asked to leave and it promises to cause no further disruptions.

Known Issues (Carried over from prior releases)

• When adding multiple products or scanning multiple barcodes, if any are "invalid" (not located in the Samples table of the related brand app), there is no confirmation of those invalid products.

• Nested child Shots are not sorting as expected (ignoring the sort parameter).

Future Enhancements

• Developing a new UI for “product centric” capture workflows, to supplement the current “shot centric” List View