Salesforce

Developer Toolkit

Printable View
« Go Back
Information
Developer Toolkit
Developer-Toolkit
Article Details

What is the Developer Toolkit?

The govAccess Developer Toolkit is a suite of advanced CMS features that are intended for advanced CMS Users. These features can be summarized by the following:

  • Subsite Builder: CMS Users create facsimilie subsites that have unique logos, main navigation, header/footer content, and can utilize the Home Page Template.
  • Custom Content: CMS Users can create Custom Content objects.
  • Component Builder: CMS Users can create their own custom components.
  • A new Security Role for providing users with access to Developer Toolkit functionality.
Note: Granicus customer support is available to provide support and answer functionality questions, but we do not provide specific development or styling guidance.

Enabling the Developer Toolkit

The Developer Toolkit requires a Developer to enable its set of features. Take the following steps once it is enabled to allow access for your CMS Users:

Super Users

Super Users have access to all of the Developer Toolkit functionality once it has been enabled for the CMS. Super Users will need to set up a Security Role in order for regular Users to access the Developer Toolkit, however.

Setting Up a Security Role for Users

Non-Super Users can be granted access to other Developer Toolkit functionality via a Security Role. Super Users can take the following steps to provide regular Users with access:

Giving users the ability to access the Developer Toolkit by creating a new security role
 

  1. Navigate to Administration > Security Roles.
  2. Add a new Security Role or Edit an existing one.
  3. A new tab called Developer Toolkit appears between Component Level Permissions and Assign Security Role to Users.
  4. The Developer Toolkit - Component Builder option gives Users access to the Component Builder functionality.
  • Add Component: User can Add new Custom Components by using the Component Builder.
  • Delete Component: User can Delete existing Custom Components.
  • Edit Component: User can Edit existing Custom Components.
  1. The Developer Toolkit - DIY Subsite Builder option gives Users the ability to create and manage Department Homepages that can utilize the Home Page Template, custom logos, and unique Header/Footer content.
  • Manage DIY Subsite Homepages: Users can Add/Edit/Delete/Copy a DIY Subsite Homepage via the Pages component.
  • Manager DIY Subsite Page Templates: Users can Add/Edit/Delete/Copy a Page Template that uses the Home layout.
  1. Assign to Users: Switch to the Assign the Security Role to Users by checking the box next to their names.
  2. Click Save.

Custom Content

Custom Content access is managed via Content Roles and Workflows. If a User had access to Custom Content, then they are now able to Add new Custom Content objects.

To give a User access to Custom Content, take the following steps:

Adding a content role to give a user access to Custom Content in the developer toolkit
 

  1. Navigate to Administration > Workflows/Approval Cycles > Content Roles.
  2. Add or Edit a Content Role.
  3. Select the applicable permissions.
    • Note: There is a new option for Archiving Custom Content, which will be expanded upon in its respective article here (add link here)
  4. Assign the Content Role to the desired Users.
  5. Assign the Content Role to a Content Group.
  6. Click Save.
  7. Double check that the Users are assigned to a given Workflow.
  8. Assign the Workflow to Custom Content for a given Content Group.

To improve usability, Custom Content now utilizes Archive functionality. Mistakes can be undone, or previous versions restored by clicking the Archive History tab.

Custom Content Types

  1. Regular: Standard RAD Editor field; any content can be placed here.
  2. Text Links: Group of text links. User can enter link text and URL hyperlinked.
  3. Image Links: Group of images that can be hyperlinked to other pages. User can select an image from Image Library and URL hyperlinked.
  4. CSS: Users can define new CSS classes, or add new CSS to the site, which overrides the existing CSS.
  5. Javascript: Users can create Javascript object.
  6. RadEditor Snippet: Users can create code snippets that can be utilized via the RADEditor.

Disabling the Developer Toolkit

Should the Developer Toolkit be disabled after content has been created using its functionality, it will have the following effects:

DIY Subsite Builder

  1. Users will lose the ability to create new DIY Subsites using the Department Homepage functionality.
    • The "Home" Page Template will no longer be available when creating a new Page.
    • Users cannot update the logo of existing DIY Subsites.
    • Users cannot Copy nor Edit the Header/Footer content at the Page level.
    • Note: Custom Content can be updated via Configurations > Custom Content.
  2. Any Department homepages that have been created will remain, and can be edited or deleted.
    • Custom logos will revert to the site default and cannot be updated.

Custom Content

  1. Users lose the ability to add new Custom Content.
  2. Existing Custom Content remains, and can be updated.
  3. Archiving remains active and users can restore/delete archived versions of the Custom Content.

Component Builder

  1. Users lose the ability to add new Components using the Component Builder.
  2. Users lose the ability to edit existing Components using the Component Builder.
    • The Development dropdown will NOT appear along with the Component Builder option.
  3. Existing custom Components created with the Component Builder will remain.
  4. Existing custom Component data will remain. CMS Users can Add/Edit/Delete items for a particular Custom Component.
  5. Custom Component Widgets and Default Widget Pages will remain.

Security Roles

  1. The Developer Toolkit Security Role tab no longer appears.
  2. Existing Security Role settings related to Developer Toolkit are disabled.
For more information on using the Developer Toolkit:
Powered by