License and Permission Assignments¶

User Licensing / Permissions¶

This area contains links to Salesforce setup pages that allow you to manually assign Skuid licenses and permission sets.

By visiting these links (or navigating the Salesforce setup UI), you may assign Skuid’s necessary permission sets to single users or to multiple users as noted in Salesforce documentation.

Org Defaults¶

This area contains tool to manage auto-assigning or auto-revoking licenses and permission sets from all new users or all deactivated users.

Profile-specific Settings¶

If you want to specify which licenses and permission sets are auto-assigned/revoked to specific profiles, you can do so by adding profile-specific rules in this section.

Once you set up a profile-specific rule, the selected licenses/permission sets are auto-assigned/revoked when any user with that profile is created/ activated / deactivated in your org.

To add a profile-specific rule:

1. Click Add within the Profile-specific settings section.

2. Start typing the name of one of your Salesforce profiles and select it from the list.

3. Check the boxes of the things you want to be auto-assigned/revoked.

   The options available in the modal mirror those described in the Org Defaults section.

4. Click Add to save the rule.

Mass assign licenses using Data Loader¶

It’s also possible to mass assign licenses to a number of end users through Salesforce’s Data Loader tool. This can be especially useful for an initial rollout, where auto-assgining licenses may not help since users are already activated.

For more information, see Salesforce’s knowledge article.

Anonymous Apex script: Mass Assign the Skuid Page Viewer Permission Set¶

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26

////////////////////////////////////////////////////////////////
// Assign a Skuid Permission Set to all active SFDC/AUL licenses
////////////////////////////////////////////////////////////////
PermissionSet ps = [SELECT Id, Name FROM PermissionSet WHERE Name = 'Skuid_Page_Viewer' limit 1];
List<PermissionSetAssignment> assn = new List<PermissionSetAssignment>();
List<User> users = [
  SELECT Id
  FROM User
  WHERE Id NOT IN (SELECT AssigneeId FROM PermissionSetAssignment WHERE PermissionSetId = :ps.Id)
  AND Profile.UserLicense.LicenseDefinitionKey IN ('AUL', 'SFDC')
  AND IsActive = true
  LIMIT 10000
];
for (User u : users) {
  assn.add(new PermissionSetAssignment(
    AssigneeId = u.Id,
    PermissionSetId = ps.Id
  ));
}
//system.assert(false,assn.size());
try {
//  insert assn;
    system.debug('Permission Sets Assigned => ' + assn.size());
} catch (Exception ex) {
  system.assert(false, ex.getMessage());
}

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31

//////////////////////////////////////////////////////////////
// Assign a Skuid Permission Set to all active Skuid licensees
//////////////////////////////////////////////////////////////
PermissionSet ps = [SELECT Id, Name FROM PermissionSet WHERE Name = 'Skuid_Page_Viewer' limit 1];
List<PermissionSetAssignment> assn = new List<PermissionSetAssignment>();
String APP_NAMESPACE_PREFIX = 'skuid';
List<User> users = [
    SELECT Id
    FROM User
    WHERE Id NOT IN (SELECT AssigneeId FROM PermissionSetAssignment WHERE PermissionSetId = :ps.Id)
    AND Id IN (
            SELECT UserId
            FROM UserPackageLicense
            WHERE PackageLicense.NamespacePrefix = :APP_NAMESPACE_PREFIX
        )
    AND IsActive = true
    LIMIT 10000
];
for (User u : users) {
    assn.add(new PermissionSetAssignment(
            AssigneeId = u.Id,
            PermissionSetId = ps.Id
    ));
}
//system.assert(false,assn.size());
try {
//  insert assn;
    system.debug('Permission Sets Assigned => ' + assn.size());
} catch (Exception ex) {
    system.assert(false, ex.getMessage());
}

Skuid Sample Page: License Management¶

If you commonly need to see an overview of active Skuid licenses within your org, consider implementing this License Management sample page in your Salesforce org.

Non-Skuid users will still access standard layouts¶

If you use the tutorials for overriding tabs in Salesforce, (either using page assignments or direct visual force page overrides) users without Skuid licenses or privileges will still be able to access the standard salesforce layouts.

In Salesforce Setup, make Pages and Page Assignments Public Read Only¶

|image2|

Potential error messages¶

• SObject row was retrieved via SOQL without querying the requested field: skuid__Page__c.skuid__MasterPage__r  An unexpected error has occurred. Your solution provider has been notified.

  This often shows if a user does not have the Skuid Page Viewer permission set. If a builder sees this message, verify they have the Skuid Page Viewer permission set assigned to them.

• It’s possible for a builder to see a variety of field relationship request errors in the Composer if the Skuid Page Builder is not assigned. If a builder sees error messages similar to the shortened examples below, verify they have the Skuid Page Builder permission set assigned to them.

  • A Skuid Model, 'page', requested a Field with relationship name ...
  • A Skuid Model, 'pageBuilder_SelectedVersion', requested a Field with relationship name ...
  • A Skuid Model, 'pgs__NewPage', requested a Field with relationship name ...
  • A Skuid Model, 'versions', requested a Field with relationship name ...
  • A Skuid Model, 'ClonePageData', requested a Field with relationship name ...

If you have other Apex triggers¶

Due to Salesforce restrictions regarding setup object operations, Skuid’s triggers may not function well in combination with other user-creation triggers. If Skuid’s triggers and your triggers are grouped as a single transaction, you may see unexpected behaviors or your licenses and permissions may not assign properly.

If you have existing user-creation triggers, or wish to implement additional triggers, consider one of the following alternatives:

• If you “own the code” for the additional triggers, consider placing setup object DML statements within future methods to ensure that they run within a separate transaction.
• If you do not wish to use future methods, consider writing your own auto-licensing and permission granting functionality into new or existing functions. This will give you greater control over how and when licenses are assigned and will reduce the likelihood of undesired results.

Customize Application and its effect on page caching¶

Skuid stores its “last modified” timestamps for v2 pages within custom settings. When pages are loaded for end users, this “last modified” timestamp is then used to determine whether or not the user’s cached page should be cleared and new page data should be retrieved.

While this helps speed up load times for end users, there can be unexpected issues if a Skuid builder does not have the Customize Application permission when they update a Skuid page. That’s because the Customize application is necessary in order to update custom setting values, including this last modified time stamp. If a builder updates a Skuid page without that permission, then the last modified timestamp is not updated correctly. That means the cache is not cleared properly, and any users with a cached version of that page will only see that cached version.

If pages appear to not be updating for some users, ensure those pages have been updated by a builder with the Customize Application permission. End users can also consider clearing their browser cache.

The steps to clear a browser’s cache and site data vary depending on the browser.

Visit the links below to learn the specific steps for a particular browser:

• Google Chrome
• Mozilla Firefox
• Apple Safari on Mac and on iOS
• Microsoft Edge

Licenses aren’t working in a sandbox org¶

Sandbox orgs are granted site licenses, meaning individual licenses are not assignable. You’ll need to contact Skuid to limit licenses in this scenario.