Skuid SFX

Overall improvement: it takes too many clicks to do anything (I have a separate post on flow actions). You have to add a condition, action, etc. then wait for it to get added to the UI, then click something in order to configure it. For conditions, my recommendation would be: Click the condition and that displays the condition details for editing Change the stacked dots to a trash icon that requires 2 clicks to delete. So for #1, clicking the condition will display this:

When adding an action sequence, my intuition was to double-click the action for it to be selected. That is currently not happening. You have to click an option then click Done

First component’s property is hidden because its too close to the header and chrome is infront.

Hi. I’m working with Google Calendar and I am able to view the calendar and events properly. But, when it comes to creating new events, there are no exceptions thrown and event record is never created. I have also experienced many difficulties with All Day events and none of the combinations seems to work. The page I’m testing is on is pCalendar

The activate/set model condition rule disappeared and related with “setCondition” When I try adding the rule back, the query rule for another model containing the Id from from the active / set model is not properly returning records. I’ve granted login access to our sandbox and the page is name is pOrganizations. It’s a simple Account / Contacts model relationship page, fetching the list of contacts by the selected account. Is it appropriate to share these details in this discussion?

Why the new default in new snippets? const params = arguments[0]; vs var params = arguments[0], $ = skuid.$;

I find it hard to position filters, especially when you need to account for smaller screens. Filters get hidden in the “more filters” drop-down. I’d like to be able to manage the filter display like you can manage form fields to add them to columns. My workaround is to use a form and responsive grids, but I’d prefer to be able to take advantage of filter set features, like the refresh button (I have to create my own custom button) and apply filters as you type (not possible with a search box on a form, for example). Also, I hate that filters get randomly added to a “More filters” drop-down (this is very confusing when it’s the search box that disappears…same thing happens on the Skuid pages list). There seems to be a huge amount of padding in the filter set by default and I want to be able to control field placement better. Features I’d like: Add fields to filter columns Add gutter size Adjust width (fixed vs. fit to width, etc.)

To recreate: Add a UI-only model to a page I did add labels to all of my UI-only fields Add a form tied to this model and select the fields in the model. Get error message (and form not added to page): There was a problem initializing a component of type skuidbuilder__builderComponent: Cannot read properties of undefined (reading ‘getLabel’) Here is the error message on my page: Here is the model definition: Step 1 of adding the form: Step 2 of adding the form: I can add a basic model form, but not a UI-only model form.

I usually just copy and paste in the XML but it would be awesome to have a feature to do this from the UI:

Add the buttons when you click into the definition of the model to clone and delete them:

I already mentioned this about tables. But adding any component seems to open a 2-step wizard modal. Let’s simplify! Just allow users to drag and drop the component like we can do in the current composer and be done with it. The modals often ask for details that are not ready (such as form fields especially if you’re using a UI-only model) and a small subset of settings (like title, which I rarely use). Instead, I just want to drag and drop the component to the page and be done.

Make the actions themselves more prominent in the list. Maybe make them blue so that they look clickable? Both the headings and actions are in gray font, and the headings are larger, so you’re not drawn in where to click. Hide the headings if there are no actions for the filter search results: Clicking action should add it to the sequence. Don’t make me select the action, then click create if I cannot define any settings within the action selection modal.

I generally use the same components over and over and it would be cool to be able to filter the list of components on most recently- or most frequently-used components or even be able to favorite them. Like I’m ordering from Instacart and want to go straight to my favorite snacks:

It’s really hard to see the components you have in the main panel of the composer in order to select and edit them. Tabs or divisions and anything nested within them are particularly difficult. For example, I have a page with a tab set with a division and then a table nested within them: If I collapse the left-hand surfaces panel, I cannot seem to figure out how to select the division or table except by selecting some component nested in the component I want, then selecting the component I really wanted from the breadcrumb list. This also makes it extremely difficult to place components into grids because you’re not quite sure where they are going. To recreate: Add a tab set to a page Add a division and/ or table into a tab Collapse the surfaces panel Try selecting the division or table component from the main (center) panel → cannot

Why the next button? This assumes that the settings on the second page are the only ones needed for every table. I rarely add a table title, for example, preferring a text component where i can use HTML or a style variant. Just make it a one-step process to select your fields and be done with it.

This is similar to Parity: Ability to add new field from form Parity: Ability to add new field from form New Composer GA currently allows you to add fields to the form, and subsequently the data model. This was from dragging a form to the canvas and going through the wizard. [image] I’d love to be able to add both a field to the current model from the SalesForce object as well as a new UI-only field from the configure table modal: Not a high-priority item, but it does reduce clicking when you realize you’re missing a field.

The first thing I do when I create all new pages is to turn this off. At least make it an organization-wide setting if other customers like to have this on. It’s very buggy in the current UI and you get the warning if you have UI-only models, hidden models that are used for display logic, that aren’t saved and don’t need to be saved or cannot be saved to prevent this message from displaying.

This is very annoying to be on by default for all models.

Low priority request Similar to DSS list, allow you to refresh modules from the page.

Ideally, this should be a Skuid setting for the Org. Or at least allow a DSS to be selected on record creation (you can when you migrate a page from v1, but not when you create a new page).

Love that you added the ability to refresh fields on model from the page! Can the same be done for objects? I.e., have a new “data sources” section in the page details pane to refresh the data source like this?

Usually our dates are called dates, but sometimes, I just want to filter by all date fields. How about adding a field type picker to the model, like this:

Assigning action sequences to anything is buried. For example, it took me a while to figure out where a page load action sequence could be configured: One suggestion is to add a way to assign an action sequence to an event or component from the action sequences pane. There is a lot of unused real estate and few actions from the action sequence view: It would be great to have “Assign” as an option from the stacked dots and be able to select the page and a list of components, similar to the way the Show/hide component action works:

When planning the new composer we decided to extend the concept of centralized resources. We had seen Action Sequences used in interesting and innovative ways. We decided to lean in and give more resources the centralized editing treatment. This is a big change. Lets talk about it and the new ways of building skuid pages that will be involved here. What are these resources? Actions Flows are an evolution of Action Sequences. You can think of them the same way. Logic Statements are the rule statements used for various forms of Display Logic. Rendering, Enabling, Style Variants etc. Surfaces are Modals and Sliding Panels – discrete page areas that sit on top of the basic page. Why are we making this change: Promote reuse. If at all possible, you should be able to define a resource and then use it multiple times in your application. Promote discoverability. If you want to edit an popup, it would be really elegant not to have to search all over the page to find its config

Thank you for your willingness to test the new Composer. It is still very much a work in progress. Skuid has a bunch of nooks and crannies we are working hard to get right. So you won’t get frustrated when testing, we’ve outlined where we think you can test well, and where there is still work planned, in each of the major areas of the new Composer. As we continue to deliver new capabilities in the coming weeks and months - we will update this document. 1. Components and component properties. This is ready to test. New features include: Different views of component list. (and we’ll make your selection sticky before too long) New arrangement of component properties in the right hand sidebar. Some of the more nested component property areas are still getting some polish. This includes: Form field validation properties. Search definition (for tables, decks, lists, and filter sets) - especially for Salesforce models. 2. Model configuration. This should mostly be ready to test. It