20249 September 2024
Article Type: Release Notes Audience: All Users Module: Platform Releases
Happy fall, everyone! The September 2024 release is packed with features and improvements we're delighted to share. Read on to learn more!
First up, this month's release includes two new screens designed to improve the ability of app builders to inspect and manage the app development process: App Component References and App Component Changes.
This new screen allows application builders to quickly understand what relationships exist between the various components of an app. As apps grow in complexity, it can become difficult to understand how the various screens, flows, and data models interact, which can lead to more issues when trying to make more significant changes.
The App Component References system analyzes screens, flows, and data models as they're edited to track the "source" (where the reference is configured) and "target" (what the reference points to) of various kinds of references: action buttons, web flows, query and mutate nodes, field relationships, and more. These references can then be quickly queried to find, for example, everywhere in the system that a particular data model is used or every flow that a screen executes. Where possible, information is included on what element (screen element, flow node, or data model field) the reference is tied to.
Users can filter by the source and target component type (screen, flow, or data model) and component and can quickly jump to a given component from this screen.
Planned future work for this system will expand the components inspected to include saved scripts, saved queries, and more, increase the detail of the reference information to include more element-level information, and bring this information into a graphical diagram view in the application designer.
Note: This screen will be renamed to App Component References in the 2024.10 release.
In addition to understanding the relationships within an app, it's often helpful for an app builder to be able to identify all changes made across an app within a specific date range - say, since the app was last updated or published. The new Application Element Changes screen does just that, displaying condensed data change information for all screens, flows, data models, and more since a given date.
The September 2024 release includes several new or significantly revamped UI components and screen elements that we're very excited about - a new Monaco-based JSON editor and a GraphQL predicate builder!
We're very happy to announce the first in a series of changes which will significantly improve the user experience with our code editors. With this month's release, JSON editors throughout the Fuuz platform will now use the Monaco editor - the same UI used by applications such as Visual Studio Code.
There are several great features built into this new editor. Users can now use right-click context menus to perform common actions; for less common actions, the F1 key opens the Command Palette, which allows users to search all available actions and displays the hotkeys for those actions.
This new editor also comes with much improved find and replace capabilities compared with the legacy editor, and in expanded mode displays a "minimap" of the code next to the scroll bar, displaying the section currently viewed and supporting quick navigation.
In upcoming releases, we'll roll out this new editor language by language, replacing Javascript, GraphQL, and JSONata code editors until we're using this new editor everywhere. Those languages will come with significant improvements to the snippet and autocomplete systems - keep an eye out for those highlights!
This release introduces a screen element aimed at complex reporting and data display screens: a new GraphQL Where Input! This element can be dropped into the filter form for any table right alongside any existing filters, which will be combined with any filters applied through this new input. There it will allow users to filter data by any field on the data model simply by adding a rule, selecting a field and predicate, and typing or selecting a value.
If users select a relation, they're able to filter by fields on the related data model, which is great for parent/child relationships or filtering by status, type, or category.
Finally, for more complex situations, the input allows for creating groups of filters with and and or logic between them - allowing for a significant amount of flexibility.
In coming releases, we'll integrate this new input into various tools and designers in the platform including the API Explorer, Data Flow Designer, and the Screen Designer itself, as well as adding it to various system screens where this level of filter flexibility would be handy!
With our recent upgrade to MongoDB 8, we were able to add support for several new aggregation operators in our Aggregate Query Framework in version 2024.9. These operators allow more streamlined inspection of aggregated data:
-
uniqueCountreturns the number of unique values in the group (e.g. unique inventory containers moved each week). This operator uses exact value comparison. -
medianreturns the median of the grouped numerical values. -
percentileallows users to specify a list of requested percentiles, and returns an array of numerical values for each of the requested percentiles (e.g. the 90th and 99th percentiles for work order completion time).
We're already using these new operators in our Data Flow Metrics Dashboard, where they're allowing us to display aggregated information about millions of data flow node executions. Check them out!
The 2024.9 release includes a very simple data import screen specifically focused on making it easier to move data between Fuuz environments. It can also help simplify importing data from external systems. Paired with data exports from tables, this screen should reduce some of the management overhead when migrating data between QA and production environments, for instance.
This screen is just the very first step in a longer initiative to build out fully-featured data export and import capabilities in the Fuuz platform. A fully configurable and schedulable data export system is slated for Q4, and a more flexible and easily configurable data import system in planned for Q1 of 2024. Those features will be highlighted when they're released, so keep an eye out!
Finally, this month's release includes updates to the Data Flow Designer and Schema Designer to standardize the panel layout with our Screen Designer. This new layout condenses the Toolbox panel, previously on the left, into a tab on the right-hand side of the screen. This comes with a new feature - just like the screen designer, you can now quickly jump to a section in the properties for a selected data flow node or data model.
This new arrangement ensures consistency across our designers and results in a much better UI experience when combined with our Application Designer.
- Updated UI to combine Toolbox with the right-hand panel, standardizing UI with the Screen Designer
- Added simplified client-side data import screen
- Added
median,percentile, anduniqueCountaggregation operators to Aggregation Query framework - Added validation to ensure
whereinputs for mutations have exactly one field and not 0 or more than 1 - Updated data change capture to ensure Changed At and Changed By User values are consistent between mutations
- Added Operation field to data change capture records, indicating the operation type (create, update, or delete)
- Corrected an issue that could cause delete mutations for models using Cascade Deletion to fail
- Improved error messages for partial or malformed Authorization headers
- Updated Policy Editor to correctly display screens with multiple routes
- Updated Authentication Event logging to retain authentication failure logs for 5 years
- Updated Tenants table to disable edit actions on non-administration tenants
- Added ADP Vista integration connector and data flow node
- Updated Native Printer driver to correctly encode
UTF-8characters - Updated logging for Edge Gateway flows to reduce log file size
- Added an Input Schema configuration option to Notification Channels, validating the shape of the input data prior to sending notifications
- Implemented publisher validation for maximum message size
- Updated data flow logging to omit context and payload fields to reduce message size when required
- Updated data flow metrics to pull correct message IDs from source nodes and to always collect metrics from Response nodes
- Updated Data Flow Metrics Dashboard to use aggregation queries instead of client-side transforms, enabling wider date ranges and larger volumes of metrics
- Updated UI to combine Toolbox with the right-hand panel, standardizing UI with the Screen Designer
- Updated package management to better handle and recover from schema deployment errors
- Updated form inputs to display a loading spinner while running initial transforms
- Updated Select and Date/Time/Datetime inputs to correctly re-run form validation on change
- Implemented Monaco editor for JSON type inputs
- Implemented Predicate Builder input element
- Reimplemented Array Input component to add support for a broader set of input types
- Corrected a bug that could cause default values for Table components to not apply during auto-load
- Updated Cards screen element to update its transform context with updated data when child elements change
- Added a configuration option to delay running page load flows
- Updated Auto-save option to persist setting between sessions and page reload
- Added a configuration option to control whether the Table element's data transform should run locally or remote
- Removed support for changing screen designer tab type within the Tabs panel
- Added Application Component References screen to allow easy introspection of relationships between app components
- Added Application Element Changes screen to streamline identifying all changes made to an app since a certain date
- Added support for dragging data models from Application Navigator into Schema Designer tabs
Source: support.fuuz.com