ShotFlow

What’s New?

• Areas are supported as Sets. For studio apps that have migrated to the new Areas/Locations structure, Capture looks for Areas with a Type value of "Set" and a Status value that does not equal "Inactive." This functionality is in preparation for the next platform release that will fully support Areas & Locations.
• Captured On Set records Area. For studio applications where Areas are utilized as Sets, when a shot is marked completed, the Captured On Set value in the Shot will populate with the value in the Area's ID field.)
• Scanned Samples retain sort order in Capture. For shots that are related to more than one sample, this functionality makes the locally scanned sample the first in the sort order, so its attributes appear first in tagged metadata. This is handy for brands that need sample attributes tagged in metadata for the specific sample used on-Set.

What Did we Change?

• Capture station could not access a Set if user failed to log out. When a capture user forgets to properly log out at the end of the day, the same capture station can now access that user's Set (as long as the user's authentication token has expired expired, typically 12 hours after initial authentication).
• Capture honors sort relationship in Shots to Samples. If a brand app has this sort relationship enabled, Capture will honor the sort order.

What Did We Fix?

• Cloning a grouping shot intermittently causes an unexpected error. Although the cloned shot was created successfully, the grouping would fail to clone and cause an error. The functionality has been corrected to work as expected.

Known Issues (Carried over from prior releases)

• Style Guide is not showing for path [Shot -> Grouping -> Product Child -> Product Parent -> Style Guide]

Future Enhancements

• A preferences panel!
  
• Capture "mini-panel" for switching shots!
• Style Guides upgrades!
• Filtering upgrades!
• Drag and Drop upgrades!
• So. Many. Things.