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
As per title.Kinda important. 😉
Hi, I want to use my own custom icon set for skuid theme (which is created by me based on modern theme). I want to get a feature similar to provided by skuid to add icons to buttons, tabs etc. Can we do that ? I don’t want to do this in the way of upload icons image and adding classes to buttons…doesn’t like hacks… just looking for a feature similar to skuid standard feature to choose icons…Team let me know is it possible now ?
AI capability like Alexa on Marketo.
I’d like the ability to configure filters (multiselect, toggle, etc.) client-side. Specifically to be used to filter a REST model.
Hi,I am new to SKUID. Want to know if we can eliminate the manual steps to unpack the skuid page in target org while migratiing the skuid changes from one org to another?Currently what we do is:1) We pack our pages in source org.2) We deploy the static resources using ANT migration toolkit.3) We unpack the static resource in target org.Can we automate this #3 manual step?Thanks,Atul
There’s one thing that’s been nagging at me. Upgrading the Skuid version is problematic in the sense of which bugs are in each version. Clearly, upon release nothing has yet been identified. But, for those waiting for a more stable version, we are waiting for a few iterations to get a more stable version.That said, it is not known which bugs we are “trading” in for. It would nice to see the known issues (regressions) of each release. It might the difference of choosing one release vs. another.
I would like to be able to create a condition of a google docs model where we can display records based on some sort of wild card eg beth for all documents that include ‘beth’ … has anyone had any success with this. I realise I can create a condition on title but it seems to be exact match only?
Like in my use case I’d relabel it to “Outstanding” as my chart categories by the Date_Completed__c field.
This functionality would be awesome in Skuid. Dynamics Sales Path and Required fields per Stage in the Path. Not as slick as Dynamics Business Process Flow, but still much better than just a Status field.I know it can accomplished quite similarly with Progress Bar custom component and Conditionally Rendered Field Editors, but seems like the metadata would have to be pulled into the Skuid Page with custom JS anyway. New component would be better due to this.https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_pathassistant.htm Otherwise have to create a simulated Sales Path using conditional rendering of a field editor for each stage. Works but prefer having a component to display this with the fields since there’s the added benefit of having “Guidance for Sucess”
I need to do rollup values from the standard Task object to my custom Project object. Apparently the Declarative Lookup Rollup Summary doesn’t work with recurring tasks. So now I’d like to use the Child Relationship multiple times with differing conditions in order to get Task Counts for each scenario. ie. Overdue Tasks, Total Hours Completed (rollup on custom field), etc. I’d have to make use of a snippet to do anything other than a count, but no big deal. I’m figuring that this something that isn’t possible with Salesforce SOQL. 😕 I don’t otherwise have a solution, unless I go to custom apex, which I’d clearly like to avoid. Anybody have an idea?
I’m finding it difficult in troubleshooting custom theme issues. It’s usually based on the issues stemming from the base theme.So, can you please add a Lookup field to the Theme record for which it was based on?I can then go directly test that theme to see if it’s the base theme or the customizations made on the custom theme.
Easier for me to articulate out-loud, so video explanation of my idea below:
There are countless locations where this applies. The more that is done here, the better the UX becomes. While stating from any assumptions in determining what to auto-set, the addition and settings can become much more automated.Search BoxesSearch box when selecting fields for component. Search box when selecting models in action framework “Save Models”, “Query Models”, “Cancel Models”, Input FieldsMessage input when “Show message and block UI”. URL input when “Redirect to URL”. Drop DownsAuto drop down drop “Model” down list in “Activate & Set value of Model Condition”, “Activate Model Condition”, “Deactivate Model Condition”, “Query Model”, “Deactivate Filterable Conditions”, “Save Models”, “Query Models”, “Cancel Models”, “Update a field on row(s)”, …Stopping here as you get the idea. 😉
As per title.
Skuid merge syntax creates a ‘field’ within whatever component it is being merged into (template, field editor, table, rich text, etc.).Is there any way to tap into that merge-syntax generated field and modify the way it’s rendered with javascript?
I have page includes that I use everywhere that I’d like to conditionally render certain things based on the query string. ie. table columns, row actions, mass action, global actions.In my use case, I have accounting journal entries that are related to one of many types of accounting records. Each of which I typically display these entries in varying ways.I can also do the model hack, but it really isn’t intuitive. Unless I could create one UI only model with a series of UI only checkbox field for each element on the page I’d like to conditionally render.Better yet, it would be great to be able to set to page input parameters on the page. Then when setting up the Page Include component, a tab dedicated to page input parameter parameters could be set. Much cleaner UX. 😃I would also use with Task and Event page includes.
Add save/cancel to button set so we can ditch using page titles just for buttons. Available page title actions right now: Available page button set actions right now:
As discussed in the conversation on this post and this post, the Chatter feed component has some serious drawbacks. It is a component supplied by Salesforce itself and cannot be refreshed on demand, must render with a valid record when the page loads, and cannot be used more than once on a page. We need a component with equivalent functionality but is more compatible with how other Skuid components function, eliminating these problems. For instance, if the model upon which the feed is based refreshes, the feed needs to refresh.
Add UI only child relationship. This way we can relate objects that are not directly related and decide which is the parent on the page even if they just share a relationship with another object type. Example use cases: Contacts as UI only child object of opportunity Junction records as child records of either parent object Allow for adopt rows as an action in the action framework so we can relate all contacts to opportunities through the account field. End result would look like this. Model object: Opportunity, Child UI Object: contacts (added through action framework or conditions) End product would look like this
So … now that Skuid has it’s own platform, it also has it’s own “server side” possibilities.Why not it’s own server side action framework workflow? I’d even go ape and make a super cool set of workflow UX for Process Boxes, If/Else Routing, Looping, etc, etc, etc. Similar to Salesforce Flow, but way way better. We’d models and action framework.We could then make use of these more complex/common in a single location from other Skuid Pages or Workflows!!!Use Case 1: Large Data Processing Requirement. Client needs to process records across 1+ Skuid Connection and thus requiring a more distributed server load processing.Use Case 2: A multi Skuid Workflow called from one Skuid Page Action Framework action.Use Case 3: Create one Skuid Workflow that is called from multiple Skuid pages.Use Case 4: Help with an Import Component to supplement ETL.I’m just scratching the surface but the possibilities are awesome.
Again, now that Skuid is it’s own platform, why enable ETL? It would be fairly easy I think. 😉Create an Import Component as per the Skuid Connections available on the platform. One could query the objects/entities/tables available, perform mapping, and finally hook into Skuid Workflows to do the actual work.
As per subject. 😃
Ever since filters came out I’ve been adding them incessantly to Skuid pages.I noticed that as users learn to filter tables into useful views, they start instructing their peers on filter setting. However, some people are ahead of the curve and can create more complex and meaningful views than others. What if there was a function, both across entire page contexts and on the filter set level, to save filter conditions and share them via link to fellow users? That way the users who are more capable of creating meaningful views could whip them up and share them with other users.
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.