Skuid NLX, SFX, & EXP

As we’ve continued to build out much more complex Skuid pages across different objects (Lead, Lead tab, Opportunity, Account, Contact and now some custom objects), and as we’ve continue to grow our team so that we have multiple people collaborating on developing these pages, I’ve realized the need to be able to call “methods” if you will on performing the same actions in different places.Here’s my current use case: creating new opportunities from our Account page. I need to update all of the Opportunity create pop-ups with an additional lookup field to a custom object called Subscription, and within that want to modify the “Search Fields”. The problem is these are the different pop-ups we have for Opportunity creation:Manual New Opportunity (Record Type = Enterprise) Manual New Opportunity (Record Type = Renewal) Manual New Opportunity (Record Type = Coterminous) Automated Product Overage Tasks leading to Opp Creation (exists on our main tab and an Activities tab) Scheduled Events lead

Would be nice. 🙂

Can you block the page while saving the page? It’s annoying having to scroll up to the top when saving page to know for sure it’s saved or in the process of saving after using Ctrl+S hotkey.

This is Scotty’s idea.

For those of you looking for a solution for box.com’s Salesforce integration, I used this post as a template to create the following code. Replace “Contact” with the name of your object. Add a template component to your Skuid page and paste the code in. Worked like a charm. https://community.skuid.com/t/how-to-view-a-visualforce-page-on-a-skuid-detail-page

It would be awesome if the picklist options for a field could be displayed in this big plank space (when you click on the field in the model), just to make it easier to reference: This is especially handy when setting render conditions based on a value in a picklist. (Interaction_Purpose__c = ‘Initial Pregnancy Appointment’, for instance). I often find myself returning to the object in SFDC to figure out exactly how a picklist option is spelled. And if I could see that info in Skuid, it would speed up page development. It would be even awesomer if the list of picklist options came with checkboxes, so we could select the values that we want included in the picklists (default to all selected).

Skuid has a great selection of icons for row actions, but if I could display row actions as text, then I could make a page even clearer to the user. This would be especially useful in communities, where often the user does not receive any kind of formal training for using the pages and processes. 

I would be great if there was some kind of option to choose ‘standard’ or ‘merge syntax’ for various fields where merge syntax can be used in the page editor. In my case, tab labels. I find it hard (and ugly) to deal with long strings of merge syntax in a small text field.It would be great to be able to change a setting to show the tab label field as a larger text box with more room to edit. Perhaps the merge syntax could be collapsed as well so that we wouldn’t end up with tabsets looking like this in the editor:

Below is the webinar that we conducted yesterday introducing the high level features of the Superbank release.  We will be scheduling further deep dives to provide deeper details about specific features. Enjoy!  

Currently, to customize a field a snippet is required.  Not sure of the viability of this idea but throwing it out there to see if it sticks…Would be nice to be able to create a custom field renderer similar to the way you can create a custom component.  You could then choose it from the page builder and it would add a tab (or something similar) with custom properties, etc.Use CaseThere are several “stock” custom renders that I’ve built for the framework I am working on.  For each field that requires one of these renderers, the personal building the page must choose “custom snippet” and then write a snippet for each field.  The snippet is essentially one line of code for each of the fields, the only difference is the properties passed to the custom renderer.  By offering the ability in the page builder to choose “Custom Renderer” and pick from the registered renderers, the person building the page could specify the properties required to provide to the renderer via the declarative inte

As I’m making pages, I’d like the ability segregate who sees which pages based on the app their assigned.

When editing template fields using either the default or custom popup, would be great to see a “cancel” button.  The cancel button would revert any changes made to any fields in the popup only, not the entire model.  Currently, from a UX perspective, since there is no cancel button, the user will likely click the “X” on the popup when they want to dismiss changes and instinctively they will think that they cancelled any changes they made on that screen.  However, current functionality persists any changes they made.  By adding a cancel button and having the “X” result in a cancel, users will have a clear option for reverting changes made on the popup while still maintaining any other changes they have made on the main page.

Currently, when a model is re-queried via the action framework, any existing changes to rows in the model are cancelled and then new data is merged in.  One of the great benefits of the action framework is pulling in data only as its needed.  However, once the data is pulled in, it would be extremely beneficial to be able to just slipstream in new data and not affect any data that is already contained within the model.Use Case - Account Tab page contains a table which has a drawer that displays related contacts.  As rows in the table are clicked, data is re-queried and merged.  This provides the benefit of only accessing the data from Contacts if the user wants to see the details of the contact.  Once displayed, the user can edit properties of the contact.  However, if they choose another row’s drawer or collapse the current drawer, the changes they made are lost.  Ideally, the user could edit one or more contacts, navigate the contacts table and then click a single “save” button at th

I’d like to see new functionality when these options are set. Max # = 0 and Create Default = True.So whenever this model is set to load on page load or it is queried, the following things should happen:Clear Model Create New Row This would allow for a reduced complexity in setting actions. Just query the model and you’re set. Would not have to cancel and create new row.The one major drawback to this is that merge properties could not be used to set default values. ie data.length of a model has been useful for me, but could not set this using conditions.I just think that the “Create default row if Model has none” isn’t completely fleshed out. Sure, if setting Max to 1 and there isn’t a record, then create a default row. But there isn’t a clean way to always create a new record.

Talkin to Rob about this today. Wouldn’t it be nice to have a place to store stuff without having to create a field for it in an object. I’ll be updating fields on the model so I can interact with it in terms of rendering, storing values to be used at a later time, etc. That way I can rely on the data being a certain value by default regardless of which object or record I’m on. The reason I wanted this was to be able to place a page include across the top of a contact and account tab and detail page for a call logger. Can anyone help with adding some javascript functionality to the template field to update my custom setting field. {{{Office_Phone__cPhone}}}

I’ve been tinkering to see how far these can take me into the future without having to use javascript. I happened upon this release note and was momentarily stunned.This would allow many more possibilities in how to interact with the data. The only thing is, how can I use this apex method from a skuid page?I know I can use worklows and add trigger-ready flows to it, but I would also like the ability to control when to run a flow from within a skuid page without workflow.Another option would be to use the URL of the flow, but then I’d have to display the page. Maybe someway of loading the page without showing on the current skuid page? Typing as I’m thinking really.I hand the baton to whoever can answer this.Would be pretty cool though.

With the Skuid Summer 14 release, we’ve made some changes to Skuid to improve automatic synchronization of Model data with visual Components when the Model data changes are initiated from JavaScript.In a nutshell, the changes amount to this: if you have a Model called Accounts, and a Table that is bound to that Model, and you then make changes to data in the Accounts Model from JavaScript using the following lines, the Table will rerender the appropriate areas within itself to reflect the changes:var AccountsModel = skuid.model.getModel(‘Accounts’);var row = AccountsModel.getFirstRow();AccountsModel.updateRow(row,‘Industry’,‘Manufacturing’);Previously, to get the Table component to show the changes, you would have had to either  - (a) Save the Model - (b) Rerender either the whole Table or parts of the TableWith Summer 14, we’ve eliminated the need to do either (a) or (b). If you call updateRow(), your changes will be reflected in the UI, immediately. You don’t have to know which parts

Ever want to see Sales Cloud on Skuid? Now you can with Skuid for Sales.Skuid for Sales is a managed package that shows off Skuid in the Salesforce.com Sales Cloud.  All the pages and overrides are in place for you to see Skuid at work immediately.For more information see this tutorial. Install Skuid for CRM in a Production or Developer Edition org:  https://login.salesforce.com/packaging/installPackage.apexp?p0=04ti0000000Xwb0Install Skuid for CRM in a Sandbox org:  https://test.salesforce.com/packaging/installPackage.apexp?p0=04ti0000000Xwb0

In order to place a custom class or id on a field in a field editor or column in a table, a custom snippet is required.  Being able to set these through the declarative would be of great value!Thanks!

Zach provided an introduction to the Salesforce Console view,  and showed how Skuid can be used to make this an even more effective interface for high volume transactional environments like call centers etc. Note:  We will be posting some supporting documentation for this video in the next week or so,  including XML of the pages Zach reviewed.  In the mean time here is an initial tutorial on including Skuid pages in the console: http://help.skuidify.com/s/tutorials/m/supercharge-your-ui/l/166801-using-skuid-with-the-service-clo…

When I have a record with a lookup field to other objects, the normal way of showing the lookup field is to include the reference field on the layout. In standard SF, you will see the name of the related record and it will have a hyperlink to that related record. When you click on the link, if you don’t have permission to access the record, you get an error paged telling you so. This is a real annoyance to users in complex environments, as they can never tell which record the can and can’t see until trying to click on it.However, I’ve noticed that with Skuid, instead of seeing the name and a (unusable) link, you will not see the name of the related record at all; The field will be blank to the user. This is annoying, too, because that piece of information can be quite important. For instance, I need to see the name of the related person, even if I’m not allowed to see all of that person’s details. I tried to remedy this by creating a formula field in SF and a template field in Skuid wh

Below is the recording of the Spring 14 Release Deep Dive. The following items were overviewed. - Conditional rendering of Skuid components. - Mobile Builder - Inclusion of Skuid pages in Salesforce console implementations - Use of Call Center and click to call links - Automatically add custom redirect buttons to Skuid pages Remember - we have scheduled follow up sessions where we will dive into detailed use cases for our major feature announcements: - Conditional Rendering: 28 Feb. 1 pm EST - Skuid Mobile Introduction: 07 Mar. 1 pm EST - Skuid Mobile Use Cases: 21 Mar 1 pm EST - Skuid Sales Cloud Console: 07 Apr 1 pm EST

I often will add a field to a Skuid Model and Page, but after saving the Page, cannot view the field I just added. In every case, this has been due to the field not having been assigned the appropriate field-level security settings when originally created in my object. (Setup > Customize > {Objectname} > Fields > etc.) It would be very helpful if Skuid could give me a warning when I try to add a field with inadequate field-level security settings. Something like: “{{fieldname}} does not have the appropriate field-level security settings to be made visible on this page. You will need to change the field-level security settings to make this field visible on this page.” Even better, if I’m an admin, give me a pop-up that allows me to change field-level security settings for this field without the five clicks it typically takes to do this with the Salesforce Setup.