Dubai Update 3

Welcome to the documentation for the Dubai Update 3 release!

Don’t hesitate to send your feedback on these new features as we improve the product:

Major features

  • Client-side validation: A long requested feature that looks at field values and ensures they’re in the correct format before users attempt to save—offering them helpful feedback on how to update their fields to meet specific requirements. This feature allows for custom validations using formulas and snippets, as well as the following standard field type validations:

    • Date
    • Email
    • Social security number
    • URL

    This example uses a snippet to ensure the field value only contains lowercase and capital letters. Numbers, symbols, and other characters will cause the validation to throw an error.

This is an example page with sample data. The data resets each time the page is loaded.

Released in beta

Beta features represent valuable Skuid additions that we offer to cutting-edge builders for feedback before we mark them as generally available.

  • Skuid Database CSV import and export (NLX only): Now it’s possible to get data into and out of your Skuid Database—our own in-platform database designed from the ground up to work in NLX environments.

Released in pilot

Pilot features are not yet intended for prime time production use, but they are available to select customers to gather feedback as we prepare them for a broader audience.

To request access to features listed below, contact product@skuid.com.

  • Continued improvements to NLX’s page dependency features, including performance enhancements and locking names of pages used in Page Include components to safeguard page references.

    • This feature is activated for all new sites, but existing sites must request access.

Other updates

  • We’re continuing to make building complex forms easier than ever:

    • You can now style navigation items in the Design System Studio. These items appear in Navigation, Vertical Navigation, and Wizards that use navigation progress indicators.

      This allows for more intuitive navigation experiences when combined with style variant conditions, such as navigation items updating in response to user actions / data changes or navigation items that display unique cursors for disabled states.

      If you utilize a more advanced Navigation/Vertical Navigation + Wizard combination, you can implement ideas like:

      • Highlighting the user’s current step in a primary style
      • Calling attention to steps that contain incomplete field information
      • Reinforcing step completion with a success style

    • For Wizard components, we’ve added the ability to enable the Disable step buttons property but still style the disabled step buttons.

      Previously, this property meant step buttons always appeared disabled. With this update, Wizard experiences can now feature step buttons you can style to match your designs, but those buttons do not allow users to navigate the Wizard out of sequence.

    • We’ve improved the spacing of Form fields in the Composer, more closely aligning the label and field types in the canvas. This makes Form components easier to scan and read for builders when creating longer, complex experiences.

  • In the Composer, we’ve added the ability to sync design system changes without refreshing the entire page.

    Previously, when design system changes occurred in another window, you had to refresh your page to see those changes, which was likely disruptive as you built your page.

    Now, you can see design system changes reflected in your page without a full refresh in two ways:

    • Click dots-vertical Open design system options > Refresh next to the design system page property
    • Click refresh Refresh style variants beside any Style variant property

  • We’ve updated NLX to fully transition sites to an app-centered development feature set.

  • We’ve added a new tooltip style that takes up less room than the icon: tooltip as underline.

  • Some model APIs appear differently in Chrome browser, but they work the same. If you use skuid.debug.page() to access these APIs at runtime, you may find information you’re looking for in a slightly different place.

    While all APIs and attributes are still accessible, some internal API changes mean some attributes (most notably skuid.model.Model.data) are now inherited from the prototype chain instead of residing on the Model object directly. While this has no effect on snippet logic, it causes Chrome browsers to render in-console information a little differently.

    Whereas before the data attribute was near the top of the returned object information, in Dubai Update 3 this attribute appears in a dimmed style at the bottom of the returned information:

    Note

    As a reminder, while skuid.model.Model.data can be useful for debugging, do not use it directly to adjust model data. Use skuid.model.Model.getRows() instead.

  • We’ve fixed an issue with on-click actions for Scatter and Bubble type charts.

    Previously it was possible to set on-click actions for Scatter and Bubble type charts in the Composer, but these actions were not accessible at runtime. With this fix, on-click actions now run as expected for end users at runtime in Scatter and Bubble charts.

    We’ll also be pushing this fix to some older, but still supported versions of Skuid.

Included tickets

APPS-2003

In Skuid SFX’s page pack creation modal: - Better indicate only loaded pages are added by “Add all” button - Check that page packs do not exceed static resource max file size (5MB) - Adjust modal copy

APPS-2122

In Skuid SFX, add link to “About” page in Skuid’s Help menu

APPS-2137

In Skuid SFX, ensure a module’s full title can display on hover if it must be truncated in the UI

APPS-2158

In Skuid Database, add link to “About” page in the UI’s help navigation section

APPS-2179

Add the ability to access page revisions from the Composer’s XML editor view

APPS-2198

Fix bug with “About” page’s release notes link for patch releases ending in “.0”

APPS-2205

Adjust padding at the bottom of the XML Editor

CORE-3610

Incorporate on-click actions for series in Scatter and Bubble type charts Previously it was possible to set on-click actions for Scatter and Bubble type charts in the Composer, but these actions were not accessible at runtime. With this fix, on-click actions now run as expected for end users at runtime in Scatter and Bubble charts.

CORE-3617

Add field value validation for social security numbers, emails, URLs, and date formats

CORE-3636

Add support for HTML in child relationship field templates in List and Table components

CORE-3713

Add navigation items as a stylable element in the Design System Studio

CORE-3823

In the Composer, add the ability to sync any design system changes without having to refresh the browser window

CORE-3836

Client-side validation: Expand number of compatible field types

CORE-3874

Hide character length properties for Salesforce rich text fields—which do not support max character/length properties

CORE-3889

Adjust spacing within Form components in the Composer canvas to improve readability

CORE-3914

In the “Adopt rows into model” action, add option to append/prepend rows

CORE-3919

Fix issue where dragging a button from a Button Set component into a Wizard component would result in the button appearing in both components—even though it was removed from the original Button Set component

CORE-3924

Fix Composer issue where interacting with a filter in the canvas—but not making changes to that filter—would sometimes cause the Save button to enable as if there were changes to the page

CORE-3925

Improve condition detection on models used as inputs within action sequences Previously, when using a model as input for an action sequence, invoking that action sequence and trying to select a model condition to update would display inaccurate condition options. While this was not universal, this change ensures more accurate condition options appear when invoking an action sequence that updates an input model’s conditions.

CORE-4346

Prevent editing of a principal page’s Masthead component from within its dependent pages

CORE-4351

Adjust custom formula function boilerplate template

CORE-4359

Fix Composer regression where template fields could not be editing within a Form in the canvas

CORE-4362

Allow the deletion of a step that was previously the first step in a Wizard component without having to refresh the Composer

CORE-4363

Fix bug where “Adopt rows into model” action would create duplicate rows if no row ID was available

CORE-4372

Internal optimizations for deployment sizes

CORE-4378

Implement the ability to set style variant conditions for navigation items

CORE-4379

Internal developer tool improvements

CORE-4384

In the Design System Studio, fix issue where “More Options” menu for style variants appears offset incorrectly

CORE-4387

In the Design System Studio, ensure “Background Color” property applies to navigation item style variants

CORE-4388

Adjust Wizard component action copy to use “layout” instead of “direction”

CORE-4392

Fix “cannot access Symbol(PageContext)” console error in Composer

CORE-4393

Fix issue where top-level items in the Horizontal Navigation component would not display the proper style variant for those items

CORE-4395

Fix positioning of dropdown caret in Table component’s Visible Rows property

CORE-4406

Update navigation item icon

PLIN-3630

Resolve intermittent “connection reset by peer” errors when querying PostgreSQL data

PLIN-3648

For SQL data sources, ensure that picklist entry position is saved correctly

PLIN-3736

Fix bug where having model conditions on SQL data sources would cause searches from Table components to break at runtime

PLIN-3774

For SQL data sources, implement backend logic ensure that picklist entry position is saved correctly

PLIN-3891

Allow picklist entry order to be set in data source objects

PLIN-3902

Remove internal formula function from Composer function list

PLIN-3923

Backend code consolidation related to app dependencies

PLIN-3945

General design adjustments to Skuid Database CSV import experience

PLIN-3946

In Skuid Database CSV import, autoassign fields created when mapping an imported column

PLIN-3960

Internal adjustments for Skuid CSV import/export release

PLIN-4015

Fix copy error in Skuid Database

Skuid Database data import/export

The following tickets were related to the general develop of the Skuid Database data import/export features

CORE-4341, INTEG-128, INTEG-133, INTEG-135, INTEG-136, INTEG-140, INTEG-141, INTEG-185, INTEG-214, PLIN-3694, PLIN-3711, PLIN-3729, PLIN-3775, PLIN-3833, PLIN-3834, PLIN-3835, PLIN-3837, PLIN-3851, PLIN-3852, PLIN-3853, PLIN-3854, PLIN-3855, PLIN-3856, PLIN-3861, PLIN-3871, PLIN-3900, PLIN-3903,

Future feature development

The following tickets represent internal code changes made for future features.

APPS-2174, APPS-2175, APPS-2176, APPS-2177, APPS-2178, APPS-2180, APPS-2182, APPS-2185, APPS-2186, APPS-2187, APPS-2188, APPS-2189, INTEG-125, PLIN-3693, PLIN-3718, PLIN-3728, PLIN-3730, PLIN-3785, PLIN-3862