Skip to main content
Conga Support

ActionGrid Deployment Process

The process for deploying ActionGrid℠ into a production organization ("org") is similar to deploying other Salesforce® custom solutions. These steps may differ based on your own internal processes and deployment strategies. You can modify the steps to meet your specific needs. Please contact ActionGrid Support if you have any questions.

Here is a typical deployment lifecycle:

  1. Create a sandbox or use an existing sandbox environment.
  2. Install ActionGrid in the sandbox.
  3. Configure ActionGrid.
  4. Determine security settings for users.
  5. Test the configuration in the sandbox.
  6. Install ActionGrid in the production org.
  7. Move configured items from the sandbox to production org.
  8. License a subset of users in the production org.
  9. Test the production org functionality to ensure it is the same as the sandbox.
  10. Expand the base of licensed users until all licenses are consumed.

Refer to the Salesforce Development Lifecycle Guide for more information. ActionGrid follows a similar deployment path.

Create a Sandbox or Use an Existing Sandbox Environment

Refer to the Create or Refresh a Sandbox topic in the Salesforce documentation. Creating a sandbox based on a production org after ActionGrid has been installed in the production org will replicate the ActionGrid settings and configuration.

Install ActionGrid in the Sandbox

See the ActionGrid installation instructions. Click Install in sandbox when prompted for an installation option.

Assign permission sets to users separately. This will restrict most users (non administrators) from accessing ActionGrid Setup.

Configure ActionGrid

During this process, please contact the ActionGrid team as needed to resolve any questions. Typical configurations include:

Determine Security Settings for Users

The views and features that you set up will depend on your organization's needs. ActionGrid is flexible in letting you choose which features to expose to your end users. The default setting is to expose all features, but with a few clicks, you can easily turn off (hide) features globally, per profile, or per individual user. Here are some simple guidelines:

Test the Sandbox Configuration

Consider the following scenarios when testing the configuration:

  • Access to the ActionGrid app in general 
  • Access to Visualforce pages
  • Logging in as users of different profiles
  • Verifying settings and functionality as both administrative and non-administrative users

Install ActionGrid in the Production Org

Refer to the ActionGrid installation instructions. When installing ActionGrid into a production org, the default license type is a 15-day trial for five users. Contact your ActionGrid account representative to activate licenses and to set the seat count appropriately.

Move Configured Items from the Sandbox to Production Org

See the topic Export and Import ActionGrid Settings for instructions. ActionGrid versions 1.49.83 and earlier require you to also export ActionGrid settings and to create a change set for custom actions. We recommend upgrading to the latest version of ActionGrid to avoid this process.

License a Subset of Users in the Production Org

Select a team of ActionGrid power users to internally test the initial deployment, and assign them licenses as needed. Ensure they have the duplicate security settings as defined in the sandbox org.

Test Functionality

Test the production org functionality to ensure it is the same as that of the sandbox org. Consider loading two separate screens: one for the sandbox instance and another for the production instance. Gather feedback, and adjust accordingly. The team may even consider writing internal documentation that describes key workflows.

Expand the User Base of Licensed Users

Continue to add users in larger pools. Here are some scenarios that have worked well in the past:

ActionGrid deployment within a department of 50 users

  • Select one to five power users.
  • Power users train a larger set of 10 to 20 users.
  • Power users train the entire department.

ActionGrid deployment within a company of three departments, 150 users total

  • Determine a core team of 1 to 10 cross-departmental power users.
  • Power users train a larger set of users within their department.
  • Power users train the entire respective department.
  • Host a company-wide training session.

Timeline for Deployment

The timeline for deployment will vary based on your organization. If you need help determining a timeline for your specific organization, please contact your ActionGrid account representative.

  • Was this article helpful?