Upcoming Event - Nintex Automation K2: Back to basics
Connect with peers and experts to ask questions, share insights, and find solutions for Nintex products.
Recently active
Problem: Using the Skuid component in Lightning App Builder pages is currently yielding an error: A component error has occurred! [There was an error rendering a Skuid Page component for page ___ TypeError: Cannot read property ___] Who may be affected: Skuid clients using the Skuid component to bring Skuid pages into Lightning App Builder PagesWho should NOT be affected (please let us know if you are affected!!!): Skuid clients NOT using Lightning Skuid clients using VisualForce to display Skuid pages in Lightning Workaround: Create a VisualForce page for your Skuid page as shown here: https://docs.skuid.com/latest/en/skuid/deploy/salesforce/visualforce/#visualforce-markup-overview Bring that VisualForce page into your Lightning App Builder page as explained here: https://docs.skuid.com/latest/en/skuid/deploy/salesforce/lightning/#visualforce-page-lightning-compo… What is being done: Skuid opened a case with Salesforce about this issue. We are working collaboratively to get this iss
We use conditional rendering quite a bit on our pages. In Spark, there’s a bit more nesting of components and the wrapper component is proving to be a powerful solution for laying out pages and standardizing site UI. Conditional rendering impacts the entire contents of the wrapper (or other containing component), which means that redundant components need to be added to additional wrappers if there is an outside style that need to be changed A simple use case is being able to display a colored border or changing the background if there is a condition where highlighting a page section is necessary (like an error condition). In V1 I would typically handle this by using merge syntax to dynamically inject a class or a style override based on either a Salesforce formula field or a Skuid UI field, but since these properties have been moved to the DSS, this kind of dynamic styling is tough. A conditional change of DSS variants would probably be the best approach to keep this declarative.
I’d like to be able to have a bit more flexibility with the navigation component in Spark including adding an image (ie. an html tag) and to independently style icon colors. Here’s an example in V1 that we’re doing today.
It would be very helpful to tie an accordion component (in Spark) to a Skuid model. An example use case would be an FAQ page that interacts with knowledge. It looks like that’s the desired capability given the fact that the context tab is in the page builder.
Just watched this youtube video for interactive wrappers. https://www.youtube.com/watch?v=8B2wrTHwvuE Can you add on hover functionality when the wrapper has a click action.
Would like to see an option to display the wizard labels below the icons in Spark.
Is it possible to have all sections of the accordion component load in the closed state?
The 12.0.1 and 12.0.4 of the Wizard has built in step navigation bar. We have the option to click on it to navigate directly to that step. There are times when I’d like to display the step but not allow clicking on the step to navigate. ie. required fields
I have an oData request header that is 528 characters, and I can’t have more than 255 in skuid. How do I resolve this issue?
First things first, I have to say that Spark is amazing and I love the direction the product is going. However, during my time spent tinkering, I’ve started to notice missing features that are nice to have. Is there a plan to build parity with existing Millau functionality? I’m keeping a running list of features/functionality that are currently available in API v1. Would love to get them incorporated in Spark. Please feel free to add to the list. Custom CSS in design system and/or skuid pages Form option to display field labels next to field (vs. above) Form collapsible section headers Required field red border? Cant find any styling for the required fields Table row edit? Is table limited to inline only? Nice to have in Spark Design SystemMin/Max widths on components (button for example) Style for form section headers
I’ve had many instances of creating the same popup in several places on a page. Some times I’ll just switch it to a separate page and page include, but if it’s a simple popup that doesn’t make much sense. Could you give popups a unique id, then show them via the Action Framework with Toggle Component? It might have to include choosing a model to give the popup a context.
Currently rebuilding in v2 (as there currently isn’t a streamlined process to convert). When creating a template field within an Ink Table component, I noticed that the ‘Allow HTML’ option is no longer there. (present in v1). This causes the HTML inputted in the template to appear as text: Is there a way to enable HTML for an Ink Table template field in v2? There is no HTML option in the Ink Table properties. Although support documentation mentions that you can use HTML alongside table field data, I am not seeing the option in v2. Perhaps it is inherently enabled in the new v2 component? The Ink Text component is essentially the new Template component (has HTML enabling), however, I need the Ink Table template for this particular function. Let me know if I am missing something here. Any input appreciated, thanks.
Hi Community~All preview sandboxes were updated to Spring '19 last weekend and the first round of production orgs is getting updated this weekend. We have been working with Salesforce on an issue with the Spring ‘19 release wherein a blank page displays on the page if you have ALL of the following in play:Enable clickjack protection for customer Visualforce pages with EITHER standard headers or headers disabledA My Domain name that contains a capital letterUsing VisualForce pages in Lightning ExperienceIf the above scenario describes your org, please whitelist your My domain name via Session Settings as explained in this documentation. Please note that only Spring '19 orgs have the option to whitelist domains from Session Settings.As always, we encourage you to try this out in a sandbox environment first. If you continue to have issues with this after whitelisting your domain name, please let us know and we will continue to investigate. Thanks!Karen
Just thought you should know…
Along with the new Spark release, we are proud to acknowledge our latest community champion:Mike Dwyer Mike has been exceptional in his willingness to assist our members overcome problems via the community. Skuid would like to thank you for helping to break down obstacles so others can see the amazing things you can build with Skuid. By bringing known issues to our attention and sharing workarounds with other members, you have helped the Skuid community to grow as a valuable source for solutions.We can’t thank you enough, Mike!!!
It would be great if actions could be deactivated and grayed out for testing purposes.
Hey! It’d be great if merged counters in tabs would update on model save/query. I know this is a long-standing issue but I think it’d be sooooooo cooooool to get this sorted. I know we can do this by re-rendering the component with a javascript snippet but this often causes issues particularly when tab components are nested, etc. I’m guessing that if we were able to assign tabs to a particular model then this problem would be fixed? I know it’s easier said than done but could there be other benefits to assigning a particular tab to a model? Or multiple models? I’m not sure the best approach but this would be such an ace feature. Cheers! Louis
This one would likely take a lot of overhaul the page composer…but I think it could be very helpful in accelerating the learning curve for new admins/builders. In my experience Skuid admins tend to struggle the most with the concept of a model when they first start learning to build with Skuid. On the other hand, the concept of the Component is very intuitive. So re-designing the page composer to be oriented around the Component would be valuable for new admins/builders.For example…When a user places a Component on a page, the first tab within the Component’s properties section could be named “Data” and it would allow the user to setup the Model properties (naming it “Data” to fully abstract away the concept of Models).If Skuid auto-named each model as Pat suggested here, that Model’s data could still be referenced in other actions, conditions, etc. but it would be named something like “Field from another Component’s Data”…instead of “Field from another model”.Regarding Model Fields, I
This is probably a pretty “far left-field” request…so I get that it’s nothing that would be implemented quickly…but I’ll still throw it out there. I’m building longer and longer action sequences these days, often times executed on a button within a drawer or popup…and my screen gets very cluttered with the popup/drawer window, then having to expand the action sequence builder/editor…see attached image as an example. It would be nice to have that action sequence builder/editor reveal from a sliding panel on the left or right side of the screen…so I could endlessly scroll through my action sequence while still keeping the rest of the composer nicely in view.
As per subject. This would be especially useful the picklist has many many options.
We have a page that uses a table control. The table has six columns. The columns can be logically organized into two groups of three. We would like to display a second-level header above the normal column headers that spans the three columns that make up each group. Can this be done within the table control? If not, is there a good way to fake it?
This one’s troubled me for years! When you set a default date (e.g. on new row action) you can’t just enter some merge text to reference a date from another model - you can only select a specific date or a relative date. It’d be so lovely if I could just write ‘{{$Model.MODELNAME.data.0.SOMEDATEFIELD}}’ whereas instead I have to overwrite it in the XML. Cheers! Louis
What I’d like is an easier way to create child record defaults (more complicated ones, requiring a formula) when creating that record from a parent - which is a frequent process. When creating a quick-action in Salesforce to create a new record from a parent you can set predefined field values via a formula. It’d be really swell if you could do the same in Skuid as the way I’m currently doing this in Skuid is to create some ui-only formula fields on the parent model and to then reference these via ‘{{$Model.MODELNAME.data.0.FIELDNAME}}’ in the new row action. This is a lot more work/overhead than the Salesforce quick action process. Screenshot sums it up best! Let me know if I’m missing something! Cheers! Louis(p.s. some validation in the formula editor would also be SWEET - including making sure referenced fields are in the models)
Finally got a chance to finish watching the sneak peak to the Skuid Spark release. Mind blown!!! Well done Skuid Product Team! Super excited to dive in!
I’d try to explain my use case but honestly it’s nutso. Suffice to say that I have a dashboard page that has hundred’s of charts and tables using one 1 aggregate model. The charts and tables make use of XML based conditions and javascript to customize each. Basically I group by everything possible and use conditions in the charts to further filter and aggregate to the desired data set.
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.