Low-Hanging Fruit Release (deployed 6/17/2022)

Modified on Fri, 17 Jun, 2022 at 9:16 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.1.8 and higher (please note older releases of ShotFlow Capture will no longer connect after this platform release)


What’s New?

  • List Search "Show Difference" function. This one has been on the wish list for ages and we are excited to finally deliver it! Now when executing a List Search, the user can enable a "Show Difference" check box. If enabled, and the results of the List Search differ from the input values, the value(s) that did not match will be shown in a dialog. So a List Search for 50 items that returns 47 can show a dialog listing the missing 3! Yeah, this seems pretty easy to do but... it wasn't. The key turned out to be bribing the developers with a lot of Pay Day bars, so it finally got done!
  • [Unlink all] button when editing a record that has more than one related record for a table. When editing an individual record that has at least two related records of the same type (e.g. a Product Child with at least two linked shots), a new button enables removing all the related records of that type with a single action. This is great for removing many shots from a Shot List, many samples from a shipment, and many other scenarios.
  • Ability to protect data ingest configurations. Now a Data Ingest Configuration can be designated as "protected" to prevent unauthorized edits that could corrupt critical mappings and/or logic. The new corresponding permission is “Manage protected configurations” to enable which role(s) can manage this function. 


What Did We Change?

  • Nested view navigation "tabs" functions have changed for easier navigation. When utilizing nested views, the prior "tab" elements would enable both visibility to the source record the user navigated from for each table, as well as the option to navigate back to a prior table in the navigation stack. However, these controls weren't obvious or easy to recall for many users. We have changed the design of the navigation "tabs" and essentially reversed the button functionality to better align with what users expect, as follows:
    • The entire tab is now a “button” to return to the prior table nav (functionality previously tied to the tiny "embedded" arrow button).
    • The tiny arrow button has been replaced with a larger (info) icon that can be selected to show the source record the user navigated from, without actually navigating to that table (functionality previously tied to the rest of the tab area)
  • The experience of accessing a chart from a report/dashboard has changed. The prior [Open View] button on a report has been changed to an [eye] button and the associated behavior has changed to enable full screen interaction with the chart. The [Open View] button which displays a view of the source data in the chart when selected, has now moved to the chart level, so it is still accessible with one extra click. The drill down experience from the report/dashboard (selecting a chart segment to see the source data) is unchanged. The new button experience enables additional chart interaction identical to accessing the chart from its summary card.
  • Label on Views visual mode switcher is now "Display." The prior "View" label could be confusing given the specific definition of a ShotFlow "View," so it was changed to avoid using the same term for a different function.
  • Label on Chart dynamic filter function is now "Advanced Search." The prior "Filter" label could be confusing given the revised Filter vs. Search terminology established with the SuperViews release, so it was changed to align better with how Views work (any dynamic search that is not going to be configured with the object is no longer a "filter").
  • Default interval selection is now Days instead of Minutes. When configuring time-based functions for searches, the default interval is now days, which is the most common selection, instead of minutes, which is much less popular!
  • Permissions header changed from "Labels" to "Table Labels." This will group all permissions that now live under the Tables header together in the permissions panels.
  • Removal of inactive "replace any existing relationships" checkbox when updating a many:many relationship via action button. This message was grayed out in prior state but could be confusing for a user, as it was not applicable to a many:many action (only a one:many action). It has been removed for clarity.
  • Events can utilize the same field for both Start Date and End Date. In prior state, configuring an event required two separate date fields for start date and end date functions. If the user selected the same source field for both dates, an error was thrown and the event could not be saved. Now, a single date field such as Due Date can be used for both the start date and end date event values.
  • App name field is limited to 40 characters. This prevents creation of apps with names that are too long for proper display in the UI.

 

What Did We Fix?

  • Not Equal Boolean logic doesn't return value of null. Previously, when applying filters or searches where a field is set to not equal some value, the return data wasn’t include records with values of null. Now it does!
  • Tooltip panel for stacked horizontal bar charts displayed differently than other chart types. Previously the tooltip panel that appeared when hovering over a horizontal stacked bar chart reported all the values for the bar (not just for the current segment) and it also included results with zero values. This was not aligned with how other chart type tooltip panels worked, and it sometimes resulted in a panel too large to see properly in the UI. This functionality is now updated to only show value(s) for the current bar segment (not the whole stack), to align with other chart types and the expected behavior when drilling down to source data.
  • Unable to see Purge tables without Delete Table permission. The Purge Tables permission was dependent on the Delete Tables permission, but should not have been, and no longer is.
  • Text display in action button panel shows html code attributes. This resulted in extraneous characters displaying the action button panel in cases where the source value has HTML formatting. Fixed!
  • Error after deleting a record that was opened directly (not from a View). This is weird one you probably never saw, and now you won't get that chance.

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