Nintex Apps for Salesforce release notes

Note: Skuid SFX is now Nintex Apps for Salesforce.

We support the current and previous major releases. Both will be updated periodically with maintenance releases and hot fixes.

Release type Description Cadence
Major Collection of key features, new architecture, performance improvements, bug fixes. Yearly
Update Collection of key features, performance improvements, bug fixes. Every 6 weeks or as needed
Maintenance Bug fixes only. Every 2 weeks or as needed
Hotfix 1-2 bug fixes focused on a critical issue. Rare, only as needed

Important: Nintex Apps for Salesforce versions 17.8.5 and above only have the Page Designer enabled by default for new pages. Existing pages will open in the Composer where they were created. If you require access to previous Composer experiences, reach out to account manager with your Salesforce org Id.

Latest release: 17.9.5: 2025-09-04

Download links:

  • Page Designer:

    • Updated labels for Deck, List, and Table component footer properties improve consistency across Nintex Apps.

    • Improved Page Designer performance.

    • Improved handling for unsupported field types. Sometimes, connections have field types that are not yet supported by Nintex Apps. In the model data area, unsupported field types are designated with a distinct icon. These fields cannot be added to the model.

    • Fixed an issue where table headers displayed field names instead of labels for SQL connections.

    • For more information, see the Page Designer help topic.

  • Connectors:

    • You can now set up and use connection variables to store connection settings instead of static setting values. If you move the application with the connection to another environment, the connection variable is also moved, but the value in it is not. This feature allows the values to be different in each environment. For more information, see the Connection variables help topic.

    • The database URL port and database host/IP address for SQL connections are combined into one database URL field.

    • Clarified parameter condition description text in legacy REST models. For more information, see the REST help topic.

    • The Authentication Providers tab is no longer available in the Connections page. Authentication providers are now configured inline for all connector types.

  • User and session management:

    • As an improved security measure, platform-managed users (those using an identity provider or Nintex authentication) can no longer use a Nintex Apps username/password to authenticate. They must use the platform-configured authentication method. They also can no longer request a password reset or have their password reset by the admin through the manage users experience in Nintex Apps.

    • The create and import manage users actions are de-emphasized in tenants that are connected to Nintex Workflow. All user management should be completed in Nintex Workflow.

    • For all new tenants, the rights a user has in Nintex Apps will be dictated by the role they have in Nintex Workflow. Upon login, users assigned a Participant role in Nintex Workflow will be assigned the Standard site permission set in Nintex Apps; all other users will be assigned the Admin site permission set. This removes the need to separately assign Nintex Workflow Designers as Designers in Nintex Apps. Existing tenants will also have this feature enabled where it doesn't conflict with any existing authentication and authorization settings.

      For more information, see the Nintex Workflow and Nintex Apps connected user management help topic.

    • User properties, including name and email address, can no longer be updated by users in Nintex Apps if their account is managed in Nintex Workflow.

    • User properties, including name and email address, can no longer be updated by admins in Nintex Apps if their account is managed in Nintex Workflow. Site permission sets, locale, and timezone can still be configured in Nintex Apps.

    • Upon logout, users are now presented with a Signed Out page instead of being directed back to the login page. This provides a more consistent experience with Nintex Workflow and ensures the default single sign-on behavior is always respected. Users that require a Nintex Apps-Only username/password can still access the login form at ui/login on their tenant.

    • The Site Permission User Signup feature is no longer available by default. If you require it, request enablement from Support.

  • General bug fixes:

    • You are now able to take a product tour from the Help menu. Simply click Help > Take Apps Tour to begin.

    • Improved login behavior after timeout. When a user's Nintex Apps session expires and they click the Log In button, they will be directed through the organization's default login flow. Previously, users in some tenants with multiple authentication options were directed to choose from a list they may not have been familiar with.

Previous releases

Download links:

  • Page Designer:

    • The new Page Search feature allows you to easily search for page elements in the Page Designer, especially on long pages and pages that were built by others.

    • Updated tab naming conventions to clearly differentiate between editing and preview modes, reducing confusion when multiple tabs are open. Now Page Designer tabs will use the convention Page Name - Edit and preview tabs will use the convention Page Name - Preview.

    • Improved interface for selecting multiple fields in the Search component.

    • Fixed an issue where Table component search did not allow adding search fields when using MSSQL or Postgres data sources.

    • For more information, see the Page Designer help topic.

  • General bug fixes:

    • Salesforce: Restored the ability to use merge syntax in the Submit for Approval action.

    • Salesforce: Fixed an issue with the ServiceAppointment object where Name was improperly included in model queries.

    • Fixed an issue where field from another model type conditions were not being created correctly.

Download links:

  • Page Designer:

    • Fixed an issue where Toggle filters created in the Page Designer were not displaying labels properly during runtime.

    • Implemented improvements for updating styles for a page's design system and updating the list of available design systems.

    • For more information, see the Page Designer help topic.

  • General bug fixes:

    • Fixed an issue where calendar event source colors wouldn't render correctly at runtime.

    • Fixed an issue where calendars in Table drawers were not rendering properly at runtime.

Download links:

  • UI-only model properties: These properties now include Label and Plural label fields.
  • Variables panel: Now available in formula builder.

  • General bug fix: Fixed an issue where searching and selecting a model field made the checkboxes disappear.

Download links:

  • Page Designer: Fixed an issue where component properties wouldn't load.
  • Form component: Fixed an issue where the properties sections were out of order.

Download links:

  • Current REST connector: It is now easier to create conditions on current REST models:

    • Added a parameter conditions area for URL parameter conditions.

    • Fixed issues related to creating client-side conditions.

    For more information, see the REST help topic.

  • Page Designer: Continued improvements to this workspace make it easier to use:

    • Clarified the help description for the Create default row property in models.

    • The Size and Spacing section of the Wrapper properties has been updated to Layout to be consistent with other components.

    • Improved the consistency of breadcrumb link styles at the bottom of the Page Designer.

    • Improved the reliability of keyboard shortcuts in Action flows.

    For more information, see the Page Designer help topic.

  • General bug fixes:

    • Fixed an issue where drag and drop would upload a file twice.

    • Fixed an issue where charts failed to re-render when resizing the browser window.

    • The Page Designer and Welcome to Apps tours are now accessible.

    • Fixed an issue preventing users from adding links to rich text fields in Lightning.

Download links:

  • Components:

    • You can now right-click on components in the Index or canvas to show a menu. This menu allows you to access nearby components and includes relevant options for the component in focus (such as clone, remove, and add fields or features).

    • The Components panel now closes when clicking on the canvas (or clicking outside of it).

      For more information, see the Components help topic.

  • Variables: The Insert variables panel now includes action flow inputs and outputs. For more information, see the Variables help topic.

  • Current REST connector: It's now easier to create models with multiple methods. Previously, you had to move back and forth between the Methods and Properties tabs to create models with more than one method. For more information, see the REST help topic.

  • General bug fixes:

    • Fixed an issue where the image height strategy could not be set to "Fit to content" in the legacy Composer.

    • Fixed issues with input fields in action flows.

    • Group by fields are now queried properly for Salesforce orgs with metadata caching enabled.

    • Adding fields from a reference relationship no longer adds duplicate fields to model.

  • Known issues: The Page Designer and Welcome to Apps tours are no longer accessible, but will be restored soon.

Download links:

  • Variables: The Insert variables panel now appears when templates are expanded. For more information, see the Variables help topic.

  • General bug fixes:

    • Fixed an issue where the toggle action property only opened the sliding panel action. For more information, see the Visual Navigation help topic.

    • Fixed an issue where Table interactions only worked on the first page of the table.

    • Silk icons are now available again.

    • Show errors inline in a Form component now work with Salesforce validation rules.

  • Known issues: The Page Designer and Welcome to Apps tours are no longer accessible, but will be restored soon.

Download links:

  • Page Designer: Improved the component search. For more information, see the Page Designer help topic.

  • Known issues: The Page Designer and Welcome to Apps tours are no longer accessible, but will be restored soon.

Download links:

  • Variables: The new Insert variables panel is now displayed for string value fields in an action flow. This is available while setting field values when updating a model or creating a new row. For more information, see the Variables help content.

  • General bug fix: Fixed an issue where filters would interfere with table field interactions.

Download links:

  • Variables: A new Insert variables panel allows you to easily add merge syntax in places like Text components and component headers. Variables can be inserted in any field that accepts merge syntax. For more information, see the Variables help content.

    Note: 

    We will be enabling additional variables functionality soon, including:

    • Displaying the panel for value fields in an action flow. This will be available when inserting values to start a Nintex Workflow or a DocGen Package, or while setting field values when updating a model or creating a new row.

    • Providing access to input and output variables from the panel in action flows.

  • Chart Context: A new Navigate to chart action (previously the Drilldown action) gives you the ability to connect charts in a chart set and pass data from one chart into the next one. In addition, you can add conditions to a target chart to filter data based on the end user selections from the source chart. For more information, see the Enhancing charts with actions help topic.

  • Action flows: Use new keyboard shortcuts (hotkeys) to quickly navigate, edit, and manage actions in the action flow canvas.

    • Delete (Mac) and Backspace (Windows) hotkeys make removing an action from a flow easier.

    • Use arrow keys to navigate through actions.

    • The Enter hotkey makes it easier to edit an action that you’re focused on.

    • The S hotkey allows you to skip an action in a flow.

    • Press Esc when focused on properties to return to the action.

    • Look at the bottom of the canvas for a hotkey legend. For more information, see the Action Flows help content.

  • Components: The usability of the toolbar has improved, allowing you to more easily remove components. For more information, see the Components help topic.

  • Page Designer:

    • Performance of the component drag and drop function has been improved.

    • Fixed an issue where Salesforce reference fields were not displaying in the table component field selector.

    • For more information, see the Page Designer help topic.

  • General bug fixes: 

    • Automatic context conditions now default to the appropriate Id field for the connection:  Id, id, or _id

    • Fixed an issue where some model behaviors changed on requeries.

Download links:

  • UI-only models: It is now easier to edit and remove UI-only fields. For more information, see the UI-only fields and models help topic.

  • [Beta] Page Designer Migration Utility: Fixed an issue with migrating modals with buttons in the body.

  • General bug fix: Fixed an issue where Nintex Apps for Salesforce pages were not responding to Aura events.

Download links:

  • [Beta] Page Designer Migration Utility: Fixed an issue where render conditions and condition logic weren’t migrating properly. For more information, see the Page Designer Migration Utility help topic.

  • Page Designer: 

    • Fixed an issue where the selected state was missing in List component properties.

    • Fixed an issue where connected components couldn't be selected from display logic statements.

      For more information, see the Page Designer help topic.

  • General bug fixes:

    • Improved the page import feature. Importing an XML file will now update the page name field if it is empty.

    • Fixed a problem where the Design System Studio would break when viewing a component with a style referencing a deleted color variable.

    • Fixed an issue with triggering invocable Apex from a page render event.

Download links:

  • [Beta] Page Designer Migration Utility: This utility helps existing users easily migrate from using the Composer to using the new Page Designer. For more information, see the Page Designer Migration Utility help topic.

    • Known issue: Some aspects of display logic aren't migrating correctly including render conditions, OR logic, and custom logic.

  • Page Designer: 

    • Fixed an issue with the scroll bar settings causing jitters in the Page Designer.

    • Fixed an issue where the guided tour wasn't displaying for new users.

    • Fixed an issue with the Navigate to Wizard Step action where the steps weren’t displaying.

  • General bug fixes:

    • Fixed an issue that occurred when entering a decimal value in a number field. Previously, the cursor unexpectedly moved to the beginning of the line.

    • Fixed an issue where the date format didn't respect Singapore user locale settings in Salesforce.

    • Improved the styling for Tab Containers with tabs displayed as accordions.

    • Fixed an issue where email standard client-side validation was no longer working properly for UI-Only email fields. Also, fixed an issue with filtering UI-Only formula fields.

    • Fixed an issue where sticky page footers weren’t working in runtime.

    • Fixed an issue where button sliding panels wouldn’t work when deployed in Lightning.

Download links:

  • Page Designer: The new Page Designer is the default experience for creating pages. For more information, see the Page designer help topic. Some of the many improvements to the page design experience include:

    • Vertical design with more space for the canvas

    • Preview style variants and display logic within the canvas

    • New action flow builder

    • Reusable display logic conditions

    • Index drag and drop

  • Salesforce API Version Upgrade:

    • The Salesforce API version has been upgraded to 62. This update allows users to access newer objects and fields like Grantmaking objects for Nonprofit cloud and VoiceCall Name in Service Cloud Voice.

Download links:

CORE-5709

Fixes table refresh error in runtime with reordering columns and sorting.

CORE-5810

Fixes responsive grid divisions with fit to content strategy extending beyond bounds of grid when content is large.

CORE-5893

Fixes an issue where an error message wasn’t shown when a save was unsuccessful for a specific Salesforce field configuration.

CORE-5636

Modernized the way Skuid fetches custom labels to be compatible with LWS.

CORE-5804

Fixed style variants not working for row action buttons.

CORE-5808

Fixed runtime issue where rich text field would duplicate its content when edited.

Download links:

CORE-5607

Updates logic used to set the language parser of the Monaco editor

PLIN-5965

Fixes an issue where the user could not fully cancel out of editing a picklist field, if the picklist entries were modified.

CORE-5536

Fixed the order in which styles are compiled, ensuring global page styling comes first. This allows custom styles to be better applied to components. Update any problematic design systems to see this effect.

CORE-5568

Fixed Lightning Rich Text fields issue where typing would cause errors, such as “i.getAttribute is not a function”

PLIN-6017

Fixed Data Console issue where editing an existing field and discarding the changes would cause a browser console error

CORE-5626

Fixed bug with model condition logic generated by adding an autofilter condition

CORE-5392

Fixed an occasional error where upon opening any page in any Composer/Page Designer experience, a banner would appear stating the “skuid” component pack was missing. While functionality was unaffected by this, the issue behind this banner has been resolved.

PLIN-5815

Fixed a regression in the new query engine that prevented models with child relationships from loading

PLIN-5964

Fixed a Data Console issue where the access control header would be present in unexpected views

PLIN-5999

Fixed a Data Console issue where picklist field drop downs weren't positioned correctly in the data table view

PLIN-5874

Fixed a Data Console issue where picklist entries would not delete properly until the page was refreshed

CORE-5372

Ensure the transparent Page component variant works properly insetad of always displaying a white background

CORE-5543

Ensure images with spaces in their file name display correctly

PLIN-4982

Data Source Console development

PLIN-5963

Data Console updated so that field columns in the data table are sorted by created date, rather than alphabetically

CORE-5166

Corrected two issues in the mass update process

PLIN-5530

As part of the Nintex connected experience, allow tenants to create an app package through the admin UI.

CORE-5752

Adjusted logic to better accommodate how recent Digital Experience changes affect Salesforce REST service calls—most notably accessing record type metadata for certain objects and for record type dependent picklists.

Download links:

PLIN-5968

Updated release notes links in the SFX and NLX Admin experiences to point to the new Nintex hosted documentation sites

CORE-5193

Dependency upgrades

CORE-5549

(SFX Only) Fixed an issue in SFX Lightning where charts would sometimes show as blank with errors in console

Download links:

CORE-5198

Security enhancements

PLIN-5795

On SFX, fix Pages list issue where users without “Modify Metadata Through Metadata API Functions” permission in Salesforce would see errors

PLIN-5828

On SFX, fix issue where Hyperforce Salesforce sites were unable to connect to SQL based data sources.

CORE-5413

Move Chat component and OpenAI data source out of beta

CORE-5466

Internal codebase improvements

CORE-5454

In the Ink icon library, add new icons: worfklows, upgrade, expand-alt and contract-alt

CORE-5456

For XML parser, recognize standard property names independent of their case.

CORE-5163

For Chat component, formatting, flexibility and stability improvements

CORE-5397

For Chat component, enhanced support for REST models

CORE-5317

Fixes new composer issues with tab and wizard components not saving correctly after a reorder change is made.

CORE-5496

Fixed an unreleased issue where HTML Tags were appearing in the runtime for a Navigation component with Allow HTML Enabled.

CORE-5495

Fixed an issue where sometimes selecting an OData object in the composer would result in an error.

CORE-5473

Fix New Composer issue where browser reported unsaved changes even when none were made.

CORE-5442

Fix for Design System Studio issue where code editor panel would not update when tabs were changed. Also, Fix for issue where code components within a modal could lose their data if opened and closed more than once.

CORE-5467

Fix Design System Studio issue where adding an API name to a variable would cause errors when trying to update components using the variable

CORE-5459

Fix Composer issue where Ui-Only fields were not shown in field-picker for display logic conditions

CORE-5455

Fix Composer issue where some Chat component properties would not update

CORE-5426

Ensure multi-picklist “Include filter” property defaults to being off

New Composer (Page Designer) development

CORE-4866, CORE-4999, CORE-5177, CORE-5348, CORE-5368, CORE-5380, CORE-5401, CORE-5403, CORE-5409, CORE-5410, CORE-5427, CORE-5439, CORE-5441, CORE-5445, CORE-5458, CORE-5474, CORE-5486, CORE-5490, CORE-5497

Dependency upgrades

CORE-5185, CORE-5408

Future feature development

CORE-5491, CORE-5501

Download links:

CORE-5049
Fix issue where newly added actions appear to remain as "Save model" actions, even when set to other action types. While only a label issue, and navigating away and back to an action list would resolve the issue, this misleading action list rendering behavior has been corrected.
CORE-5050
Fix Form component issue with date/time fields where browser focus would unexpectedly shift from edit mode before end users could complete time entry—requiring users to double click the field to re-enter edit mode
CORE-5051
Fix Table issue where drawers wouldn't display if end users hid the Table's leftmost column
CORE-5077
Fix record type ID lookups for reference fields that display as picklists—which previously had an issue where those picklists would appear as blank even after choosing a value
CORE-5090
Fix sub-navigation item issue where merge variables were not being processed properly for URLs within the item's Go to URL action
CORE-5127
Fix Salesforce mobile issue where, in addition to the native mobile date picker, Skuid's date picker would sometimes unexpectedly appear and sometimes remain even after picking a date

Previous releases (no longer supported)

Download links:


CORE-5426

Ensure multi-picklist “Include filter” property defaults to off

CORE-5420

Update page name uniqueness logic in SFX to allow pages to have the same name in different modules

CORE-5413

Move Chat component and OpenAI data source out of Beta

CORE-5406

Fixed issue when previewing a page with parameters, where the Page Parameters modal was not supporting type ahead

CORE-5405

Fixed an issue in the Composer where Search was not working as expected for Actions and Snippets

CORE-5404

Fixed an issue in Design System where the Data Grid Mode property Accordion was showing a Beta tag, even though the feature is no longer in Beta

CORE-5403

New Composer development

CORE-5402

New Composer development

CORE-5399

New Composer development

CORE-5398

Fixed an issue in the DB Console where text duplicates itself when navigating away and back

CORE-5397

For Chat component, enhanced support for REST models

CORE-5396

Fixed an issue in Design System Studio by removing three invalid nested component properties from the Table component: “Row (Table Header Row)”, “Row (Table Body Row)”, and “Row (Table Footer Row)”

CORE-5393

New Composer development

CORE-5379

New Composer development

CORE-5378

Fixed an issue in composer where Save/Cancel buttons were not always enabled correctly when opening Component Properties tab

CORE-5377

New Composer development

CORE-5376

New Composer development

CORE-5375

New Composer development

CORE-5373

New Composer development

CORE-5363

Fixed an issue in the composer in the Action Sequences and Javascript tabs where the empty state was being presented incorrectly

CORE-5362

New Composer development

CORE-5359

New Composer development

CORE-5358

New Composer development

CORE-5357

Fix appearance of trust policy example shown when AWS role is used as an authentication method

CORE-5356

New Composer development

CORE-5352

New Composer development

CORE-5350

New Composer development

CORE-5349

Fixed an issue in Lightning design system where the checkbox appeared pushed down and to the right of expected location

CORE-5347

Fixed a composer issue where unique IDs on Form and Page Include components were not being saved after clearing and setting new values

CORE-5346

New Composer development

CORE-5344

New Composer development

CORE-5343

New Composer development

CORE-5342

Fixed runtime issue where opening a Drawer in a Table with a fixed height will cover up the Table header

CORE-5341

Prepared codebase for packaging

CORE-5339

New Composer development

CORE-5337

New Composer development

CORE-5334

New Composer development

CORE-5329

Dependency upgrades

CORE-5323

New Composer development

CORE-5322

Fixed reference field issue where lookup filters in the Form component would not properly filter Record Type values

CORE-5321

Fixed a design system static resource issue where design systems would be stored as undefinedDESIGNSYSTEM instead of their actual names

CORE-5320

New Composer development

CORE-5318

New Composer development

CORE-5316

New Composer development

CORE-5315

New Composer development

CORE-5314

New REST data source development

CORE-5312

New Composer development

CORE-5307

Fixed a Design System Studio issue where filtering for color variants with "+" or "-" symbols would not work as expected

CORE-5306

Fixed a menu selection issue where end users could not select certain elements, like search inputs, when a select menu was open

CORE-5305

New Composer development

CORE-5304

New Composer development

CORE-5303

Added “Include filter” property for multi-picklist fields, allowing end users to filter available items at runtime

CORE-5302

Fixed a condition issue where expected operators would not appear for field types

CORE-5301

When renaming a model condition, ensured actions that use the condition reflect the updated label

CORE-5300

Fixed a Table component issue where adjusting styles on mass action buttons would cause an additional, empty button to appear at runtime

CORE-5299

Improved unexpected scrollbar appearances in the Design System Studio, particularly for color pickers and Chat component code blocks

CORE-5297

Internal code refactoring

CORE-5296

New Composer development

CORE-5295

Fixed an NLX issue where icons for the find/replace panel in the XML editor would not appear

CORE-5294

Fixed an authentication provider issue where additional token request body parameters were not being sent properly at runtime, which notably affected SharePoint data sources

CORE-5293

New Composer development

CORE-5292

New Composer development

CORE-5291

New Composer development

CORE-5287

New Composer development

CORE-5286

New Composer development

CORE-5285

Fixed a Calendar issue where event source actions were broken in the Composer

CORE-5284

Internal developer setup script improvements

CORE-5283

New Composer development

CORE-5281

New Composer development

CORE-5280

New Composer development

CORE-5279

New Composer development

CORE-5278

New Composer development

CORE-5275

New Composer development

CORE-5274

New Composer development

CORE-5270

Fixed an autocomplete/combobox issue where user drop-down selections were not captured when a component was in read with inline edit mode

CORE-5269

New REST data source development

CORE-5266

Fixed a Form component issue where boolean fields with label displayed on right displayed as "false" if component does not allow HTML

CORE-5263

New Composer development

CORE-5259

New Composer development

CORE-5258

New Composer development

CORE-5254

Fixed a "Run component action" issue where Form component actions would not appear if the component was in a modal that had not yet been opened in the Composer browser window

CORE-5253

New Composer development

CORE-5252

New Composer development

CORE-5250

New Composer development

CORE-5249

New Composer development

CORE-5246

New Composer development

CORE-5245

Fixed a Design System Studio issue where the color selection drop-down options would show color ID values instead of their labels

CORE-5244

New Composer development

CORE-5243

New Composer development

CORE-5242

New Composer development

CORE-5238

New Composer development

CORE-5236

Fix dependent page issue where action sequences could not be reordered in the Composer

CORE-5235

New Composer development

CORE-5234

Fixed a Design System Studio issue where spacing variables would display incorrect names/values and display JavaScript errors in the console

CORE-5233

New Composer development

CORE-5232

Fixed an aggregate model issue where client-side conditions would not properly update the model

CORE-5229

New Composer development

CORE-5228

New Composer development

CORE-5227

Adjusted combobox field input behaviors for existing field values so that all menu options appear on focus and when clicked. Previously, combobox inputs would filter based the existing field value—meaning users would first have to delete that value to see the full list of options.

CORE-5226

New Composer development

CORE-5224

Centralized and improved “Size and scrolling” properties and streamlined flex properties for a variety of components in current Composer as well as New Composer

CORE-5220

New Composer development

CORE-5218

New Composer development

CORE-5216

New Composer development

CORE-5210

New Composer development

CORE-5209

New Composer development

CORE-5208

New Composer development

CORE-5206

New Composer development

CORE-5204

New Composer development

CORE-5203

New Composer development

CORE-5199

New Composer development

CORE-5195

Fixed a Design System Studio issue where the color selection drop-down would not display type-ahead options

CORE-5163

For Chat component, formatting, flexibility and stability improvements

CORE-5154

New Composer development

CORE-5151

New Composer development

CORE-5144

New Composer development

CORE-5136

Fixed an inconsistent action sequence label issue for sequences created before EU3 that were event-triggered

CORE-5123

New Composer development

CORE-5114

New Composer development

CORE-5112

New Composer development

CORE-5073

New Composer development

CORE-5068

New Composer development

CORE-5035

New Composer development

CORE-5008

New Composer development

CORE-5006

New Composer development

CORE-5000

New Composer development

CORE-4944

New Composer development

CORE-4912

New Composer development

CORE-4805

New Composer development

CORE-4804

New Composer development

CORE-4795

New Composer development

CORE-4794

New Composer development

CORE-4793

New Composer development

CORE-4792

New Composer development

CORE-4779

New Composer development

CORE-4770

New Composer development

CORE-4708

New Composer development

CORE-4551

New Composer development

CORE-4444

New Composer development

CORE-5407

Future feature development

CORE-5361

Future feature development

CORE-5162

Future feature development


Download links:

CORE-5114

New Composer development

CORE-5306

Fix menu selection issue where end users could not select certain elements, like search inputs, when a select menu was open

CORE-5136

Fix inconsistent action sequence label issue for sequences created before EU3 that were event-triggered

CORE-5195

Fix Design System Studio issue where the color selection dropdown would not display typeahead options

CORE-5245

Fix Design System Studio issue where the color selection dropdown options would show color ID values instead of their labels

CORE-5234

Fix Design System Studio issue where spacing variables would display incorrect names/values and display JavaScript errors in the console

CORE-5236

Fix dependent page issue where action sequences could not be reordered in the Composer

CORE-5285

Fix Calendar issue where event source actions were broken in the Composer

CORE-5270

Fix autocomplete/combobox issue where user dropdown selections were not captured when a component was in read with inline edit mode

CORE-5232

Fix aggregate model issue where client-side conditions would not properly update the model

CORE-5254

Fix "Run component action" issue where Form component actions would not appear if the component was in a modal that had not yet been opened in the Composer browser window

CORE-5227

Adjust combobox field input behaviors for existing field values so that all menu options appear on focus and when clicked. Previously, combobox inputs would filter based the existing field value—meaning users would first have to delete that value to see the full list of options.
 

Download links:

CORE-5125

Upgrade timezone-related dependencies

CORE-5191

Upgrade Mustache and Moment libraries in API v1 to address security concerns

CORE-5052

Update labeling to reflect pilot status of new Composer

CORE-5107

Security-related dependency upgrades

CORE-5135

Security-related dependency upgrades

CORE-5096

Resolve design system file inconsistencies that appear when downloading the file from Skuid’s admin interface versus retrieving it via the CLI, which began after recent updates to streamline that file’s format

CORE-5155

Remove unused SFX labels from source control files

CORE-5174

Remove unnecessary content from exported design system JSON files

CORE-5175

Refactoring of chat data source actions for future development

CORE-5097

OpenAI data source (for use with Chat component) development

CORE-4946

On Skuid SFX, implement the JsonAccess annotation to correct unexpected behaviors arising from serialization logic—notably Skuid model saves—that would cause “Apex object cannot be serialized” errors.

CORE-5078

On SFX, adjust styles of components within Lightning Experience to account for Salesforce CSS updates

CORE-5248

Non-customer facing metadata API changes to facilitate build deployments

CORE-5120

Migrate to a newer, non-deprecated third-party library for some UI elements

CORE-5131

JS API additions to better test pages when loaded as included pages

CORE-5126

Internal file size logging improvements

CORE-5169

Internal code refactoring to address linting issues

CORE-5159

In new Composer, adjust process for renaming page revisions to utilize a modal for improved UX

CORE-5061

Hyphenate “Vertical top-level navigation” in the Design System Studio

CORE-5182

For Navigation and Vertical Navigation components in the DSS, add the ability to set font family—and improve the display and grouping of various text properties

CORE-5201

Fix Vertical Navigation issue where navigation items with the default “Go to URL” action would not respect design system styles, and instead always appeared as blue

CORE-5090

Fix sub-navigation item issue where merge variables were not being processed properly for URLs within the item’s Go to URL action

CORE-5127

Fix Salesforce mobile issue where, in addition to the native mobile date picker, Skuid’s date picker would sometimes unexpectedly appear and sometimes remain even after picking a date

CORE-5102

Fix Pages list issue where the Preview option would cause errors when pages required parameters—not opening the modal for setting those parameters and ultimately not previewing the page

CORE-5161

Fix new row creation regression where fields on the new row that were displayed as comboboxes would have their values cleared out when the row was saved

CORE-5098

Fix model regression where the child relationships sub-tab would not appear within the model fields tab

CORE-5150

Fix issue with UI-only filters where the inability to retrieve condition logic caused “getField is not a function” errors—particularly for date fields

CORE-5095

Fix issue with nested properties not properly updating the selected area

CORE-5167

Fix issue with “Last/Next n <unit>” related date property values, where number values were reset to 1 in the page XML instead of the entered number value whenever the date range value was changed. For example, if a user had selected “Next n weeks” and set N to 5, then changed to “Last n weeks”, the 5 would remain in the Composer but would be saved in XML as 1.

CORE-5100

Fix issue where “Warn users if page has unsaved changes” page property would unexpectedly revert to “Yes” even when set to “No,” which affected by standard page edits and v1-v2 page migrations

CORE-5239

Fix issue where the “Allow HTML” property would cause console errors in the Composer

CORE-5134

Fix issue where Skuid’s mass update modal would not function properly with number and currency fields—causing a call stack error

CORE-5176

Fix issue where setting a field’s label position to “Right of Input” on checkbox fields broke HTML rendering in labels

CORE-5149

Fix issue where “Hide label” property (A Form-exclusive property) appeared on Table component fields

PLIN-5354

Fix issue in Skuid Database where the CSV import view would not scroll, preventing users from seeing all fields that may be imported for CSV files with many columns

CORE-5044

Fix Header component issue where its buttons were not respecting record context after their first use, resulting in experiences where editing one record would unexpectedly update all records

CORE-5145

Fix Form issue where the component would attempt to render fields that were not in the component’s model. Notably this issue could occur when, due to user permissions, fields were removed from the model to prevent unauthorized access, but the component would still attempt to render those removed fields.

CORE-5158

Fix Composer issue where the “Custom field renderer” property rendered as a text input instead of a combobox

CORE-5115

Fix Composer issue where model fields and conditions were being unexpectedly removed when the builder selected the model within the model list

CORE-5117

Fix Chart component regression where series interactions were unavailable—instead appearing as an unusable text field within the Properties pane

CORE-5202

Fix Calendar component style issue where the changing the “Default color” value for an event on a Calendar in the Design System Studio would not properly update the color

CORE-5138

Ensure that UI-only picklist fields marked as required auto-select the first picklist entry, which is the current behavior for non-UI-only fields

CORE-5103

Ensure OpenAI data source functions with the API Keys authentication option

CORE-5119

Ensure consistency between SFX and NLX API calls for the OpenAI data source type

CORE-5132

Ensure Chat components configured for model rows display new rows as expected when their models are requeried

CORE-5094

Codebase and internal process enhancements to better avoid APIs noted as distorted by Salesforce

CORE-5128

Code base modularization

CORE-5106

CDN deployment config updates

CORE-5105

Adjust streamlined action sequence triggering behavior to account for issues surrounding what were previously event-triggered sequences

CORE-4967

Added HTML support in the following component properties through use of related “Allow HTML” toggle properties:

  • Button: Button label
  • Button Group: Label, when displayed as a menu
  • Wizard: Step labels
  • Header: Title and subtitle
  • Message Area: Title, as well as description
  • Search: In each return object’s header display name and display template
  • Toast (from the Show toast action): Message to display
  • Deck: Title
  • Table: Title, as well as column headers
  • List: Title

CORE-5076

Add “Beta” tag to Chat component and OpenAI data source type

CORE-5108

Add proper permissions for new Composer experience to Skuid Page Builder permission set

CORE-5223

Add “col” scope to Table column headers to improve accessibility for screen reader tools like JAWS

New REST data source development

The following tickets represent code changes made while developing the new REST data source:

PLIN-4923, PLIN-5173, PLIN-4994, PLIN-5370, PLIN-5310, PLIN-5255, PLIN-5186, PLIN-5197, PLIN-5211, PLIN-5301, PLIN-5362, PLIN-5270, PLIN-5350, PLIN-5225, PLIN-5194, PLIN-5043, PLIN-4996, PLIN-5268, PLIN-5435, PLIN-5170

New Composer development

The following tickets represent code changes made while developing the new Composer experience:

CORE-5147, CORE-4377, CORE-4355, CORE-5083, CORE-5113, CORE-5124, CORE-5231, CORE-4923, CORE-5165, CORE-5171, CORE-5173, CORE-5181, CORE-5110, CORE-5179, CORE-5099, CORE-4930, CORE-5152, CORE-5060, CORE-5172, CORE-5109, CORE-5168, CORE-5143, CORE-5074, CORE-5207, CORE-5114, CORE-5213, CORE-5058, CORE-4885, CORE-4943, CORE-5214, CORE-5111, CORE-5211, CORE-4803, CORE-4844, CORE-5062, CORE-5212, CORE-5170, CORE-5084, CORE-5153, CORE-5036, CORE-4807, CORE-5217, CORE-4884, CORE-5215, CORE-5221, CORE-4826, CORE-5240, CORE-5241, CORE-4965, CORE-5137, CORE-4541, CORE-4660, CORE-5081, CORE-4621, CORE-5089, CORE-5104, CORE-4475

Future feature development

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

CORE-3499, PLIN-5126, PLIN-5062, PLIN-4683, PLIN-4748

Download links:

CORE-5174

Remove unnecessary content from exported design system JSON files

CORE-5239

Fix issue where the "Allow HTML" property would cause console errors in the Composer

CORE-5248

Non-customer facing metadata API changes to facilitate build deployments

CORE-5256

Internal deployment script updates

CORE-5300

Fix Table component issue where adjusting styles on mass action buttons would cause an additional, empty button to appear at runtime

CORE-5302

Fix condition issue where expected operators would not appear for field types

CORE-5321

Fix design system static resource issue where design systems would be stored as undefinedDESIGNSYSTEM instead of their actual names

CORE-5322

Fix reference field issue where lookup filters in the Form component would not properly filter Record Type values

Download links:

CORE-5104

New Composer development

CORE-5061

Hyphenate "Vertical top-level navigation" in the Design System Studio

CORE-5182

For Navigation and Vertical Navigation components in the DSS, add the ability to set font family—and improve the display and grouping of various text properties

CORE-5161

Fix new row creation regression where fields on the new row that were displayed as comboboxes would have their values cleared out when the row was saved

CORE-5167

Fix issue with "Last/Next n <unit>" related date property values, where number values were reset to 1 in the page XML instead of the entered number value whenever the date range value was changed. For example, if a user had selected “Next n weeks” and set N to 5, then changed to “Last n weeks”, the 5 would remain in the Composer but would be saved in XML as 1.

CORE-5176

Fix issue where setting a field’s label position to "Right of Input" on checkbox fields broke HTML rendering in labels

CORE-5149

Fix issue where "Hide label" property (A Form-exclusive property) appeared on Table component fields

CORE-5158

Fix Composer issue where the “Custom field renderer” property rendered as a text input instead of a combobox

CORE-5223

Add "col" scope to Table column headers to improve accessibility for screen reader tools like JAWS

Download links:

New Composer development

The following tickets represent work completed on the new Composer delivered in this release:

CORE-4475, CORE-4803, CORE-4923, CORE-5036, CORE-5062, CORE-5084, CORE-5099, CORE-5109, CORE-5110, CORE-5111

CORE-4946

On Skuid SFX, implement the JsonAccess annotation to correct unexpected behaviors arising from serialization logic—notably Skuid model saves—that would cause "Apex object cannot be serialized" errors.

CORE-5044

Fix Header component issue where its buttons were not respecting record context after their first use, resulting in experiences where editing one record would unexpectedly update all records

CORE-5052

Update labeling to reflect pilot status of new Composer

CORE-5090

Fix sub-navigation item issue where merge variables were not being processed properly for URLs within the item's Go to URL action

CORE-5100

Fix issue where “Warn users if page has unsaved changes” page property would unexpectedly revert to “Yes” even when set to “No,” which affected by standard page edits and v1-v2 page migrations

CORE-5127

Fix Salesforce mobile issue where, in addition to the native mobile date picker, Skuid's date picker would sometimes unexpectedly appear and sometimes remain even after picking a date

CORE-5134

Fix issue where Skuid's mass update modal would not function properly with number and currency fields—causing a call stack error

CORE-5138

Ensure that UI-only picklist fields marked as required auto-select the first picklist entry, which is the current behavior for non-UI-only fields

CORE-5145

Fix Form issue where the component would attempt to render fields that were not in the component's model. Notably this issue could occur when, due to user permissions, fields were removed from the model to prevent unauthorized access, but the component would still attempt to render those removed fields.

CORE-5191

Upgrade Mustache and Moment libraries in API v1 to address security concerns

Updates

  • Action sequences: Streamlined and enhanced
  • Simpler design system files, better for source control
  • API key authentication method
     

Pilot

  • Chat component
  • New Composer
     

Heads up!

  • Vertical top level navigation works, but you may see differences

Included tickets

Tickets for prior early access releases are also represented below.

New Composer development

The following tickets represent code changes made while developing the new Composer experience:

CORE-4929, CORE-4539, CORE-4994, CORE-5012, CORE-5083, CORE-5009, CORE-4911, CORE-4854, CORE-5022, CORE-4860, CORE-4961, CORE-4853, CORE-5066, CORE-4863, CORE-5018, CORE-4913, CORE-4927, CORE-4864, CORE-4896, CORE-4935, CORE-4962, CORE-4975, CORE-4960, CORE-4963, CORE-4895, CORE-4897, CORE-4924, CORE-4997, CORE-4996, CORE-3622, CORE-4889, CORE-4891, CORE-4887, CORE-4865, CORE-4822, CORE-4819, CORE-4958, CORE-4783, CORE-4888, CORE-4892, CORE-4823, CORE-4824, CORE-4959, CORE-4806, CORE-4873, CORE-4807, CORE-4884, CORE-4808, CORE-4787, CORE-4907, CORE-4977, CORE-4558, CORE-4541, CORE-4768, CORE-5081, CORE-4857, CORE-4850, CORE-4879, CORE-4995, CORE-4914, CORE-4903, CORE-4954, CORE-4904, CORE-4902, CORE-5089, CORE-4559, CORE-4475, CORE-4386, CORE-4622, CORE-5032, CORE-4541

New REST data source development

The following tickets represent code changes made while developing the new REST data source:

PLIN-4794, PLIN-4733, PLIN-5051, APPS-2348, PLIN-5115, PLIN-4956, PLIN-4873, PLIN-4967, PLIN-4789, PLIN-5042, PLIN-5082, PLIN-4924, PLIN-4415, PLIN-4414, PLIN-5049, PLIN-4996, PLIN-4825, PLIN-4783, PLIN-4905, PLIN-4799, PLIN-4788, PLIN-4854, PLIN-5048

CORE-4871

When Skuid LWC is activated, enable Aura-related features to be used within the Skuid Page (Aura) component

CORE-4899

Upgrade build dependencies

CORE-4883

Updates to allow the Skuid Page (LWC) component to run properly in Lightning communities on Skuid SFX

CORE-5052

Update labeling to reflect pilot status of new Composer

CORE-4874

Update analytics tooling

CORE-5096

Resolve design system file inconsistencies that appear when downloading the file from Skuid’s admin interface versus retrieving it via the CLI, which began after recent updates to streamline that file’s format

PLIN-4804

Remove SSL options that erroneously display for Microsoft SQL Server during data source configuration

CORE-5088

Packaging tasks for Skuid NLX

CORE-5069

OpenAI data source (for use with Chat component) development

CORE-5097

OpenAI data source (for use with Chat component) development

APPS-2340

On SQL data sources, ensure the permission summary at the top of the access control page displays proper access summary

Previously, some permission changes would not trigger an update, instead displaying “No access” even when access was granted. Now the summary properly updates to reflect granted permissions, particularly for “Full access” scenarios

CORE-4950

On Skuid SFX, ensure LWC feature labels can be found when Skuid is installed as managed package

CORE-5082

On Skuid SFX, enable Skuid LWC to run with the “Relaxed CSP” Salesforce setting

CORE-4941

On Skuid SFX, cache the chosen Lightning render mode (Aura or LWC) for improved load times

CORE-4869

On Skuid SFX, add Skuid LWC section in Org Preferences

APPS-2352

On Skuid SFX, add necessary backend support for API key authentication method

APPS-2350

On Skuid NLX, add necessary backend support for API key authentication method

CORE-5078

On SFX, adjust styles of components within Lightning Experience to account for Salesforce CSS updates

CORE-4727

Move component merge variables (like {{searchValue}}) out of beta

CORE-5059

Internal-only XML additions

CORE-5014

Internal refactoring

PLIN-4907

Internal codebase adjustments for feature flags

CORE-4678

In the Design System Studio, utilize enhanced color picker for brand colors

PLIN-4959

In the Database Console, fix issue where the field searchbar and the mass actions for deleting and editing rows were not appearing

CORE-5027

In the Chat component, support rich text

PLIN-4692

Improve UI indicators for an internal beta feature

CORE-5013

Improve loading message indicators for Chat component

CORE-4909

Improve Composer performance for large pages, particularly by adjusting page index logic

PLIN-4300

Generate code coverage reports on NLX

APPS-2356

For SQL data sources, ensure selected SSL options persist across page refreshes, and that certificate information is properly erased when options are changed on-screen

CORE-5117

Fix Chart component regression where series interactions were unavailable—instead appearing as an unusable text field within the Properties pane

CORE-5085

On Skuid SFX, fix issue that caused Skuid Page (LWC) Lightning component to have load failures

CORE-5023

Fix v1->v2 migration issue where <span> HTML elements, particularly in v1 Queues, would cause “There was an error running the migration” errors—failing the migration itself. Now migrations complete as expected.

CORE-5051

Fix Table issue where drawers wouldn’t display if end users hid the Table’s leftmost column

PLIN-4903

Fix Skuid NLX permission set issue where adding a condition to a site permission set with the “Configure site” permission would not register as a change—preventing the Save button from enabling as expected

CORE-5091

Fix SFX issue where some data source types were not appearing

CORE-4947

Fix regression where fields displayed as buttons groups collapsed to minimum width instead of expanding to fill their given space

CORE-4948

Fix regression where button groups—particularly for picklist fields displayed as button groups—failed to respect width specified for button variants in a given design system

CORE-5077

Fix record type ID lookups for reference fields that display as picklists—which previously had an issue where those picklists would appear as blank even after choosing a value

CORE-4991

Fix Properties pane issue where, after setting its properties in the Advanced tab, focus would unexpectedly shift from the Text component’s canvas input back to the Advanced tab properties after a short delay in typing

CORE-5102

Fix Pages list issue where the Preview option would cause errors when pages required parameters—not opening the modal for setting those parameters and ultimately not previewing the page

PLIN-5090

Fix NLX issue where search bars would collapse into the page’s filters on data source, app, page, and design system admin pages

CORE-5040

Fix navigation item issue where “Sub-navigation item” carets would appear even though there were no sub-navigation items

Previously, deleting sub-navigation items in the Composer would not appropriately update the page XML. This resulted in “Sub-navigation item” carets appearing on these navigation items even though there were no longer sub-navigation items. This affected both top-level and sub-level navigation items.

Now, page XML is updated appropriately and navigation items do not show a caret unless there truly is a sub-item.

CORE-5015

Fix multipicklist issue where displayed values were not updated properly when picklist entries were changed

CORE-5098

Fix model regression where the child relationships sub-tab would not appear within the model fields tab

CORE-5095

Fix issue with nested properties not properly updating the selected area

CORE-4916

Fix issue where the Tab Container component would switch between tab and accordion views at unexpected breakpoints when the browser window was resized

CORE-4984

Fix issue where the some hover state style settings (border radius and background color) for Vertical Navigation items were not being applied correctly at runtime—despite previewing correctly in the Design System Studio

CORE-4918

Fix issue where the “Merge field” field picker, used for setting context conditions, would incorrectly point to the current component’s model instead of the “parent” component’s model—producing incorrect context conditions

CORE-4870

Fix issue where Responsive Grids with a main axis of “Column” would display at unexpected heights at runtime due to incorrect CSS

CORE-5049

Fix issue where newly added actions appear to remain as “Save model” actions, even when set to other action types. While only a label issue, and navigating away and back to an action list would resolve the issue, this misleading action list rendering behavior has been corrected.

PLIN-4955

Fix issue where illustrations used in Skuid Database would incorrectly render with a black background

CORE-5034

Fix issue where icon selectors were not displaying icons

CORE-4901

Fix issue where Geochart components would appear not to reflect model changes, sometimes rendering before model load operations completed

CORE-4900

Fix issue where display logic rules (particularly render conditions) were not enforced as expected on Geochart components

CORE-4890

Fix issue where Chatter components do not properly render input areas within Skuid Page (Aura) components when Skuid LWC is enabled

CORE-4969

Fix issue where Carousel components with slides containing nested Carousels would display incorrect slide count numbering + reimplement ability to remove slides in manually sourced Carousels

CORE-4915

Fix issue where buttons couldn’t be deleted in the Composer once more than one existed in a button group unless the Composer was refreshed

CORE-4992

Fix Form field issue where the “Horizontal alignment” property was not respected for boolean fields in edit mode—defaulting to “Left” alignment instead

CORE-5050

Fix Form component issue with date/time fields where browser focus would unexpectedly shift from edit mode before end users could complete time entry—requiring users to double click the field to re-enter edit mode

CORE-5047

Fix Form column issue where “Align self” properties were not respected—resulting in columns that were always set to flex-start

CORE-4931

Fix EU2 regression where the implied context condition of Id = Id was no longer applied and had to be manually specified, causing unexpected results in context-driven components like Decks

CORE-4978

Fix Edinburgh Update 2 on SFX runtime issue where sometimes icons would not render or would disappear when navigating back and forth between Lightning tabs

CORE-4880

Fix Edinburgh Update 1 issue where metadata overrides that changed Number fields into Picklist fields were not respected in Edit Mode, notably when metadata caching was not enabled for the data source

CORE-5029

Fix Design System Studio issue where the Chat component’s avatar element would not disappear when previewing the element without the avatar

CORE-4942

Fix design system issue where Spacing variables had a blank unit of measurement (instead of ‘px’ or ‘rem’ options)

CORE-4952

Fix date/time field validation behavior on mobile devices, which previously caused incorrect “Must match required format: [date]” errors

CORE-5115

Fix Composer issue where model fields and conditions were being unexpectedly removed when the builder selected the model within the model list

CORE-4940

Fix Composer issue where horizontal scrolling was not possible in Tab Set components in the canvas

CORE-5117

Fix Chart component regression where series interactions were unavailable—instead appearing as an unusable text field within the Properties pane

CORE-4682

Fix Calendar component issue where the view option picklist wasn’t rebuilding after a Month or List view was deleted, preventing the creation of a new view. Also improve disabled entries logic to accurately display the selectable Month/List entries. Additionally, some future feature work.

CORE-4919

Fix “problem initializing component” error that appeared when attempting to create an event in the Calendar component on mobile devices

CORE-4938

Ensure v2 components properly listen for user time zone changes

Previously custom time zone handling through snippets would not propagate as expected in v2 components—particularly the Calendar. For users migrating from v1, this meant snippets were no longer working on otherwise-identical v2 pages.

Now we’ve improved how the user’s current time zone is retrieved and the event subscription logic used by components to ensure these changes are accounted for at runtime

CORE-5005

Ensure the “lang” HTML attribute applied to Skuid pages uses hyphens instead of underscores to specify the language subtag.

Previously these attributes would with underscores: “lang=en_US” Now they appear with hyphens: “lang=en-US”

CORE-4937

Ensure that internal methods used to reparent nested components properly clean up and remove the reparented component from the previous parent

CORE-5024

Ensure switch toggles can be toggled on/off using the keyboard (Selecting them with Tab and toggling them with Spacebar)

CORE-4933

Ensure style variant conditions update the visual appearance of components

Previously style variant conditions would sometimes not properly update the styling of components, particularly when changing values in edit mode. This fix adjusts conditional class assignment, ensuring variants are better applied when expected

CORE-5103

Ensure OpenAI data source functions with the API Keys authentication option

CORE-4917

Ensure initial sections on Accordion components are assigned a unique Id

CORE-4973

Ensure exported design system files only contain updatable properties within the file

CORE-4932

Ensure existing Lightning preview methods continue to function with LWC enabled

CORE-5004

Ensure aria-label values for pagination buttons (page number, previous, next) contain properly updated alternative text and are available to accessibility tools

CORE-4949

Ensure “# of decimal places” property for Table summaries properly respects field metadata when “Use field metadata” is checked

PLIN-5101

Enable API key authentication for v1 runtime

CORE-5087

Disable Skuid Page (LWC) component usage in LWR sites to avoid errors until functionality is completed

CORE-4893

Core adjustments necessary to support improved sidebar and canvas rendering for Skuid Database

CORE-5094

Codebase and internal process enhancements to better avoid APIs noted as distorted by Salesforce

CORE-5053

Chat component development

CORE-5031

Chat component development

CORE-5080

Chat component development

CORE-4985

Chat component development

PLIN-4830

Adjusting behavior of site instance banner on early access sites to better indicate environment

CORE-5105

Adjust streamlined action sequence triggering behavior to account for issues surrounding what were previously event-triggered sequences

CORE-4926

Adjust Drawer chevron icon rendering so that it doesn’t appear extra wide if the drawer contains a Table component

CORE-5017

Adjust design system file format to fix issue where Skuid pages appeared blank in the Composer—which affected builders with large design system files

CORE-4970

Adjust Composer component rendering logic for internal testing

PLIN-4925

Address some spacing issues on Skuid NLX’s admin screens

CORE-5086

Additional work to disable Skuid LWC in LWR while generating passing builds

CORE-5028

Additional design system style properties for the Chat component

CORE-4967

Added HTML support in the following component properties through use of related “Allow HTML” toggle properties:

  • Button: Button label
  • Button Group: Label, when displayed as a menu
  • Wizard: Step labels
  • Header: Title and subtitle
  • Message Area: Title, as well as description
  • Search: In each return object’s header display name and display template
  • Toast (from the Show toast action): Message to display
  • Deck: Title
  • Table: Title, as well as column headers
  • List: Title

CORE-5076

Add “Beta” tag to Chat component and OpenAI data source type

CORE-5108

Add proper permissions for new Composer experience to Skuid Page Builder permission set

CORE-4701

Add interaction functionality to all field types

CORE-5079

Add appropriate implements so the Skuid Aura component can be used when Lightning Locker is disabled

CORE-4951

Add “Copy to clipboard” and “Evaluate formula fields on model” actions

CORE-5049

Fix issue where newly added actions appear to remain as "Save model" actions, even when set to other action types. While only a label issue, and navigating away and back to an action list would resolve the issue, this misleading action list rendering behavior has been corrected.

CORE-5050

Fix Form component issue with date/time fields where browser focus would unexpectedly shift from edit mode before end users could complete time entry—requiring users to double click the field to re-enter edit mode

CORE-5051

Fix Table issue where drawers wouldn't display if end users hid the Table's leftmost column

CORE-5077

Fix record type ID lookups for reference fields that display as picklists—which previously had an issue where those picklists would appear as blank even after choosing a value

CORE-5078

On SFX, adjust styles of components within Lightning Experience to account for Salesforce CSS updates

CORE-5090

Fix sub-navigation item issue where merge variables were not being processed properly for URLs within the item's Go to URL action

CORE-5100

Fix issue where “Warn users if page has unsaved changes” page property would unexpectedly revert to “Yes” even when set to “No,” which affected by standard page edits and v1-v2 page migrations

CORE-5127

Fix Salesforce mobile issue where, in addition to the native mobile date picker, Skuid's date picker would sometimes unexpectedly appear and sometimes remain even after picking a date

CORE-5134

Fix issue where Skuid's mass update modal would not function properly with number and currency fields—causing a call stack error

CORE-5024

Ensure switch toggles can be toggled on/off using the keyboard (Selecting them with Tab and toggling them with Spacebar)

CORE-5047

Fix Form column issue where "Align self" properties were not respected—resulting in columns that were always set to flex-start

CORE-5034

Fix issue where icon selectors were not displaying icons

CORE-5040

Fix navigation item issue where "Sub-navigation item" carets would appear even though there were no sub-navigation items Previously, deleting sub-navigation items in the Composer would not appropriately update the page XML. This resulted in "Sub-navigation item" carets appearing on these navigation items even though there were no longer sub-navigation items. This affected both top-level and sub-level navigation items. Now, page XML is updated appropriately and navigation items do not show a caret unless there truly is a sub-item.

CORE-5023

Fix v1->v2 migration issue where <span> HTML elements, particularly in v1 Queues, would cause "There was an error running the migration" errors—failing the migration itself. Now migrations complete as expected.

CORE-4978
Fix Edinburgh Update 2 on SFX runtime issue where sometimes icons would not render or would disappear when navigating back and forth between Lightning tabs 

CORE-4984

Fix issue where the some hover state style settings (border radius and background color) for Vertical Navigation items were not being applied correctly at runtime—despite previewing correctly in the Design System Studio


CORE-4991

Fix Properties pane issue where, after setting its properties in the Advanced tab, focus would unexpectedly shift from the Text component's canvas input back to the Advanced tab properties after a short delay in typing

CORE-4992

Fix Form field issue where the "Horizontal alignment" property was not respected for boolean fields in edit mode—defaulting to "Left" alignment instead

CORE-5004
Ensure aria-label values for pagination buttons (page number, previous, next) contain properly updated alternative text and are available to accessibility tools

CORE-5005
Fix invalid lang attribute value. Lang attribute now shows with a hyphen instead of an underscore.

CORE-5015
Fix multipicklist issue where displayed values were not updated properly when picklist entries were changed

CORE-5017

Adjust design system file format to fix issue where Skuid pages appeared blank in the Composer—which affected builders with large design system files

CORE-4682

Fix Calendar component issue where the view option picklist wasn't rebuilding after a Month or List view was deleted, preventing the creation of a new view. Also improve disabled entries logic to accurately display the selectable Month/List entries. Additionally, some future feature work.

CORE-4918

Fix issue where the "Merge field" field picker, used for setting context conditions, would incorrectly point to the current component's model instead of the "parent" component's model—producing incorrect context conditions

CORE-4926

Adjust Drawer chevron icon rendering so that it doesn't appear extra wide if the drawer contains a Table component

CORE-4940

Fix Composer issue where horizontal scrolling was not possible in Tab Set components in the canvas

CORE-4942

Fix design system issue where Spacing variables had a blank unit of measurement (instead of 'px' or 'rem' options)

CORE-4947

Fix regression where fields displayed as buttons groups collapsed to minimum width instead of expanding to fill their given space

CORE-4948

Fix regression where button groups—particularly for picklist fields displayed as button groups—failed to respect width specified for button variants in a given design system

CORE-4949

Ensure "# of decimal places" property for Table summaries properly respects field metadata when "Use field metadata" is checked

CORE-4951

Add "Copy to clipboard" and "Evaluate formula fields on model" actions

CORE-4952

Fix date/time field validation behavior on mobile devices, which previously caused incorrect "Must match required format: [date]" errors

CORE-4969

Fix issue where Carousel components with slides containing nested Carousels would display incorrect slide count numbering + reimplement ability to remove slides in manually sourced Carousels

CORE-4970

Adjust Composer component rendering logic for internal testing
 

  • Updates

    • Interactions support for all field types

    • New Action Framework actions

      • Expand/collapse drawers in Tables and Lists and sections in Accordions and Filter Sets

      • Copy text to clipboard: Copy a string or field value to the user's clipboard

      • Reevaluate formulas: Update one or more rows in a model to reevaluate formulas 

  • Beta

    • Skuid as LWC now available: Users can toggle this feature to use Skuid in LWC-exclusive contexts with a new Lightning component. Aura components should still function as expected.

Feature updates

New Action Framework actions

Expand/collapse drawers and sections with actions

Several Skuid components feature expandable/collapsible portions that respond to end user clicks. Drawers appear in Table and List components as context containers for rows—allowing additional details to be described in components within those drawers. Similarly, Accordion components allow for segmenting a page’s elements into easily discoverable sections, which users can freely open and close. These drawers and sections appear in other components as well—including Lists and Filter Sets.

Previously, it was not possible to expand and collapse these UI elements without hacky workarounds. It’s not uncommon to require one part of the page to expand in reaction to a user’s actions elsewhere—or to collapse a section of the page when the user’s completed all necessary actions within it.

With Edinburgh Update 2, we’ve incorporated more builder control over these expandable/collapsible drawers and sections through the Run component action.

For more information on individual component actions:

Copy to clipboard

It’s a common UI paradigm to allow users to copy text with the click of a button—perhaps a link, email address, or a templated piece of text. Skuid builders have built clever JavaScript solutions, but code no more!

With the Copy text to clipboard action, you can send specific strings or field data (using merge syntax) to the user’s clipboard.

Evaluate formula fields on model

Formulas are a powerful part of Skuid’s toolkit, and many UIs use formula fields alongside data fields. To have more tailored control and ensure formula fields remain in sync with actions elsewhere on the page, the Evaluate formula fields on model action can be used to reevaluate formulas on a specific row, any rows in context, or all rows in the model.

Beta features

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

Deploy Skuid pages using a Lightning web component

With Salesforce’s investment in the Lightning Web Components (LWC) programming model, developers and admins have more tools to build UIs based on modern web standards. And with Edinburgh Update 2, we are releasing our new Skuid Page (LWC) component in beta.

Note: 

This component is currently only avaialable through the Lightning App Builder. Support for Experience Cloud sites and other deployment contexts will be available in an upcoming release.

While enabling this feature shouldn’t cause any issues with Skuid’s Aura-based Skuid Page and Skuid Page Assignment components, builders can freely toggle this feature on and off for their org if they see unexpected behaviors. We recommend admins try this in a sandbox org by navigating to Settings > Org Preferences.

Pilot features

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.

Heads up!

skuid CLI versions older than 0.6 no longer supported

With the GA release of skuid CLI 0.6 during Edinburgh Update 1 last quarter, we published notice that older versions of the CLI would not be supported after Edinburgh Update 2’s release.

That time has come. We encourage all CLI users to upgrade to a 0.6 release. Issues from older CLI versions will no longer be addressed.

In case you missed it

These useful features made their way into Skuid in recent releases before this update.

Improved image properties

As part of CORE-4470, we made improvements the Image component’s properties, as well as related Image background properties of various container components (Page, Wrapper, Grid, etc)

  • Improved help text for Model and Merge model properties

  • The Alternative text property is always visible and supports merge syntax

  • Default Image source is now “URL”

  • Image source property:

    • Always shows the “URL” and “Attachment” options
    • NLX – Shows the “File” option
    • SFX – Shows the “Static Resource” option

  • When “Attachment” is the Image source:

    • The “Model” property is shown and is required
    • The “Image field” property is shown

  • Other streamlined properties:

    • Removed unnecessary Data source type, and Data source properties
    • Image URL supports merge syntax, and is only visible when the Image source is “URL”
    • Resource name is only visible when Image source is “Static resource”
    • File Path (within ZIP Static Resources) is only visible when Image source is “Static resource” and Resource name is a ZIP file
    • File name is only visible when Image source is “File”

Removed unneeded “Insert fields” button

In CORE-4732, we removed the extra “Insert fields” button since one now exists within the code editor when a related model is available

Set a custom amount of visible rows in multi-row components

Previously, you could only choose certain amounts of visible rows for Table, List, and Deck components. In CORE-4553 we added the ability to set a custom amount of visible row amounts.

This is particularly useful for Deck components, which could display a lot of empty space depending on the amount of rows shown.

Included tickets

v16.2.5.0 - Edinburgh U2 GA release

APPS-2333

On Skuid NLX when working with custom domains, provide UI feedback if DNS entry is removed after initial setup

APPS-2340

On SQL data sources, ensure the permission summary at the top of the access control page displays proper access summary

Previously, some permission changes would not trigger an update, instead displaying “No access” even when access was granted. Now the summary properly updates to reflect granted permissions, particularly for “Full access” scenarios

CORE-3641

Reserve Click interactions on Template-type fields for editing field values

CORE-3736

Fix issue where using the Undo button in the Design System Studio would not update the previews of any affected components

CORE-3737

Fix issue in Design System Studio where datepicker style variant previews do not show correct color for weekend days

CORE-3771

Fix field picker issue where clicking the picker on child relationship template fields displayed fields from the parent model instead of the child relationship

CORE-3794

Add actions for expanding/collapsing drawers in Tables and Lists and sections in Accordions and Filter Sets

CORE-4470

Improvements to user experience of properties in the Image Component and in Image background properties of various container components (Page, Wrapper, Grid, etc)

  • Improved help text for Model and Merge model properties
  • The Alternative text property is always visible and supports merge syntax
  • Default Image source is now “URL”
  • Image source property:
    • Always shows the “URL” and “Attachment” options
    • NLX – Shows the “File” option
    • SFX – Shows the “Static Resource” option
  • When “Attachment” is the Image source:
    • The “Model” property is shown and is required
    • The “Image field” property is shown
  • Other streamlined properties:
    • Removed unnecessary Data source type, and Data source properties
    • Image URL supports merge syntax, and is only visible when the Image source is “URL”
    • Resource name is only visible when Image source is “Static resource”
    • File Path (within ZIP Static Resources) is only visible when Image source is “Static resource” and  Resource name is a ZIP file
    • File name is only visible when Image source is “File”

CORE-4553

Changed the “Visible rows” property for Deck, Table, and List components to be a “type ahead control” to allow for custom numbers of items to display (e.g. show 12 Deck Cards in 3 rows of 4)

CORE-4608

With Salesforce’s beta release of Lightning Web Security (LWS) for Aura components, we found some errors would surface for our own Aura components (the Skuid Page and Skuid Page Assignment Lightning components). We’ve proactively updated our components so they will function as expected when LWS for Aura components reaches general availability on Salesforce.

CORE-4614

Fix Composer preview issue where using certain URL parameters would not display queried results appropriately—particularly for RecordTypeId parameters on the Case object in Salesforce

CORE-4655

Fix Composer issue where rearranging fields within Form and Table components would sometimes duplicate the fields instead of changing their location

CORE-4657

Update {{startDate}}, {{endDate}}, and {{allDay}} merge variables to provide more consistent values in on-click and update event actions

CORE-4674

For data sources using the “Client credentials” OAuth grant type, support sending specified scopes within network request headers

CORE-4685

Ensure custom headers with “Sticky” property enabled are sticky in Aura contexts (Salesforce Lightning)

Previously the “Sticky” property for Skuid page headers would have no effect in Aura contexts, and the header would scroll out of view as the user navigated the page.

Now, an enabled “Sticky” property on a page header will cause it to remain affixed to the top of page area allowed by Lightning Experience.

CORE-4699

Add “Copy to clipboard” and “Evaluate formula fields on model” actions

CORE-4701

Add interaction functionality to all field types

CORE-4711

For REST models, utilize the custom template request when making sample requests

CORE-4714

Fix read with inline-edit mode picklist rendering issue in Safari

Previously when editing picklist fields set to “read with inline-edit” mode at runtime in Safari, clicking the dropdown to display picklist values would return the field to Read mode instead of displaying available picklist items. Now the picklist items appear as expected.

CORE-4716

Internal build process improvements

CORE-4719

Internal code improvements

CORE-4725

Improvements for Skuid LWC functionality, particularly around URL handling and rendering certain UI elements

CORE-4726

On Skuid SFX, create scaffolding and user-facing option for toggling Skuid LWC functionality, as well as internal refactoring of some Salesforce data source type code

CORE-4727

Move component merge variables (like {{searchValue}}) out of beta

CORE-4728

Fix issue where Skuid builders without “Customize application” could not update timestamps used for caching—requiring users manually clear their cache to see updates

Previously, Skuid stored certain timestamps in custom settings that could only be updated by those with the “Customize application” Salesforce permission.

While this is permission is commonly granted to Skuid builders, those without that permission would attempt to preview their changes and—since the timestamp had not been updated because they didn’t have the proper permissions—their cache would not clear, and an older version of the page would appear. This resulted in some users being able to see the updated page, and other users needing to manually clear their cache to see the updated page.

Now, timestamps are handled so that even those without the “Customize application” permission can update them, properly clearing the cache for other users.

CORE-4729

Fix regression where button groups could not be deleted—only buttons within them or the entire Button Set component

CORE-4731

Fix regression where navigation item labels were not properly updated in the XML and did not render at runtime

CORE-4732

In the Composer, remove extra “Insert fields” button since one now exists within the code editor when a related model is available

CORE-4733

Visual defect in the Composer: The number of the condition is missing is condition type is “Viewport width” or “Snippet returns true.”

CORE-4734

Ensure “false” boolean values appear properly when displayed checkbox-returning picklists outside of Edit mode

CORE-4735

Fix Design System Studio issue where style variant preview of sliding panel would block the properties pane—preventing the user from making edits

CORE-4736

Fix action sequences issue where model conditions were not used to populate field values for rows created later in a sequence

CORE-4737

Fix issue where “Button Icon position” values were not appearing in the dropdown menu within the Properties pane

CORE-4738

Fix inability to override Vertical Navigation item styles via JSS in the Design System Studio

CORE-4739

Fix Wizard issue where step indicators would only appear when using buttons within the Wizard’s attached button group

Previously step indicators would only render if at least one button within the Wizard’s attached button group was configured. This prevented Wizard component utilizing custom step navigation buttons from displaying step indicators.

Now, step indicators appear as expected based on the number of available steps and whether or not the “Show step indicators” property is enabled.

CORE-4741

On Skuid NLX, address issues with template properties within Text component’s not properly saving empty-space content

CORE-4742

Template fields in Forms missing the “Hide label” property

CORE-4743

Fix bug where action sequence input values were not properly passed to “Show/hide menu” actions within the action sequence

CORE-4744

Fix v1-v2 migration utility issue where “Run snippet” actions were erroneously turned into “Multi” type actions after conversion

CORE-4750

Address a memory leak that can occur when editing large pages

CORE-4752

Fix v1 to v2 migration utility issue where Wrapper components would break migration in newer releases

CORE-4755

Internal code improvements

CORE-4761

Fix Table Settings modal issue where setting pagination would break when end users navigated to a previous page

CORE-4762

Internal refactors to improve loading of v2 resources

CORE-4763

Ensure that display logic condition numbering updates gracefully when conditions are removed

CORE-4765

Text inside the Horizontal Alignment property for Forms was invisible

CORE-4766

Fix Table issue where fields marked as read-only on the component would become editable after saving the Table’s model

CORE-4767

Reference Field Filter Conditions are no longer filtering related records in Field components

CORE-4771

Fix Form reference field issue, where the Form’s field would remain blank even after selecting a value in certain scenarios.

This issue occurred in scenarios where the Form was dealing with a newly created record, typically in a previous Wizard step, and the Form was displayed in Edit mode. After selecting a new value, the Form would not update properly to display the selected field—even though the data had been updated.

Now, the Form field displays updates as expected.

CORE-4772

Unnecessary horizontal scrollbar in the middle section of the Design System Studio

CORE-4774

X Axis on Bubble charts is ignoring the minimum range value

CORE-4778

In design systems based on the Lightning design system, prevent unwanted scrollbars on Table fields in edit mode

CORE-4781

Unnecessary required value error for From fields Unique ID properties in the Composer

CORE-4782

Addressed internal builder defect

CORE-4786

Fix aggregate model regression where date field values returned from Salesforce were evaluated as the incorrect data type

CORE-4788

“No fields are marked as filterable for search” error sometimes encountered on SQL models

CORE-4797

Adjust metadata retrieval for Salesforce content document features to address “Access to entity denied” errors

CORE-4798

Show/Hide component action breaks the page when it references a component that does not exist

CORE-4800

V2 Table Filter based on a Salesforce Dependent Picklist shows no values

CORE-4802

Incorporate additional aggregate model logic to better ensure date field values returned from Salesforce are evaluated as the correct data type, even when metadata caching is disabled

CORE-4811

Wrapper with height strategy “Fit to content” shows scrollbar if it contains a Deck component with a hidden footer

CORE-4812

Error loading the Vertical Navigation component when source is “Salesforce tabs for current app”

CORE-4813

Fix Composer issue that prevented more than 1 model from being added to a page

CORE-4816

Adjust Accordion icon display behavior

CORE-4817

Fix pagination label issue that caused “Infinity rows” to display instead of “All rows”

CORE-4827

Fix bug where errors occurring inside modals were displayed behind those modals when they were part of an included page—even when the modal’s “Display errors” property indicated errors should appear in the modal. Now errors appear where expected.

CORE-4832

Ensure certain container components that have nested items have two of those items by default (Carousel, Tab Container, Tab Set)

CORE-4838

Internal refactoring of component code

CORE-4841

Fix Composer bug where components could not be added to page regions within dependent pages

CORE-4842

Improve performance by adjusting “global” event subscriptions to use a new page-level API (instead of window or document scope) that intelligently unsubscribes unneeded event subscriptions

CORE-4847

Within Forms in read with inline-edit mode, activate the field’s Edit icon hover state not only when users hover directly over that icon, but when they hover over any part of the field

CORE-4849

Fix “Create new page” modal rendering issue discovered by automated testing

CORE-4856

Fix v1 Table issue where headers would not align with columns while scrolling

CORE-4869

On Skuid SFX, add Skuid LWC section in Org Preferences

CORE-4870

Fix issue where Responsive Grids with a main axis of “Column” would display at unexpected heights at runtime due to incorrect CSS

CORE-4871

When Skuid LWC is activated, enable Aura-related features to be used within the Skuid Page (Aura) component

CORE-4874

Update analytics tooling

CORE-4876

Fix feature parameter deployment for Salesforce-related features

CORE-4880

Fix Edinburgh Update 1 issue where metadata overrides that changed Number fields into Picklist fields were not respected in Edit Mode, notably when metadata caching was not enabled for the data source

CORE-4883

Updates to allow the Skuid Page (LWC) component to run properly in Lightning communities on Skuid SFX

CORE-4886

Deployment script preparations for Edinburgh Update 2 release

CORE-4890

Fix issue where Chatter components do not properly render input areas within Skuid Page (Aura) components when Skuid LWC is enabled

CORE-4893

Core adjustments necessary to support improved sidebar and canvas rendering for Skuid Database

CORE-4900

Fix issue where display logic rules (particularly render conditions) were not enforced as expected on Geochart components

CORE-4901

Fix issue where Geochart components would appear not to reflect model changes, sometimes rendering before model load operations completed

CORE-4909

Improve Composer performance for large pages, particularly by adjusting page index logic

CORE-4915

Fix issue where buttons couldn’t be deleted in the Composer once more than one existed in a button group unless the Composer was refreshed

CORE-4916

Fix issue where the Tab Container component would switch between tab and accordion views at unexpected breakpoints when the browser window was resized

CORE-4917

Ensure initial sections on Accordion components are assigned a unique Id

CORE-4919

Fix “problem initializing component” error that appeared when attempting to create an event in the Calendar component on mobile devices

CORE-4931

Fix EU2 regression where the implied context condition of Id = Id was no longer applied and had to be manually specified, causing unexpected results in context-driven components like Decks

CORE-4932

Ensure existing Lightning preview methods continue to function with LWC enabled

CORE-4933

Ensure style variant conditions update the visual appearance of components

Previously style variant conditions would sometimes not properly update the styling of components, particularly when changing values in edit mode. This fix adjusts conditional class assignment, ensuring variants are better applied when expected

CORE-4937

Ensure that internal methods used to reparent nested components properly clean up and remove the reparented component from the previous parent

CORE-4938

Ensure v2 components properly listen for user time zone changes

Previously custom time zone handling through snippets would not propagate as expected in v2 components—particularly the Calendar. For users migrating from v1, this meant snippets were no longer working on otherwise-identical v2 pages.

Now we’ve improved how the user’s current time zone is retrieved and the event subscription logic used by components to ensure these changes are accounted for at runtime

CORE-4941

On Skuid SFX, cache the chosen Lightning render mode (Aura or LWC) for improved load times

CORE-4950

On Skuid SFX, ensure LWC feature labels can be found when Skuid is installed as managed package

CORE-4955

Remove internal files related to Skuid LWC functionality that prevented successful deployments

CORE-4957

Revert future feature code

CORE-4976

Adjust Accordion icon display behavior

PLIN-4410

Remove unused third-party plugin

PLIN-4477

Move NLX session variables out of beta

PLIN-4504

Add banner indicating NLX environment type to admin and builder workspaces

PLIN-4511

Fix Skuid Database issue where marking fields “read-only” from the Fields tab would result in fields still being editable in the Data tab

PLIN-4525

In Skuid Database, fix regression in CSV import process where data type mismatch checks were not properly interrupting the import process

PLIN-4576

On Skuid NLX, fix a content type issue during the certificate uploading experience that caused an “Invalid request payload input” error

PLIN-4601

Backend adjustments for proxy features

PLIN-4639

In the Database Console, ensure the Permissions UI correctly switches as you navigate from object to object

PLIN-4692

Improve UI indicators for an internal beta feature

PLIN-4722

On Skuid NLX, remove unexpected scrollbars from admin UI

PLIN-4726

Adjusting runtime behavior of site instance banner

PLIN-4804

Remove SSL options that erroneously display for Microsoft SQL Server during data source configuration

PLIN-4830

Adjusting behavior of site instance banner on early access sites to better indicate environment

Future feature development

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

CORE-3608, CORE-3725, CORE-3726, CORE-4438, CORE-4467, CORE-4483, CORE-4493, CORE-4531, CORE-4543, CORE-4561, CORE-4620, CORE-4628, CORE-4652, CORE-4662, CORE-4677, CORE-4703, CORE-4709, CORE-4721, CORE-4722, CORE-4723, CORE-4724, CORE-4751, CORE-4753, CORE-4760, CORE-4769, CORE-4780, CORE-4784, CORE-4785, CORE-4787, CORE-4790, CORE-4791, CORE-4806, CORE-4809, CORE-4810, CORE-4815, CORE-4820, CORE-4822, CORE-4825, CORE-4829, CORE-4830, CORE-4831, CORE-4833, CORE-4834, CORE-4846, CORE-4850, CORE-4851, CORE-4852, CORE-4857, CORE-4859, CORE-4861, CORE-4867, CORE-4872, CORE-4879, PLIN-4411, PLIN-4412, PLIN-4413, PLIN-4414, PLIN-4417, PLIN-4422, PLIN-4627, PLIN-4740, PLIN-4766, PLIN-4788, PLIN-4789, PLIN-4799, PLIN-4854

CORE-4682

Fix Calendar component issue where the view option picklist wasn't rebuilding after a Month or List view was deleted, preventing the creation of a new view. Also improve disabled entries logic to accurately display the selectable Month/List entries. Additionally, some future feature work.

CORE-4918

Fix issue where the "Merge field" field picker, used for setting context conditions, would incorrectly point to the current component's model instead of the "parent" component's model—producing incorrect context conditions

CORE-4926

Adjust Drawer chevron icon rendering so that it doesn't appear extra wide if the drawer contains a Table component

CORE-4933

Ensure style variant conditions update the visual appearance of components Previously style variant conditions would sometimes not properly update the styling of components, particularly when changing values in edit mode. This fix adjusts conditional class assignment, ensuring variants are better applied when expected

CORE-4938

Ensure v2 components properly listen for user time zone changes Previously custom time zone handling through snippets would not propagate as expected in v2 components—particularly the Calendar. For users migrating from v1, this meant snippets were no longer working on otherwise-identical v2 pages. Now we've improved how the user's current time zone is retrieved and the event subscription logic used by components to ensure these changes are accounted for at runtime

CORE-4940

Fix Composer issue where horizontal scrolling was not possible in Tab Set components in the canvas

CORE-4942

Fix design system issue where Spacing variables had a blank unit of measurement (instead of 'px' or 'rem' options)

CORE-4947

Fix regression where fields displayed as buttons groups collapsed to minimum width instead of expanding to fill their given space

CORE-4948

Fix regression where button groups—particularly for picklist fields displayed as button groups—failed to respect width specified for button variants in a given design system

CORE-4949

Ensure "# of decimal places" property for Table summaries properly respects field metadata when "Use field metadata" is checked

CORE-4952

Fix date/time field validation behavior on mobile devices, which previously caused incorrect "Must match required format: [date]" errors

CORE-4969

Fix issue where Carousel components with slides containing nested Carousels would display incorrect slide count numbering + reimplement ability to remove slides in manually sourced Carousels

CORE-3771

Fix field picker issue where clicking the picker on child relationship template fields displayed fields from the parent model instead of the child relationship

CORE-4763

Ensure that display logic condition numbering updates gracefully when conditions are removed

CORE-4778

In design systems based on the Lightning design system, prevent unwanted scrollbars on Table fields in edit mode

CORE-4870

Fix issue where Responsive Grids with a main axis of "Column" would display at unexpected heights at runtime due to incorrect CSS

CORE-4880

Fix Edinburgh Update 1 issue where metadata overrides that changed Number fields into Picklist fields were not respected in Edit Mode, notably when metadata caching was not enabled for the data source

CORE-4893

Core adjustments necessary to support improved sidebar and canvas rendering for Skuid Database

CORE-4900

Fix issue where display logic rules (particularly render conditions) were not enforced as expected on Geochart components

CORE-4901

Fix issue where Geochart components would appear not to reflect model changes, sometimes rendering before model load operations completed

CORE-4909

Improve Composer performance for large pages, particularly by adjusting page index logic

CORE-4916

Fix issue where the Tab Container component would switch between tab and accordion views at unexpected breakpoints when the browser window was resized

CORE-4919

Fix "problem initializing component" error that appeared when attempting to create an event in the Calendar component on mobile devices

Future feature development

CORE-3726, CORE-4724

CORE-4766

Fix Table issue where fields marked as read-only on the component would become editable after saving the Table’s model

CORE-4767

Reference Field Filter Conditions are no longer filtering related records in Field components

CORE-4771

Fix Form reference field issue, where the Form's field would remain blank even after selecting a value in certain scenarios. This issue occurred in scenarios where the Form was dealing with a newly created record, typically in a previous Wizard step, and the Form was displayed in Edit mode. After selecting a new value, the Form would not update properly to display the selected field—even though the data had been updated. Now, the Form field displays updates as expected.

CORE-4802

Incorporate additional aggregate model logic to better ensure date field values returned from Salesforce are evaluated as the correct data type, even when metadata caching is disabled

CORE-4827

Fix bug where errors occurring inside modals were displayed behind those modals when they were part of an included page—even when the modal’s “Display errors” property indicated errors should appear in the modal. Now errors appear where expected.

CORE-4856

Fix v1 Table issue where headers would not align with columns while scrolling

CORE-4820

Future feature development
 

CORE-4772

Unnecessary horizontal scrollbar in the middle section of the Design System Studio

CORE-4774

X Axis on Bubble charts is ignoring the minimum range value

CORE-4781

Unnecessary required value error for From fields Unique ID properties in the Composer

CORE-4797

Adjust metadata retrieval for Salesforce content document features to address “Access to entity denied” errors

CORE-4800

V2 Table Filter based on a Salesforce Dependent Picklist shows no values

CORE-4811

Wrapper with height strategy "Fit to content" shows scrollbar if it contains a Deck component with a hidden footer

CORE-4813

Fix Composer issue that prevented more than 1 model from being added to a page

CORE-4817

Fix pagination label issue that caused "Infinity rows" to display instead of "All rows"

CORE-4841

Fix Composer bug where components could not be added to page regions within dependent pages

Future feature development

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

CORE-3608, CORE-4467

CORE-4470

Improvements to user experience of properties in the Image Component and in Image background properties of various container components (Page, Wrapper, Grid, etc):

  • Improved help text for Model and Merge model properties
  • The Alternative text property is always visible and supports merge syntax
  • Default Image source is now “URL”
  • Image source property:
    • Always shows the “URL” and “Attachment” options
    • NLX – Shows the “File” option
    • SFX – Shows the “Static Resource” option
  • When “Attachment” is the Image source:
    • The “Model” property is shown and is required
    • The “Image field” property is shown
  • Other streamlined properties:
    • Removed unnecessary Data source type, and Data source properties
    • Image URL supports merge syntax, and is only visible when the Image source is “URL”
    • Resource name is only visible when Image source is “Static resource”
    • File Path (within ZIP Static Resources) is only visible when Image source is “Static resource” and  Resource name is a ZIP file
    • File name is only visible when Image source is “File”

PLIN-4639

Skuid DB: Permissions UI correctly switches as you navigate from object to object

CORE-4812

Error loading the Vertical Navigation component when source is “Salesforce tabs for current app”

CORE-4798

Show/Hide component action breaks the page when it references a component that does not exist

CORE-4788

“No fields are marked as filterable for search” error sometimes encountered on SQL models

CORE-4786

Fix aggregate model regression where date field values returned from Salesforce were evaluated as the incorrect data type

CORE-4782

Addressed internal builder defect

CORE-4765

Text inside the Horizontal Alignment property for Forms was invisible

CORE-4742

Template fields in Forms missing the “Hide label” property

CORE-4733

Visual defect in the Composer: The number of the condition is missing is condition type is “Viewport width” or “Snippet returns true.”

CORE-4719

Internal code improvements

CORE-4685

"Ensure custom headers with ""Sticky"" property enabled are sticky in Aura contexts (Salesforce Lightning)

Previously the ""Sticky"" property for Skuid page headers would have no effect in Aura contexts, and the header would scroll out of view as the user navigated the page.

Now, an enabled ""Sticky"" property on a page header will cause it to remain affixed to the top of page area allowed by Lightning Experience."

CORE-4553

Changed the “Visible rows” property for Deck, Table, and List components to be a “type ahead control” to allow for custom numbers of items to display (e.g. show 12 Deck Cards in 3 rows of 4)

Future feature development

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

CORE-4703, CORE-4483, CORE-4493, CORE-4531, CORE-4628, CORE-4677, CORE-4723, CORE-4769, CORE-3725

CORE-4655

Fix Composer issue where rearranging fields within Form and Table components would sometimes duplicate the fields instead of changing their location

CORE-4674

For data sources using the “Client credentials” OAuth grant type, support sending specified scopes within network request headers

CORE-4736

Fix action sequences issue where model conditions were not used to populate field values for rows created later in a sequence

CORE-4744

Fix v1-v2 migration utility issue where “Run snippet” actions were erroneously turned into “Multi” type actions after conversion

CORE-4761

Fix Table Settings modal issue where setting pagination would break when end users navigated to a previous page

PLIN-4410

Remove unused third-party plugin

PLIN-4511

Fix Skuid Database issue where marking fields “read-only” from the Fields tab would result in fields still being editable in the Data tab

New features

  • New label properties:
    • Label position: Available on Checkbox and Switch field types, allows labels to be set on top of input or to the right of input.
    • Hide label: Hide a field label from the interface, but it's still available for screen readers
  • Upgraded to use Salesforce API 48 to API 57, allowing for new features like accounts as campaign members and Net Zero Cloud object access in Skuid pages
  • Updated compatibility for Lightning Web Security, ensuring Skuid's Aura components function as expected when this new Salesforce feature reaches GA status

Other updates

  • skuid CLI 0.6 will soon be GA: New features available on NLX, an no longer compatible with SFX. We recommend using skuid-sfdx as a CLI tool when using SFX.
  • IE11 is no longer supported

Included tickets

CORE-4608

With Salesforce’s beta release of Lightning Web Security (LWS) for Aura components, we found some errors would surface for our own Aura components (the Skuid Page and Skuid Page Assignment Lightning components). We’ve proactively updated our components so they will function as expected when LWS for Aura components reaches general availability on Salesforce.

CORE-4653

When working within Sliding Panels and Table drawers in the Composer, fix issue where Responsive Grid divisions would disappear from view (though remain in the XML) when components were dragged into them

CORE-3433

Upgrade Salesforce API from version 48 to version 57

CORE-4657

Update {{startDate}}, {{endDate}}, and {{allDay}} merge variables to provide more consistent values in on-click and update event actions

CORE-4707

Update error message for Author Apex permission requirement to remove reference to “profile,” since that permission can also be assigned through permission sets

CORE-4643

Update component pack editor UI styles

CORE-4630

Set “Sanitize field values” property to default off for Table components

CORE-3744

Responsive Grid vertical alignment improvements for “fit to content” + minimum heights

Previously, Responsive Grids set to have vertical alignment, with a minimum height, and the “Fit to content” height strategy would only consider the contents of the divisions—instead of the full minimum height of the component—when determining vertical alignment.

Now, Responsive Grids properly consider the minimum height when applying vertical alignment to their divisions.

PLIN-4410

Remove unused third-party plugin

CORE-4586

Re-add missing runtime export options for Chart components

CORE-3545

Prevent invalid values in reference fields

CORE-4659

Pass context into conditional rendering snippets

CORE-4623

On the Search component, fix issue where the field picker for setting Return Objects would not function

CORE-4670

On the Deck component, fix issue where “Required field” error message would only appear on the first card in the Deck component. Now, these error messages appear on the appropriate card.

PLIN-3780

On Skuid SFX, update OData data source detail screen to match updated NLX UI

CORE-4549

On Skuid SFX, fix issue where users without Skuid licenses were not being redirected to standard Salesforce

CORE-4600

On Skuid SFX, fix issue where tooltip text wouldn’t fade on pages deployed in Lightning with the Skuid Page Lightning component

PLIN-4252

On Skuid SFX, fix issue where adding the first picklist entry value for a picklist field on a data source object would not properly populate the “Position” property

CORE-4607

On Skuid SFX in Lightning experience, fix lookup filters for polymorphic fields (e.g. OwnerId on the Case object)

Previously when selecting a value for a polymorphic reference field, an error stating a field doesn’t exist would appear—even with properly configured lookup filters. This fix ensures that reference field works as expected.

CORE-4661

On Firefox, fix issue where multiple authentication popups would appear for pages using Salesforce data sources

CORE-4640

Internal test fixes

CORE-4609

Internal improvements for future features

CORE-4717

Internal config adjustments to support deployment of newer SFX releases

CORE-4687

Internal code utility method improvements

CORE-3611

Internal code structure improvements

CORE-4719

Internal code improvements

CORE-4695

Internal code improvements

CORE-4705

Internal code improvements

CORE-4715

Internal code improvements

CORE-4755

Internal code improvements

CORE-4616

Internal build process improvements

CORE-4716

Internal build process improvements

CORE-4658

In v2 Page Include components, allow the use of merge syntax within the “Skuid page” property

CORE-4650

In the Wizard component, fix issue where enable messages for step buttons would not display in the expected area if the Wizard was below other components

CORE-4675

In the v2 Page API Migration Utility, fix component targeting behavior

CORE-4669

In the Design System Studio, ensure changes to Sliding Panel style variants are properly reflected in their preview

CORE-4732

In the Composer, remove extra “Insert fields” button since one now exists within the code editor when a related model is available

CORE-4654

In Table components, add interaction functionality to child relationship fields

CORE-4686

In Page Include components, improve merge variable handling for URL parameters—ensuring that using the “Load new page” action will properly update the Page Include even if the only change is a URL parameter value from a merge variable

CORE-4646

Improve row creation logic to prevent looping errors, which were apparent when working with models on data source objects that contained an “Id” field

CORE-3876

Improve rendering speed for Deck components, particularly for high record counts

In v16.0.3 this ticket also represents work to adjust how Skuid handles HTML encoding, which has effects particularly in Text components.

CORE-4711

For REST models, utilize the custom template request when making sample requests

CORE-4739

Fix Wizard issue where step indicators would only appear when using buttons within the Wizard’s attached button group

Previously step indicators would only render if at least one button within the Wizard’s attached button group was configured. This prevented Wizard component utilizing custom step navigation buttons from displaying step indicators.

Now, step indicators appear as expected based on the number of available steps and whether or not the “Show step indicators” property is enabled.

CORE-4624

Fix where builders previously could not disable the “Skip entry criteria” property for existing “Submit for Approval” Salesforce data source actions. Now builders can enable/disable this property as expected.

CORE-4752

Fix v1 to v2 migration utility issue where Wrapper components would break migration in newer releases

CORE-4606

Fix Table field issue where “Required” checkbox was not a visible property in the Composer

CORE-4612

Fix rendering issue with picklist fields within sliding panels that are activated within Page Include components

CORE-4638

Fix rendering issue for updated reference fields for PostgreSQL.

Previously, selecting a reference field value in a component attached to a PostgreSQL model would “blank out” the field, even though the value was updated. Now, reference fields update and render as expected.

CORE-4731

Fix regression where navigation item labels were not properly updated in the XML and did not render at runtime

CORE-4729

Fix regression where button groups could not be deleted—only buttons within them or the entire Button Set component

CORE-4714

Fix read with inline-edit mode picklist rendering issue in Safari

Previously when editing picklist fields set to “read with inline-edit” mode at runtime in Safari, clicking the dropdown to display picklist values would return the field to Read mode instead of displaying available picklist items. Now the picklist items appear as expected.

APPS-2134

Fix page crash when creating page packs containing 300+ pages through the Add All button

CORE-4702

Fix OAuth authentication request errors, which particularly affected ServiceNow connections

CORE-4666

Fix large gap that temporarily appeared between properties in Properties pane and add height properties to Tab Set component

CORE-3736

Fix issue where using the Undo button in the Design System Studio would not update the previews of any affected components

CORE-4601

Fix issue where the Composer would not recognize setting a previously-configured margin property back to “None” as a change, meaning it was not possible to save the page unless another change was made. Now the Composer recognizes the change, and enables the Save button, as expected.

CORE-4696

Fix issue where running the “Navigate to Step” component action would display all Wizard steps on the page instead of the steps for the chosen Wizard. Now, only the expected steps appear.

CORE-4633

Fix issue where Responsive Grid components would not reflect layout property changes within the canvas

CORE-4486

Fix issue where reference fields were not properly to showing updates in edit mode—even when models were refreshed and contained accurate data

CORE-4611

Fix issue where reference field searches would not return expected records on some objects (such as the Case object in Salesforce) due to search value and record value/label discrepancies

CORE-4649

Fix issue where new font families could not be added to design systems

CORE-4472

Fix issue where mass actions displayed as menus or comboboxes were always deactivated

CORE-4610

Fix issue where mass action buttons would unexpectedly remain enabled after running—even when no rows were selected

CORE-4619

Fix issue where included page model conditions would ignore Page Include query parameters for identically named parameters in the container page

With an included page and a container page, if the container page has a URL parameter that shares the same name as a Page Include query string parameter, the Page Include’s query string would win out—since it more specifically applied to the included page’s use.

However a bug appeared where model conditions would ignore the identically named Page Include query parameter and use the value of the container page’s parameter instead.

This fix returns the model condition behavior to the previous expected process—where Page Include query strings win out even when identically named.

CORE-4577

Fix issue where having one denied data source would prevent any permitted data sources from querying. Now permitted data sources can query, even if an unpermitted one is used within a page.

CORE-4419

Fix issue where Go to URL actions in a Chart series would not accept some Chart context-related merge variables

CORE-4673

Fix issue where clicking outside of sliding panels triggered by Table row actions would not close them

CORE-4599

Fix issue where Calendar components were not providing actions for “Run component action” picklist

CORE-4697

Fix issue where Autocomplete filters using model rows as options would not properly filter results based on user input

CORE-4613

Fix issue where “required” validations were incorrectly running on optional picklist fields

CORE-4737

Fix issue where “Button Icon position” values were not appearing in the dropdown menu within the Properties pane

CORE-3737

Fix issue in Design System Studio where datepicker style variant previews do not show correct color for weekend days

CORE-4684

Fix issue for donut-style Chart components where merge variables were not displaying properly without other content

Previously, when merge variables were the only value for a donut-style Chart component’s content template, no value would be displayed. The workaround was to use some empty space character, which would then cause the value to display as expected. Now, workarounds are not needed and merge variables display as expected, even if they are the only value in the template.

CORE-4738

Fix inability to override Vertical Navigation item styles via JSS in the Design System Studio

CORE-4592

Fix Edinburgh early access issue where “Required” validations were incorrectly enforced

CORE-4593

Fix Edinburgh early access issue where “Required” validations would sometimes run incorrectly if users pressed the Tab key to proceed to the next field

CORE-4735

Fix Design System Studio issue where style variant preview of sliding panel would block the properties pane—preventing the user from making edits

CORE-4635

Fix Design System Studio display issue when using JSS to extend variants with code

CORE-4614

Fix Composer preview issue where using certain URL parameters would not display queried results appropriately—particularly for RecordTypeId parameters on the Case object in Salesforce

CORE-4584

Fix CKEditor rendering in Form and Table components set to Edit mode within Tab Sets

CORE-4548

Fix Chart bug where context was not properly set after drilling down, returning to the main chart, and then drilling down into a new value

Clicking into a Chart component segment sets the context, which can be used to display filtered drilldown information. Before this fix, returning to the main chart and then drilling down into another value would not properly set the context—instead using the previous drilldown’s values. With this fix, drilldowns work as expected.

CORE-4676

Fix Carousel issue where nested components were not properly displaying UI-only model data

CORE-4597

Fix bug where the Calendar component’s “+n more” view modal displayed the previous date

CORE-4644

Fix bug where pencil icons would appear on button fields within a Form when changed into read/edit mode via a component action

CORE-4637

Fix bug where iterating over an empty REST data array using merge syntax displays “[object][Object]” instead of nothing

CORE-4743

Fix bug where action sequence input values were not properly passed to “Show/hide menu” actions within the action sequence

CORE-4642

Fix “Unpack pages from page pack” issue where setting the filter to “Last modified by me” would not not allow the filter to be set to “Last modified by any” afterwards

CORE-4698

Ensure context is properly handled when updating a Page Include with the “Load new page” component action

Before this ticket, some areas of Skuid NLX’s admin interface experience display errors, particularly around data source permissions. These errors are now resolved with no change or loss to saved data.

CORE-4734

Ensure “false” boolean values appear properly when displayed checkbox-returning picklists outside of Edit mode

CORE-4588

Deployment-related internal config updates

CORE-4667

Backend code structure improvements

CORE-4651

Allow hotkeys to be set without a selected modifier key

CORE-4590

Allow enable conditions and style variant conditions on global actions for Table components

CORE-4641

Allow “Export Table data” component action to run even if the Table component is hidden

PLIN-4452

Adjust streaming behavior for Microsoft SQL data sources

APPS-2304

Adjust page API version selector when creating new Skuid page to account for future feature development

CORE-4617

Adjust internal sharing rules for Skuid custom objects for dev/QA purposes

CORE-4596

Adjust Calendar component behavior to query for additional events within the selected time frame

Previously, model record query limits could unexpectedly cause a Calendar sourcing its events from that model to not display all the event records for a given time frame.

To continue allowing for record limits while also not leaving end users confused about why certain events would not appear, the Calendar component now intelligently queries for records until all events within selected time frame are displayed.

CORE-4627

Adjust appearance of Search component in the Composer canvas to more accurately reflect its runtime appearance

CORE-4750

Address a memory leak that can occur when editing large pages

CORE-4604

Add “Label placement” property to fields displayed as switches or checkboxes, allowing for labels to display to the right of these inputs

CORE-4605

Add “Hide label” property for Form fields

CORE-4594

Add Calendar component merge variable functionality to event on-click actions and event update actions

APPS-2310

Add ability to unpack page packs when no other pages exist in the Skuid environment

Future feature development

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

CORE-4483, CORE-4531, CORE-3583, CORE-3588, CORE-3594, CORE-3630, CORE-3682, CORE-3702, CORE-3724, CORE-3849, CORE-3856, CORE-4373, CORE-4411, CORE-4413, CORE-4468, CORE-4492, CORE-4497, CORE-4499, CORE-4501, CORE-4516, CORE-4518, CORE-4522, CORE-4524, CORE-4530, CORE-4540, CORE-4589, CORE-4625, CORE-4629, CORE-4647, CORE-4662, CORE-4665, CORE-4671, CORE-4672, CORE-4709, CORE-4710, CORE-4712, CORE-4721, CORE-4722, CORE-4751, CORE-4753, CORE-3496, CORE-3633

CORE-4743

Fix bug where action sequence input values were not properly passed to "Show/hide menu" actions within the action sequence

CORE-4741

On Skuid NLX, address issues with template properties within Text component's not properly saving empty-space content

CORE-4739

Fix Wizard issue where step indicators would only appear when using buttons within the Wizard's attached button group Previously step indicators would only render if at least one button within the Wizard's attached button group was configured. This prevented Wizard component utilizing custom step navigation buttons from displaying step indicators. Now, step indicators appear as expected based on the number of available steps and whether or not the "Show step indicators" property is enabled.

CORE-4734

Ensure "false" boolean values appear properly when displayed checkbox-returning picklists outside of Edit mode

CORE-4714

Fix read with inline-edit mode picklist rendering issue in Safari Previously when editing picklist fields set to "read with inline-edit" mode at runtime in Safari, clicking the dropdown to display picklist values would return the field to Read mode instead of displaying available picklist items. Now the picklist items appear as expected.

CORE-4486

Fix issue where reference fields were not properly to showing updates in edit mode—even when models were refreshed and contained accurate data

CORE-4608

With Salesforce's beta release of Lightning Web Security (LWS) for Aura components, we found some errors would surface for our own Aura components (the Skuid Page and Skuid Page Assignment Lightning components). We've proactively updated our components so they will function as expected when LWS for Aura components reaches general availability on Salesforce.

CORE-4614

Fix Composer preview issue where using certain URL parameters would not display queried results appropriately—particularly for RecordTypeId parameters on the Case object in Salesforce

CORE-4696

Fix issue where running the "Navigate to Step" component action would display all Wizard steps on the page instead of the steps for the chosen Wizard. Now, only the expected steps appear.

CORE-4675

In the v2 Page API Migration Utility, fix component targeting behavior

CORE-4697

Fix issue where Autocomplete filters using model rows as options would not properly filter results based on user input

CORE-4702

Fix OAuth authentication request errors, which particularly affected ServiceNow connections

CORE-4686

In Page Include components, improve merge variable handling for URL parameters—ensuring that using the “Load new page” action will properly update the Page Include even if the only change is a URL parameter value from a merge variable

CORE-4684

Fix issue for donut-style Chart components where merge variables were not displaying properly without other content

Previously, when merge variables were the only value for a donut-style Chart component’s content template, no value would be displayed. The workaround was to use some empty space character, which would then cause the value to display as expected. Now, workarounds are not needed and merge variables display as expected, even if they are the only value in the template.

CORE-4673

Fix issue where clicking outside of sliding panels triggered by Table row actions would not close them

CORE-4670

On the Deck component, fix issue where “Required field” error message would only appear on the first card in the Deck component. Now, these error messages appear on the appropriate card.

CORE-4668

On Skuid NLX, fix data source object regression where it was not possible to mass edit more than 25 field permissions at a time

CORE-4661

On Firefox, fix issue where multiple authentication popups would appear for pages using Salesforce data sources

CORE-4658

In v2 Page Include components, allow the use of merge syntax within the "Skuid page" property

CORE-4654

In Table components, add interaction functionality to child relationship fields

CORE-4653

When working within Sliding Panels and Table drawers in the Composer, fix issue where Responsive Grid divisions would disappear from view (though remain in the XML) when components were dragged into them

CORE-4650

In the Wizard component, fix issue where enable messages for step buttons would not display in the expected area if the Wizard was below other components

CORE-4644

Fix bug where pencil icons would appear on button fields within a Form when changed into read/edit mode via a component action

CORE-4641

Allow "Export Table data" component action to run even if the Table component is hidden

CORE-4577

Fix issue where having one denied data source would prevent any permitted data sources from querying. Now permitted data sources can query, even if an unpermitted one is used within a page.

CORE-4635

Fix Design System Studio display issue when using JSS to extend variants with code

CORE-4637

Fix bug where iterating over an empty REST data array using merge syntax displays "[object][Object]" instead of nothing

CORE-4640

Internal test fixes

CORE-4642

Fix "Unpack pages from page pack" issue where setting the filter to "Last modified by me" would not not allow the filter to be set to "Last modified by any" afterwards

CORE-4646

Improve row creation logic to prevent looping errors, which were apparent when working with models on data source objects that contained an "Id" field

CORE-4649

Fix issue where new font families could not be added to design systems

CORE-4651

Allow hotkeys to be set without a selected modifier key

CORE-3545

Prevent invalid values in reference fields

CORE-3744

Responsive Grid vertical alignment improvements for "fit to content" + minimum heights Previously, Responsive Grids set to have vertical alignment, with a minimum height, and the "Fit to content" height strategy would only consider the contents of the divisions—instead of the full minimum height of the component—when determining vertical alignment. Now, Responsive Grids properly consider the minimum height when applying vertical alignment to their divisions.

CORE-3876

Improve rendering speed for Deck components, particularly for high record counts

CORE-4601

Fix issue where the Composer would not recognize setting a previously-configured margin property back to "None" as a change, meaning it was not possible to save the page unless another change was made. Now the Composer recognizes the change, and enables the Save button, as expected.

CORE-4610

Fix issue where mass action buttons would unexpectedly remain enabled after running—even when no rows were selected

CORE-4623

On the Search component, fix issue where the field picker for setting Return Objects would not function

CORE-4624

Fix where builders previously could not disable the "Skip entry criteria" property for existing "Submit for Approval" Salesforce data source actions. Now builders can enable/disable this property as expected.

CORE-4630

Set “Sanitize field values” property to default off for Table components

CORE-4638

Fix rendering issue for updated reference fields for PostgreSQL. Previously, selecting a reference field value in a component attached to a PostgreSQL model would “blank out” the field, even though the value was updated. Now, reference fields update and render as expected.

Major features

  • Client-side validation additions: 
    • Validate based on length as defined in the field's metadata—which can be set by the data source or field metadata overrides. 
    • Set custom error messages for required fields. 
  • Calendar component enhancements 
    • Improved handling of Unassigned groups: Configure the visibility, label, and order placement of the Unassigned category 
  • Use Apex to provide authentication values in data sources: (SFX only) Use server-side Apex logic to generate values used for authentication requests from Skuid's proxy
  • Sanitize fields values for CSV export on Table component

Other updates

  • Apply margin to all sides of a component in the Composer
  • On Skuid SFX, we've updated property labels related to Salesforce Classic header and sidebar and default them to off

Included tickets

APPS-1748

Add inactive users to site permission set list and detail screens

APPS-1905

Skuid NLX backend scaffolding to support custom domains

APPS-2244

In Skuid NLX, fix bug where clicking Help > About would not refresh the screen if the builder was already in a Settings screen tab

APPS-2268

On Skuid SFX, fix links within admin UI to correctly redirect to Salesforce Setup’s permission set settings page

APPS-2304

Adjust page API version selector when creating new Skuid page to account for future feature development

CORE-3752

Internal codebase configuration file adjustments

CORE-3895

Update “Spacing” label to “Margins,” and allow margin spacing values to be applied to all sides—or set individually

CORE-3899

On Skuid SFX, update property labels and default values related to Salesforce header and sidebar:

  • “Show salesforce header” is now “Show Salesforce Classic header”
  • “Show salesforce sidebar” “Show Salesforce Classic sidebar”
  • Both properties are now unchecked by default

CORE-4344

Add feature for sanitizing field values on export for Table components

CORE-4398

Update tooltip for refresh style variants button

CORE-4415

Remove unneeded field selector from Channel property in “Publish event” actions and event-triggered action sequences

CORE-4419

Fix issue where Go to URL actions in a Chart series would not accept some Chart context-related merge variables

CORE-4420

Add visibility options for Calendar component’s “Unassigned” grouping

CORE-4447

On Skuid SFX, remove unnecessary permissioning syntax from Skuid permissions sets

CORE-4453

Internal improvements to Page Index functionality

CORE-4459

Add validation method for field length

CORE-4464

Adjust UI to better display a field’s “required-ness” within the validation framework

CORE-4472

Fix issue where mass actions displayed as menus or comboboxes were always deactivated

CORE-4538

Internal codebase improvements

CORE-4548

Fix Chart bug where context was not properly set after drilling down, returning to the main chart, and then drilling down into a new value

Clicking into a Chart component segment sets the context, which can be used to display filtered drilldown information. Before this fix, returning to the main chart and then drilling down into another value would not properly set the context—instead using the previous drilldown’s values. With this fix, drilldowns work as expected.

CORE-4569

In Skuid SFX, fix issue where interacting with a Rich Text Field in a Salesforce form and then leaving that field would cause the following error: Uncaught Action failed: skuid:teleporter$controller$eventHandler [Unable to get value from Rich Text component.]

CORE-4574

On Skuid SFX, provide method of retrieving data source authentication values from Apex when using proxy

CORE-4584

Fix CKEditor rendering in Form and Table components set to Edit mode within Tab Sets

CORE-4586

Re-add missing runtime export options for Chart components

CORE-4587

Fix issue where validations were not applied to Salesforce string fields as expected

CORE-4588

Deployment-related internal config updates

CORE-4590

Allow enable conditions and style variant conditions on global actions for Table components

CORE-4591

Deployment-related internal config updates

CORE-4592

Fix Edinburgh early access issue where “Required” validations were incorrectly enforced

CORE-4593

Fix Edinburgh early access issue where “Required” validations would sometimes run incorrectly if users pressed the Tab key to proceed to the next field

CORE-4594

Add Calendar component merge variable functionality to event on-click actions and event update actions

CORE-4595

Fix Form component issue where template fields couldn’t be deleted in the Composer without removing the entire section

CORE-4597

Fix bug where the Calendar component’s “+n more” view modal displayed the previous date

CORE-4599

Fix issue where Calendar components were not providing actions for “Run component action” picklist

CORE-4600

On Skuid SFX, fix issue where tooltip text wouldn’t fade on pages deployed in Lightning with the Skuid Page Lightning component

CORE-4603

Rollback of future feature code

CORE-4606

Fix Table field issue where “Required” checkbox was not a visible property in the Composer

CORE-4607

On Skuid SFX in Lightning experience, fix lookup filters for polymorphic fields (e.g. OwnerId on the Case object)

Previously when selecting a value for a polymorphic reference field, an error stating a field doesn’t exist would appear—even with properly configured lookup filters. This fix ensures that reference field works as expected.

CORE-4611

Fix issue where reference field searches would not return expected records on some objects (such as the Case object in Salesforce) due to search value and record value/label discrepancies

CORE-4612

Fix rendering issue with picklist fields within sliding panels that are activated within Page Include components

CORE-4613

Fix issue where “required” validations were incorrectly running on optional picklist fields

PLIN-3499

Backend improvements on Skuid NLX to support displaying inactive users on site permission sets

PLIN-3566

Internal documentation updates

PLIN-3843

Implement backwards compatible behavior in new version of skuid CLI

PLIN-3935

For Skuid Database data import for picklist fields when the “Create missing picklist entries” option is checked, remove case-sensitivity when matching CSV values to existing picklist options to ensure only new options are added upon import

PLIN-3945

General design adjustments to Skuid Database CSV import experience

PLIN-3963

In Skuid NLX, display a count of both active and inactive users for app permission sets, indicate which users are inactive from a permission set’s detail screen, and improve dependency checks related to permission sets and users

PLIN-3966

Improvements to internal tooling

PLIN-3974

PLIN-3974 In Skuid NLX, internal bug fixes to support change from “profiles” to “site permission sets”

PLIN-3990

On Skuid NLX in SAML IdP configurations, allow user properties to be updated by SAML attributes—even after a user is provisioned

PLIN-4018

In Skuid NLX, fix issue where 0 (zero) would erroneously appear in bottom left of the Database Console screen when there are no objects configured

PLIN-4028

Add user status filter to user list within app permission set details

PLIN-4029

Allow Skuid Database object permissions to be configured from an app/site permission set detail screen (or when creating a new one)

PLIN-4252

On Skuid SFX, fix issue where adding the first picklist entry value for a picklist field on a data source object would not properly populate the “Position” property

PLIN-4277

Adjust page API version query to account for future feature development

Future feature development

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

APPS-1846, APPS-2162, APPS-2245, APPS-2256, APPS-2265, APPS-2266, APPS-2267, CORE-3587, CORE-4339, CORE-4364, CORE-4365, CORE-4366, CORE-4374, CORE-4380, CORE-4401, CORE-4405, CORE-4408, CORE-4409, CORE-4410, CORE-4427 , CORE-4428 , CORE-4430 , CORE-4433 , CORE-4442 , CORE-4445, CORE-4454, CORE-4455, CORE-4487, CORE-4488, PLIN-3919, PLIN-3953

Released on 3/13/2023

CORE-5040

Fix navigation item issue where "Sub-navigation item" carets would appear even though there were no sub-navigation items Previously, deleting sub-navigation items in the Composer would not appropriately update the page XML. This resulted in "Sub-navigation item" carets appearing on these navigation items even though there were no longer sub-navigation items. This affected both top-level and sub-level navigation items. Now, page XML is updated appropriately and navigation items do not show a caret unless there truly is a sub-item.

CORE-5023

Fix v1->v2 migration issue where <span> HTML elements, particularly in v1 Queues, would cause "There was an error running the migration" errors—failing the migration itself. Now migrations complete as expected.

CORE-5047

Fix Form column issue where "Align self" properties were not respected—resulting in columns that were always set to flex-start

CORE-5024

Ensure switch toggles can be toggled on/off using the keyboard (Selecting them with Tab and toggling them with Spacebar)

CORE-4984

Fix issue where the some hover state style settings (border radius and background color) for Vertical Navigation items were not being applied correctly at runtime—despite previewing correctly in the Design System Studio


CORE-4991

Fix Properties pane issue where, after setting its properties in the Advanced tab, focus would unexpectedly shift from the Text component's canvas input back to the Advanced tab properties after a short delay in typing

CORE-4992

Fix Form field issue where the "Horizontal alignment" property was not respected for boolean fields in edit mode—defaulting to "Left" alignment instead

CORE-5004
Ensure aria-label values for pagination buttons (page number, previous, next) contain properly updated alternative text and are available to accessibility tools

CORE-5005
Fix invalid lang attribute value. Lang attribute now shows with a hyphen instead of an underscore.

CORE-5017

Adjust design system file format to fix issue where Skuid pages appeared blank in the Composer—which affected builders with large design system files

CORE-4926

Adjust Drawer chevron icon rendering so that it doesn't appear extra wide if the drawer contains a Table component

CORE-4933

Ensure style variant conditions update the visual appearance of components Previously style variant conditions would sometimes not properly update the styling of components, particularly when changing values in edit mode. This fix adjusts conditional class assignment, ensuring variants are better applied when expected

CORE-4938

Ensure v2 components properly listen for user time zone changes Previously custom time zone handling through snippets would not propagate as expected in v2 components—particularly the Calendar. For users migrating from v1, this meant snippets were no longer working on otherwise-identical v2 pages. Now we've improved how the user's current time zone is retrieved and the event subscription logic used by components to ensure these changes are accounted for at runtime

CORE-4940

Fix Composer issue where horizontal scrolling was not possible in Tab Set components in the canvas

CORE-4949

Ensure "# of decimal places" property for Table summaries properly respects field metadata when "Use field metadata" is checked

CORE-4952

Fix date/time field validation behavior on mobile devices, which previously caused incorrect "Must match required format: [date]" errors

CORE-4969

Fix issue where Carousel components with slides containing nested Carousels would display incorrect slide count numbering + reimplement ability to remove slides in manually sourced Carousels

CORE-3771

Fix field picker issue where clicking the picker on child relationship template fields displayed fields from the parent model instead of the child relationship

CORE-4763

Ensure that display logic condition numbering updates gracefully when conditions are removed

CORE-4778

In design systems based on the Lightning design system, prevent unwanted scrollbars on Table fields in edit mode

CORE-4870

Fix issue where Responsive Grids with a main axis of "Column" would display at unexpected heights at runtime due to incorrect CSS

CORE-4874

Update analytics tooling

CORE-4898

Dubai-specific work to ensure that display logic condition numbering updates gracefully when conditions are removed

CORE-4900

Fix issue where display logic rules (particularly render conditions) were not enforced as expected on Geochart components

CORE-4901

Fix issue where Geochart components would appear not to reflect model changes, sometimes rendering before model load operations completed

CORE-4916

Fix issue where the Tab Container component would switch between tab and accordion views at unexpected breakpoints when the browser window was resized

CORE-4919

Fix "problem initializing component" error that appeared when attempting to create an event in the Calendar component on mobile devices

CORE-4766

Fix Table issue where fields marked as read-only on the component would become editable after saving the Table’s model

CORE-4767

Reference Field Filter Conditions are no longer filtering related records in Field components

CORE-4771

Fix Form reference field issue, where the Form's field would remain blank even after selecting a value in certain scenarios. This issue occurred in scenarios where the Form was dealing with a newly created record, typically in a previous Wizard step, and the Form was displayed in Edit mode. After selecting a new value, the Form would not update properly to display the selected field—even though the data had been updated. Now, the Form field displays updates as expected.

CORE-4827

Fix bug where errors occurring inside modals were displayed behind those modals when they were part of an included page—even when the modal’s “Display errors” property indicated errors should appear in the modal. Now errors appear where expected.

CORE-4856

Fix v1 Table issue where headers would not align with columns while scrolling

CORE-4766

Fix Table issue where fields marked as read-only on the component would become editable after saving the Table’s model

CORE-4767

Reference Field Filter Conditions are no longer filtering related records in Field components

CORE-4771

Fix Form reference field issue, where the Form's field would remain blank even after selecting a value in certain scenarios. This issue occurred in scenarios where the Form was dealing with a newly created record, typically in a previous Wizard step, and the Form was displayed in Edit mode. After selecting a new value, the Form would not update properly to display the selected field—even though the data had been updated. Now, the Form field displays updates as expected.

CORE-4827

Fix bug where errors occurring inside modals were displayed behind those modals when they were part of an included page—even when the modal’s “Display errors” property indicated errors should appear in the modal. Now errors appear where expected.

CORE-4856

Fix v1 Table issue where headers would not align with columns while scrolling

CORE-4798

Show/Hide component action breaks the page when it references a component that does not exist

CORE-4788

“No fields are marked as filterable for search” error sometimes encountered on SQL models

CORE-4744

Fix v1-v2 migration utility issue where "Run snippet" actions were erroneously turned into "Multi" type actions after conversion

CORE-4685

"Ensure custom headers with ""Sticky"" property enabled are sticky in Aura contexts (Salesforce Lightning)

Previously the ""Sticky"" property for Skuid page headers would have no effect in Aura contexts, and the header would scroll out of view as the user navigated the page.

Now, an enabled ""Sticky"" property on a page header will cause it to remain affixed to the top of page area allowed by Lightning Experience."

CORE-4674

For data sources using the "Client credentials" OAuth grant type, support sending specified scopes within network request headers

CORE-4655

Fix Composer issue where rearranging fields within Form and Table components would sometimes duplicate the fields instead of changing their location

CORE-4743

Fix bug where action sequence input values were not properly passed to "Show/hide menu" actions within the action sequence

CORE-4741

On Skuid NLX, address issues with template properties within Text component's not properly saving empty-space content

CORE-4739

Fix Wizard issue where step indicators would only appear when using buttons within the Wizard's attached button group Previously step indicators would only render if at least one button within the Wizard's attached button group was configured. This prevented Wizard component utilizing custom step navigation buttons from displaying step indicators. Now, step indicators appear as expected based on the number of available steps and whether or not the "Show step indicators" property is enabled.

CORE-4734

Ensure "false" boolean values appear properly when displayed checkbox-returning picklists outside of Edit mode

CORE-4714

Fix read with inline-edit mode picklist rendering issue in Safari Previously when editing picklist fields set to "read with inline-edit" mode at runtime in Safari, clicking the dropdown to display picklist values would return the field to Read mode instead of displaying available picklist items. Now the picklist items appear as expected.

CORE-4700

Expose Unique ID property for Form fields
 

CORE-4486

Fix issue where reference fields were not properly to showing updates in edit mode—even when models were refreshed and contained accurate data

CORE-4614

Fix Composer preview issue where using certain URL parameters would not display queried results appropriately—particularly for RecordTypeId parameters on the Case object in Salesforce

CORE-4696

Fix issue where running the "Navigate to Step" component action would display all Wizard steps on the page instead of the steps for the chosen Wizard. Now, only the expected steps appear.

CORE-4675

In the v2 Page API Migration Utility, fix component targeting behavior

CORE-4697

Fix issue where Autocomplete filters using model rows as options would not properly filter results based on user input

CORE-4702

Fix OAuth authentication request errors, which particularly affected ServiceNow connections

CORE-4686

In Page Include components, improve merge variable handling for URL parameters—ensuring that using the "Load new page" action will properly update the Page Include even if the only change is a URL parameter value from a merge variable

CORE-4684

Fix issue for donut-style Chart components where merge variables were not displaying properly without other content Previously, when merge variables were the only value for a donut-style Chart component’s content template, no value would be displayed. The workaround was to use some empty space character, which would then cause the value to display as expected. Now, workarounds are not needed and merge variables display as expected, even if they are the only value in the template.

CORE-4673

Fix issue where clicking outside of sliding panels triggered by Table row actions would not close them

CORE-4670

On the Deck component, fix issue where "Required field" error message would only appear on the first card in the Deck component. Now, these error messages appear on the appropriate card.
 

CORE-4668

On Skuid NLX, fix data source object regression where it was not possible to mass edit more than 25 field permissions at a time

CORE-4661

On Firefox, fix issue where multiple authentication popups would appear for pages using Salesforce data sources

CORE-4658

In v2 Page Include components, allow the use of merge syntax within the "Skuid page" property

CORE-4654

In Table components, add interaction functionality to child relationship fields

CORE-4653

When working within Sliding Panels and Table drawers in the Composer, fix issue where Responsive Grid divisions would disappear from view (though remain in the XML) when components were dragged into them

CORE-4650

In the Wizard component, fix issue where enable messages for step buttons would not display in the expected area if the Wizard was below other components

CORE-4644

Fix bug where pencil icons would appear on button fields within a Form when changed into read/edit mode via a component action

CORE-4641

Allow "Export Table data" component action to run even if the Table component is hidden

CORE-4577

Fix issue where having one denied data source would prevent any permitted data sources from querying. Now permitted data sources can query, even if an unpermitted one is used within a page.

CORE-4642

Fix "Unpack pages from page pack" issue where setting the filter to "Last modified by me" would not not allow the filter to be set to "Last modified by any" afterwards

CORE-4646

Improve row creation logic to prevent looping errors, which were apparent when working with models on data source objects that contained an "Id" field

CORE-4651

Allow hotkeys to be set without a selected modifier key

CORE-3876

Improve rendering speed for Deck components, particularly for high record counts

CORE-4419

Fix issue where Go to URL actions in a Chart series would not accept some Chart context-related merge variables

CORE-4584

Fix CKEditor rendering in Form and Table components set to Edit mode within Tab Sets

CORE-4586

Re-add missing runtime export options for Chart components

CORE-4601

Fix issue where the Composer would not recognize setting a previously-configured margin property back to "None" as a change, meaning it was not possible to save the page unless another change was made. Now the Composer recognizes the change, and enables the Save button, as expected.

CORE-4607

On Skuid SFX in Lightning experience, fix lookup filters for polymorphic fields (e.g. OwnerId on the Case object) Previously when selecting a value for a polymorphic reference field, an error stating a field doesn't exist would appear—even with properly configured lookup filters. This fix ensures that reference field works as expected.

CORE-4610

Fix issue where mass action buttons would unexpectedly remain enabled after running—even when no rows were selected

CORE-4612

Fix rendering issue with picklist fields within sliding panels that are activated within Page Include components

CORE-4623

On the Search component, fix issue where the field picker for setting Return Objects would not function

CORE-4624

Fix where builders previously could not disable the "Skip entry criteria" property for existing "Submit for Approval" Salesforce data source actions. Now builders can enable/disable this property as expected.

CORE-4638

Fix rendering issue for updated reference fields for PostgreSQL. Previously, selecting a reference field value in a component attached to a PostgreSQL model would “blank out” the field, even though the value was updated. Now, reference fields update and render as expected.

Released 2/28/2023

CORE-4597

Fix bug where the Calendar component’s "+n more" view modal displayed the previous date

CORE-4594

Add Calendar component merge variable functionality to event on-click actions and event update actions

CORE-4611

Fix issue where reference field searches would not return expected records on some objects (such as the Case object in Salesforce) due to search value and record value/label discrepancies

CORE-4548

Fix Chart bug where context was not properly set after drilling down, returning to the main chart, and then drilling down into a new value Clicking into a Chart component segment sets the context, which can be used to display filtered drilldown information. Before this fix, returning to the main chart and then drilling down into another value would not properly set the context—instead using the previous drilldown’s values. With this fix, drilldowns work as expected.
 

CORE-4571

Fix issue where buttons could not be dragged from one Button Group component to another

CORE-3671

Ensure combobox renderer properly uses properties for search template and search fields

CORE-4579

Internal developer tooling improvements

CORE-4547

Fix issue in Design Systems screen where Update All button would fail with a “Visualforce Remoting Exception” error when updating batches of design systems that are larger in file size

CORE-4591

Deployment-related internal config updates

CORE-4585

Fix issue where Message Area component prevents saving changes to fields or autofilter conditions

CORE-4545

Fix issue where saving a blank value to a number field would cause issues on some SQL data sources

CORE-4576

Fix issue where reference fields set to "Option source: Automatic" would result in modals with no options and browser console errors

CORE-4562

Fix mobile device rendering for reference fields on SQL data sources displayed as picklists

CORE-4588

Deployment-related internal config updates

CORE-4569

In Skuid SFX, fix issue where interacting with a Rich Text Field in a Salesforce form and then leaving that field would cause the following error: Uncaught Action failed: skuid:teleporter$controller$eventHandler [Unable to get value from Rich Text component.]

CORE-4580

Fix issues for reference field lookup modals:

  • Raw SOQL queries appeared in the modal instead of the expected user-facing search terms

  • Deleting and re-entering a valid search string in the modal hid valid results

Both issues are resolved by this ticket.

CORE-4566

Fix issue where the time zone conversions for datetime field pickers and the Calendar component conflicted with each other, causing datetimes to render incorrectly for non-all day events

CORE-4568

Remove style variant options from filters, because they cannot have style variants

CORE-4546

Fix issue where, when trying to upload a file larger than the size limit, the File Upload component would incorrectly say the file had successfully uploaded

CORE-4420

Add visibility options for Calendar component’s “Unassigned” grouping

CORE-4463

Internal tooling updates

CORE-4456

Ensure Filter Set data range label has appropriate spacing in comparison to other labels within the component

CORE-4426

For reference fields on UI-only models in v1 and v2, fix issue where the field picker modal only displayed the selected field instead of the expected fields available on the referenced object

CORE-4476

Fix issue where "Select navigation item" action would not properly load available items to target

CORE-4437

Internal improvements to Composer initialization

CORE-4450

Better timezone handling in the Calendar component, addressing experience issues around the following:

* Clicking "+n more events" on a day previously would sometimes display the previous day's events

* Expanding single date events (like tasks) which should not be able to expand/contract

* Event creation showing an error in the modal even though it was successful before closing the modal

* Save button disabled state when creating/editing an event in the modal

* Single date event sources should now always render on the same date no matter the timezone/locale

* Start/end date should now always render on the same date no matter the timezone/locale

* Start/end datetime should adapt to the org locale setting as expected

* Start/end datetime should render based on timezone properly for users at runtime. As an example: In America/New_York an event is created for 11am. In Australia/Sydney it should be represented at 3am the next day.

CORE-4417

Allows open/close drawer action to work regardless of visibility of drawer icons, as it previously would fail if “Show drawer icon” was disabled

CORE-4495

Fix issue for Salesforce data sources where SOSL queries were being run as SOQL queries when initiated from within a modal

CORE-3891

Update {{startDate}} and {{endDate}} Calendar merge variables to properly return date values instead of datetime values—which are still available via {{startDateTime}} and {{endDateTime}}

CORE-4491

Fix web font loading in v1 pages, which caused loading failures for Page Include components and their pages at runtime

CORE-4422

Fix issue where URL parameters for boolean values would cause page previews from the Composer to fail
 

CORE-4456

Ensure Filter Set data range label has appropriate spacing in comparison to other labels within the component

CORE-4449

Fix regression in Design System Studio styling that caused component list items to not expand to full area of the navigation pane

CORE-4417

Allows open/close drawer action to work regardless of visibility of drawer icons, as it previously would fail if “Show drawer icon” was disabled

CORE-4495

Fix issue for Salesforce data sources where SOSL queries were being run as SOQL queries when initiated from within a modal

CORE-3891

Update {{startDate}} and {{endDate}} Calendar merge variables to properly return date values instead of datetime values—which are still available via {{startDateTime}} and {{endDateTime}}

CORE-4422

Fix issue where URL parameters for boolean values would cause page previews from the Composer to fail
 

CORE-4431
Fix issue where "Update all" button for design systems does not complete updates in Dubai Update 3

CORE-3847
Fix Calendar component height issues, where bottoms rows unexpectedly expanded to fill the whole page

CORE-4399
Fix issue in Table components set to read with inline-edit where an edited row outside of the browser's viewport would cause the Save button to shift focus to that out-of-sight row instead of saving

CORE-4414
Fix issue where sliding panels restrict the size of modals, making them too small

CORE-4432
Fix runtime errors for Tables with Sort Builder enabled

CORE-4416
Make the hover behavior for v1 disabled buttons consistent, ensuring tooltips display and cursor changes display as expected

CORE-4434
In Skuid SFX on the Calendar component, fix issue where "View more events" in Month view does not work

CORE-3927
Fix issue in Calendar component's Week view where setting the end time to 12AM causes the component to freeze with JavaScript errors
 

CORE-3847
Fix Calendar component height issues, where bottoms rows unexpectedly expanded to fill the whole page

CORE-4395
Fix positioning of dropdown caret in Table component's Visible Rows property

CORE-4399
Fix issue in Table components set to read with inline-edit where an edited row outside of the browser's viewport would cause the Save button to shift focus to that out-of-sight row instead of saving

CORE-4414
Fix issue where sliding panels restrict the size of modals, making them too small

CORE-4416
Make the hover behavior for v1 disabled buttons consistent, ensuring tooltips display and cursor changes display as expected

CORE-4434
In Skuid SFX on the Calendar component, fix issue where "View more events" in Month view does not work

CORE-3927
Fix issue in Calendar component's Week view where setting the end time to 12AM causes the component to freeze with JavaScript errors
 

The Dubai Update 3 SFX GA release features several enhancements that make it even easier to build intuitive, complex forms:

  • Client-side validation
  • Navigation item style variant and style variant conditions
  • Wizard disabled step enhancements
  • Sync design system changes without leaving Composer
  • On-click actions for Scatter and Bubble charts
  • Other bug fixes and improvements

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.

  • 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 Open design system options > Refresh next to the design system page property
    • Click 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: 

    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

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-3859
Fix issue where runtime pages with only a Calendar component (or few other components) would sometimes crash Chrome browsers---especially at smaller page widths

CORE-3867
Fix runtime issue where date pickers appear in incorrect places when dates are the first field within a modal

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-3923
Fix issue where reference field search model does not look at orderBy property, preventing proper sorting of returned records

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-3926
Improve scrolling behaviors for the Page Index when there are deeply nested components

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-4362
Allow the deletion of a step that was previously the first step in a Wizard component without having to refresh the Composer

APPS-2198
Fix bug with "About" page's release notes link for patch releases ending in ".0"

CORE-3567
In the Wizard component, allow alternate styling for progress indicator step buttons, even when "Disable step buttons" is enabled on the component

Previously when "Disable step buttons" was enabled, the progress indicator step buttons would become locked in a "disabled state" style. While builders may want these steps disabled, they may not want them to display disabled styling. This fix ensures that, even if the buttons are disabled, other styles can be displayed.

CORE-3770
Fix issue where exporting child relationship data from a Table component previously output "[object Object]" instead of the expected values

CORE-3821
In the Table component's data grid mode, fix issues for date/datetime fields when user locale is set to a date format besides MM/DD/YYYY by verifying user locale and better handling format discrepancies

CORE-3862
Prevent entire page from crashing if there is an error in loading custom component packs

CORE-3878
Fix date picker bug where the first day of a month would not appear in the picker if that day was a Sunday and the user's locale sets the week to start on a Monday

For example, May 1st of 2022 was a Sunday. Previously May 1st would not appear in date pickers if the user's locale determined that weeks began on Mondays. After this ticket, May 1st will appear as expected.

CORE-3882
Remove unused personalization property from "Clear search on models" action

CORE-3890
Adds visible dropzone placeholders when dragging actions, models, conditions, etc. in Composer

CORE-3892
Improve spacing on Calendar component's week view to prevent time labels from overflowing to event area

CORE-3909
Prevent newly added sliding panels from closing when users click outside of them by default---even though "Close when user clicks outside of panel" is not enabled

CORE-3915
SFX-specific fixes to prevent entire page from crashing if there is an error in loading custom component packs

CORE-3916
Backend configurations to support build dependency upgrades

CORE-3928
Ensure error message blocks for Form components appear at the top of the component instead of the top of a section within it
 

CORE-3531
Fix issue in Design System Studio where cloning default variants would cause certain properties to not save their changes

HEADS UP: Existing clones may continue to see issues with certain properties. If possible, we recommend re-cloning these variants to ensure they work as expected.

CORE-3791
Fix v1 Search component regression that caused fields within the component to display API names instead of labels

CORE-3813
Fix issue where multi-select filters that affect other conditions do not retain multiple selected values
Previously, when a component filter was set to "Affect other condition(s)," there would be issues ensuring the affected condition contained all values selected within the filter. With this fix, conditions are now updated appropriately, ensuring all selected values within the filter are used by the condition to filter records.

CORE-3818
Fix issue where hotkey triggered action sequences attached to the Skuid page would not activate, even when the hotkeys were pressed

CORE-3828
Fix issue where Table components set to "Read with inline-edit" would revert to a false disabled state if users began editing a field but then made no changes

CORE-3831
Fix issue where end users needed to click twice to save change in Form components set to read with inline edit

CORE-3841
Fix issue where Show/hide menu actions would cause "Cannot read properties of undefined (reading 'length')" errors if a menu section had no menu items

CORE-3861
Fix picklist alignment issues in pages that use the Lightning design system (or one based on it)

CORE-3864
Fix issue where builders could not clone the Carousel's default variant in the Design System Studio

CORE-3865
Prevent builders from removing model-driven Carousel's template slide in the Composer

CORE-3872
Ensure render conditions for Table columns test all rows instead of only the first row

Previously, to determine whether or not a column should render, the Table component would only test the first row in its model and render/unrender based on that. This ticket updates that component behavior so that all rows are tested to determine whether or not to render the column.

CORE-3873
Streamline render condition logic to increase Table component rendering speed

CORE-3877
Only initialize Table cell elements when necessary to improve overall performance of Table component

CORE-3880
Fix Dubai-era regression in UI-only reference fields that prevented them from displaying field values

CORE-3881
Fix Carousel issue where adjusting properties on later slides refreshes the canvas view to the component's first slide

CORE-3885
Fix issue where conditions on relational models that use the "Abort this Model's Query" option to deal with missing parameters caused pages to break
 

Dubai (Update 2): Release Notes

With this release, we focused on guiding users more effectively through complex processes (like multi-part forms) by enhancing both the Wizard and Navigation components. Additional launches include the Carousel component in beta, along with many frequently-requested features (such as clearing search components), as well as several performance improvements.

Improved Navigation component for guiding complex business processes

Build complex forms with our improved Navigation components. Features in this release enable the Navigation component to work in tandem with the Wizard to guide users effectively through complex forms or other multi step business processes. Navigation items can inform users to complete required actions before proceeding to the next steps. In addition, the user can:

  • Select and expand an item or its sub-navigation list.
  • Choose style variants by design states for “not started”,“in progress” or “completed.”

Improved Wizard for complex forms

Generally, the Wizard component is the first component users choose when building some kind of multi-step business process, be that a complex form or a set of actions that need to be executed sequentially.

In this release, we’ve made multiple improvements to this component. For example, users can now:

  • Conditionally render a Wizard step.
  • Trigger actions from a Wizard step.
  • Switch between horizontal and vertical arrangements.

Carousel Component (beta)

We’re also introducing a Carousel component in beta. It’s Skuid’s first iteration of the common UI element for displaying a set of images or information as a slideshow, a format commonly seen at the top of landing pages.

You can now define each slide in the Composer or bind the carousel to a model.You can also use the DSS to style navigation controls.

Clear search condition and box

With this release, we are providing an option to clear search conditions for models, resetting any components attached to them. This provides a declarative way to reset search boxes.

Other features and changes

  • Skuid SFX now allows builders to open Design Systems Studio in a new tab.
  • We’ve added performance improvements in the App detail page and other resources for NLX.
  • All supported versions of Skuid have been updated so that there will be no loss in functionality when turning on Salesforce’s new “enhanced domains” feature.

Included tickets

CORE-3844
Fix issue where merge variables displaying child relationship picklist fields would cause pages to break

CORE-3837
Ensure the skuid.model.Model.loadAllRemainingRecords() API triggers only one model.loaded event---improving page performance since components must rerender when that event is published

CORE-3830
Carousel component copy improvements

CORE-3827
Add Enable conditions to List component row actions

CORE-3825
Adjust progress indication property to allow for "None" option, resolving unexpected behaviors when combined with vertical navigation

CORE-3824
Fix issue where adding a Responsive Grid to the canvas triggers automatic title case on action labels and some properties

CORE-3822
Ensure font weights applied to Toast messages in Design System Studio are applied

CORE-3819
Fix global merge variables not updating in Geochart titles

CORE-3816
Improve UI-only formula field performance by adjusting adoptRows API logic

CORE-3815
Fix issue where adding a row action to a List component would also add row actions to any nested elements (drawers, modals, sliding panels)

CORE-3812
In Safari, ensure fields receive browser focus when toggling from read to edit in Forms set to read with inline edit

CORE-3810
Ensure components that paginate (Decks, Lists, Tables) allow users to navigate pages properly, even if their footers are hidden

CORE-3805
Ensure that JSS used to extend design systems is not erased when changes are saved in orgs without the feature enabled, which affected some default design systems

CORE-3782
Fix issue where component names render twice in the canvas, e.g. "WrapperWrapper" instead of "Wrapper"

CORE-3764
Ensure newly supported merge syntax within Wizard and Navigation component actions functions within action sequences where context may vary

CORE-3762
Ensure checkbox fields displayed as switches can be returned to read mode after they've been toggled into edit mode

CORE-3738
In the Calendar component, ensure horizontal grouping lanes show correct start/end times

CORE-3735
Don't show "View" link in Composer for design systems that are not editable

CORE-3719
Adjust "Block UI with message" action behavior so that its animation completes before moving to the next action
This fix resolves an issue where, when the action after Block UI takes a long time, the UI blocking animation would never complete, effectively freezing the page.

CORE-3706
Ensure global merge variables update properly in Chart and Image components

CORE-3696
Internal enhancements for Button Group spacing settings

CORE-3683
Pass row context into menus when available on iterating components (like Decks and Lists)

CORE-3678
Implement the Carousel component

CORE-3662
Add Actions tab for Wizard steps, allowing sets of actions to run the first time a step is shown or whenever it is shown

CORE-3661
Add conditional rendering to individual Wizard steps and add dynamic step actions "Navigate to next step" and "Navigate to previous step"

CORE-3660
Add enable conditions to navigation items, as well as allow the disabled state for these items to be styled in the Design System Studio

CORE-3659
Add Navigation and Vertical Navigation component actions to expand sub-navigation items

CORE-3658
Add Navigation and Vertical Navigation component actions to select navigation items

CORE-3656
Add component merge variable for current Wizard step

CORE-3655
Update Wizard component action so the "StepID" property accepts merge syntax

CORE-3653
Adjust available Wizard properties to support Dubai Update 2 enhancements around progression indication

CORE-3480
Ensure sort order preferences are retained for models sorted client-side
While component-based sorting preferences were previously saved (when sorting is set in Table headers or the Sort Builder), this fix ensures end user sort preferences are also saved on the model when appropriate.

CORE-3468
Add action to clear Search condition and search box

CORE-2994
Reset component-level sort end user preferences when a field is removed from the component in the Composer

APPS-2085
Update release notes link for version information screen in Skuid SFX

APPS-2084
Update version information screen in Skuid SFX

APPS-2029
In Skuid SFX, allow builders to open the Design System Studio in a new tab from the design systems list page

APPS-2025
Implement enhanced user/permission endpoints in the app detail screen

APPS-1986
Backend scaffolding to support page dependency detection

CORE-3657
Add component action to set Wizard layout to horizontal, vertical, or toggle between the two
 

CORE-3861
Fix picklist alignment issues in pages that use the Lightning design system (or one based on it)

CORE-3841
Fix issue where Show/hide menu actions would cause "Cannot read properties of undefined (reading 'length')" errors if a menu section had no menu items

CORE-3837
Ensure the skuid.model.Model.loadAllRemainingRecords() API triggers only one model.loaded event---improving page performance since components must rerender when that event is published

CORE-3831
Fix issue where end users needed to click twice to save change in Form components set to read with inline edit

CORE-3822
Ensure font weights applied to Toast messages in Design System Studio are applied

CORE-3810
Ensure components that paginate (Decks, Lists, Tables) allow users to navigate pages properly, even if their footers are hidden

CORE-3791
Fix v1 Search component regression that caused fields within the component to display API names instead of labels

CORE-3706
Ensure global merge variables update properly in Chart and Image components

CORE-3735
Don't show "View" link in Composer for design systems that are not editable

CORE-3738
In the Calendar component, ensure horizontal grouping lanes show correct start/end times

CORE-3762
Ensure checkbox fields displayed as switches can be returned to read mode after they've been toggled into edit mode

CORE-3812
In Safari, ensure fields receive browser focus when toggling from read to edit in Forms set to read with inline edit

CORE-3815
Fix issue where adding a row action to a List component would also add row actions to any nested elements (drawers, modals, sliding panels)

CORE-3816
Improve UI-only formula field performance by adjusting adoptRows API logic

CORE-3819
Fix global merge variables not updating in Geochart titles

CORE-3824
Fix issue where adding a Responsive Grid to the canvas triggers automatic title case on action labels and some properties

CORE-3574
Allow v2 custom field renderers to be set even if there are no snippets on the page---which enables the use of custom field renderers stored as resources outside the page

CORE-3576
Fix animations for various charts within the Chart component in v2

CORE-3679
In Skuid SFX, ensure Console navigation for Name and Reference field links in Salesforce Classic work within orgs with enhanced domains enabled

CORE-3727
Ensure checkbox fields respect enable conditions in "Read with inline-edit" mode

CORE-3730
Ensure that opened menus close when a new menu is opened from a component in a Deck card

CORE-3733
Prevent models from requerying when the "Empty search behavior" property is set to "Remove all model data"

The "Empty search behavior" property is available on Filter Set, Table, List, and Deck components. Previously the "Remove all model data" option would not work appropriately, causing the model to requery even when the search term is blanked out. Now, all data will be removed properly.

CORE-3675
For Skuid SFX, ensure skuid.page.runningOnForceSite variable is set properly in orgs with enhanced domains enabled

When enhanced domains are enabled, this fix resolves the following issues:

- "Edit Page" button in Skuid pages no longer showing for admin users

- Page problems no longer displaying for admin users

- Some File Upload methods for the "Salesforce" data source not working as intended

As part of this fix, admin users may now see page problems that previously did not display. No new errors have been introduced; they just render correctly now.

CORE-3679
In Skuid SFX, ensure Console navigation for Name and Reference field links in Salesforce Classic work within orgs with enhanced domains enabled

CORE-3681
Fix issue where Table component filter's that source values from aggregate models display the first option from the source model instead of the selected option

CORE-3734
Remove erroneous Data grid options from Button Group properties

CORE-3766
Resolve errors that can occur when saving models in a browser window with multiple Skuid pages, like Salesforce Lightning pages

CORE-3765
In Skuid Database, fix issue where the "Default value" property for picklist/multipicklist fields would not display added picklist values

CORE-3743
Fix issue in Dubai releases where hidden Responsive Grid divisions still applied their margin, causing unexpected spacing layouts

CORE-3741
Ensure return object actions display in the Search component's View All modal
Previously, clicking the "View All" link from a Search component would display rows of records related to the search, but the row actions for those records would not display. This fix ensures the configured return object actions display on each row.

CORE-3734
Remove erroneous Data grid options from Button Group properties

CORE-3715
Fix an issue where hiding unregistered tooltips would cause console errors

CORE-3714
Fix issue in Dubai Update 1 where user's focus is placed on tooltip icons instead of the appropriate input element

CORE-3711
Prevent model requeries from breaking display logic on Table component buttons

Previously, when requerying the model attached to a Table component with buttons that utilize display logic would break the display logic of the buttons---causing unexpected behaviors (like all buttons disappearing). This ticket fixes the underlying issue.

CORE-3669
Fix issues where the Filter Mode property was still configured after switching to manual filters

Previously it was possible for builders would not realize a filter was operating client-side, because the Filter mode property would disappear when options and conditions were picked manually, but the "filterMethod" XML attribute would remain. As of this ticket, the XML attribute will be removed when necessary.

CORE-3704
In Dubai Update 1 when working within principal pages, fix an issue where builders must click Cancel twice in the Create New Dependent Page modal

CORE-3691
Adjust runtime error messaging

CORE-3681
Fix issue where Table component filter's that source values from aggregate models display the first option from the source model instead of the selected option

CORE-3675
For Skuid SFX, ensure skuid.page.runningOnForceSite variable is set properly in orgs with enhanced domains enabled
When enhanced domains are enabled, this fix resolves the following issues:

- "Edit Page" button in Skuid pages no longer showing for admin users

- Page problems no longer displaying for admin users

- Some File Upload methods for the "Salesforce" data source not working as intended
As part of this fix, admin users may now see page problems that previously did not display. No new errors have been introduced; they just render correctly now.

CORE-3536
Fix issue in Table component's data grid mode where pasting an incompatible value from one field to a field with a different field type results in an unexpected value, instead of canceling the change reverting back to the field's original value

CORE-3535
Ensure custom picklist field renderers override default options

CORE-3347
Ensure that picklists in v2 components properly display labels when Salesforce's state and country/territory feature enabled
 

Skuid makes it easier and faster to build inclusive apps. With this release, data grids are now easier to navigate, DSS is easier to edit, and we’re enhancing the enterprise look and feel of components! App-centered design, permissions, and page pack experience have major improvements to make them simpler and faster.

Application building

Data grid mode for Tables

Hey, remember data grid mode, the cool thing you could try out with Tables in Dubai? Now it’s officially GA—with new features, like the ability to copy and paste data and use the keyboard for data entry (including date fields).

Undo/redo in DSS

We’re introducing a feature in the Design System Studio (DSS) that users loved with the Composer. When making a change to any property in DSS, you now have the option to undo it. The undo arrow will step you back through your changes and a redo arrow will be enabled, too.

Components with global merge variables now listen for changes in model data

With the new Sort Builder, your data components like Tables, Lists, Decks, and Filter Sets now have a way to build sorts. Users can dynamically manipulate these data sets instead of builders baking sorts into the page or changing data sorts via JavaScript.

Name change from master to principal and child to dependent

As we work to improve our terminology, we’ve updated the name of our master and child page feature to principal and dependent pages. You’ll see this change throughout our user interface in Dubai Update 1.

Administration and deployment

App-centered dev structure (NLX only)

With our commitment to app-centered development, app resources are now strongly tied to the application, while also remaining shareable across applications. We’ve updated this feature with:

  • Improvements for enterprise customers by adding more backend logic and processes.
  • Bug fixes and UI enhancements.

App-level permission sets (NLX only)

We’ve improved our app-specific permission setting feature and made it enterprise-friendly by:

  • Adding UI updates and performance improvements.
  • Fixing issues with permission enforcement.

Improved module organization and page pack building experiences (SFX Only)

Dubai Update 1 makes it easier to create and unpack page packs through an updated experience. In addition, we’ve added a new modules section to the Pages screen in SFX, making it easier to organize your pages into modules. Create modules from Skuid UI and easily move pages in and out of modules to aid in page organization.

Data service

Skuid Database updates (beta) (NLX only)

Handle your entire stack, including database needs, in Skuid. We’re continuing to improve this major feature with:

  • A new fields tab view to focus on metadata.
  • New and improved picklists and multi-picklists fields.
  • Performance enhancements and bug fixes on Access Control.

Changelog


INTEG-174
In Skuid SFX, display error if JWT signing certificate doesn't exist when trying to create a SQL data source

INTEG-168
Fix an issue where errors loading metadata would hang the browser window

Previously, the "Loading metadata for Data Dource" message would freeze the browser window if Skuid could not locate metadata at the supplied URL. Now a proper error message displays, allowing the user to continue working.

INTEG-162

In Skuid SFX when configuring a SQL data source, fix an issue where toggling the "Active" property and clicking "Cancel" would cause the General properties tab to disappear

INTEG-161
Prevent DSS undo/redo from breaking with child variants

INTEG-155

On SQL data sources, disable the "Test connection" button until changes are saved

INTEG-150

Ensure data source type cannot be changed once data sources are created

DSC-3508
Internal improvements to the Image component

DSC-3507
Make tooltips placed on field labels keyboard accessible

DSC-3506
Fix issue where List quick config throws error when "Done" is clicked

DSC-3497

To improve keyboard accessibility, adjust the keyboard focus and tab order of the Table component's drawer icon and row actions

Previously users attempting to tab or shift-tab past a Table drawer's chevron icon, or left-aligned row actions, would be "trapped" by its focus. This would prevent arrow keys from moving keyboard focus as expected, and pressing Escape would not reset focus. This was particularly apparent when working with checkboxes or rows while using mass actions. We've improved the way our Table tab focus is handled, allowing tabs and arrow keys to adjust focus in a more consistent way.

DSC-3417
Enable HTML use in modal title text by adding "Allow HTML in title" property

DSC-3388
For internalization purposes in v1, convert the "Clear Value" button into label metadata

DSC-3387
Add undo/redo functionality in the Design System Studio

DSC-3386
Add link to page's design system in the Composer

DSC-3362
Copy/paste support for Data Grid mode in the Table component

DSC-3300
Backend developments for future features

DSC-3297
In the Table component's data grid mode, add keyboard support in Date and DateTime fields

DSC-3268
Expand "Toggle Row Mode" to work for mass actions

DSC-2903
DSS Form Background color doesn't apply

CORE-3705

Fix issue with variable setting on Salesforce data source code that caused the following error "Cannot set property size of #<Set> which has only a getter"

CORE-3701

In v2, allow the columns of Table components attached to UI-only models to set sorting

Previously this sorting could be done through the Sort Builder or Sort model action, but this fix allows end users to sort on columns at runtime

CORE-3699
Ensure that Skuid pages in environments without data sources containing data source actions do not break when "Run data source action" is selected

CORE-3698
Fix merge syntax parsing bug causing issues with $Component merge variables

CORE-3697
Fix issues in Salesforce data sources regarding Opportunity and OpportunityLineItems model changes

CORE-3695

Fix regression where message blocks within the Message Area component were no longer respecting context, displaying empty merge variables where values would be expected

CORE-3690
Minify internal page XML and remove deprecated admin pages

CORE-3674
Update availability of undo/redo in DSS and Data grid features for Dubai Update 1

CORE-3648
Prevent "Remove Row(s)" actions set to "Context row" from removing all rows if no context row is found

CORE-3646

Ensure merge variables work properly for placeholder properties on text, text area, and picklist fields

CORE-3615
Add “Restrict closing the modal” to modal properties

CORE-3577

Ensure input fields properly re-render the number zero (0) as 0

CORE-3555

Address issue where Responsive Grid column gutter settings cause undesired wrapping

CORE-3543
Add style variant conditions to modal

CORE-3541
Abstract out copy/paste to field renderer specific methods to allow for extensibility

CORE-3532

In the Design System Studio on SFX, ensure Undo/Redo tooltip appears


CORE-3506
Update master/child page terminology to principal/dependent page

CORE-3483
Fix issue where cancelling changes on a model with rows marked for deletion does not unmark the rows

CORE-3472
In v2, make global merge syntax used within components respond to model changes

CORE-3455
Fix issue where, in some instances, cancelling changes on multiple models no longer worked after recent refactor

This issue would arise if the end user attempted to cancel multiple models, and one or more of the models contained no changes—preventing the other changes from being canceled.

CORE-3422
Adjust the properties on Skuid's Model JavaScript objects

This change introduces an improved way to access model changes through a consistent Record API. In doing this, we are deprecating the 'model.changes' and 'model.originals' properties on skuid.model.Model objects. As part of this ticket's work we've replaced many instances of it within our own codebase.

While model.changes and model.originals will continue to function as JavaScript proxies, they will no longer be true objects. We recommend reviewing any custom code that utilizes these properties to check that it continues to function as intended.

CORE-3362
Fix issue where events published with the "Only This Page" scope were published outside the current page

CORE-3219
Adjust error message copy for certain Skuid SFX messages

CORE-3174
Update master/child page terminology to principal/dependent page

CORE-2652
Change default page revision description to be the current date time based on server settings

APPS-1998
Spacing adjustments for Skuid SFX's new unpack page flow

APPS-1995
Update page pack creation wizard button text from "Add pages" to "Next"

APPS-1993
Fix managed values error for Skuid SFX's new module creation flow works in installed orgs

APPS-1989
Fix issue in new Skuid SFX module flow where creating or deactivating a module fails if special characters are included

APPS-1974

Propagate various Skuid admin UI design updates


APPS-1950
Use icons to differentiate principal pages from other pages in the Pages screen and in the App detail screen's Pages tab

APPS-1937
In Skuid SFX's new "add pages to module" flow, remember selected pages as users search

APPS-1934
Fix issue where adding pages to modules shows "Remove all" when none are selected

APPS-1927
Internal product support enhancements

APPS-1926
Admin UI improvements for feature access

APPS-1901

Adjust Data Sources header spacing

APPS-1899
Admin UI updates to support new page pack and module flows in Skuid SFX

APPS-1815
Create 'Add pages to module' flow

APPS-1813
Add module navigation to the Pages screen, allowing users to create new modules in Skuid or filter pages by selected module

APPS-1764
Update Skuid's edit user profile screen to reflect backend enhancements

APPS-1647
Adjust Skuid admin screens to reflect related backend enhancements

APPS-1619
Remove all conditional copy used in the transition from "profile" to "site permission set"

APPS-1546
Improve UI warnings for invalid characters in data source name

APPS-1471

Improve authentication provider name entry, preventing invalid characters from being used and resolving invalid "This name is already in use" errors for existing providers
 

APPS-1471

Improve authentication provider name entry, preventing invalid characters from being used and resolving invalid "This name is already in use" errors for existing providers    Actions

CORE-3555

Address issue where Responsive Grid column gutter settings cause undesired wrapping    

CORE-3577

Ensure input fields properly re-render the number zero (0) as 0    

CORE-3646

Ensure merge variables work properly for placeholder properties on text, text area, and picklist fields    

CORE-3695

Fix regression where message blocks within the Message Area component were no longer respecting context, displaying empty merge variables where values would be expected    

CORE-3705

Fix issue with variable setting on Salesforce data source code that caused the following error "Cannot set property size of #<Set> which has only a getter"    

INTEG-150

Ensure data source type cannot be changed once data sources are created    

INTEG-155

On SQL data sources, disable the "Test connection" button until changes are saved    

INTEG-162

In Skuid SFX when configuring a SQL data source, fix an issue where toggling the "Active" property and clicking "Cancel" would cause the General properties tab to disappear    

INTEG-168
Fix an issue where errors loading metadata would hang the browser window

Previously, the "Loading metadata for Data Dource" message would freeze the browser window if Skuid could not locate metadata at the supplied URL. Now a proper error message displays, allowing the user to continue working.    

INTEG-174
In Skuid SFX, display error if JWT signing certificate doesn't exist when trying to create a SQL data source
 

APPS-1974

Propagate various Skuid admin UI design updates    

CORE-3524

In the Table component, allow Template fields to be edited in Data Grid mode

Previously editing Template fields in Data Grid mode would not work and cause browser console errors. This change fixes this issue and updates the experience to match how editing works in "Read with inline-editing" mode    

CORE-3533

In Form components, prevent combobox fields at the top of the component from unexpectedly expanding their menus as soon as their Form is switched to Edit mode.

Note that if multiple components are switched to Edit mode via an action, if the last component is a Form—and that Form has a combobox as its first field—that combobox will still expand its menu. This is to retain consistency with current field focus behaviors.    

CORE-3537

Address issue where field enable conditions are ignored if a component is toggled into Edit mode more than once. Now field enable conditions are properly enforced, even after multiple component mode changes.    

CORE-3555

Address issue where Responsive Grid column gutter settings cause undesired wrapping    

CORE-3665

Adjust "Before Load Actions" behavior so that actions run each time before opening a drawer, matching the feature's behavior in Chicago U2    

CORE-3676

Remove "Add Button Group" option on List columns, because it isn't actually possible to add Button Groups there    

DSC-3480

Fix issue where time fields would begin to overlap each other in modals or on smaller screen sizes. Now time fields keep their spacing as expected.    

DSC-3497

To improve keyboard accessibility, adjust the keyboard focus and tab order of the Table component's drawer icon and row actions

Previously users attempting to tab or shift-tab past a Table drawer's chevron icon, or left-aligned row actions, would be "trapped" by its focus. This would prevent arrow keys from moving keyboard focus as expected, and pressing Escape would not reset focus. This was particularly apparent when working with checkboxes or rows while using mass actions. We've improved the way our Table tab focus is handled, allowing tabs and arrow keys to adjust focus in a more consistent way.    

DSC-3509

Fix issue where the Calendar's Create Event model would not display time selectors for start/end datetime fields, only allowing users to set the date. Now users can properly set the event's start and end time as well. 

CORE-3502
Fix issue where similarly named models would mistakenly be protected from deletion due to action dependencies

When a model is used in an action, it's protected from deletion to maintain page stability. However, Skuid previously would protect similarly named models from deletion as well, even if they were not used in an action. For example, a model named "account" could not be deleted if another model named "parent_account" was used in an action. Now models can be deleted as expected.    Actions

CORE-3534
Fix layout issue in model actions that are triggered by model conditions

Previously, the selected conditions' labels would overflow their container. Now conditions are truncated to indicate the number of selected conditions, revealing the full list when clicked by the builder.    

DSC-3224
Prevent users working with Salesforce records from seeing record type field options that are not assigned to them

Previously, users (regardless of Salesforce profile) could see all active record type values at runtime when editing records on Salesforce objects with record types enabled. Now Skuid validates the available options, ensuring users only see active record types that are assigned to them.    
 

DSC-3466
Fix issue where Skuid treated datetime fields as date fields when filtering for subqueries

Previously, when setting a subquery using a datetime field, Skuid would treat that datetime field as a date field, causing filters to fail. Builders could not resolve this issue in the Composer. Now Skuid properly parses the field metadata and treats the datetime fields as datetime fields.    Actions

DSC-3438
Fix issue where the "Required > Indicator placement" design system property also affected the placement of tooltip icons.    

DSC-3486
Fix issue where users would see an empty error block when opening a modal containing a Page Include referencing a page that also contained a modal or sliding panel

Previously if a page containing a modal or sliding panel was referenced through a Page Include component that was also contained in modal, there would be rendering issues that caused an empty error block to appear on the page. Now modals and sliding panels utilize conditional logic that allow them to function better when used in an included page, ensuring this empty error block does not appear.    

DSC-3487
Allow URLs to be clickable even if there is a "Click" interaction set on the component containing the URL    

APPS-1857
Limit design system and theme names to 38 characters on creation to account for static resource naming requirements    

DSC-3464
Fix issue where the Composer's Save button would unexpectedly enable when interacting with Responsive Grid components, even when no changes were made by the builder    

DSC-3500
Respect selected icon for Button Group menus in Tables at runtime    

DSC-3503
Fix styling in Database Console for autosave tooltip    

DSC-3514
Fix issue in Skuid Database where creating a reference field to an object would produce server and UUID errors    

DSC-3516
Fix malformed font family CSS generated by the Design System Studio so fonts render at runtime    

DSC-3520
Ensure custom field renderers render appropriately if a dataGrid strategy does not exist    

DSC-3502
Table column header labels using merge variables don't update when the merge variables change    

DSC-3496
Sort Builder jumps back and forth on the page as you add Sort lines    

DSC-3493
Allow Table column summaries (like Sum) to use Salesforce labels so they can access translation values    

DSC-3491
Data Grid: Double clicking a value in a cell while it's in Edit Mode doesn't select the value    

DSC-3490
Table Buttons with non-default style variants lose their styling when toggled between the Table's default mode (e.g. read mode) and an edit mode (e.g. Data Grid mode).    

DSC-3449
Allow Message Area component to properly read row context when in components like Decks 

APPS-1794
Update design system (and theme) naming modal text with more concise information about naming requirements

APPS-1856
Prevent page metadata text from wrapping

CORE-3511 - Affects v1
Fixes issues where Visualforce pages in v1 fail to load in IE11

DSC-3365
Add and adjust style properties for the Table component's data grid mode

DSC-3415
Address issue where promise rejection errors would stop the debugger, but only when developer tools were open on the user's browser

DSC-3428
Address issue where, within a Table drawer, a nested Table with frozen columns on the left side (typically because of actions) would have offset columns

DSC-3454
Fix the multipicklist selectors displayed when Skuid pages are shown on mobile devices

DSC-3458
Fix issue where Table components in data grid mode would not load in Lightning

DSC-3462
Fix Page name errors hidden behind modal when creating child pages from within the Composer

DSC-3465
Fixes an issue where Table buttons would sometimes lose their styling variant when toggling read/edit modes, particularly when style variant conditions are used

DSC-3468
New chart drilldowns don't work after deleting first chart drilldown

After deleting the first chart on a page, new charts would retain that first, deleted chart's ID. Because of this, they would not work as expected. This tickets fixes that behavior.

DSC-3469
Changing a Chart Series back to default hides category field property in the Properties pane

Changing a Chart component's Series from the "Chart default" model to a specific model allows builders to set a specific category field. Changing back the chart back to the default model would then hide the category field. The page XML would reflect the old field, even if was on a different mode, and builders were unable to correct this.

Now when the model is changed, the category field property remains visible and reverts to "Chart default" if needed.

DSC-3470
Fix instances in Dubai releases where v2 Charts were failing to render at runtime

DSC-3471
Fixes an issue where the category field property for new category axes would not appear until users navigated away from that property tab and navigated back

DSC-3477
Fix slowdown caused by adding unnecessary model listeners to components with background images

DSC-3484
Fix models that disappear after being used for reference lookup options

In Dubai releases and Chicago U2 releases beginning with 14.4.12, when a model was used to look up options for reference fields, the model would be unregistered from Skuid—preventing it from being accessed. This ticket addresses that issue, and models will no longer disappear.

DSC-3499
Backend testing fixes
 

DSC-2595    
In V2, the UI for Action Sequences on a master page viewed from the child page don't deselect, even when clicking elsewhere

DSC-3450
v2 Button sets in tables create uncaught error when using mass actions if a button group has no label

DSC-3411 - v1 to v2 Migration
v1 Tables with 2 or more unique drawers have their drawers converted into sliding panels to retain their nested components when converted to v2

DSC-3463    
Adjust Calendar time zone behaviors to more consistently account for differences between the user machine's time zone and server time zone

Previously our Calendar component would have issues if the user's machine's timezone did not match their locale time zone on the server. Users would see times in the calendar that were adjusted by that time zone difference.

Now we consistently use the user's server time zone to retrieve and format the time displayed in the component.

DSC-3479
Regression: Picklists using SQL models displaying inconsistently across Table modes

CORE-3511    - Affects v1
Fixes issues where Visualforce pages in v1 fail to load in IE11

APPS-1802
Lightning design system: Long text ellipsis not working in forms

DSC-3473    
Toggling a sliding panel only works for the first button that calls it

DSC-3427 - Affects v2
Picklist values not appearing in SF mobile

DSC-3401
Data grid Table mode click behavior not behaving predictably

DSC-3362
Copy/Paste support for Data grid Table mode
 

Fixes

APPS-1529    
Page Preview Modal: Improve copy and streamline previews

APPS-1537    
Update Theme/DS Creation modal in SFDC to inform users of naming limitations

APPS-1602    
Product design systems are available for selection when creating new Design System

APPS-1676    
Switching between data source objects in DSO permissions view toggles to the table profile view and selects the first profile

APPS-1751    
Lightning DSS updates based on user feedback

APPS-1765        
"Skuid Page Builder" Permission Set should add Skuid-related Custom Setting definitions

APPS-1769    
Add explicit class for "checkbox column" in Tables

APPS-1770    
Fix Lightning Design System Table JSS issues

APPS-1785    
Leave site popup after saving and exiting Data Source Object Fields/Access Control

DSC-3322: Affects v2
Page problems don't go away when user enters invalid content and then corrects it

DSC-3346    
Improvements to data source type options

DSC-3395    
Move 'add field' action to Table header

DSC-3396    
Hide search icon and show search bar when search is the only action in the Masthead

DSC-3421    
Improvements to admin features

DSC-3422    
Page Revision "Description" field has scroll bars

DSC-3424: Affects v2
Within the Composer, the search in the Models tab doesn't filter out Models on the Master Page

DSC-3429: Affects v2
Mass Update feature on Table automatically updated all rows of a required column to first value of picklist

DSC-3430: Affects v2
Sliding Panel throws console error

DSC-3432    
Read-only indicator for Table cells is off in unsaved records

DSC-3435    
Long picklist values no longer cut off with ellipsis in the Form layout

DSC-3442 
Attempting to access Schemas for a Data Source in Mac Safari, iOS Safari and iOS Chrome throws error "No 'Authorization' header present"

DSC-3443: Affects v2
Persistent error formatting after Cancel

DSC-3448    
Clicking Add Field button in Composer models section closes the fields list

DSC-3451    
Table component does not update UI on duplicate model update

DSC-3455    
Style Variants Conditions updates Table fields inconsistently based on UI Model values

Fixes

APPS-1685: Affects v1 and v2 
Update SFDC Skuid central page to include a section for Skuid Skool

APPS-1726: Affects v1 and v2
Empty state icons oversized

APPS-1741: Affects v1 and v2
Admin improvements for platform features

DSC-3323: Affects v2
After using keyboard navigation to pass out of a Table component, navigating back to that table will not work correctly

DSC-3340: Affects v2
Unable to use keyboard navigation to pass into a table drawer

DSC-3378: Affects v2
Standard fields will now appear as the last columns in the Table component

DSC-3390: Affects v1 
UI-only picklist values can't read custom labels in Salesforce

DSC-3398: Affects v2
Intermittent failure when importing design systems

DSC-3403: Affects v1 and v2
UI-only fields referencing Record Type picklists are not saving the initial selection in the dependent picklist

DSC-3410: Affects v1 and v2
Page with Queue component without "rendertemplate" will not migrate from v1 to v2

DSC-3412: Affects v2
Fields that have links trigger an error when clicked

DSC-3413: Affects v2
Performance improvements to DSS loading time

DSC-3414: Affects v2
Action to close all drawers in a Table component does not work

DSC-3418: Affects v2
Text Area using rich text will not render in pages deployed in Lightning Experience

DSC-3423: Affects v2
Tab Container with no rendered tabs will prevent a modal from rendering

DSC-3434: Affects v2
Fixed a bug in automated testing

Fixes

APPS-1667: Affects v2
Update Lightning Design System labels and descriptions

APPS-1698: Affects v2
Add padding in the Lightning Design System to Pagination control for default table

CORE-2988: Affects v2
Model names do not update on actions

DSC-3314: Affects v2
Keyboard support for Template Interactions in data grid mode for Table component

DSC-3319: Affects v2
For Landmark Components in HTML there is not a way to configure a Unique Role or Aria Label

DSC-3361: Affects v2
Focused class not applied to fields in data grid mode of the Table component

DSC-3389: Affects v2
Multipicklists near the bottom of a long page cannot be edited

DSC-3408: Affects v2
Fix for automated testing

Dubai: 15.0.5

From the Burj Khalifa to the Burj Al Arab, the ultramodern skyline of Dubai harbor leaves a big impression. It's the inspiration for our first 2022 release that offers major product enhancements to help you build the right apps.

Whether you’re supporting revenue teams, customer operations, or employee portals, this release gives you more tools to rapidly deliver design-led, inclusive experiences.

Dubai includes:

  • Fast navigation in DSS. Spend less time searching and more time finding elements.
  • Reduce user dependence on spreadsheets. Tables will have an additional mode called “data grid” with cleaner preset style defaults that support tab key navigation, making tables a better option for power users trying to leave spreadsheets behind.
  • Match your styles with Lightning. Salesforce design standards get regular updates. So, we’ve updated our own Lightning design system. You can also clone it and make modifications to add your own branding.
  • Create more accessible apps. Take advantage of new enhancements like Aria labels that make 508-compliance easier to achieve.
  • Stay tuned. More to come this March on Skuid app creation and management with multilevel permissions for users, app-centered development, and supplemental data with Skuid Database!

CORE-4611

Fix issue where reference field searches would not return expected records on some objects (such as the Case object in Salesforce) due to search value and record value/label discrepancies

CORE-4548

Fix Chart bug where context was not properly set after drilling down, returning to the main chart, and then drilling down into a new value Clicking into a Chart component segment sets the context, which can be used to display filtered drilldown information. Before this fix, returning to the main chart and then drilling down into another value would not properly set the context—instead using the previous drilldown’s values. With this fix, drilldowns work as expected.
 

CORE-4580

Fix issues for reference field lookup modals: * Raw SOQL queries appeared in the modal instead of the expected user-facing search terms * Deleting and re-entering a valid search string in the modal hid valid results Both issues are resolved by this ticket.

CORE-4579

Internal developer tooling improvements

CORE-4571

Fix issue where buttons could not be dragged from one Button Group component to another

CORE-4568

Remove style variant options from filters, because they cannot have style variants

CORE-4547

Fix issue in Design Systems screen where Update All button would fail with a “Visualforce Remoting Exception” error when updating batches of design systems that are larger in file size

CORE-4546

Fix issue where, when trying to upload a file larger than the size limit, the File Upload component would incorrectly say the file had successfully uploaded

CORE-4545

Fix issue where saving a blank value to a number field would cause issues on some SQL data sources

CORE-4546

Fix issue where, when trying to upload a file larger than the size limit, the File Upload component would incorrectly say the file had successfully uploaded

CORE-4463

Internal tooling updates

CORE-4495

Fix issue for Salesforce data sources where SOSL queries were being run as SOQL queries when initiated from within a modal

CORE-4491

Fix web font loading in v1 pages, which caused loading failures for Page Include components and their pages at runtime

CORE-4456

Ensure Filter Set data range label has appropriate spacing in comparison to other labels within the component

CORE-4449

Fix regression in Design System Studio styling that caused component list items to not expand to full area of the navigation pane

CORE-4422

Fix issue where URL parameters for boolean values would cause page previews from the Composer to fail

CORE-3891

Update {{startDate}} and {{endDate}} Calendar merge variables to properly return date values instead of datetime values—which are still available via {{startDateTime}} and {{endDateTime}}
 

CORE-4434
In Skuid SFX on the Calendar component, fix issue where "View more events" in Month view does not work

CORE-4416
Make the hover behavior for v1 disabled buttons consistent, ensuring tooltips display and cursor changes display as expected

CORE-4414
Fix issue where sliding panels restrict the size of modals, making them too small

CORE-4399
Fix issue in Table components set to read with inline-edit where an edited row outside of the browser's viewport would cause the Save button to shift focus to that out-of-sight row instead of saving

CORE-4395
Fix positioning of dropdown caret in Table component's Visible Rows property

CORE-3927
Fix issue in Calendar component's Week view where setting the end time to 12AM causes the component to freeze with JavaScript errors

CORE-3847
Fix Calendar component height issues, where bottoms rows unexpectedly expanded to fill the whole page
 

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-4351
Adjust custom formula function boilerplate template

CORE-3926
Improve scrolling behaviors for the Page Index when there are deeply nested components

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-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-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-3859
Fix issue where runtime pages with only a Calendar component (or few other components) would sometimes crash Chrome browsers---especially at smaller page widths

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-3928
Ensure error message blocks for Form components appear at the top of the component instead of the top of a section within it

CORE-3923
Fix issue where reference field search model does not look at orderBy property, preventing proper sorting of returned records

CORE-3915
SFX-specific fixes to prevent entire page from crashing if there is an error in loading custom component packs

CORE-3892
Improve spacing on Calendar component's week view to prevent time labels from overflowing to event area

CORE-3890
Adds visible dropzone placeholders when dragging actions, models, conditions, etc. in Composer

CORE-3878
Fix date picker bug where the first day of a month would not appear in the picker if that day was a Sunday and the user's locale sets the week to start on a Monday

For example, May 1st of 2022 was a Sunday. Previously May 1st would not appear in date pickers if the user's locale determined that weeks began on Mondays. After this ticket, May 1st will appear as expected.

CORE-3818
Fix issue where hotkey triggered action sequences attached to the Skuid page would not activate, even when the hotkeys were pressed

CORE-3813
Fix issue where multi-select filters that affect other conditions do not retain multiple selected values

Previously, when a component filter was set to "Affect other condition(s)," there would be issues ensuring the affected condition contained all values selected within the filter. With this fix, conditions are now updated appropriately, ensuring all selected values within the filter are used by the condition to filter records.

CORE-3770
Fix issue where exporting child relationship data from a Table component previously output "[object Object]" instead of the expected values
 

CORE-3861
Fix picklist alignment issues in pages that use the Lightning design system (or one based on it)

CORE-3841
Fix issue where Show/hide menu actions would cause "Cannot read properties of undefined (reading 'length')" errors if a menu section had no menu items

CORE-3837
Ensure the skuid.model.Model.loadAllRemainingRecords() API triggers only one model.loaded event---improving page performance since components must rerender when that event is published

CORE-3831
Fix issue where end users needed to click twice to save change in Form components set to read with inline edit

CORE-3822
Ensure font weights applied to Toast messages in Design System Studio are applied

CORE-3810
Ensure components that paginate (Decks, Lists, Tables) allow users to navigate pages properly, even if their footers are hidden

CORE-3791
Fix v1 Search component regression that caused fields within the component to display API names instead of labels
 

CORE-3738
In the Calendar component, ensure horizontal grouping lanes show correct start/end times

CORE-3762
Ensure checkbox fields displayed as switches can be returned to read mode after they've been toggled into edit mode

CORE-3812
In Safari, ensure fields receive browser focus when toggling from read to edit in Forms set to read with inline edit

CORE-3815
Fix issue where adding a row action to a List component would also add row actions to any nested elements (drawers, modals, sliding panels)

CORE-3824
Fix issue where adding a Responsive Grid to the canvas triggers automatic title case on action labels and some properties

CORE-3574
Allow v2 custom field renderers to be set even if there are no snippets on the page---which enables the use of custom field renderers stored as resources outside the page

CORE-3679
In Skuid SFX, ensure Console navigation for Name and Reference field links in Salesforce Classic work within orgs with enhanced domains enabled

CORE-3711
Prevent model requeries from breaking display logic on Table component buttons

Previously, when requerying the model attached to a Table component with buttons that utilize display logic would break the display logic of the buttons---causing unexpected behaviors (like all buttons disappearing). This ticket fixes the underlying issue.

CORE-3730
Ensure that opened menus close when a new menu is opened from a component in a Deck card

CORE-3733
Prevent models from requerying when the "Empty search behavior" property is set to "Remove all model data"

The "Empty search behavior" property is available on Filter Set, Table, List, and Deck components. Previously the "Remove all model data" option would not work appropriately, causing the model to requery even when the search term is blanked out. Now, all data will be removed properly.
 

CORE-3347
Ensure that picklists in v2 components properly display labels when Salesforce's state and country/territory feature enabled

CORE-3535
Ensure custom picklist field renderers override default options

CORE-3675
For Skuid SFX, ensure skuid.page.runningOnForceSite variable is set properly in orgs with enhanced domains enabled

When enhanced domains are enabled, this fix resolves the following issues:
- “Edit Page” button in Skuid pages no longer showing for admin users
- Page problems no longer displaying for admin users
- Some File Upload methods for the “Salesforce” data source not working as intended

As part of this fix, admin users may now see page problems that previously did not display. No new errors have been introduced; they just render correctly now.

CORE-3681
Fix issue where Table component filter's that source values from aggregate models display the first option from the source model instead of the selected option

CORE-3669
Fix issues where the Filter Mode property was still configured after switching to manual filters
Previously it was possible for builders would not realize a filter was operating client-side, because the Filter mode property would disappear when options and conditions were picked manually, but the "filterMethod" XML attribute would remain. As of this ticket, the XML attribute will be removed when necessary.

CORE-3533

In Form components, prevent combobox fields at the top of the component from unexpectedly expanding their menus as soon as their Form is switched to Edit mode.

Note that if multiple components are switched to Edit mode via an action, if the last component is a Form—and that Form has a combobox as its first field—that combobox will still expand its menu. This is to retain consistency with current field focus behaviors.    Actions

CORE-3537

Address issue where field enable conditions are ignored if a component is toggled into Edit mode more than once. Now field enable conditions are properly enforced, even after multiple component mode changes.    

CORE-3555

Address issue where Responsive Grid column gutter settings cause undesired wrapping    

CORE-3646

Ensure merge variables work properly for placeholder properties on text, text area, and picklist fields    

CORE-3676

Remove "Add Button Group" option on List columns, because it isn't actually possible to add Button Groups there    

CORE-3695

Fix regression where message blocks within the Message Area component were no longer respecting context, displaying empty merge variables where values would be expected    

CORE-3701

In v2, allow the columns of Table components attached to UI-only models to set sorting

Previously this sorting could be done through the Sort Builder or Sort model action, but this fix allows end users to sort on columns at runtime    
CORE-3705

Fix issue with variable setting on Salesforce data source code that caused the following error "Cannot set property size of #<Set> which has only a getter"    

DSC-3480

Fix issue where time fields would begin to overlap each other in modals or on smaller screen sizes. Now time fields keep their spacing as expected.    

DSC-3509

Fix issue where the Calendar's Create Event model would not display time selectors for start/end datetime fields, only allowing users to set the date. Now users can properly set the event's start and end time as well.
 

CORE-3534
Fix layout issue in model actions that are triggered by model conditions.
Previously, the selected conditions' labels would overflow their container. Now conditions are truncated to indicate the number of selected conditions, revealing the full list when clicked by the builder.    Actions

DSC-3224
Prevent users working with Salesforce records from seeing record type field options that are not assigned to them

Previously, users (regardless of Salesforce profile) could see all active record type values at runtime when editing records on Salesforce objects with record types enabled. Now Skuid validates the available options, ensuring users only see active record types that are assigned to them.

DSC-3487
Allow URLs to be clickable even if there is a "Click" interaction set on the component containing the URL    

DSC-3466
Fix issue where Skuid treated datetime fields as date fields when filtering for subqueries

Previously, when setting a subquery using a datetime field, Skuid would treat that datetime field as a date field, causing filters to fail. Builders could not resolve this issue in the Composer. Now Skuid properly parses the field metadata and treats the datetime fields as datetime fields.    

DSC-3516
Fix malformed font family CSS generated by the Design System Studio so fonts render at runtime    Actions

DSC-3500
Respect selected icon for Button Group menus in Tables at runtime    

DSC-3438
Fix issue where the "Required > Indicator placement" design system property also affected the placement of tooltip icons.
 

DSC-3502
Table column header labels using merge variables don't update when the merge variables change

DSC-3496
Sort Builder jumps back and forth on the page as you add Sort lines

DSC-3449
Allow Message Area component to properly read row context when in components like Decks

DSC-3454
Fix the multipicklist selectors displayed when Skuid pages are shown on mobile devices

DSC-3465
Fixes an issue where Table buttons would sometimes lose their styling variant when toggling read/edit modes, particularly when style variant conditions are used

DSC-3468
New chart drilldowns don't work after deleting first chart drilldown

After deleting the first chart on a page, new charts would retain that first, deleted chart's ID. Because of this, they would not work as expected. This tickets fixes that behavior.

DSC-3469
Changing a Chart Series back to default hides category field property in the Properties pane

Changing a Chart component's Series from the "Chart default" model to a specific model allows builders to set a specific category field. Changing back the chart back to the default model would then hide the category field. The page XML would reflect the old field, even if was on a different mode, and builders were unable to correct this.

Now when the model is changed, the category field property remains visible and reverts to "Chart default" if needed.

DSC-3471
Fixes an issue where the category field property for new category axes would not appear until users navigated away from that property tab and navigated back

DSC-3477
Fix slowdown caused by adding unnecessary model listeners to components with background images

DSC-3484
Fix models that disappear after being used for reference lookup options

In Dubai releases and Chicago U2 releases beginning with 14.4.12, when a model was used to look up options for reference fields, the model would be unregistered from Skuid—preventing it from being accessed. This ticket addresses that issue, and models will no longer disappear.

DSC-3499
Backend testing fixes

CORE-3511 - Affects v1
Fixes issues where Visualforce pages in v1 fail to load in IE11

DSC-3473    
Toggling a sliding panel only works for the first button that calls it

DSC-3463    
Adjust Calendar time zone behaviors to more consistently account for differences between the user machine's time zone and server time zone

Previously our Calendar component would have issues if the user's machine's timezone did not match their locale time zone on the server. Users would see times in the calendar that were adjusted by that time zone difference.

Now we consistently use the user's server time zone to retrieve and format the time displayed in the component.

DSC-3411 - v1 to v2 Migration
v1 Tables with 2 or more unique drawers have their drawers converted into sliding panels to retain their nested components when converted to v2

DSC-2595    
In V2, the UI for Action Sequences on a master page viewed from the child page don't deselect, even when clicking elsewhere

Fixes

         
DSC-3443: Affects v2
Persistent error formatting after Cancel

DSC-3442 
Attempting to access Schemas for a Data Source in Mac Safari, iOS Safari and iOS Chrome throws error "No 'Authorization' header present"

DSC-3430: Affects v2
Sliding Panel throws console error

DSC-3429: Affects v2
Mass Update feature on Table automatically updated all rows of a required column to first value of picklist

DSC-3424: Affects v2
Within the Composer, the search in the Models tab doesn't filter out Models on the Master Page

DSC-3322: Affects v2
Page problems don't go away when user enters invalid content and then corrects it

APPS-1765        
"Skuid Page Builder" Permission Set should add Skuid-related Custom Setting definitions

Fixes

DSC-3390: Affects v1 
UI-only picklist values can't read custom labels in Salesforce

DSC-3403: Affects v1 and v2
UI-only fields referencing Record Type picklists are not saving the initial selection in the dependent picklist

DSC-3410: Affects v1 and v2
Page with Queue component without "rendertemplate" will not migrate from v1 to v2

DSC-3412: Affects v2
Fields that have links trigger an error when clicked

DSC-3423: Affects v2
Tab Container with no rendered tabs will prevent a modal from rendering

Fixes

CORE-3371: Affects v2
When dragging parent fields from properties panel into component, Skuid doesn't handle fields with the same name correctly

CORE-3466: Affects v2
Form component: Dragging fields from model's property panel does not work

DSC-3260: Affects v2
Table field with error does not use Input text variant warning border attribute

DSC-3290: Affects v2
Issues with Display templates and Search templates when reference fields have the same API name

DSC-3317: Affects v1 and v2
Issues with Display templates and Search templates when selecting fields

DSC-3334: Affects v2
Manual filters with an initial condition defaulted to on are unable to return to original value

DSC-3338: Affects v2
Some fields in a Form component in read only mode become editable when data actions affect the Form's model

DSC-3342: Affects v2
Creating Child variant for Tab Containers in DSS throws console error

DSC-3368: Affects v2
Intermittent failure of design system import

DSC-3381: Affects v2
Navigating to a Reference field in the Search properties enables the Composer's save button

DSC-3384: Affects v2
List component does not reflect changes when model is updated

DSC-3389: Affects v2
Multipicklists near the bottom of a long page cannot be edited

DSC-3394: Affects v2 
Messages (errors, warnings) on field labels need role alert

DSC-3408: Affects v2
Fix for automated testing

Fixes

APPS-1641
Improvements to design system list

APPS-1659
Updated online learning portal link

CORE-3434: Affects v1 and v2
Can't close Lightning Quick Actions from within Skuid Page

DSC-695
A11Y: Improvements to Message Block component's accessibility features

DSC-3310: Affects v1 and v2
All rows are updated when Image field updates in table

DSC-3353: Affects v1 and v2
WCAG compliance: Allow the developer to specify the [lang] attribute for the page

Fixes

DSC-3279: Affects v2
Formatting issues for the "required" field icon and error message when deleting a value from a required field in a Table component

CORE-3454: Affects v1 and v2
Installation of Skuid managed package failed for Salesforce Spring '22 orgs

Fixes

CORE-3438: Affects v1 and v2
Performance improvements to the event unsubscribe process

DSC-2570: Affects v2
Imported Design Systems are not recompiled

DSC-2935: Affects v2
Run design system migrations on save of a design system

DSC-3226: Affects v2
Picklist displayed as Combobox does not support "Add None option" property

DSC-3249: Affects v2
Unable to interact with the Read with inline-editing icon as expected when Voice Over enabled in Form component

DSC-3253: Affects v2
Page properties do not display when selecting "Page" in the Index

DSC-3259: Affects v2
Vertical Navigation component items with Render Conditions do not work with hash navigation

DSC-3267: Affects v2   
Personalition framework does not remember which columns were frozen when end user interacts with Table settings menu

DSC-3315: Affects v2
toggleMenu action sometimes references incorrect component when toggling

Fixes

DSC-3255: Affects v2
Autocomplete does a query upon focus which can cause issues if the reference has thousands of records

DSC-3252        
Infrastructure changes for upcoming release

DSC-3248: Affects v2
Calendar throws error when viewed at mobile viewport sizes

DSC-3246: Affects v2
Can't insert fields into Text component

DSC-3241: Affects v2
Masthead spacing divisions dont respect min-width property

DSC-3240: Affects v2
Fix breaking richtext tests due to new ckeditor upgrade

DSC-3238: Affects v2
List component slow rendering performance on data updates

DSC-3233: Affects v2    
Show / Hide Menu action doesn't "HIDE" the menu

DSC-3223: Affects v2
Activate/Set Model Condition action on a Sub-Condition with Update Personalization checked is not remembered

DSC-3222: Affects v2
Filters that remember last-selected do not show the filter is active when the metadata changes

DSC-3220: Affects v2
"None" option doesn't work on combo boxes

DSC-3218: Affects v2
'Remember last-selected filter value' doesn't seem to be remembered when the condition is a subquery with a sub-condition that's field in another model

DSC-3217: Affects v2
Rich text toolbox gets stuck onscreen when scrolling in sliding panel or modal

DSC-3195: Affects v2
Display issues with Salesforce Boolean fields overridden with display type = picklist

DSC-3158: Affects v2
Make table actions menu button readable by assistive technology

DSC-3113: Affects v2
Polymorphic filtering is only searching on a single object

Fixes

CORE-3409: Affects v1
Polymorphic reference fields do not auto-populate as expected when metadata is overridden

DSC-2165: Affects v1 and v2
Web Content Accessibility Guidelines (WCAG) compliance: Improved support for screen readers

DSC-3157: Affects v2
508 compliance: Make picklist dropdown buttons and menus readable by assistive technology

DSC-3183: Affects v2    
When an updated Ui-only field queries a Table component's model, column display logic based on that field does not work

DSC-3204: Affects v2
508 compliance: Make multipicklist dropdown buttons and menus readable by assistive technology

DSC-3215: Affects v2
List of values for a reference field reappears after selecting a value

Fixes

CORE-3419
Editing Component packs in the Skuid code editor errors on save

DSC-2970: Affects v2
v1 Template's "Allow HTML" attribute does not correspond to the v2 Text component's "Allow HTML" property when migrating a page from v1 to v2

DSC-3145: Affects v2
Sort Builder fields misaligned

DSC-3150: Affects v2
Deck rerenders more components than needed on Model changes

DSC-3159: Affects v2
Assistive technology support for row action, drawer actions, mass action column labels, and Table select checkboxes (as reported in DSC-3161)

DSC-3174: Affects v2
Duplicate aggregate model countId created automatically when used in a rendering condition

DSC-3185: Affects v2
In the Calendar component, "Add an event" modal picklist shows sources that don't have any actions available

DSC-3191: Affects v2
Menu remains open and focused when ENTER key is used to open modal

DSC-3193: Affects v2
Reference field autocomplete doesn't handle non-string key values properly

DSC-3200: Affects v2
Skuid menus in LEX modals appear offset

Fixes

CORE-3414: Affects v1 & v2
When Salesforce's API access control settings restrict API access to only allowlisted connected apps, then picklists in Skuid would appear empty in Lightning Experience

CORE-3415: Affects v2
When multiplickist fields are in a model, searches on that model will result in an error when spaces exist between search criteria

DSC-3095: Affects v2
Picklist for selecting a data source intermittently displays incorrectly

DSC-3139: Affects v2
Modals and sliding panels do not work in Salesforce Mobile app on iOS devices

DSC-3146: Affects v2
Filtered Lookup rendered as picklist displays no results

DSC-3153: Affects v2
Rich text fields are narrower than other form fields in Lightning Experience

DSC-3162: Affects v2
Labels for required fields now support assistive technology

DSC-3168: Affects v2
Double-clicking on an aggregate model allows a "quick create" of a Table component connected to that model, the save and cancel buttons can not be removed when using the quick create method

DSC-3169: Affect v2
Improved logic for determing which modes are available for a Table component based on the model connected to that table

DSC-3170: Affects v2
When a sliding panel is in a Wizard component within a Page Include component, the sliding panel may activate without user interaction

DSC-3171: Affects v2
When a sliding panel is in a Page Include component within a Tab Container component, the sliding panel may activate when an end user selects any of the tabs on the Tab Container component

DSC-3172: Affects v2
In the Deck component, the context for row ID inconsistently persists when the model is queried

DSC-3173: Affects v2
Right-justification of table columns persists in mass update modal layout

DSC-3179: Affects v2
In the Design System Stuidio, the background color style for the selected state in a Tab Container component affects the content area, as well

DSC-3180: Affects v2
When clicking on a field link configured to navigate to the link according to the data source's default behavior, then a Skuid page in Lightning Experience will be unable to scroll

DSC-3181: Affects v2
Enable Conditions not working with Table Action buttons

DSC-3182: Affects v2
Column Gutter properties ignored when the Form component is nested within another component

DSC-3184: Affects v2
Fixes time locale automated test

DSC-3199: Affects v2
Fixes address field automated test

Fixes

DSC-3140: Affects v2
Lucida Sans font family not supported by design systems

DSC-3147: Affects v2
Table settings modal shows fields that are hidden by display logic

DSC-3148: Affects v2
In Lightning Experience, rich text fields duplicate on the first query when displayed in drawers

DSC-3166: Affects v2
Object picklists for polymorphic fields, like WhatId, are not alphabetized

Fixes

CORE-3407: Affects v1
Polymorphic reference fields display an empty object selector when the model is set to process server-side and when a field's setup meets the following criteria:

  • Override field metadata: checked
  • Display Type: Reference
  • Field properties > Reference tab > SObject Type: set to a single object

DSC-2790: Affects v1 & v2
On some Salesforce objects, record type values may appear as available field values even when those record type values are inactive or not assigned to the user's profile

DSC-3092: Affects v2
Filters with a combination of source options - model-based and manual - may not display label values correctly and may not filter when some values are selected

DSC-3123: Affects v2
For the Table component, when Allow HTML in column headers is checked, HTML code may appear in page-level error messages, mass update modals, and Table settings modal

DSC-3130: Affects v2
In navigation components, selecting the navigation item source as Salesforce tabs for current app or Salesforce apps with tabs may cause errors

DSC-3131: Affects v2
In the Calendar component, event source actions may disappear and event source actions may reappear after deletion

DSC-3133: Affects v2
Accordions do not have mouse-over changes to sections/section icon

DSC-3143: Affects v2
Design System Studio fails to load sections with large amounts of styles

Fixes

DSC-3057: Affects v2
Unable to remove a UI-Only field from a Table component after changing the Field Id value of the UI-Only field

DSC-3076: Affects v2
Fixes for style variant conditions:

  • Tooltip for adding a style variant condition rule now reads "Add new rule"
  • Tooltip for adding a style variant condition now reads "Add new condition"
  • Label for style variant conditions now indicates when the default style variant is selected

Fix for Calendar event sources:

  • Tooltip for adding a new event source now reads "Add new event source"

DSC-3079: Affects v2
Fixes missing text in Aria label for the search button on reference fields

DSC-3089: Affects v2
In the Form component, when the column property, Width, was set, the value of the column width was ignored when only one column was present in the Form

DSC-3090: Affects v2
Multiple instances of the same field in a Table component may fail to render when the field property in the Table component, Allow user to hide/show?, was set to allow end users to show or hide those fields

DSC-3091: Affects v2
After successfully uploading a file in a modal, a Lightning page will no longer scroll after closing the modal.

This occurs when:

  • the Skuid page is embedded in a Lightning page

  • the File Upload component is in a modal

  • the File Upload component Use Lightning's file upload component property is checked

  • a file successfully uploads

After these criteria are met, the Lightning page locks the ability to vertically scroll after the modal is closed.

The underlying cause is that the Lightning page fails to reset a CSS property (overflow) that allows for scrolling beyond the padding box of the rendered screen.

Skuid programmatically addresses this issue starting with the Chicago 14.4.6 and Boston 13.0.29 maintenance releases.

DSC-3094: Affects v1
Creating a child page from a master page (More Page Actions > Child Pages > Create New Child Page) results in a mismatched Page API

DSC-3132: Affects v2
In date fields, selecting a year or month value from the year or month picklists would close the date picker. This prevented a day value from being selected

Fixes

CORE-3374: Affects v1 & v2
Incorrect URL for MomentJS resources may cause Skuid pages to fail to load

DSC-3022: Affects v1
In the Table component, sticky column headers misaligned after switching the Tables mode then scrolling in the Table

DSC-3059: Affects v2
When a Skuid page is deployed in Lightning Experience, fields rendered as a checkbox will be misaligned vertically by a few pixels

DSC-3061: Affects v2
In the Search component, searching on objects generates a JavaScript error in the browser JavaScript console

DSC-3065: Affects v2
In a sliding panel, selecting a field rendered as textarea closes the sliding panel

DSC-3066: Affects v2
For textarea fields with a high character count, resizing the screen may cause unnecessary whitespace to appear below the field

DSC-3067: Affects v2
For data sources that support entities, configuring models in the Safari browser may truncate the entity name picklist

DSC-3073: Affects v2
In search modals for reference fields, columns are not sortable

Fixes

DSC-2940: Affects v2
In a Form component, the first column set in the Form or a section displays no properties in the Composer

DSC-3055: Affects v2
Long property labels may obscure Beta tag in the Composer

DSC-3056: Affects v2
In the Wizard component, some steps in a wizard may remain enabled after being set to inactive

DSC-3058: Affects v2
In the Form component, a field rendered as a slider may display incorrect value on page load

DSC-3062: Affects v2
In the Design System Studio, changes made to the Field subcomponent failed to reflect in the preview

DSC-3063: Affects v2
In the Form component,  the Allow HTML in field labels and section headers may fail to affects field labels

DSC-3072: Affects v2
In search modals for reference fields, autocomplete does not work; hitting the Enter key required to search for reference fields

DSC-3077: Affects v2
In filters, lookup filters do not apply to reference fields

Fixes

DSC-3002: Affects v2
Modal property: show errors in page does not work

DSC-3028: Affects v
Can not change Message Area component style variant after initial change

DSC-3029: Affects v2
Sliding Panel on requery throwing console Error when using Image field on Form component

DSC-3030: Affects v2
Sliding Panel on requery not loading Form's reference field picklists

DSC-3034: Affects v2
File Upload component button for file browsing does not work inside a Responsive Grid with interactions

DSC-3037: Affects v2
In modals with reference fields, record names are hyperlinked by default

DSC-3040: Affects v2
A very specific combination of Tables components with interactions on a page cause certain interactions to fail

DSC-3041: Affects v2
Kebab icon rendering in row number area of Table components

DSC-3042: Affects v2
Conditionally rendered navigation items sometimes appear in focus even when user has not intereacted with the items

DSC-3046: Affects v2
Calendar event query performance improvements

DSC-3054: Affects v2
Form component's allowHTML property overrides the Field's allowHTML property

Beta labels, context menus, and so much more. Update 2 is twice as exciting and built with YOU in mind.

Polish your UI with precision

More support for HTML in labels (beta)

Fine tuning UI controls just got easier! With the “Allow HTML” property, you can render HTML for elements in runtime.

Property in the Composer:

Page in runtime (Table component with HTML icons in column headers):

Options to choose error display location (modals and sliding panels)

Display error messages wherever you choose—in the parent page, modal, or sliding panel—making way for smoother user interactions.

“Defer tab rendering” for Tab Containers and Tab Sets

Optimize page load times by rendering only the current content (a much-loved feature from v1). Load background tabs only when you access them, preventing page slowness.

Make context menus more powerful

Skuid is built with Skuid, Inception-style, so we’ve added a feature that we wanted to use in other parts of the product.

You can now right-click on an element at the page level, on deck cards, lists, wrappers, or tables, and get the context menu.

By adding right-click interactions (beta), Table row interactions (beta), and the ability to set menu location (beta) with a mouse click, context menus become much more powerful and useful.

Additionally, tables now support interactions across the whole row, opening up options for context menus, drill down actions, and more functionality with a single click—no buttons needed.

Expand your Search component options

Search component merge variables (beta)

Providing a consumer-grade search experience is key to driving user engagement. The component-specific merge variable helps you build more search options for users.

Search component: enter keystroke property and actions (beta)

You’re no longer limited by the component’s dropdown menu with initial results. You can now hit Enter and see all search results when you run a search. Bring an elevated search experience to your communities and portals.

With beta labels, context menus, faster rendering times, and features you missed from v1, check out this version and get the latest Skuid experience!

Beta labels, context menus, and so much more. Update 2 is twice as exciting and built with YOU in mind.

Polish your UI with precision.

More support for HTML in labels (beta)

Fine tuning UI controls just got easier! With the “Allow HTML” property, you can render HTML for elements in runtime.

Property in the Composer:

Page in runtime: (Table component with HTML icons in column headers)

Options to choose error display location (modals and sliding panels)

Display error messages wherever you choose—in the parent page, modal, or sliding panel—making way for smoother user interactions.

"Defer tab rendering" for Tab Containers and Tab Sets

Optimize page load times by rendering only the current content (a much-loved feature from v1). Load background tabs only when you access them, preventing page slowness.

Make context menus more powerful.

Skuid is built with Skuid, Inception-style, so we’ve added a feature that we wanted to use in other parts of the product.

You can now right-click on an element at the page level, on deck cards, lists, wrappers, or tables, and get the context menu.

By adding right-click interactions (beta), Table row interactions (beta), and the ability to set menu location (beta) with a mouse click, context menus become much more powerful and useful.

Additionally, tables now support interactions across the whole row, opening up options for context menus, drill down actions, and more functionality with a single click—no buttons needed.

Expand your Search component options. 

Search component merge variables (beta)

Providing a consumer-grade search experience is key to driving user engagement. The component-specific merge variable helps you build more search options for users.

Search component: enter keystroke property and actions (beta)

You’re no longer limited by the component's dropdown menu with initial results. You can now hit Enter and see all search results when you run a search. Bring an elevated search experience to your communities and portals.

With beta labels, context menus, faster rendering times, and features you missed from v1, check out this version and get the latest Skuid experience!

Fixes

DSC-2958: Affects v2
v2 Page Migration Utility: when migrating actions that activate model conditions and set their value, the configuration of the set value may not migrate correctly

DSC-3004: Affects v2
Tab focus on recently opened modals defaults to the "Close" icon

DSC-3019: Affects v2
Table component: row height does not Fit to content if the height of the Table component is set to a fixed value

Fixes

DSC-2915: Affects v2
Reordering summary columns in a Table component with frozen columns causes an error message to appear in the browser's Javascript console

DSC-2944: Affects v1 and v2
Skuid's File Upload component prevents the Lightning File Upload component from uploading more than 1 file at a time

DSC-2960: Affects v2
Icons in the List component prevent access to row actions

DSC-2961: Affects v2
Divisions within the Responsive Grid component do not respect the height value of that component

DSC-2990: Affects v2
When end users open multiple drawers and modals from the List component, context for the models within the drawers and modals may be lost

DSC-2992: Affects v2
Migration utility fails to migrate reference field filters

DSC-2995: Affects v2
Unable to relocate column set within the Form component

DSC-2996: Affects v2
Improvements to rowId check

Fixes

CORE-3345: Affects v2
Lightning Workspace API inaccessible from a Page Include component

CORE-3357: Affects v1 and v2
Unable to select a model as an option source for polymorphic reference fields

DSC-2887: Affects v2
Aria labels now available for the Block UI and show message action

DSC-2933: Affects v2
Menus do not render on target element in Lightning Experience

DSC-2962: Affects v2
Data persists in reference fields when data is cleared out by the end user

DSC-2977: Affects v2
Improves Table component rendering and addresses accessibility issues reported in DSC-3160

DSC-2983: Affects v2
In a Table component with many template fields, clicking on a template configured to run actions may result in the Table shifting away from the click location

Fixes

DSC-2391: Affects v2    
Unnecessary property appears in Button Group properties

DSC-2875: Affects v1 & v2
Bubble Chart Labels show in triplicate

DSC-2877: Affects v1
When creating a new row via Action Sequence, cursor focus starts in reference field

DSC-2897: Affects v2
Buttons break when inside of a Responsive Grid component when changing Design System

DSC-2898: Affects v2
Collapsed horizontal Filter Set component still shows label of hidden filter

DSC-2900: Affects v2
Filter Set component with Picklist option source doesn't display dropdown values as expected if a search field is added

DSC-2912: Affects v2
Moving fields between components breaks field's connection to model

DSC-2917: Affects v2
Removing rows in components with pagination via an action causes "Uncaught RangeError" error

DSC-2920: Affects v1 & v2
Calendar Event start date goes back one day when users in timezones east of UTC create events based on Salesforce Task Due Date

DSC-2928: Affects v2
Disabled message not showing on hover for buttons and for tables and forms in read with inline-edit mode

DSC-2929: Affects v2
Searching for models in Models tab produces unexpected results

DSC-2931: Affects v2
Editing .RTF with existing data in Table drawers in Lightning Experience throws page error.

DSC-2934: Affects v2
Sort Builder button does not initially appear on page load when no models queried on page load

DSC-2937: Affects v2
When entering column widths, the input re-renders and focuses at end of cell

DSC-2938: Affects v2
When horizontal scroll enabled on the Table component with inline edit mode, first click on a field does not activate edit mode when that field was off-screen on page load

DSC-2941: Affects v2
When filters are collapsed, Date Range calendars may remain visible

DSC-2945: Affects v2
Unable to create lookup filters on polymorphic reference fields

DSC-2947: Affects v2
Performance issues related to rendering the Table component with enable conditions on fields

DSC-2949: Affects v2
Remove unnecessary rendering logic from Table component's render cycle

Fixes

DSC-2762: Affects v2
Validation errors not appearing in Salesforce Experience Cloud

DSC-2856: Affects v2
Column properties in the Form component may not apply at runtime

DSC-2899: Affects v2
Table column display logic based on the result of a formula runs inconsistently

Chicago Update 1

Additional display logic for Table row actions

With Chicago’s addition of button group fields in Tables and Forms, row actions in Tables didn’t have additional display logic options for conditional enabling or style variants. These options will now be available for builders who want them for Table row actions as well as button fields.

Ink Classic icons now available in icon library

Some customers shared that the change of styles in the new Ink icons were a potential issue for them in upgrading to Chicago. They requested that we add the old ones back as a set. You can select Ink Classic icons from the icon selector wherever they’re available in the Composer.

Search component: “View All” in results dropdown

The migration utility in Chicago revealed a product gap in v2: results in a Search component dropdown should have an option to “View All” if there are more results for an object than a dropdown can display. To help support migration for customers who depended on this feature, we’ve added this capability to v2 with new designs to make it consistent with v2 look and feel. It behaves similarly to the View All option in v1.

Calendar event sources now collapsible

With all of their actions, multiple event sources in the calendar can get unwieldy as soon as you have more than one. They now collapse and expand just like models do to help manage that space better.

Time field renderer

This small enhancement has been a long time coming. It’s one of the few Salesforce metadata types that Skuid hasn’t supported, but Time field renderers will be available in this update.

 

Improvements

CORE-3330: Affects v1 and v2
CSS moved to .css file, instead of inline CSS 

DSC-2799: Affects v2   
Add message to migration utility that says Visualforce includes are not supported

DSC-2823: Affects v2
Migrated Table components default to "sortable off"

DSC-2843: Affects v2
Remove cell mouse listeners which trigger hover states in the Table component

DSC-2851: Affects v2
Clean up the calls to Table component renderer

Fixes

CORE-3271: Affects v2
When an action auto-selects the first SFDC Weblink action on the list in the Composer, the weblinkname attribute isn't populated in the XML

DSC-2536: Affects v2
Form component: the autocomplete in Chrome populates field in focus but blanks out other fields

DSC-2558: Affects v2
Multiselect Filters on Reference Fields do not show "None Selected" text

DSC-2753: Affects v2
Migration:  Wrapper margin is not being migrated to respective Design System spacing

DSC-2756: Affects v2
Editing a dependent picklist with no values freezes the page

DSC-2796: Affects v2
Migration: Child pages are forcing "Theme: INK" instead of adopting the Design System of master page

DSC-2814: Affects v2
Calendar component actions behave unpredictably after viewing a grouped view

DSC-2816: Affects v2
Error message on File Upload component in DSS

DSC-2819: Affects v2
Sorting a Table component causes its column display logic to fail

DSC-2828: Affects v2
Minimum field height not applied when Form component configured to display labels on left

DSC-2835: Affects v2
If a Form component is in an Accordion component, the fields will not drag and drop

DSC-2836: Affects v2
Table component rows do not stripe background color properly

DSC-2837: Affects v2
Modified state no longer works in Table component

DSC-2838: Affects v2
Composer does not load in Safari browser

DSC-2840: Affects v2
Form component's Nested Components Style Variants are not being rendered 

DSC-2863: Affects v2
Unable to mass delete page revisions

DSC-2870: Affects v2
Lightning component error when editing date time fields

Fix

DSC-2815: Affects v2
Editing an empty date field in the Form component may cause an error when saving data
Previously, if an end user triggered edit mode for an empty date field in a Form component, but did not change the blank value of that date field, and changed the value of a different field, then an error would occur when saving the record.

Now, empty date fields in Form components will not trigger an error when records are saved.

Other issues included in this release:

DSC-2495

v2

Viewing a JS resource in Composer enables Save button
DSC-2810

v2

 Form component not getting new model context in builder
DSC-2825

v2

Revise mouse event logic to improve Table rendering

Welcome to Skuid Chicago

It’s here! Our 2021 Chicago release—a culmination of extensive customer feedback, insights from industry analysts, and months of hard work and innovation. Chicago has some exciting enhancements you’re going to love, like a new Calendar component, a migration utility, and more.

Skuid continues to expand the declarative toolkit with the Chicago release. It includes several enhancements to the core product, all of which can help customers build better apps and improve user experience.

So you can make the most of Chicago, we designed an entire release series with videos, blog posts, demos, and more. The Skuid developer community is another resource with peer-to-peer user support and knowledge sharing. Connect with us there and see what awesome things Skuid builders are doing in Chicago.

Declarative expansion

Calendar

With Chicago, building calendar pages has never been easier and the new Calendar component gives your users the ability to do more in a calendar view. Display Salesforce events, tasks, custom object records, or data from other sources like a REST API or Google Calendar. With the flexibility of Skuid data modeling and Action Framework, builders can set controls for users to add, edit, or delete calendar events.

In fact, by more tightly integrating the Calendar with Action Framework and Design System Studio, we’ve reduced the need for excess custom code that building previous calendar experiences required.

One big update you’ll appreciate: all-day/multi-day events. Display week-long conferences and all-day kickoffs, or even just reminders and deadlines, alongside meetings and calls.

The new Calendar component also comes with new styling options in Design System Studio. Create seamless branded calendar experiences in your customer or partner community as well as internal apps like group calendars for sales and project teams.

With these powerful calendar updates, build an entire sales app around a calendar experience, share a calendar on a partner portal, or embed calendars into record details to make account planning faster and easier. 

Button fields for Tables and Forms

Put a button anywhere. OK, that sounds a bit much, but it’s true. A builder can now design apps and pages to match how people work, and the user can take action right at the point of decision. Here’s what that means: 

Instead of the user needing to search for the button (usually by scrolling, left, right, up, or down), builders can put the button or interaction where it’s needed on Tables and Forms. 
 

Responsive Grid properties

We’ve updated the Responsive Grid to support additional properties like background color, image, and vertical alignment for grid divisions. Centering elements vertically and horizontally within a page is now a more straightforward process.

Custom font

Small touches make big impacts, and we’ve made several tweaks to help you personalize your brand. 

If you want to stand out in a crowded market, consistency in styling matters. That’s why you don't have to stick with out-of-the-box typography anymore. With our new custom font feature, add your own unique fonts to reinforce your brand identity.

Design System Studio will now support referencing a custom font by URL. It may be in a CDN, or maybe it's a static resource in your Salesforce org, but now you can get that iconic font that represents you, without code.
 

Conversion simplified 

There’s a new interface, new features, and a more powerful Skuid experience. Our v2 pages represent the next step for user interface development, and we've built a migration utility to help bring your v1 pages into the future.

Migration utility

With all the amazing features we've packed into Chicago, taking advantage of them means moving to v2. To help make the transition easier, we've added a migration utility tool that reduces the heavy lifting, making the process smoother and faster. The migration wizard is your guide. 

Vertical tabs

Vertical tab sets are used commonly for side navs and subtabs in v1, presenting an issue for customers who want to migrate. We’ve added a Vertical Navigation component in the Chicago release as an option for how a tab container renders.

Form columns

Add columns to a form without splitting  the form into multiple components, allowing for easier adherence to design specs. This removes an obstacle for customers wanting to migrate their pages with v1 Field Editors that use columns and column sets. Now, those columns and column sets will migrate into a v2 Form component. For new users, this update makes the Form component even more powerful.

Ditch the sheet

Export data

Exporting data shouldn’t feel like a tooth extraction. For instance, there are times you want to trigger an export of a Table component's data without requiring the user to click through a menu. Now you can trigger an export of Table data from anywhere by adding an export action to a button or any interactive part of a page.

List component enhancements

With the improvements to our List component, it’s easier to create hierarchy navigation pages, contact queues, task management consoles, and more. These “small” enhancements to the list component—styling the selected state for a list item and drawer actions—translate to big impact. With a list and a detailed view on the same page, your users can quickly and easily find what they’re seeking without opening another tab and breaking their flow of work.

Complex data sorting: multi-column Table sorting & Sort Builder

You don’t have to swivel between experiences when working with data in spreadsheets and Skuid. Some powerful spreadsheet tools that users rely on are now available in Chicago.

With the new Sort Builder, your data components like Tables, Lists, Decks, and Filter Sets now have a way to build sorts. Users can dynamically manipulate these data sets instead of builders baking sorts into the page or changing data sorts via JavaScript.

Small tweaks

Ink icon update

We’ve freshened up the Ink icon set used within the Skuid app-admin experience—just a few tweaks with heavier lines to improve readability on different types of monitors and screens. Your existing apps are in for a facelift using the default Ink icon set.

Known issue

DSC-2796
Migrated child pages do not inherit the design system of the master page
If you migrate a v1 child page to v2, the child page will apply the default Ink design system at runtime - rather than the design system of the master page. For now, you can go to the child page's properties and set the Design system property to match the design system of the master page.

This issue will be resolved in an upcoming maintenance release.

CORE-3675
For Skuid SFX, ensure skuid.page.runningOnForceSite variable is set properly in orgs with enhanced domains enabled

When enhanced domains are enabled, this fix resolves the following issues:
- “Edit Page” button in Skuid pages no longer showing for admin users
- Page problems no longer displaying for admin users
- Some File Upload methods for the “Salesforce” data source not working as intended

As part of this fix, admin users may now see page problems that previously did not display. No new errors have been introduced; they just render correctly now.

DSC-3224
Prevent users working with Salesforce records from seeing record type field options that are not assigned to them

Previously, users (regardless of Salesforce profile) could see all active record type values at runtime when editing records on Salesforce objects with record types enabled. Now Skuid validates the available options, ensuring users only see active record types that are assigned to them.
 

Fix

DSC-3442 
Attempting to access Schemas for a Data Source in Mac Safari, iOS Safari and iOS Chrome throws error "No 'Authorization' header present"

Fixes

DSC-3390: Affects v1 
UI-only picklist values can't read custom labels in Salesforce

DSC-3403: Affects v1 and v2
UI-only fields referencing Record Type picklists are not saving the initial selection in the dependent picklist

DSC-3423: Affects v2
Tab Container with no rendered tabs will prevent a modal from rendering

Fixes

CORE-3371: Affects v2
When dragging parent fields from properties panel into component, Skuid doesn't handle fields with the same name correctly

CORE-3466: Affects v2
Form component: Dragging fields from model's property panel does not work

DSC-3260: Affects v2
Table field with error does not use Input text variant warning border attribute

DSC-3290: Affects v2
Issues with Display templates and Search templates when reference fields have the same API name

DSC-3334: Affects v2
Manual filters with an initial condition defaulted to on are unable to return to original value

DSC-3342: Affects v2
Creating Child variant for Tab Containers in DSS throws console error

DSC-3381: Affects v2
Navigating to a Reference field in the Search properties enables the Composer's save button

DSC-3394: Affects v2 
Messages (errors, warnings) on field labels need role alert

Fixes

CORE-3434: Affects v1 and v2
Can't close Lightning Quick Actions from within Skuid Page

DSC-695
A11Y: Improvements to Message Block component's accessibility features

DSC-3310: Affects v1 and v2
All rows are updated when Image field updates in table

DSC-3353: Affects v1 and v2
WCAG compliance: Allow the developer to specify the [lang] attribute for the page

Fixes

DSC-3279: Affects v2
Formatting issues for the "required" field icon and error message when deleting a value from a required field in a Table component

CORE-3454: Affects v1 and v2
Installation of Skuid managed package failed for Salesforce Spring '22 orgs

Fixes

DSC-2935: Affects v2
Run design system migrations on save of a design system

DSC-3226: Affects v2
Picklist displayed as Combobox does not support "Add None option" property

DSC-3249: Affects v2
Unable to interact with the Read with inline-editing icon as expected when Voice Over enabled in Form component

DSC-3253: Affects v2
Page properties do not display when selecting "Page" in the Index

DSC-3259: Affects v2
Vertical Navigation component items with Render Conditions do not work with hash navigation

DSC-3267: Affects v2   
Personalition framework does not remember which columns were frozen when end user interacts with Table settings menu

DSC-3315: Affects v2
toggleMenu action sometimes references incorrect component when toggling

Fixes

DSC-3255: Affects v2
Autocomplete does a query upon focus which can cause issues if the reference has thousands of records

DSC-3252        
Infrastructure changes for upcoming release

DSC-3241: Affects v2
Masthead spacing divisions dont respect min-width property

DSC-3240: Affects v2
Fix breaking richtext tests due to new ckeditor upgrade

DSC-3223: Affects v2
Activate/Set Model Condition action on a Sub-Condition with Update Personalization checked is not remembered

DSC-3222: Affects v2
Filters that remember last-selected do not show the filter is active when the metadata changes

DSC-3220: Affects v2
"None" option doesn't work on combo boxes

DSC-3218: Affects v2
'Remember last-selected filter value' doesn't seem to be remembered when the condition is a subquery with a sub-condition that's field in another model

DSC-3217: Affects v2
Rich text toolbox gets stuck onscreen when scrolling in sliding panel or modal

DSC-3195: Affects v2
Display issues with Salesforce Boolean fields overridden with display type = picklist

Fixes

CORE-3409: Affects v1
Polymorphic reference fields do not auto-populate as expected when metadata is overridden

DSC-2165: Affects v1 and v2
Web Content Accessibility Guidelines (WCAG) compliance: Improved support for screen readers

DSC-3183: Affects v2    
When an updated Ui-only field queries a Table component's model, column display logic based on that field does not work

DSC-3215: Affects v2
List of values for a reference field reappears after selecting a value

Fixes

CORE-3414: Affects v1 & v2
When Salesforce's API access control settings restrict API access to only allowlisted connected apps, then picklists in Skuid would appear empty in Lightning Experience

CORE-3415: Affects v2
When multiplickist fields are in a model, searches on that model will result in an error when spaces exist between search criteria

DSC-3095: Affects v2
Picklist for selecting a data source intermittently displays incorrectly

DSC-3139: Affects v2
Modals and sliding panels do not work in Salesforce Mobile app on iOS devices

DSC-3153: Affects v2
Rich text fields are narrower than other form fields in Lightning Experience

DSC-3170: Affects v2
When a sliding panel is in a Wizard component within a Page Include component, the sliding panel may activate without user interaction

DSC-3171: Affects v2
When a sliding panel is in a Page Include component within a Tab Container component, the sliding panel may activate when an end user selects any of the tabs on the Tab Container component

DSC-3172: Affects v2
In the Deck component, the context for row ID inconsistently persists when the model is queried

DSC-3173: Affects v2
Right-justification of table columns persists in mass update modal layout

DSC-3179: Affects v2
In the Design System Stuidio, the background color style for the selected state in a Tab Container component affects the content area, as well

DSC-3180: Affects v2
When clicking on a field link configured to navigate to the link according to the data source's default behavior, then a Skuid page in Lightning Experience will be unable to scroll

Fixes

CORE-3414: Affects v1 & v2
When Salesforce's API access control settings restrict API access to only allowlisted connected apps, then picklists in Skuid would appear empty in Lightning Experience

CORE-3415: Affects v2
When multiplickist fields are in a model, searches on that model will result in an error when spaces exist between search criteria

DSC-3095: Affects v2
Picklist for selecting a data source intermittently displays incorrectly

DSC-3139: Affects v2
Modals and sliding panels do not work in Salesforce Mobile app on iOS devices

DSC-3153: Affects v2
Rich text fields are narrower than other form fields in Lightning Experience

DSC-3170: Affects v2
When a sliding panel is in a Wizard component within a Page Include component, the sliding panel may activate without user interaction

DSC-3171: Affects v2
When a sliding panel is in a Page Include component within a Tab Container component, the sliding panel may activate when an end user selects any of the tabs on the Tab Container component

DSC-3172: Affects v2
In the Deck component, the context for row ID inconsistently persists when the model is queried

DSC-3173: Affects v2
Right-justification of table columns persists in mass update modal layout

DSC-3179: Affects v2
In the Design System Stuidio, the background color style for the selected state in a Tab Container component affects the content area, as well

DSC-3180: Affects v2
When clicking on a field link configured to navigate to the link according to the data source's default behavior, then a Skuid page in Lightning Experience will be unable to scroll

Fixes

DSC-3140: Affects v2
Lucida Sans font family not supported by design systems

DSC-3147: Affects v2
Table settings modal shows fields that are hidden by display logic

DSC-3148: Affects v2
In Lightning Experience, rich text fields duplicate on the first query when displayed in drawers

DSC-3166: Affects v2
Object picklists for polymorphic fields, like WhatId, are not alphabetized

Fixes

CORE-3407: Affects v1
Polymorphic reference fields display an empty object selector when the model is set to process server-side and when a field's setup meets the following criteria:

  • Override field metadata: checked
  • Display Type: Reference
  • Field properties > Reference tab > SObject Type: set to a single object

DSC-2790: Affects v1 & v2
On some Salesforce objects, record type values may appear as available field values even when those record type values are inactive or not assigned to the user's profile

DSC-3092: Affects v2
Filters with a combination of source options - model-based and manual - may not display label values correctly and may not filter when some values are selected

DSC-3133: Affects v2
Accordions do not have mouse-over changes to sections/section icon

DSC-3143: Affects v2
Design System Studio fails to load sections with large amounts of styles

Fixes

DSC-3076: Affects v2
Fixes for style variant conditions:

  • Tooltip for adding a style variant condition rule now reads "Add new rule"
  • Tooltip for adding a style variant condition now reads "Add new condition"
  • Label for style variant conditions now indicates when the default style variant is selected

Fix for Calendar event sources:

  • Tooltip for adding a new event source now reads "Add new event source"

DSC-3079: Affects v2
Fixes missing text in Aria label for the search button on reference fields

DSC-3090: Affects v2
Multiple instances of the same field in a Table component may fail to render when the field property in the Table component, Allow user to hide/show?, was set to allow end users to show or hide those fields

DSC-3091: Affects v2
After successfully uploading a file in a modal, a Lightning page will no longer scroll after closing the modal.

This occurs when:

  • the Skuid page is embedded in a Lightning page

  • the File Upload component is in a modal

  • the File Upload component Use Lightning's file upload component property is checked

  • a file successfully uploads

After these criteria are met, the Lightning page locks the ability to vertically scroll after the modal is closed.

The underlying cause is that the Lightning page fails to reset a CSS property (overflow) that allows for scrolling beyond the padding box of the rendered screen.

Skuid programmatically addresses this issue starting with the Chicago 14.4.6 and Boston 13.0.29 maintenance releases.

DSC-3094: Affects v1
Creating a child page from a master page (More Page Actions > Child Pages > Create New Child Page) results in a mismatched Page API

DSC-3132: Affects v2
In date fields, selecting a year or month value from the year or month picklists would close the date picker. This prevented a day value from being selected

Fixes

DSC-3022: Affects v1
In the Table component, sticky column headers misaligned after switching the Tables mode then scrolling in the Table

DSC-3059: Affects v2
When a Skuid page is deployed in Lightning Experience, fields rendered as a checkbox will be misaligned vertically by a few pixels

DSC-3061: Affects v2
In the Search component, searching on objects generates a JavaScript error in the browser JavaScript console

DSC-3065: Affects v2
In a sliding panel, selecting a field rendered as textarea closes the sliding panel

DSC-3067: Affects v2
For data sources that support entities, configuring models in the Safari browser may truncate the entity name picklist

DSC-3073: Affects v2
In search modals for reference fields, columns are not sortable

Fixes

DSC-3045: Affects v1
Composer for v1 pages does not correctly parse legacy XML for Apex actions

DSC-3056: Affects v2
In the Wizard component, some steps in a wizard may remain enabled after being set to inactive

DSC-3058: Affects v2
In the Form component, a field rendered as a slider may display incorrect value on page load

DSC-3062: Affects v2
In the Design System Studio, changes made to the Field subcomponent failed to reflect in the preview

DSC-3072: Affects v2
In search modals for reference fields, autocomplete does not work; hitting the Enter key required to search for reference fields

DSC-3077: Affects v2
In filters, lookup filters do not apply to reference fields

Fixes

DSC-3028: Affects v2
Can not change Message Area component style variant after initial change

DSC-3029: Affects v2
Sliding Panel on requery throwing console Error when using Image field on Form component

DSC-3030: Affects v2
Sliding Panel on requery not loading Form's reference field picklists

DSC-3034: Affects v2
File Upload component button for file browsing does not work inside a Responsive Grid with interactions

DSC-3037: Affects v2
In modals with reference fields, record names are hyperlinked by default

DSC-3042: Affects v2
Conditionally rendered navigation items sometimes appear in focus even when user has not intereacted with the items

Fixes

DSC-2915: Affects v2
Reordering summary columns in a Table component with frozen columns causes an error message to appear in the browser's Javascript consoleActions

DSC-2944: Affects v1 and v2
Skuid's File Upload component prevents the Lightning File Upload component from uploading more than 1 file at a time

DSC-2960: Affects v2
Icons in the List component prevent access to row actions

DSC-2990: Affects v2
When end users open multiple drawers and modals from the List component, context for the models within the drawers and modals may be lost

DSC-2993: Affects v2
Field style modified state overridden by Table cell's modified state

DSC-2996: Affects v2
Improvements to rowId check

DSC-3019: Affects v2
Table row height does not fit to content if the height of the Table itself is set to a fixed value

DSC-3021: Affects v2
Buttons and navigation items inherit the styling of links; ignoring the styling set for buttons and navigation items

DSC-3031: Affects v2
In the Filter Set component, if setting the values for multiple filters, then only the first value is applied - the other values are ignored

DSC-3036: Affects v2
Table component renders as empty after saving new rows in a modal

Fixes

CORE-3345: Affects v2
Lightning Workspace API inaccessible from a Page Include component

CORE-3357: Affects v1 and v2
Unable to select a model as an option source for polymorphic reference fields

DSC-2887: Affects v2
Aria labels now available for the Block UI and show message action

DSC-2933: Affects v2
Menus do not render on target element in Lightning Experience

DSC-2962: Affects v2
Data persists in reference fields when data is cleared out by the end user

DSC-2977: Affects v2
Improvements to Table component rendering

DSC-2983: Affects v2
In a Table component with many template fields, clicking on a template configured to run actions may result in the Table shifting away from the click location

Fixes

DSC-2391: Affects v2
Unnecessary property appears in Button Group properties

DSC-2938: Affects v2
When horizontal scroll enabled on the Table component with inline edit mode, first click on a field does not activate edit mode when that field was off-screen on page load

DSC-2947: Affects v2
Performance issues related to rendering the Table component with enable conditions on fields

Fixes

CORE-3262: Affects v1 & v2
Page breaks when displaying dependent picklist without controlling field in model

DSC-2762: Affects v2   
"Validation Error" not displaying on Salesforce Experience Cloud page

DSC-2801: Affects v2     
Double-click row action to open drawer generates console error

DSC-2830: Affects v2     
Mass Update modal does not display title

DSC-2864: Affects v2     
In Lightning Experience, Rich text fields don't update when model changes cancelled

DSC-2865: Affects v2     
In Accordion components, Chart components with drilldown actions clone themselves when the Accordion opens and closes

DSC-2892: Affects v2     
Pressing ENTER to edit cell in Table component does not work with frozen columns

DSC-2893: Affects v2     
List component's with footers may render incorrectly in Composer

DSC-2899: Affects v2     
In Table components, column-based display logic using the result of a formula works inconsistently

Improvements

DSC-2843: Affects v2
Remove cell mouse listeners which trigger hover states in Table component

DSC-2851: Affects v2
Clean up calls to Table component render

Fixes

CORE-3271: Affects v2
When an action auto-selects the first SFDC Weblink action on the list in the Composer, the weblinkname attribute isn't populated in the XML

DSC-2536 : Affects v2   
Form component: the autocomplete in Chrome populates field in focus but blanks out other fields

DSC-2558: Affects v2
Multiselect Filters on Reference Fields do not show "None Selected" text

DSC-2756: Affects v2
Editing a dependent picklist with no values freezes the page

DSC-2816: Affects v2
Error message on FileUpload component in DSS

DSC-2819: Affects v2
Sorting a Table component causes its column display logic to fail

DSC-2828: Affects v2
Minimum field height not applied when Form component configured to display labels on left

DSC-2836: Affects v2
Table component rows do not stripe background color properly

DSC-2837: Affects v2
Modified state no longer works in Table component

DSC-2840: Affects v2
Form's Nested Components Style Variants are not being rendered (Chicago only)

DSC-2863: Affects v2
Unable to mass delete page revisions

DSC-2870: Affects v2
Lightning component error when editing datetime fields

Fix

DSC-2815: Affects v2
Editing an empty date field in the Form component may cause an error when saving data
Previously, if an end user triggered edit mode for an empty date field in a Form component, but did not change the blank value of that date field, and changed the value of a different field, then an error would occur when saving the record.

Now, empty date fields in Form components will not trigger an error when records are saved.

Other issues included in this release:

DSC-2495

v2

 Viewing a JS resource in Composer enables Save button
DSC-2780

v2, v1

Caret icon is located below the center of the input when selecting Component in Run component action
DSC-2805

v2

Components inside of a Deck in a sliding panel or modal lose context
DSC-2813

v2

Changing Unsaved changes warning property to "No" removes property from XML
DSC-2825

v2

Revise mouse event logic to improve Table rendering

Fixes

CORE-3229: Affects v1 and v2
Sorts on unsortable fields
Previously, Skuid models permitted sorting, like column sorting in a Table component, on fields that are specified as unsortable, like textarea fields, by the data source’s metadata. This caused components with sorting capabilities and, sometimes, whole pages to freeze. Refreshing the page would not fix the issue because Skuid’s personalization framework stored the invalid sort in the cache. System administrators or page builders would need to intervene.

Now, Skuid models remove the ability to sort on unsortable fields.

DSC-2668: Affects v2
Unable to change manual sources for filters based on model conditions using subqueries
Previously, Skuid builders could not change the manual sources for filters when those filters were configured to interact with model conditions based on the results of subqueries. The workaround involved changing the target model condition for the filter to a non-subquery type.

Now, Skuid builders can change the manual sources for filters that interact with a model condition based on a subquery.

DSC-2672: Affects v2
In Table components, row actions do not render when templates have interactions
Previously, row actions in a Table component will no longer render in the Composer if a template field is configured with an interaction that launches a modal containing a Table component. At runtime, the row actions will appear in the Table, but the Composer will no longer display the row actions.

Now, in the Composer, row actions will appear in the Table component when template fields have interactions that launch modals with Tables in them.

DSC-2684: Affects v2
Context property tab missing for components within a modal launched by a chart
Previously, components within a modal launched from an on-click action on a Chart series would not have the context property tab available in the Composer. The workaround was to add context conditions via the XML editor.

Now, the context property tab is available for components within an on-click action that launches a modal from a Chart.

DSC-2779: Affects v2
Removing values from numeric range filter generates errors
Previously, in runtime, if an end user cleared out (deleted/backspaced) the numbers in the numeric range filter, then errors would appear on the page. Clicking the filters Reset button would not generate an error - only deleting the values in the numeric range filter.

Now, end users can remove the numbers in the numeric range filter without triggering an error.

Other fixes included in this release:

CORE-3268, DSC-2600, DSC-2701, DSC-2713, DSC-2725, DSC-2727, DSC-2729, DSC-2732, DSC-2741, DSC-2765, DSC-2775, DSC-2777, DSC-2780, DSC-2783, and DSC-2786.
 

Fixes

CORE-3098: Affects v2
Marking, then unmarking, Table rows for deletion breaks display logic
Previously, when marking a Table row for deletion, then unmarking for deletion, the Table component’s model still registers unsaved changes, even though the changes were rejected. This caused display logic based on model data changes to display/hide elements based on inaccurate conditions.

Now, marking, then unmarking, Table rows for deletion will affect display logic based on model changes in an expected way.

DSC-2631: Affects v2
Reference field displayed as a picklist displays checkmarks for all field values
Previously, reference fields - when rendered as a picklist - displays all values as “checked”. This meant that you could not tell from the picklist menu which value had been previously selected - they all appeared to be selected.

Now, reference fields will properly check the selected value when the field is rendered as a picklist.

DSC-2679: Affects v2
Fixes for Tab Set styling in Design System Studio
Previously, the Label text decoration property did not work for Tab, Selected state, and Hover state elements of Components > Tab Set in Design System Studio. Additionally, Background color for Selected state was unavailable.

Now, Tab Set styling in Design System Studio works as expected.

DSC-2682: Affects v2
Section headings in Form component do not receive context
Previously, the section headings in the Form component would not receive the values in context conditions. This meant that merge syntax in section headings would not display contextual values.

Now, section headings in Form components properly receive values from context conditions.

Other fixes included in this release:

DSC-2637, DSC-2638, DSC-2669, DSC-2676, and DSC-2677.
 

Fixes

CORE-3247: Affects v1 and v2
Picklist values do not render in Lightning Communities when the model’s object has record types
Previously, when a Skuid was deployed in a Lightning Community, picklist fields appeared empty when the field was on a model connected to a Salesforce object with record types. 

Now, picklist fields display data from object’s with record types on Skuid pages deployed in Lightning Community.

DSC-2612: Affects v2
Template fields in the List component do not render HTML
Previously, if a builder adds HTML to a child relationship field that is rendered as a template in a List component, then the HTML will not render even though the Render HTML field property is checked. Instead, the end user will see the HTML syntax.

Now, a child relationship template field in a List component will render HTML.

DSC-2619: Affects v2
Merge syntax fails to load data in field labels in the Form component
Previously, merge syntax in the Custom label of a field in a Form component would fail to load the expected values. The workaround was to use global merge syntax to access the data.

Now, merge syntax in the Custom label of a field in a Form component will load data.

Other fixes included in this release:

CORE-3236, CORE-3252, DSC-2540, and DSC-2625.
 

Fixes

DSC-2503: Affects v2
Dropdowns for date and picklist fields do not appear
Previously, end users would not be able to interact with the dropdowns on date and picklist fields when those fields were on data components nested within the Wrapper or Responsive Grid component on a page brought in by a Page Include component.

Now, the dropdowns for date and picklist fields will appear when displayed within a Wrapper or Responsive Grid component within a page from a Page Include component.

DSC-2590: Affects v2
Unable to edit picklist dropdowns on certain Lightning template layouts
Previously, picklist fields on Skuid pages deployed in Lightning Detail page layouts with 3 regions would fail to display when the Skuid page was in the right-hand region of the layout. If the Skuid page was in the left-hand or center region, the picklist dropdowns would display as expected.

Now, end users will be able to interact with picklist dropdowns on Skuid Pages in the right-hand region of a 3-region Lightning Detail page.

DSC-2591: Affects v2
Errors on a page from Page Include component cause page to fail to load
Previously, if an error occurred on a page from a Page Include component, then that page would fail to load into the Page Include component. The end user would see no error, but would find a JavaScript error in the browser console.

Now, errors on the page from a Page Include component will appear on the main page and the page will successfully load.

DSC-2593: Affects v1 and v2
Wrapper background image doesn't work with field variable
Background images in Wrapper components don’t work when sourced from a model
Previously, the Wrapper component failed to display a background image when the Image source was set to URL and a model field was used for the Image URL. This meant that a “dynamic” method for determining the Wrapper’s background image was not available for URL data in fields on models. 

Now, the Wrapper component can determine the background image by pulling the image URL from field data on a model.

DSC-2604: Affects v1 and v2
Unable to select model condition for a multi-select option filter
Previously, a builder could not choose a model condition, where the model condition’s Operator value was set to in and Content was set to Field from another model, for the Model condition to affect property if the filter was a multi-select filter. This meant multi-select filters could not use “model merge” to determine the filter values presented to the end user.

Now, multi-select filters can interact with model conditions where data from one model determines the data in another model.

DSC-2614: Affects v2
Error message unavailable for translation
Previously, the error message, This Field is Required, was unavailable for translation when the Salesforce org default language was any language other than English. Other error messages would translate successfully.

Now, end users will see the message, This Field is Required, in the default language of their Salesforce org.

Other fixes included in this release:

CORE-3239, DSC-2585, DSC-2589, DSC-2594, DSC-2601, DSC-2605, DSC-2606, and DSC-2607.
 

Fixes

CORE-3097: Affects v1 and v2
In Lightning Communities, Skuid fails to retrieve Record Type metadata from external Salesforce data sources
Previously, Skuid models connected to an external Salesforce data source would fail to retrieve Record Type metadata when the Skuid page was deployed in Lightning Communities for authenticated users. No error message would appear. Instead, the problem would present itself to the end user when they attempted to interact with Record Type metadata-based elements of a Skuid page. For example, if picklist options were based on the metadata for Record Type - the picklists would be empty.

Now, authenticated users to Lightning Communities will be able to interact with the elements of a Skuid page that depend upon the Record Type metadata from an external Salesforce data source.

DSC-2574: Affects v2
Navigation menus detached from navigation element
Previously, dropdown menus on items in the Navigation component were offset by several pixels by default. This meant the menus were not attached to the navigation item the end user clicked. Creating a Style Variant in Design System Studio with a negative value for the top margin would not correct the issue.

Now, you can change the offset value by adjusting the spacing properties in the Navigation component or changing the value of the Menu offset from navigation property in Design System Studio > Components > Navigation > General.

Other fixes included in this release:

CORE-3089 and DSC-2580.

Fixes

DSC-2163: Affects v1 and v2
Skuid’s Chatter component does not work as expected in Lightning environments
Previously, end users could not enter data into a Chatter component on a Skuid page when that page was deployed to a Lightning environment. The workaround was to use the Lightning’s Chatter component.

Now, Skuid’s Chatter component allows user interaction when deployed in a Lightning environment.

DSC-2547: Affects v2
Filter Set component’s reset button does not enable when a filter value is selected
Previously, if the Filter Set component’s Reset button property is set to Enable when filters activate, the reset button would not enable when a value was selected. The reset button remained disabled. If a second value was selected by the end user, then the reset button would enable.

Now, the Filter Set component’s reset button will be enabled when the end user first selects a value.

Other fixes included in this release:

DSC-2539, DSC-2548, and DSC-2555.
 

Fixes

DSC-2456: Affects v1
Link options for Name fields in Salesforce
Previously, linking behavior would fail on Name fields when the Link Options were set to respect the data source’s default behavior.

Now, Name fields configured to use the data source’s linking behavior will behave as expected.

DSC-2486: Affects v1 and v2
Currency fields go blank in charts after model query in a Salesforce org with multiple currencies enabled
Previously, data in currency fields in visualization components failed to display after the component’s model was queried. This occurred in Salesforce orgs where the multiple currencies property is enabled.

Now, for Salesforce orgs with multiple currencies enabled, data in currency fields in visualization components will update, as expected, after the component’s model is queried.

DSC-2507: Affects v1
Unable to sort date and datetime fields in a Postgres datasource
Previously, the checking the box to Allow Sorting for fields in a model connected to a Postgres datasource would not work as expected. This affected date and datetime fields only.

Now, you can enable sorting for date and datetime fields on a Postgres datasource.

DSC-2541: Affects v1 and v2
In bubble charts, the width of the bubble does not reflect the data
Previously, a Chart component configured as a Bubble chart would not respect the value of the data from the field used by the Size field property. This occurred when the Size aggregate function property was set to --None--. If an aggregate function was selected, the size of the bubbles would match the data.

Now, the size of the circle in a bubble chart will reflect the data even when the value of the field is not aggregated.

Other fixes included in this release:

CORE-3189, DSC-2485, DSC-2498, DSC-2499, DSC-2528, DSC-2531, DSC-2534, DSC-2535, DSC-2539, and DSC-2544.

Fixes

CORE-3134: Affects v2
Apex action fails to populate stored parameter value on revisit
Previously, when using the Action Framework to declaratively interact with invokable Apex, the action would appear to clear out the values input as the Apex parameter. The values were saved (and were visible in the XML view), but the action in the composer failed to show the values set by the builder. 

Now, Salesforce data source actions in Skuid will show in the composer any values set for the Apex parameter of the action.

DSC-2402: Affects v2
Filter Set component shows incorrect text when a blank value is selected
Previously, the Filter Set component would incorrectly label a blank value as "None Selected" instead of the text determined by the builder as the optional text.

Now, the user will see the text set by the builder in the Filter Set component's properties.

DSC-2453: Affects v2
Duplicate File Upload component appearing on Skuid pages in Lightning environments
Previously, a doppelgänger of Lightning's file upload component would appear on a Skuid page if the Skuid File Upload component was embedded in a Wizard component and the File Upload component was configured to use Lightning's file upload component when in a Lightning environment. Under these circumstances a duplicate file component would render - but not be usable. Refreshing the page would sometimes clear the duplicate.

Now, one file upload component will appear on the page.

DSC-2454: Affects v2
Actions assigned to first-level navigation elements that have sub-navigation elements are ignored in the Vertical Navigation component
Previously, in the Vertical Navigation component, any navigation element with sub-navigation elements would not fire actions assigned to the navigation element. Instead, the navigation element would expand to display the sub-navigation elements without firing any assigned actions.

Now, actions configured to fire when a user clicks on a first-level navigation element that has sub-navigation items will run as expected.

Other fixes included in this release:

DSC-2424, DSC-2427, DSC-2449, DSC-2451, DSC-2455, DSC-2457, DSC-2464, DSC-2468, DSC-2474, and DSC-2506.

Announcement

Breaking change to API v2 introduced by DSC-2443

skuid.component.getByType() now returns an empty array if it finds no matches.

Theskuid.component.getByType() API retrieves instances of component types and returns an array of all matching components.

Previously, if there were no matches, we returned an empty object. We've changed this behavior to now return an empty array, which better matches the behavior of a successful search.

If your code makes use of this API and expects an object, review it and update it accordingly.

Fixes

CORE-3144: Affects v2
Skuid v2 pages do not receive id parameters in certain deployment conditions
Previously, if a Skuid v2 page was deployed through a Visualforce page that overrides a Salesforce detail view, then the model conditions expecting an id parameter through page query parameter strings would not receive the id value. Model conditions based on page parameters did work on Skuid v1 pages deployed in the same manner and, also, work for Skuid v2 pages deployed in Lightning Experience.

Now, model conditions on Skuid v2 pages deployed through Visualforce pages on overridden record detail views will successfully pick up page parameters.

CORE-3162: Affects v1 and v2
Unable to use model condition to set default value of record type fields
Previously, model conditions, when set to insert a record type value from another model by using Field from another model, would fail to apply the record type value for the new record’s record type field. This meant that new records could not automatically receive a record type value from another model when the record was created - a value could be added later using model conditions and actions.

Now, setting a record type value from another model in a new record in a different model will work with the model condition type - Field from another model.

CORE-3166: Affects v2
File Upload component ignoring value of requery related models property
Previously, the File Upload component would ignore the value of the Auto-refresh related models on successful upload property. This meant that the component would refresh models whether or not the builder wanted those models to refresh.

Now, the File Upload component respects the value set by the builder.

DSC-2445: Affects v2
Dropdown menus on fields would appear in the wrong location
Previously, when a Skuid page was deployed in Lightning Experience, dropdowns on fields on the Skuid page would disconnect from the field and render in the upper left corner of the Lightning page. This made it difficult to select values. Also, it wasn’t a good look.

Now, Skuid pages in Lightning Experience will display field dropdowns in the correct location.

DSC-2452: Affects v2
Tab Container ignored value of background color set in the design system
Previously, the Tab Container component would not load the value of the background color defined in the design system. Instead, the background color for the Tab Container would be inherited from the property set for selected state.

Now, the background color for the Tab Container will match the value set in the design system.

Other fixes included in this release:

DSC-1898, DSC-2320, DSC-2404, DSC-2415, DSC-2423, DSC-2436, DSC-2438, DSC-2443 and DSC-2447.

Announcement

Breaking change to API v2 introduced by DSC-2443

skuid.component.getByType() now returns an empty array if it finds no matches.

Theskuid.component.getByType() API retrieves instances of component types and returns an array of all matching components.

Previously, if there were no matches, we returned an empty object. We've changed this behavior to now return an empty array, which better matches the behavior of a successful search.

If your code makes use of this API and expects an object, review it and update it accordingly.

Fixes

CORE-3144: Affects v2
Skuid v2 pages do not receive id parameters in certain deployment conditions
Previously, if a Skuid v2 page was deployed through a Visualforce page that overrides a Salesforce detail view, then the model conditions expecting an id parameter through page query parameter strings would not receive the id value. Model conditions based on page parameters did work on Skuid v1 pages deployed in the same manner and, also, work for Skuid v2 pages deployed in Lightning Experience.

Now, model conditions on Skuid v2 pages deployed through Visualforce pages on overridden record detail views will successfully pick up page parameters.

CORE-3162: Affects v1 and v2
Unable to use model condition to set default value of record type fields
Previously, model conditions, when set to insert a record type value from another model by using Field from another model, would fail to apply the record type value for the new record’s record type field. This meant that new records could not automatically receive a record type value from another model when the record was created - a value could be added later using model conditions and actions.

Now, setting a record type value from another model in a new record in a different model will work with the model condition type - Field from another model.

CORE-3166: Affects v2
File Upload component ignoring value of requery related models property
Previously, the File Upload component would ignore the value of the Auto-refresh related models on successful upload property. This meant that the component would refresh models whether or not the builder wanted those models to refresh.

Now, the File Upload component respects the value set by the builder.

DSC-2445: Affects v2
Dropdown menus on fields would appear in the wrong location
Previously, when a Skuid page was deployed in Lightning Experience, dropdowns on fields on the Skuid page would disconnect from the field and render in the upper left corner of the Lightning page. This made it difficult to select values. Also, it wasn’t a good look.

Now, Skuid pages in Lightning Experience will display field dropdowns in the correct location.

DSC-2452: Affects v2
Tab Container ignored value of background color set in the design system
Previously, the Tab Container component would not load the value of the background color defined in the design system. Instead, the background color for the Tab Container would be inherited from the property set for selected state.

Now, the background color for the Tab Container will match the value set in the design system.

Other fixes included in this release:

DSC-1898, DSC-2320, DSC-2404, DSC-2415, DSC-2423, DSC-2436, DSC-2438, and DSC-2443.
 

Improvement

CORE-3136: Affects v1 and v2
Improved user experience and error messaging for File Upload component
Now, guest users to Salesforce communities can upload files on community pages built with Skuid. This improvement specifically applies to File Upload components configured to use Lightning’s file upload component when the Skuid page is embedded in a Lightning page.

Additionally, error messages are now more specific and helpful. For example, if a file exceeds configured limits, then the error message will tell you so, instead of offering a general, non-specific error message.

Note: As of Salesforce’s Winter ‘20 release, guest users permissions are set to private. You need to use Salesforce’s Guest User Sharing Rules to grant record level access. 

For example, if your guest users create records and upload files as attachments with Skuid, you will need to create one or more Guest User Sharing Rules to share these newly-created records with your site’s guest user. If you do not create the sharing rules, guest users will be unable to use the File Upload component to upload attachments to records.

Other fixes included in this release:

CORE-3131, CORE-3146, CORE-3152, DSC-2292, DSC-2333, DSC-2405, DSC-2410, DSC-2413, DSC-2417, and PLIN-2677.

2020 has been a year of choppy waters and challenges. Sail into a welcoming harbor with Skuid Boston and claim your treasure: exceptional user experiences and faster app development.

Design flexibility

It's summertime, and the stylin' is easy … because we've added even more to make the design experience more flexible, including updates to Design System Studio (DSS). Go ahead: make every page of your app look exactly how you want it to.

  • Chart components: You can now customize the hole in the donut! (The donut Chart component, that is.) Enhance the value of visualized data with formatted text in the middle that can leverage text, numbers, or merged field data to tell the chart's story.

UPDATES IN DSS

  • Field styling: Boston includes DSS style variants that let you fine-tune field styles for Form and Table components. Think of them as declarative custom field renderers ... 

  • Rem or px spacing: more flexible spacing of all on-screen elements as the screen size changes. With Boston, you can choose between rem and px spacing variables to get the perfect fit.  

  • Required fields: Good app design lets users know what's expected of them. To that end, you can now customize the "required fields" indicatorsand configure how changed (but unsaved) data in both Read and Edit modes displays to the user.

  • New style variants: Thanks to input from you, the builders, we've added many new style variants throughout DSS. Plus, we drilled down to identify variant properties that needed clearer labeling (so you'd know why to use them) and made sure every property is addressed on our documentation site.  

  • Extensibility: We've worked to ensure that the most common reasons for using code can be handled fully declaratively in v2, but even with that, sometimes, to achieve a very specific scenario you're trying for, you need to add a bit of code. We have added more opportunities to extend with code.

    • CSS in DSS: Add custom styles and properties to any component or variant in your design system (including CSS animations and transitions) with a code editor built into DSS. Beta test the CSS editor in DSS to deliver more "pixel-perfect" solutions, faster—and with greater stability. 

Declarative efficiency

Gain better control over data entry and display with our improvements to your favorite components. Fields, forms, and tables are core building blocks of your pages, providing a flexible and efficient declarative building experience and letting you control how these components look and work.

  • Table components

    • Table styling: Previously, v2 Table components didn't let you control text wrapping or manage "overflow" content, which meant tables could get, well, gnarly. But new Boston properties give you control over Table row height and let you manage what happens when content overflows an individual cell. 

  • Table and Form components

    • Display As: Forms and Table components now have a new Display As option for picklist fields: Combobox. This elegant combination of a picklist and an input field lets users type into a text entry box that uses their entries to compile appropriate values into a selectable dropdown menu. 

    • Styling: Remember those DSS field variants mentioned earlier? They let you select different styles via the App Composer's Style tab. Want more styling options? Use conditional style formatting in the Display Logic tab to choose when a style is implemented.

    • Template field actions: This highly requested feature means you can set Skuid to trigger an action sequence when a user clicks on a template field. (No JavaScript required.)

    • Unlimited reference fields in picklists: Are your reference-fields-rendered-as-picklists getting a little too long? In the past, Skuid handled this problem by limiting those picklists to 50 items. But hey—we're all adults here. You should be able to set your own limit—and you can with Limit # values to.  (Be sure to render responsibly.)

  • Extensibility: We've worked to ensure that the most common reasons for using code can be handled fully declaratively in v2, but even with that, sometimes, to achieve a very specific scenario you're trying for, you need to add a bit of code. We have added more opportunities to extend with code:

    • Custom field renderers: Let's just cut to the chase: Custom field renderers are now available in v2. This was a popular tool in v1 and you clamored for it in v2. Now, builders can use the power of JavaScript to deliver custom data entry and display options to fields in both Form and Table components. Target specific user scenarios; leverage custom code snippets from Skuid Labs or the community; just make that field do exactly what you want it to do.

    • Support for HTML in template fields: HTML, we missed you. In v1 Tables and Forms, you let us efficiently format text and addresses, highlight content, and so much more. But in v2: not supported—until now. Boston fixes that, supporting HTML in v2 template fields. Welcome back, old friend. 

Builder usability

Exceptional user experiences are great for end users, but why should end users have all the fun? With Boston, we've made the building experience even better, cleaner, and easier to use so that you can build apps faster and more enjoyably.

  • Skip an action: Troubleshooting a series of actions can be challenging because it's not always clear which action in the sequence is causing problems. Here's something that should help: individual actions in a sequence can now be skipped—and later resumed—so you can more easily tease out the troublemaker (and issue a firm reprimand).

  • New code editor: In the development world, everybody loves Visual Studio Code (aka, VSCode). Us too. So we decided to use their Monaco code editor in Skuid. Cool benefits for builders: code completion (faster formulas and merge variables), syntax validation (no more breaking typos in formulas), and streamlined integration with the Skuid API (formulas on steroids). What's not to love?

  • Display logic gets a formula: Want to enable a button only if {{ModelA field2}} ≠ {{Model B field1}}? Back in the day—say, July 2020—to feed dynamic values like that into display logic (conditional rendering, enabling, or styling), you had to use a UI-only formula. Doable, but messy to configure and hard to debug. Boston includes a new display logic option called Result of a Formula that streamlines the process. 

  • Amped up administration: We improved the filtering options on the Admin pages to make it faster and easier to locate the specific item you need. And when we say item, we mean: page; user; data source…and so much more.

Behind the scenes

But wait—there's more. Skuid Boston includes the following "backstage" improvements: 

  • Sophisticated data models with layers of picklist dependencies and other complexities can affect performance. So, to improve the snappiness, you can now optionally cache Salesforce metadata locally.

  • Skuid internal JavaScript, CSS, fonts, and images have traditionally been served to the page from Salesforce static resources, but now we're using the Skuid CDN (content delivery network). This should provide a noticeable improvement in page performance, (though you can disable this if you have security concerns). 

Departures

Data Source Types

Historically, Skuid responded to requests for new data source types (DSTs) based on builder needs. Now, we've assessed builders' needs to determine which DSTs actually provide value. Auditing our library of data source types, we identified those that required continual maintenance but were not "earning their keep," bidding farewell to the following data source types:

Amazon-Lex Box Microsoft-Dynamics Microsoft-Sharepoint
Amazon-Polly DocuSign Microsoft-Excel SAP-Gateway
Amazon-SNS Jira Microsoft-OneDrive ServiceNow
Amazon-SES Marketo Microsoft-Outlook Slack


What does this mean to you? 

  1. If you're a new builder signing up for Skuid, you will not see these data source types.

  2. If you're a current builder upgrading or refreshing a sandbox, Skuid will remove any DSTs that you are not using during the upgrade. (And leave any that you are using.)

  3. If you're a current builder who's used one—or more—of these DSTs to create a data source in your app, don't worry! Any data sources created using these DSTs will continue to work, and you will also be able to create new data sources using these DSTs. 

What if I need one of these DSTs later?

These DSTs are not completely gone—all of them will be retained behind a feature flag. Ask your account representative if you need access. 

Fixes

CORE-3454: Affects v1 and v2
Installation of Skuid managed package failed for Salesforce Spring '22 orgs

Fixes

CORE-3268: Affects v1 & v2
Cloning a model and removing fields wipes out render/enable conditions that reference the source model

DSC-2790: Affects v1 & v2
On some Salesforce objects, record type values may appear as available field values even when those record type values are inactive or not assigned to the user's profile

Fix

CORE-3247
Picklist values do not render in Lightning Communities when the model’s object has record types
Previously, when a Skuid was deployed in a Lightning Community, picklist fields appeared empty when the field was on a model connected to a Salesforce object with record types. 

Now, picklist fields display data from object’s with record types on Skuid pages deployed in Lightning Community.

Fixes

CORE-3097: Affects v1 and v2
In Lightning Communities, Skuid fails to retrieve Record Type metadata from external Salesforce data sources
Previously, Skuid models connected to an external Salesforce data source would fail to retrieve Record Type metadata when the Skuid page was deployed in Lightning Communities for authenticated users. No error message would appear. Instead, the problem would present itself to the end user when they attempted to interact with Record Type metadata-based elements of a Skuid page. For example, if picklist options were based on the metadata for Record Type - the picklists would be empty.

Now, authenticated users to Lightning Communities will be able to interact with the elements of a Skuid page that depend upon the Record Type metadata from an external Salesforce data source.

Other fix included in this release:

CORE-3089.

Fix

DSC-2163: Affects v1 and v2
Skuid’s Chatter component does not work as expected in Lightning environments
Previously, end users could not enter data into a Chatter component on a Skuid page when that page was deployed to a Lightning environment. The workaround was to use the Lightning’s Chatter component.

Now, Skuid’s Chatter component allows user interaction when deployed in a Lightning environment.

Fixes

CORE-3134: Affects v2
Apex action fails to populate stored parameter value on revisit
Previously, when using the Action Framework to declaratively interact with invocable Apex, the action would appear to clear out the values input as the Apex parameter. The values were saved (and were visible in the XML view), but the action in the composer failed to show the values set by the builder. 

Now, Salesforce data source actions in Skuid will show in the composer any values set for the Apex parameter of the action.

CORE-3166: Affects v2
File Upload component ignoring value of requery related models property
Previously, the File Upload component would ignore the value of the Auto-refresh related models on successful upload property. This meant that the component would refresh models whether or not the builder wanted those models to refresh.

Now, the File Upload component respects the value set by the builder.

DSC-2453: Affects v2
Duplicate File Upload component appearing on Skuid pages in Lightning environments
Previously, a doppelgänger of Lightning's file upload component would appear on a Skuid page if the Skuid File Upload component was embedded in a Wizard component and the File Upload component was configured to use Lightning's file upload component when in a Lightning environment. Under these circumstances a duplicate file component would render - but not be usable. Refreshing the page would sometimes clear the duplicate.

Now, one file upload component will appear on the page.

DSC-2456: Affects v1
Link options for Name fields in Salesforce
Previously, linking behavior would fail on Name fields when the Link Options were set to respect the data source’s default behavior.

Now, Name fields configured to use the data source’s linking behavior will behave as expected.

DSC-2486: Affects v1 and v2
Currency fields go blank in charts after model query in a Salesforce org with multiple currencies enabled
Previously, data in currency fields in visualization components failed to display after the component’s model was queried. This occurred in Salesforce orgs where the multiple currencies property is enabled.

Now, for Salesforce orgs with multiple currencies enabled, data in currency fields in visualization components will update, as expected, after the component’s model is queried.

DSC-2507: Affects v1
Unable to sort date and datetime fields in a Postgres datasource
Previously, the checking the box to Allow Sorting for fields in a model connected to a Postgres datasource would not work as expected. This affected date and datetime fields only.

Now, you can enable sorting for date and datetime fields on a Postgres datasource.

DSC-2541: Affects v1 and v2
In bubble charts, the width of the bubble does not reflect the data
Previously, a Chart component configured as a Bubble chart would not respect the value of the data from the field used by the Size field property. This occurred when the Size aggregate function property was set to --None--. If an aggregate function was selected, the size of the bubbles would match the data.

Now, the size of the circle in a bubble chart will reflect the data even when the value of the field is not aggregated.

Other fixes included in this release:

DSC-1898, DSC-2468, DSC-2485, and DSC-2498.

Improvement

CORE-3136: Affects v1 and v2
Improved user experience and error messaging for File Upload component
Now, guest users to Salesforce communities can upload files on community pages built with Skuid. This improvement specifically applies to File Upload components configured to use Lightning’s file upload component when the Skuid page is embedded in a Lightning page.

Additionally, error messages are now more specific and helpful. For example, if a file exceeds configured limits, then the error message will tell you so, instead of offering a general, non-specific error message.

Note: As of Salesforce’s Winter ‘20 release, guest users permissions are set to private. You need to use Salesforce’s Guest User Sharing Rules to grant record level access. 

For example, if your guest users create records and upload files as attachments with Skuid, you will need to create one or more Guest User Sharing Rules to share these newly-created records with your site’s guest user. If you do not create the sharing rules, guest users will be unable to use the File Upload component to upload attachments to records.

Other fixes included in this release:

CORE-3156, CORE-3157, DSC-2336, DSC-2376, DSC-2382, DSC-2387, DSC-2409, and DSC-2413.
 

Fixes

CORE-3137: Affects v1 and v2
White screen of death
Previously, when loading a Skuid page in some versions of Google Chrome, the page would fail to load. Due to the way the Chromium codebase handles writing to the IndexDB, an error would occasionally appear in the Google Chrome console, Uncaught (In Promise)... "Failed to read large IndexedDB value". When this error occurred in Google Chrome, a Skuid page would not load.

Now, Skuid’s improved error handling of Chromium’s IndexedDB API allows the Skuid page to gracefully remove the error-causing entry in the application cache. When Skuid’s error handling kicks in, the Skuid page will load.

Note: if you, or your system administrator, recently installed Skuid 12.4.14, then you and other users may still encounter this error if the application cache has not been refreshed.

To clear browser storage in Google Chrome:

  1. Open the JavaScript Console.
  2. Select the Application tab.
  3. Select Clear storage under the Application heading.
  4. Make sure all boxes are checked except for Cookies.
  5. Click the Clear site data button.
  6. Click and hold the browser's refresh button until the menu appears.
  7. Select Empty Cache and Hard Reload.

DSC-2334 - Affects v2
SOSL search in Table components returning no results
Previously, if a Table’s search bar was configured for a SOSL search across all text fields, then the search would return no results. The search feature on the Table component created a malformed SOSL query which caused the search to fail.

Now, the Table’s search bar will search across all text fields when configured to use a SOSL query.

Other fixes included in this release:


CORE-3084 and DSC-2351.
 

2020 has been a year of choppy waters and challenges. Sail into a welcoming harbor with Skuid Boston and claim your treasure: exceptional user experiences and faster app development.

Design flexibility

It's summertime, and the stylin' is easy … because we've added even more to make the design experience more flexible, including updates to Design System Studio (DSS). Go ahead: make every page of your app look exactly how you want it to.

  • Chart components: You can now customize the hole in the donut! (The donut Chart component, that is.) Enhance the value of visualized data with formatted text in the middle that can leverage text, numbers, or merged field data to tell the chart's story.

UPDATES IN DSS

  • Field styling: Boston includes DSS style variants that let you fine-tune field styles for Form and Table components. Think of them as declarative custom field renderers ... 

  • Rem or px spacing: more flexible spacing of all on-screen elements as the screen size changes. With Boston, you can choose between rem and px spacing variables to get the perfect fit.  

  • Required fields: Good app design lets users know what's expected of them. To that end, you can now customize the "required fields" indicatorsand configure how changed (but unsaved) data in both Read and Edit modes displays to the user.

  • New style variants: Thanks to input from you, the builders, we've added many new style variants throughout DSS. Plus, we drilled down to identify variant properties that needed clearer labeling (so you'd know why to use them) and made sure every property is addressed on our documentation site.  

  • Extensibility: We've worked to ensure that the most common reasons for using code can be handled fully declaratively in v2, but even with that, sometimes, to achieve a very specific scenario you're trying for, you need to add a bit of code. We have added more opportunities to extend with code.

    • CSS in DSS: Add custom styles and properties to any component or variant in your design system (including CSS animations and transitions) with a code editor built into DSS. Beta test the CSS editor in DSS to deliver more "pixel-perfect" solutions, faster—and with greater stability. 

Declarative efficiency

Gain better control over data entry and display with our improvements to your favorite components. Fields, forms, and tables are core building blocks of your pages, providing a flexible and efficient declarative building experience and letting you control how these components look and work.

  • Table components

  • Table and Form components

    • Display As: Forms and Table components now have a new Display As option for picklist fields: Combobox. This elegant combination of a picklist and an input field lets users type into a text entry box that uses their entries to compile appropriate values into a selectable dropdown menu. 

    • Styling: Remember those DSS field variants mentioned earlier? They let you select different styles via the App Composer's Style tab. Want more styling options? Use conditional style formatting in the Display Logic tab to choose when a style is implemented.

    • Template field actions: This highly requested feature means you can set Skuid to trigger an action sequence when a user clicks on a template field. (No JavaScript required.)

    • Unlimited reference fields in picklists: Are your reference-fields-rendered-as-picklists getting a little too long? In the past, Skuid handled this problem by limiting those picklists to 50 items. But hey—we're all adults here. You should be able to set your own limit—and you can with Limit # values to.  (Be sure to render responsibility.)

  • Extensibility: We've worked to ensure that the most common reasons for using code can be handled fully declaratively in v2, but even with that, sometimes, to achieve a very specific scenario you're trying for, you need to add a bit of code. We have added more opportunities to extend with code:

    • Custom field renderers: Let's just cut to the chase: Custom field renderers are now available in v2. This was a popular tool in v1 and you clamored for it in v2. Now, builders can use the power of JavaScript to deliver custom data entry and display options to fields in both Form and Table components. Target specific user scenarios; leverage custom code snippets from Skuid Labs or the community; just make that field do exactly what you want it to do.

    • Support for HTML in template fields: HTML, we missed you. In v1 Tables and Forms, you let us efficiently format text and addresses, highlight content, and so much more. But in v2: not supported—until now. Boston fixes that, supporting HTML in v2 template fields. Welcome back, old friend. 

Builder usability

Exceptional user experiences are great for end users, but why should end users have all the fun? With Boston, we've made the building experience even better, cleaner, and easier to use so that you can build apps faster and more enjoyably.

  • Skip an action: Troubleshooting a series of actions can be challenging because it's not always clear which action in the sequence is causing problems. Here's something that should help: individual actions in a sequence can now be skipped—and later resumed—so you can more easily tease out the troublemaker (and issue a firm reprimand).

  • New code editor: In the development world, everybody loves Visual Studio Code (aka, VSCode). Us too. So we decided to use their Monaco code editor in Skuid. Cool benefits for builders: code completion (faster formulas and merge variables), syntax validation (no more breaking typos in formulas), and streamlined integration with the Skuid API (formulas on steroids). What's not to love?

  • Display logic gets a formula: Want to enable a button only if {{ModelA field2}} ≠ {{Model B field1}}? Back in the day—say, July 2020—to feed dynamic values like that into display logic (conditional rendering, enabling, or styling), you had to use a UI-only formula. Doable, but messy to configure and hard to debug. Boston includes a new display logic option called Result of a Formula that streamlines the process. 

  • Amped up administration: We improved the filtering options on the Admin pages to make it faster and easier to locate the specific item you need. And when we say item, we mean: page; user; data source…and so much more.

Behind the scenes

But wait—there's more. Skuid Boston includes the following "backstage" improvements: 

  • Sophisticated data models with layers of picklist dependencies and other complexities can affect performance. So, to improve the snappiness, you can now optionally cache Salesforce metadata locally.

  • Skuid internal JavaScript, CSS, fonts, and images have traditionally been served to the page from Salesforce static resources, but now we're using the Skuid CDN (content delivery network). This should provide a noticeable improvement in page performance, (though you can disable this if you have security concerns). 

Departures

Data Source Types

Historically, Skuid responded to requests for new data source types (DSTs) based on builder needs. Now, we've assessed builders' needs to determine which DSTs actually provide value. Auditing our library of data source types, we identified those that required continual maintenance but were not "earning their keep," bidding farewell to the following data source types:

Amazon-LEX Box Microsoft-Dynamics Microsoft-Sharepoint
Amazon-Polly DocuSign Microsoft-Excel SAP-Gateway
Amazon-SNS Jira Microsoft-OneDrive ServiceNow
Amazon-SES Marketo Microsoft-Outlook Slack


What does this mean to you? 

  1. If you're a new builder signing up for Skuid, you will not see these data source types.

  2. If you're a current builder upgrading or refreshing a sandbox, Skuid will remove any DSTs that you are not using during the upgrade. (And leave any that you are using.)

  3. If you're a current builder who's used one—or more—of these DSTs to create a data source in your app, don't worry! Any data sources created using these DSTs will continue to work, and you will also be able to create new data sources using these DSTs. 

What if I need one of these DSTs later?

These DSTs are not completely gone—all of them will be retained behind a feature flag. Ask your account representative if you need access. 

Improvement

CORE-3113: Affects v1 and v2
File Upload component intelligently supports Salesforce’s content versioning
Now, when uploading content to Salesforce’s Content Document object, the File Upload component can create a new version of an existing record, rather than a whole new record.

With the File storage location property set to In content document (with record context), the File Upload component will create a new version of the content when the File Upload component’s model provides an existingContent Document record Id. 

If no existing record Id is provided, then the File Upload component will create a new record in the Content Document object.

Fixes

CORE-3116: Affects v1
Last-selected filter value does not persist when model is processed client-side
Previously, if 1) an end user selected a value in a filter, 2) the Remember last-selected filter value property on the filter was set to true, 3) the Process Model client-side property on the model was set to true, and 4) the page was later reloaded, the last-selected value was not remembered.

Now, last-selected values for filters persist when the model is processed client-side.

CORE-3126: Affects v1 and v2
Page Assignments and the Salesforce clone action
Previously, if a page assignment was 1) set to override Salesforce’s Clone action type, and 2) the value of the property Skuid page was set to Use Standard Layout, then an end user would be incorrectly redirected to Salesforce’s record type selection page when the end user 1) the attempted to clone a record, and 2) did not have profile level permissions to that record type. 

Now, page assignments will successfully redirect the end user to the record type selection page when the end user attempts to clone a record with a record type to which they do not have permission to access.

DSC-2283: Affects v2
Column summaries in the Table component only calculated displayed values
Previously, column summaries in the Table component would only calculate values for the records visible in the current table view. Paginating through the records in the Table would result in changing summary values. The column summary failed to calculate the values of all records in the model.

Now, column summaries in the Table component will show summaries reflecting the values of all records in the Table component’s model.

DSC-2344: Affects v1 and v2
Rich text editor does not appear for editable rich text fields with overwritten field type metadata
Previously, the rich text editor failed to appear for an editable rich text field when the field’s Override field metadata property is set to true and another display type is selected. This prevented rich text fields, whose field metadata was overwritten, from being edited.

Now, rich text fields with overwritten field metadata will be editable for the end user.

Other fixes included in this release:

CORE-3122, DSC-2221 and DSC-2284.

Fixes

DSC-2280 - Affects v2
Table property for allowing users to hide columns not working as expected
Previously, if a builder configured a column in a Table component so that a user could not show/hide a column, then the user could show/hide - even though the builder disabled that property.

Now, the Table component respects the configuration for show/hide columns set by the builder.

Other fixes included in this release:

CORE-3109, CORE-3122, DSC-2145, DSC-2168, DSC-2212, DSC-2238, DSC-2242, DSC-2243, DSC-2244, DSC-2301, and DSC-2313.

Fixes

CORE-3099 - Affects v1 and v2
Regression (introduced in 12.4.9): Unexpected behavior under specific configurations for model conditions with reference fields
When a model condition uses a reference field that is not included in the model’s field list, the model condition is ignored by queries and errors occur when attempting to create a new record in the model.

This regression was introduced in the maintenance release, Salesforce 12.4.9, by a performance improvement in the behavior of how models handle metadata for reference fields and picklists. See the release note on CORE-3065 in the Salesforce 12.4.9 release notes below for more details on the change.

Now, model conditions with reference fields, which were not added to the model field list, will be respected and errors will not occur when attempting to create a new record on which that model condition exists.

DSC-2183 - Affects v2
For filters, the Reset button remains enabled after resetting the filter
Previously, in some situations, the Reset button for filters would remain enabled after a user pressed the reset button. To a user, this implied that the reset had not occurred or that something went wrong, even when the filter had, in fact, been reset.

Now, the Reset button disables after use.

DSC-2194 - Affects v2
Lookup filters, rendered as a picklist, fail on reference fields that depend on another reference field
Previously, reference fields would fail to display values if configured to:

  1. display as a picklist
  2. apply a lookup filter that depends on another reference field.

Now, a reference field configured to display as a picklist and apply a lookup filter using another reference field will display the expected values.

Other fix included in this release:

DSC-2181.
 

Fixes

CORE-3061 - Affects v2
Unexpected behavior when saving data in UI-only models
Previously, there were 2 scenarios where saving data to a UI-only model would yield unexpected results:

  1. If you saved a value in a field on a UI-only model and then canceled changes to another field on the same UI-only model, the result would be that the previously saved value would be reverted back to the value before the save.
  2. If you filtered a UI-only model by interacting with a component (like a component’s filter or search feature) and then canceled changes to a field on the same UI-only model, the result would be an error in the JavaScript console and the field value would not be canceled.

The problem originated with the way the UI-only model processed canceled field values.

Now, UI-only models gracefully handle canceled changes to field values.

DSC-2142 - Affects v2
On iOS devices using the Salesforce Mobile app, the date picker is not easy to use
Previously, when interacting with date fields on Skuid pages in the Salesforce Mobile app on iOS devices, the date picker behaved strangely. For example, when attempting to input a value into a date field, the date picker would be partially blocked by the input keyboard.

Now, the date picker renders in a way that is mobile and user-friendly.

Other fixes included in this release:

CORE-3073, DSC-2079, DSC-2179, DSC-2182, DSC-2187, DSC-2195, DSC-2209, and PLIN-2580.

Improvement

CORE-3065 - Affects v2
Performance improvements to the processing of metadata for reference and picklist fields
We improved when a model will query metadata for reference and picklist fields.

After the page loads, the initial query of a model will retrieve metadata for reference and picklist fields. Previously, querying the model after the initial query would result in the model retrieving that same metadata again. Typically, this metadata rarely changes, so the retrieval of metadata was unnecessary. Now, models will retrieve that metadata once.

Additionally, we improved when a model will load metadata for reference and picklist fields in model conditions.

If a reference or picklist field was only used in a non-filterable model condition, then the metadata for those fields was not necessary for the model condition. Now, models will not retrieve that metadata if the field is only used in a non-filterable model condition.

Note: if you wrote code that accesses the metadata for a reference or picklist field through the fieldsmap object via Skuid’s JavaScript API, then you will need to change the model’s condition to filterable. Otherwise, the code will be unable to access that metadata.

If that reference or picklist field is included in the list of model fields or if the model condition using that reference or picklist field is already filterable, then no change to your code will be needed.

Fixes

CORE-2929 - Affects v2
Cloned model data on page load does not enable Save and Cancel buttons
Previously, if a model clones data from another model when the page is loaded, the Save and Cancel buttons on data and button components will be disabled. This means that the cloned data is unsaved until an additional change is made to the model.

Now, data and button components with save and cancel actions will recognize cloned data in a model on page load as unsaved. This allows the user to save or cancel the data without making additional changes.

CORE-3057 - Affects v2
Formula fields unavailable in display logic
Previously, formula fields on UI-Only models were unselectable when setting up rendering conditions or style variant conditions.

Now, you can select formula fields on UI-Only models when setting up rendering conditions or style variant conditions.

DSC-2077 - Affects v2
In Lightning, rich text fields missing property toolbar
Previously, a rich text field in edit mode would not render the rich text toolbar when the page is displayed in Lightning Experience. Also, rich text fields would fail to save changes to data back to Salesforce’s objects.

Now, users can edit data in a rich text field and save rich text field data to Salesforce objects.

DSC-2087 - Affects v2
Unexpected behavior when cloning or double-clicking to add components to the canvas
Previously, adding components to the canvas may yield unexpected results. For example, if you were trying to add a component to a modal by double-clicking that component in the elements pane, then the component would appear in the page below - not in the modal.

Now, cloning components and double-clicking components in the elements pane will yield more predictable results.

DSC-2089 - Affects v2
Table scrolling does not work on iOS devices 
Previously, a Table component on a page viewed on a iOS device, whether through a mobile browser or the Salesforce mobile app, would not scroll. If content extended off the screen to the right, then that content was not accessible. If content extended off the screen toward the bottom of the page and the Table component had a fixed height, then that content was not accessible.

Now, you can scroll in any direction you need when viewing a Table component on an iOS device.

DSC-2095 - Affects v2
Really long names for component elements cause trouble for the Index
Previously, a long name for a component element, like the name of a tab within a Tab Set component, would push the contents of the Index past the left margin - making those elements inaccessible through the Index.

Now, long names wrap within the margins of the Index.

DSC-2155 - Affects v2
In a mobile experience, unable to select a value in a picklist if there is only one value available
Previously, when viewing a Skuid page deployed through a Visualforce tab in the Salesforce mobile app, a user could not select a value from a picklist if there was only one value in the picklist. The value would appear, but would not be selectable.

Now, single picklist values can be selected in a mobile experience.

DSC-2180 - Affects v2
Record Ids may not display for records in Page Include components within modals
Previously, record Ids would display on pages loaded into a modal by the Page Include component on the first time the modal was opened. Thereafter, the record Id would not display in the modal. The workaround was to reload the page in the browser. 

Now, record Ids will display on pages loaded into a modal by the Page Include component any time the modal is opened.

Other fixes included in this release:

APPS-1268, CORE-3053, CORE-3064, CORE-3066, DSC-1837, DSC-2040, DSC-2065, DSC-2066, DSC-2076, DSC-2086, DSC-2127, DSC-2141, DSC-2159, DSC-2160, DSC-2175, and DSC-2177.
 

Fixes

DSC-2105 - Affects v2
Tooltips persist on screen even when their element is hidden
It's possible to set tooltips, small dialog boxes that appear on when hovering over elements, for buttons in v2. Previously, however, a tooltip could get stuck on the screen if the element it was configured for disappeared. 

For example, on a Wizard where a user may hover over a button causing its tooltip to appear, navigating to the next step would not dissolve the tooltip. Instead, the tooltip would remain visible until the user returned to the previous step.

Now we've corrected tooltip behavior, and they will fade away properly when their element disappears.

DSC-2130 - Affects v2
Conditionally rendered buttons leave "ghost spacing" when hidden
Previously, for a conditionally rendered button (or button group), when the button was hidden, Skuid added extra blank space where the hidden button would ultimately display when rendered. This resulted in odd spacing on the page. 

Now, conditionally rendered buttons behave as expected, with no "ghost spacing." 

Other fixes included in this release:

APPS-1397, CORE-2886, CORE-3041, CORE-3058, DSC-2056, DSC-2072, DSC-2074, DSC-2084, DSC-2085, DSC-2088, DSC-2097, DSC-2115, DSC-2124, and DSC-2134

Fixes

CORE-3051 - Affects v1 and v2
When v1 and v2 pages are loading at the same time in Lightning Experience, errors may appear for the v2 page
Previously, when a v1 page completed loading it's theme in a Lightning Experience tab before a v2 page in the same tab, the v2 page would fail to completely load it's themes. The v2 page interpreted the load completion of the v1 page's theme as the completion of it's own theme.

Now, a v2 page will complete the loading of its themes even in the presence of a v1 page within Lightning Experience.

Other fix included in this release:

DSC-2010

Fixes

CORE-3035 - Affects v2
Characters that must be URL-encoded are getting double encoded when previewing pages
Previously, values passed to URL parameters were getting double URL-encoded when previewing pages in v2. 

So a parameter with the value of "My URL parameter," instead of being encoded to "My%20URL%20parameter" would be encoded to "My%2520URL%2520parameter." That's no good for anyone!

We solved the caper of the dubiously double encoded URL parameters, and your page previews will now have the proper values in their URL.

CORE-3038 - Affects v1
The Calendar component's Day Scheduling View would fail whenever an event didn't have the grouping field value

The Day Scheduling View uses a grouping model to split rows of events based on certain field values. For example, if using a name field on model for an object that lists accounts, events associated with client A will be in a separate row from those associated with client B, and so on.

In some previous versions of Skuid however, if one event did not contain the field used for grouping, the whole view would fail instead of just leaving out that event. We've fixed this, and now your Calendar's Day Scheduling View will function even if one of the retrieved events does not contain the grouping template field.

DSC-1910 - Affects v2
Flex ratios for navigation divisions on Mastheads now default to 1
The "Overflow to Menu Navigation" property allows Navigation components to gracefully switch from listing individual navigation items to displaying a clickable menu icon. This is meant to only occur when screen size is limited, however, these Navigation components were collapsing to menus even on desktop screens with plenty of space. 

This issue arose because the flex ratios for the navigation section containing the component had a default value of 0. Because of this low value, they began to shrink in size too early. 

Now we default all navigation divisions within Masthead components to 1. The Navigation components contained within them will no longer collapse into menus too early.

DSC-2029 - Affects v2
Multiple Row Selection using Shift-Select Works Inconsistently with UI-Only Models
Previously, when using Shift-Select to click two separate rows on a Table component (and thereby select all the rows in between the two selected rows), did not work as expected for tables on UI-Only models, with rows inconsistently selected. (Shift-Select worked as expected for Tables created on other types of models). 

Now, Shift-Select works as expected on Table components (irrespective of the type of model the Table is associated with). 

DSC-2030 - Affects v2
Inconsistent Table Sorting when a Row has Unsaved Edits
Previously, client-side sorting of a Table component column was disabled when a row had unsaved edits. 

Now, sorting works as expected: you can sort a row that has unsaved edits, but you will lose the edits on that row.  

DSC-2060 - Affects v2
“If hidden, Model field changes should be canceled" doesn’t work on a new record
Previously, when creating a new record, and using render conditions on a field, setting “If hidden, Model field changes should be canceled” didn’t work as expected.

Now, field changes should be canceled as expected.

DSC-2068 - Affects v1
Cancel button text in Mass Update doesn’t wrap correctly
Previously, if in the Mass Update modal, the cancel button text would wrap onto two lines.

Now, the button text behaves as expected.

DSC-2092 - Affects v2
Conditional Rendering leads to JavaScript exception in Lightning in Safari
Previously, conditionally un-rendering a component would cause a JavaScript exception error on Skuid pages in Lightning Experience when viewed in a Safari browser.

Now, conditionally un-rendering a component succeeds without triggering a JavaScript exception error.

DSC-2100 - Affects v2
Pages deployed in Visualforce Tabs may not render in a Page Include component when viewed in the Salesforce Mobile App
Previously, the Page Include component would load a second version of the parent page if the target page was not rendered on page load. This occurred for pages deployed as a Visualforce Tab and viewed in the Salesforce Mobile App. Yes, I know - these were really narrow circumstances.

Now, the Page Include component will load the targeted page, as expected.

Other fixes included in this release:

DSC-1724, DSC-1803, DSC-1985, DSC-2000, DSC-2017, DSC-2067, DSC-2071, and DSC-2080

What's New in Spark Update 3?

Glad you asked! Skuid builders told us what they wanted—and we listened. Skuid's Spark Update 3 offers new features that make it easier to both learn—and use—Skuid.

The Grand Tour

If you're new to Skuid and wondering what to do after you download and launch the product, we've got you covered. Just take the new in-app guided tour to get hands-on with Skuid. Learn basic concepts and build your first page—all in less than 5 minutes. The tour walks you through creating and configuring a model, adding and customizing a Table component, then previewing the finished product. To access the tour: from the Skuid navigation bar, click Help > Basic Resources, then choose Take the Tour.

Launch Skuid from Lightning

Builders told us that accessing Skuid from Lightning required several steps, so we fixed that. Now you open Skuid from Lightning's App Launcher with just a single click—and once you're in Skuid, there's no Lightning Header. That's right: Skuid in Lightning now has more "browser real estate" for you to work with.

Power up the Admin Experience

Skuid builders spent a lot of time outside the App Composer: organizing pages; creating data sources; managing and editing users; assigning subscriptions; and configuring SSO. So we redesigned the Admin Experience to make it clearer and more intuitive.

The reimagined data source creation flow allows you to edit and view the data source's authentication provider *while* creating the data source. Plus, with an improved UI, each tab in the Admin Experience has been made more user friendly, helping you find what you need, when you need it.

We've also consolidated the Themes (v1) and Design Systems (v2) into one tab (Design Systems) for easier management, with icons to quickly differentiate v1 (blue) from v2 (green).

Finally, check out the new Help tab that includes links to documentation, the Skuid community, sample pages, and our handy Basic Resources page (Skuid Central)—and more.

New in the Builder's Toolbox

Two new App Composer features make the Builder experience much more streamlined and flexible.

  • Ever been working on a Skuid page, made a modification, and then wished you could just undo it? Well, now you can! The App Composer's new Undo and Redo buttons let you undo (or redo) the last action taken when working with page components. These buttons also work in the Models, Action Sequences, and Javascript tabs in the App Elements pane.
  • On a complex page, it can be hard to find that one specific modal or button you need to modify. But not any more: the Page Index is a handy feature that displays page elements in a hierarchical outline. Use a search bar to find the specific element you need by name or type, click it, and Skuid navigates to that element on the page. (Yup. It's just that easy.) Locate components, buttons, fields, tabs, modals, drawers and much more using the Page Index.

Express Yourself with the DSS

Skuid's Design System Studio gives builders the ability to customize the look and feel of pages to a highly granular degree. So, how do you make a great feature even better?

  • Provide the option to either clone a DSS style variant  or create a child from it. Clones are copies that have no linked relationship with the variant they are copied from; child variants are linked to the "parent" variant, and inherit changes made to the parent variant.
  • Builders told us they liked the fact that they could set corner rounding for various components and elements—but they wanted to do it individually for each corner. So we made that possible.

More Functionality for Components

We're ensuring that v2 components have all the handy features of their v1 counterparts—plus a few nice v2-only enhancements.

Accordion components

  • Determine the default state for accordion sections: open when the page loads—or closed. You can select a state for the entire Accordion, or select states section-by-section.
  • Also: easily move sections up or down within the Accordion with the Change Order property.

Button components

  • Add a new property for Button Group that consolidates multiple buttons into a dropdown menu for a clean, uncluttered page.

Filter Set component and Filters

  • In the new Layout section of the Filter Set’s Styles tab, you can now set both the alignment and justification of the filter within the Filter Set to better control how filters display.
  • There are also new options in the Styles tab for Filter properties. Control the width and spacing of the filter within the Filter Set.

Form components

Ever wanted to control where the field’s label displays—above the field, or to the left of it? Well, now you can: new Field Layout properties let you place a Form’s field labels to the left of the field, and adjust their size.

Modals and Sliding Panels

  • Modals can now be customized in several ways:

    • Adjust the size of the modal or display the modal full screen.
    • Choose to display a header (with a Title embedded in it) in the modal. Or go header-free—it’s your choice.
    • If desired, display buttons in the modal’s footer and set the alignment of those buttons.

  • If builders can set After Close Actions for Modals, why can’t they do the same for sliding panels? It was a good question, so now both component accessories have After Close Actions.

Table components

  • Specify how many columns on the left side of the Table to freeze—and then give users the ability to adjust the number of frozen columns in runtime using either Table Settings or by dragging a “freeze bar.”

  • Allow users to show or hide columns  on a field-by-field basis.
  • Set whether a designated column is shown or hidden by default.
  • Display error messages right next to the field.

Component variants

When adjusting a component’s variant from the Styles tab, it can be hard to know what “Increased” or “Regular” really mean. Now, style variant menus include unit of measurement values alongside the variant name:

Behind the scenes

In addition to adding functionality to components, Skuid Spark Update 3 includes the following updates:

  • Personalization data now persists even after changes are made to a Skuid page using (for example) filter states.
  • The new Action Framework action Logout lets users log out of an instance of Skuid on either Salesforce VisualForce or Lightning Experience.
  • We’ve leveraged the UI-Only formula editor to provide a consistent experience everywhere formula editing is available in Skuid (including branch, and other actions that use a formula to return values).
  • Sometimes when users are mass editing within a Table Component, they need to be able to indicate that some fields in the row do not need to be updated in the Mass Edit popup. These fields should be left blank, or left with the current value. Now, the Mass Edit popup indicates where there are multiple (different) values for fields in a row, with an edit link that allows users to decide what kind of action they want to take on each field.
  • With Spark Update 3, Skuid now supports the use of all Lightning Workspace API methods in both v1 and v2 pages. This allows builders to write code that can programmatically manipulate workspace tabs to close, refresh, get the currently focused tab, and so on—using Skuid code.

Sample Pages in Github

We completely reworked our publicly available Github resources. 

We added new sample pages, updated existing pages, and removed less relevant pages. We added or rewrote the explanations and instructions for these resources to make them easier to find, understand, and install. 

Now, finding a resource to help you get started or learn a new technique is simpler and easier than ever before.

For the first time, we added design systems to our Github repository. If you want to see what Material Design would look like as a Skuid design system, now you can!