Heritage Products

Kinda hate wasting trying to fix a page when only one character is out of place. Prevent invalid values.

There are a few things that Skuid can have if only they were to put them in as advanced features section. In there each would have an agreement for each of the following: Acknowledgement of known and unknown issues. Review this list of known issues below to better understand your risks: Acknowledgement that any page and/or org using this is not supported. In order to get support this feature must be removed from the page and/or org.

When setting a Query action, the models selected should be all the models in Active/set model condition actions immediately preceding. When setting the Behavior to Activate and Set Value on the Active/set model condition actio, the value should default to {{Id}} when condition is a lookup to the same object this action is being called from. Save model changes should auto select any models being updated in any row from actions preceding it. There are more I’m sure, but these are the obvkous ones.

Adding Block UI with message should add Unblock UI at bottom of list. Adding Activate/Set model condition should add Query models immediately after unless there’s one already. There’s likely more of these, but these two are the obvious ones for me.

There are so many times that I need to navigate through a series of drawers, modals, panels, etc. Currently this is possible for modals and drawers when the actions are directly in the actions. This doesn’t work in the following situations. Sliding Panels anywhere Action Sequences for any of the three above types from Actions Sequences tab Action Sequences being used as an action Modal Actions Probably a ton more places, but it would be great to have for UX.

There are a few UX gripes I have in the Actions property pane. Buttons only show when selected. This is especially bad adding multiple fields when creating or updating rows. Same thing when wanting to remove multiple. 3 clicks vs 1 click Options are always behind the 3 dots when 2+ options are available. With the addition of undo and redo, we should be able to put the emergency brake down now. Set all options as Icon only with tooltip instead of text.

The number of actions can sometimes get to be quite longer. For Update Rows & Create New Rows this issue is easily exasperated when setting many fields.

Surprised I’m the first to notice this. All actions have the lightning bolt icon. It would be much easier to find the desired action than looking at the text only if they all had unique icons.

Based on this post for a simpler more direct solution. Add Accordian component actions “Open All Sections”, “Close All Sections”, “Open X Section”, and “Close X Section” where X is either the heading or id if you add this property to sections. Displaying error messages when Accordian section is collapsed Questions Skuid currently do not evaluate the Required fields if they are inside of a collapsed Accordian section, is there any action that would open the Accordian sections on the click of a button and display error messages on the Required fields to the users? Any suggestions would be of great help.

This could be used to solve things like the following: Skuid page data updated elsewhere notification How to change colour of a field, timed colour change

Could then use this to get call an Action Sequence with everything needed to execute. This goes hand in hand with this other idea Target Row by Index and Get Index from Row.

Based on this post.

Similar to what Salesforce Audit Trail does, it would be great if Skuid pages had a similar reporting capability. I’ve found this js that seems like it would great. diff-js-xml I can see this being pretty slick for Skuid page builders needing to easily capture the changes for reporting purposes. As any decent builder knows, it’s way faster to build a page from an idea than to write down any technical requirements beforehand. A user story and acceptance criteria is all that is needed, along with the design philosophy for the org, and a DSS. Spitballing here, but I see the following: Object Page_Comparison__c Revision_Changed_From__c Lookup to skuid__Page_Version__c Revision_Changed_To__c Lookup to skuid__Page_Version__c Page_Changed_From__c Lookup to skuid__Page__c Page_Changed_To__c Lookup to skuid__Page__c Original_XML_Layout__c 1-5 Long Text Area Changed_XML_Layout__c 1-5 Long Text Area All the common fields between skuid__Page_Version__c & skuid__Page__c Object Page_Comparison_

Based on my question Is there a way to trigger an interaction on anything but a template field in a table? Can we add interactions to fields?

STRING(numberValue) DATE_VALUE(datetimeValue)

Similar to the other idea I put forward about the “Where am I used?” Salesforce field button, it would be a no brainer to add element names to the index as opposed to just the generic names. One could click a button “Where am I used?” and be brought to the Index tab with elements name entered and searched for in the index. Easy peasy lemon squeazy to extend functionality. Alternatively, or additionally, add the index component to a tab on the right properties pane with everything already prefiltered for the component, model, field, snipper, action sequence. Boom! Done.

Button to go to model from component. Would be really handy when working on an intricately designed page with many models.

Just like the Salesforce field button with this name, it would be great to have this feature for all the following: models fields action sequences snippets

Pretty straightforward. Having the ability to use {{index}} would be awesome. Especially for row actions to move a row up or down. Same is possible by creating a field using one field but it just seems wasteful to create a field in order to expose this functionality. IF({{Record.isFirst}}, “First”, IF({{Record.isLast}}, “Last”, “Middle”)) Slightly better UX for formula option. I’m sure a use case for {{index}} has been wanted before as well.

In the actions of Update rows, Create new rows, Mark rows for deletion, Unmark rows for deletion, Remove rows from model, and Adopt rows into model there is an ability to target rows. It would be nice to use a formula to set the index(s) of which rows to target. Along with this I would include some OTB options like first row, previous row, current row, next row, last row when setting the index. I could reorder rows in a table without javascript this way.

This idea has been thrown around for quite some time. I know it would be an entirely new effort for Skuid to make it possible as an in house effort. Alternatively, and I prefer this option, we can do something like https://unofficialsf.com/ where everything is a collaboration for creating and sharing Skuid resources. I would be more happy to do this. For this we would need Skuid to provide a framework to allow us to build custom components, custom apps and extend Skuid with something like Component Templates.It would be pretty good bang for the buck

I can see using the camera component to capture a barcode to quickly enter a value into an input field and autoset the input to the next expected field.

We love Salesforce, but navigating Salesforce Setup can be tricky. That’s why we created seven new Skuid Skool courses to make your life as a Salesforce admin easier. Walk step by step through deploying Skuid apps on Salesforce. Now you can be confident in setting up user permissions, embedding Skuid in Lightning pages, Visualforce pages, and Experience cloud. New Learning Path: Deploy and Manage Skuid Apps in Salesforce New Courses Deploy Skuid in Salesforce: Introduction Prepare to Deploy in Lightning Deploy in Salesforce: Lightning Coming later in 2023 Deploy in Salesforce Classic: Visualforce Deploy in Communities, Portals, and Sites Skuid SFX Security Briefing: Licenses and Permissions Upgrade Skuid in Salesforce

It would be extremely helpful to include a visual indicator that there is display logic active on a component, directly on the component in the editor. Right now, the only way to know if you have display logic active on a component is to: Click the component Click the “Display Logic” tab under the component properties This causes a lot of fumbling around to try and figure out what is going on with pages that have a lot of Display Logic sporadically across components. If instead every component displayed a special icon when display logic was in use, it would be much clearer directly in the editor that there is conditional logic involved on the component. Perhaps you could even click this icon to get directly to the Display Logic tab of the component’s properties:

This is a suggestion for a new component in SKUID, a Hidden Tab Tab Set. Hidden Tab Tab Set: This would function almost exactly like a normal Tab Set in SKUID, however the actual tabs at the top of the Tab Set would not display to end-users; only the content of the Tab Set would be displayed. The editor would show everything like a normal Tab Set, though it should be clear visually to the editor that this is a Hidden Tab Tab Set, not a normal Tab Set. What This Achieves This allows for an editor to better organize items on their page, and make the page logic clearer visually in the editor, especially in relation to Display Logic. For example if you have a SKUID page that should display differently for different departments in your organization, you could use this hidden tabset with each tab having display logic conditioned on the user’s department. Now, the end-user will only see the tab content they are supposed to see, but to the page editor they can clearly see that we have a situa