Sharing is Caring Release (deployed 1/20/2023)

Modified on Fri, 20 Jan, 2023 at 9:47 PM

Requirements

  • A modern web browser updated to a current release. Tested browsers include:
    • Google Chrome Version 102.0.5005.115 (Official Build) (x86_64)
    • Apple Safari Version 15.1 (17612.2.9.1.20)
    • Mozilla Firefox Version 101.0.1 (64-bit)
  • ShotFlow user seat with access to at least one app
  • For local capture work: ShotFlow Capture Version 2.2.1 and higher (please note older releases of ShotFlow Capture will no longer connect)


What’s New?

  • Non-Restricted Relationships setting. Sharing data (Samples, Shots, etc.) across applications is a critical function between brands and studios. In prior state, sharing data between applications required records to be shared individually, providing very granular control over the shared data. This also required extra work for "captive" brand/studio relationships where all records should be available to both sides of the workflow process. So we are introducing a new setting for multi-application relationships that supports two distinct states:
    • Restricted (identical to prior state) - each record must be shared independently to be accessible from the other application, or be related to a shared record (e.g. Samples must be shared directly or related to a shared Shipment)
    • Non Restricted - a new state in which all the records in a brand/app relationship are automatically exposed to the other application. This eliminates the need for "tying" records to Shipments or Shot Lists in order to enable studio visibility to the records. This may also reduce Capture errors related to accessibility of Sample or Shots to the studio, among other workflow implications. Please contact your Technical Account Manager to discuss if this new setting is right for your brand/studio process.
  • Remove Relationship Action. This new action type enables users to remove relationships between multiple records directly from a View with a single action. This will significantly improve the workflow for scenarios such as removing Shots from Shot Lists, removing Samples from Shipments, removing Shot Lists from Sets, etc.
  • Share Records Action. This new action type enables users to share records with related applications directly from the a View with a single action. This action is only relevant for application relationships that will continue to utilize Restricted relationships (see Non-Restricted Relationships above). Those with Non Restricted relationships won't need to share records through an action.

 

What Did We Fix?

  • Action applies to records no longer selected if "Select All" was initially utilized. After the "Select All" checkbox was enabled for a View, then some of the records were manually de-selected, executing an action applied to all originally selected records (instead of just the intended subset). Fixed!
  • Related Dynamic (Historical) fields can now be searched. Previously attempting to search in a view containing a Related Dynamic (Historical) field resulted in a message: [SF-A1000] "related_field_historical" is not a supported dynamic field type. This has now been fixed.
  • Cell selection in Grid Edit for copying a value does not apply until the cursor is moved out of the cell. Now the visual effect will apply as soon as the user selects a cell.
  • Error message presented when records aren't actionable via a cross-table action. When the user executes a related records action on a record that does not have related records, the prior error was "No records selected." This was misleading, as record(s) are selected, but the issue is no applicable related records. The new error message displaed is: "Selected records are not applicable to this action."
  • Wrong error message if application does not exist. Prior "insufficient permissions" error was inaccurate, the new error message displayed is "[SF-A1001] Not found."

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article