Nintex Automation K2: Back to basics
Access resources, discussions, and troubleshooting tips to build custom applications and streamline workflows with Skuid NLX, SFX, & EXP.
Recently active
Not sure where but please not at the top of the page. Warnings should be front and center, but I consider these warnings.
Seems obvious to me.
The deck components has conditional rendering. Components within each card has conditional rendering. The card itself doesn’t have conditional rendering. Would be nice to have.
I’ve started using Big Objects and found that on the latest version, 11.1.1 that the table doesn’t correctly display rows.I’ve run a query succesfully that has 15 results though only the first row shows in the table:Looking at both the number of rows at the bottom and the console using I can see all the data was queried correctly so this appears to be a simple output issue.Thank you,Dan
We want to notify you that, after upgrading to or installing the Skuid 11.1.1 version, some customers are encountering a server-side error (see image below) when trying to edit the Sharing Settings in the Salesforce setup menu. We are aware of this issue and are jointly troubleshooting it with Salesforce. An update will be provided here in 12-24 hours.
I know you can restore a page, but it would useful to be able to see multiple versions in preview.Additionally, if previewing a version, have that Page & Version show up somewhere on the page overlayed on the top left or something.
Hey! Forgive me if this has already been asked/requested. When building lightning components you can declare attributes which are filled in by the user when they drag the component into the app builder or community builder. Like this: <aura:attribute name="title" type="String" default="Title" access="global" /> I was wondering if, when in the same component you declare a Skuid page, you could somehow pass in those attributes and use them in the Skuid page (e.g. via merge syntax). Like this (but you’d need to somehow pass in multiple attributes): <aura:component implements="forceCommunity:availableForAllPageTypes" access="global" > <aura:attribute name="title" type="String" default="Title" access="global" /> <skuid:page <b>STUFFTOPASS={!v&#46;title}</b> page="Lovely_Skuid_Page"/> </aura:component> y’ dig? Cheers! Louis
This post details how you can access Salesforce Files in a Skuid page. I’m using Millau 11.0.3 in this post.My requirement was to display a list of files (via a Deck) related to an opportunity. Here’s how I did it.Firstly I created a model based on the ContentDocumentLink object. Querying this object retrieves the file ids related to the opportunity. I created a condition based on the field LinkedEntityId, which I filled with Opportunity Id.Then I created a second model based on the ContentDocument object. This model then fed the Deck component with the fields I wanted to display (Title, Size, Type etc). The model had a condition set against the Id field (set to multiple specified values as there may be multiple files per opportunity).I populated the condition’s values and querying of the models in the required sequence via a series of actions (against an opportunity list in a table, which shows a popup containing further details of the opportunity along with related objects such as th
Love Skuid and want to make it your full time job?Rosetree Solutions is hiring a full time Sr Consultant and a Solutions Engineer. We’re Skuid Alliance Certified consulting and developer partners and have worked with Skuid since 2014. We help new and existing Salesforce and Skuid customers get the most value out of the platform. We’re based out of Dallas, TX.Since Skuid is such an integral part of our company and direction, good working knowledge of Skuid is required for both positions. The Solutions Engineer is a pre-sales technical consultant that will work with Skuid and Salesforce AEs doing demos, tracking deals, and creating statement of works for clients.The Sr Consultant position involves communicating directly with customers to work through their process and determine the best way to solve those issues combining Skuid and Salesforce tools. If you’re interested, check out the job postings on Dice: Salesforce Solutions Engineer and Senior Salesforce Consultant. We’re currently ho
Phone number fields would format similarly to when input in standard Salesforce (xxx) xxx-xxxx. I have seen that java and input masks can do this, but it would be great functionality out of the box for Skuid.
My use case is in a Wizard that creates multiple associated records and only Save the records at the very end once the user reviews everything for accuracy. I’d like to Conditionally enable the button below only once all the required fields have data. I’ll create a snippet to set a UI-Only field “hasRequiredFields” to true in the meantime.
That would be cool!
I’m trying to find a way to change the borders for navigation components in my custom theme, but I can’t find the setting?
Snippets are a great way to extend the Skuid framework and writing parameter driven snippets that allow allow data and components to dynamically run the snippet is a best practice that we try to stick to. When I see a specific model reference or a unique Id in a snippet, it’s in need of generalizing. It would be really handy to have a parameter string available in the action framework for the Run Javascript Snippet action. This would be a similar design to the query string option when using a page include. Here’s where I would envision this going: There are a currently a few approaches to handling this functionality that work well with the current Skuid platform, but it would be helpful to be able to make it more declarative. Here are a couple examples of passing custom parameters into a snippet to illustrate what I’m describing: You can use the skuid.snippet.getSnippet method in the Goto URL actions, links in templates, or in javascript event listeners like onclick(). The issue
Think of the component rendering action. If there was a similar action where you could choose the unique ID of a tabset and the set the tab that displays, you could create wizards with virtually unlimited formatting options. A wizard is basically a tabset with a hidden tab menu and buttons that navigate to other tabs of the tabset. So if there was an option in the tabset to hide the tab menu, you could create any manner of button anywhere on the page that could navigate the “wizard”. Use case would: think of a smart phone. You have a “Home” screen and it has icons or tiles of different shapes and sizes (depending on your smartphone). You click an icon and the menu disappears and just the content you want appears. Then you can go back to the home screen. This can be accomplished through rendering of components but that process would be streamlined if it could be don’t in a tabset instead of recreating a tabset like functionality through rendering components. Also, when you have a page i
I see from years back Skuid did not support Dated Exchange Rates. Does Skuid currently support dated exchange rates and if so, when did that support come out/what version?Thanks! Jeff
I’ve had to add a User model all too often in order to get just one custom fields value.Can you add custom fields on the User to the list of Running User Attributes?
There may be limited use cases for this, but for certain things in a page header or footer (even the entire page header or footer) it would be nice to hide components until the component hot spot is hovered over. I could see this being valuable for popups and sliding panels. Hover over an icon and a sliding panel comes out, for example.
Clean up the screen. We have some pretty complex navigation components in our header and footer, and they take up a lot of screen space. Scrolling past a huge dark box has become the norm when editing a child page (75% of our pages). It would be great to have the master page header and footer content collapsed initially (but expandable) in the builder.
Maybe I wasn’t fully paying attention to the Millau release video, but I don’t remember this being covered much…and before I even dig in and try it out…this seems BIG. Very exciting where the direction of Skuid platform is heading. “Millau introduces the Action Sequences tab, which allows you to save—and name—sets of actions that can be reused throughout a Skuid page or automatically triggered by events. Use inputs to create flexible, reusable action scripts or to create a page that listens to other Skuid pages or components in your Salesforce Lightning app.”
Thought for sure there was a post for this. Such a frustrating thing to happen when the performed is lost instantly without confirmation.
Hey!I was wondering if it would be possible to include some additional search properties (e.g. those that you might find in a search/filter component) for the ‘Search Model’ action.These could include:Tokenizing search termsSOSL searchField optionsServer vs. Clientetc.This would be fab!Many ThanksLouis
Another one of those small but very much appreciated tweaks to the page builder experience. Current Desired I’ve missed clicked so so so many times.
Sliding panel with origin bottom. Nav component with manual horizontal items. ‘dropdowns’ from items should be aware of the bottom of the screen and go up (like they do if the nav component is in the footer), but they just expand the bottom of the sliding panel beyond the bottom of the screen and add a scroll bar: Looks like the idea to hide menus in a sliding panel at the bottom is a no-go until this gets fixed. Any potential workarounds? 9.5.16
It would be awesome if we could set a rendering condition on a component based on whether a different component was rendered/visible. This would be particularly handy when we have two components that need to be rendered on opposite ends of a complex set of conditions.[Apologies if this is a duplicate. I thought I’d seen this idea somewhere, but didn’t find it on a quick search.]
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.