What’s New in Skuid?

Millau Update 2 - Update Release

We’re always looking for better ways to help our customers efficiently and elegantly create exceptional user experiences. This drives our product roadmap and informs our desire to constantly update and iterate. Here’s what we’ve been up to lately.

Big Announcement

Skuid Millau Update 2 brings powerful enhancements to Skuid’s ability to extend Salesforce. Skuid already works like a “super component” when using the Skuid Page Lightning component or Skuid Page Assignments Lightning component, replacing the need to write code for a custom Lightning component with a declaratively-built Skuid page. Millau expands Skuid’s presence within Salesforce Lightning by enhancing functionality, increasing inter-component communication, improving performance, and bolstering Skuid’s feature set.

Skuid pages can now seamlessly communicate with standard Lightning components—sending out and responding to events that update your Salesforce data. Update an account in your Lightning component? Any Skuid Page components on the same page will automatically requery their Account model to match that new data.

All you have to do is enable a new model property; no need to write a custom Lightning component or configure an event listener. No more programmatic fixes or manual page refreshes required!

New Product Features—Skuid

  • Need to activate some component-specific actions? Look no further than Run Component Action! Using this new action, you can navigate the steps of your Wizard components and change the edit mode of your Table and Field Editor components from anywhere the Action Framework is accessible. Use this to create intuitive experiences that respond to your users’ needs from Button Sets, model actions, and so on.

  • Re-use the output of model-related action types, like Create New Row(s) and Query Model, within an Action Sequence or a set of actions. Assign a label to the output of an action and use the label to recall the output within a subsequent action. The named output acts like temporary storage for data within an Action Sequence or series of actions.

  • Additional data source actions are now available to manage the Salesforce Approval process, including the ability to approve, recall, or reject approval requests, or unlock records that have been submitted for approval.

  • It’s now possible to cache Salesforce metadata in Skuid. Pages that utilize lots of models, with large picklists, and many fields will now load much faster because Skuid won’t need to fetch all of that data on each page load.

    Note

    These performance gains are only available when deploying within Visualforce or accessing Salesforce data from Skuid Platform. They are currently not available in Lightning Experience.

New Product Features—Skuid Platform

Minor Updates

  • Want users to remain in Offline Mode until revisions have finished syncing, even when they regain a connection? Now you can. Select Display Unsynced Changes Status Bar in the Offline Mode settings. Skuid stays offline, and all changes made (both on and offline) are stored until the user selects Sync from the status bar.

  • Add interactions, like click, swipe, or press, to the Wrapper component itself, not just the components inside the Wrapper.

  • Assign unique Ids and/or CSS classes to items within the Navigation component, making them easier to style and toggle-able at the same time!

  • You can now edit any model fields used in template fields within either Field Editors and Tables by double-clicking them, which opens a popup prompting the user for input.

  • Turn on or off the loading indicator for a page displayed by the Page Include component in the advanced properties of the Page Include component.

  • The Table Export automatically includes the Name field for reference fields when exporting Table data. Previously, the output of a reference field included the ID without the Name field. With the Name and ID field exported on each reference field, the output from a Table is easier to interact with when used in a spreadsheet.

  • We’ve published a new CLI release that allows you to pull specific Skuid pages within Skuid on Salesforce as opposed to downloading all of the pages within a Salesforce org or page module. Get only the pages you need.

  • Use DynamoDB? How about secondary indexes? Now you can query against them in Skuid! Secondary indexes allow for querying table data using something besides its primary key, and they can even be customized to return less data, which means faster queries for your pages and a lower cost on your AWS bill.

  • We’ve upgraded our Ace code editor, which is used wherever code is entered into the Skuid App Composer, to the 1.33 release.

  • The Search component already supports a limit to the number of records returned in the search dropdown list, but a new property, Result Limit, allows a record limit on each returned object for the results displayed in a search popup.

  • The Skuid theme that is based on the Lightning Design System now includes the most recent updates to Lightning’s markup and style. Skuid’s updated Lightning Design theme creates a consistent look-and-feel across your Lightning and Skuid components in Lightning Experience.

    For more information about the Lightning Design System, check out the latest Salesforce release notes.

  • We’ve refreshed the look of our settings page within Skuid on Salesforce. Primary navigation areas are now placed on a left-side tab bar for a cleaner visual experience and parity with the Skuid Platform settings page.

    No worries; you’ll still find your settings where you expect and our docs still reflect where to find all the properties you need.

Heads Up!

Skuid on Salesforce: Upgraded Salesforce API version to 42.0

Skuid on Salesforce is now running Salesforce API version 42.0, which enables you to use Skuid models to access Salesforce objects only available in API version 42.0. See Salesforce documentation for more details about this API version.

Skuid on Salesforce: Improved JavaScript Error Reporting when Skuid Page Not Found

In Lightning Experience, an invalid Skuid page name no longer generates JavaScript errors in the console. The Skuid Page component will instead report that the page has not been found.

Model Query Actions Now Fail If Their Model Does Not Exist

In previous versions of Skuid, when a model query action ran, the action would continue even if the model did not exist and no model was actually queried. This can be an issue if models get renamed and the actions that query them are not updated to reflect new models names; the user would never know their data isn’t updating. Skuid now registers this behavior as a failure and will alert the user to it. If you begin to see errors with your model query actions, ensure they are targeting a valid model within your page.

Left Bar Tab Set and Right Bar Tab Set Use the CSS Overflow Property

Dropdowns in the Tab Set (when the tab navigation was set to Left Tab Bar or Right Tab Bar) were clipped when the size of the Tab Set’s height didn’t fit the navigation content. The CSS for the Tab Set now uses the overflow property. The dropdown will expand to fit the navigation content without clipping.

Note

This property is not fully supported by IE9.

$PreviousAction Displays Results More Consistently

The $PreviousAction merge variable now lists the values of a returned SObject directly within the result node: $PreviousAction.result.<sobject_field_api_name>.

Prior to 11.2, these results were stored under the output node: $PreviousAction.result.output.<sobject_field_api_name>.

The Create New Rows Action Now Functions As Intended within Field Editors

The Create new row(s) action creates new rows in Skuid models, and through its Have associated Components initially show this row in… property, admins could set which mode (Edit or Read) the new rows would be displayed as. In previous versions of Skuid, this property would have no effect on Field Editor components, meaning new rows always displayed in Read mode when created. As of Skuid 11.2 this behavior has been corrected, and Field Editors will also display new rows as specified in the Create new row(s) action. Because of this, Field Editors may display rows in Edit mode where they previously did not. This can cause issues for snippets that analyze the HTML and expect rows to be in a certain mode. Ensure that your Field Editors display newly created rows as expected.

Components Nested in Decks and Render Conditions

Deck components render cards for each row in a model. Formerly, a card of components within a Deck would only check against the first row. That means you can render and unrender components based on row data. Only want to show a Field Editor for certain types of contacts? (Maybe a Button Set for accounts over a certain value?) Now you can! With 11.2, those components can utilize render conditions that look at their context row.

Note

If you’ve implemented render conditions on components within a Deck in the past, you’ll want to update them as they’ll now be considering _a different row_.

The UI-only Model Property for Warning the User of “Unsaved Changes” Now Defaults to False, or Unchecked.

The default behavior of the UI-only model property, Prevent users from leaving page if this Model has unsaved changes, now defaults to false because many more app builders turned “off” this warning than left “on” the warning.

Failed to Execute ‘setItem’ on ‘Storage’: Local Browser Storage Needs to Be Cleared

If your Skuid page fails to load, you may see this error at the top of the page or within your browser’s console. This means that your local storage may be full and needs to be emptied. How to do this varies depending on your browser:

Google Chrome

Firefox

Microsoft Edge