Multi-Update Action Release (deployed 7/11/2020)

What’s New?

• Enable Update Action to update multiple fields at once. Now Update Actions (dark blue buttons) can be configured to address multiple fields, instead of just one. Update actions are the most common type created by our clients, and used for many purposes, such as updating Sample records throughout the workflow. Now an Update Action can change the Status, Location and receipt date (for example) of many Samples from a single button. This can reduce the need for multiple Update Actions buttons on a given table, simplifying the workflow and reducing the opportunity for manual error by skipping a key workflow step.

• Enable URLs to display as an image preview/thumbnail in the UI. For clients utilizing URLs that resolve to an image, such as assets in a DAM system, ShotFlow now supports rendering previews of a URL field in table and record views.
  

What Did We Change?

• Each Report component now loads independently when displaying and editing. This provides faster performance for seeing the simpler Report components (e.g. Text), while other Components that may be slower (e.g. complex Table Views) can continue to load. This also addresses an issue where Reports with a "broken" component (e.g. a Table View that was included in the Report, but subsequently deleted) were breaking the whole Report and preventing the user from editing it. Now the "broken" component throws an error but the others load as expected, enabling users with editing permissions to fix those component(s) without re-creating the entire Report.
• Required field behaviors when defining Forms. The behavior has been updated to be a little smarter. To wit: If a field is Required, not Unique, and a Default value is set, it’s not required to be on any Forms. If the field is Required, but the Default value is not set, it’s required in the Clone and Create Form, but not required in the Edit Form. If the field is Required and must be in the Form, the “Required” label is now red (critical). If the field is Required and does not need to be in the form, the “Required” label is now yellow (warning).
• System errors when attempting to create a relationship to over 1000 records. In order to improve system performance and prevent possible data loss issues with very large related records sets, ShotFlow will not create more than 1000 relationships to any individual records for most applications. This applies to all interfaces and components (Data Ingest, ShotFlow capture, Samples & Styling Mobile App, Client API). This rule applies regardless of when those relationships were created (e.g. if the record already had 800 related records prior to a data ingest, and the ingest logic attempts to link the record to 201 additional records, 200 records will be related but record relationship 1001 will not be created and will display an error in the Data Ingest log).
• System prevents editing relationships of over 4500 records in web UI. If a record has a single relationship to more than 4500 other records, the web UI no longer allows the user to edit that relationship, as this would cause some or all of those relationships to "break" due to API limitations. Clients that have these large sets of related records should work with the ShotFlow Professional Services team to re-configure their app to conform to best practices of keeping related records to 1000 or less.