PowerClerk Support Center

Program Design
Automations
Questions to ask yourself
Locating the Automations feature
Creating an Automation
FAQs
Communication Templates
Questions to ask yourself
Locating the Communications feature
Creating Communication templates
Feature reference
FAQs
Deadlines
Questions to ask yourself
Locating the Deadlines feature
How to create Deadlines
Feature reference
FAQs
Forms
Questions to ask yourself
Locating the Forms feature
How to create and edit Forms
Adding data fields
Configuring Forms
VersaForms
Sensitive Data Fields
Feature reference
FAQs
Roles
Questions to ask yourself
Locating the Roles feature
How to create and edit a Role
Feature reference
FAQs
Workflow
Questions to ask yourself
Locating the Workflow feature
How to create and edit the Workflow
Transitions
Changing a project's status
Feature reference
FAQs
Advanced Program Design
Channels
Locating the Channels feature
What are Channels?
Channels Checklist
3-Step Publishing Process
Channel Type A: Mark As Child
Channel Type B: Make Successor
Channel Type C and D: Create/Submit Related Project
Sending Signals
Document Templates
Questions to ask yourself
Locating the Document Templates feature
How to define a new Template
Feature reference
eSignatures
DocuSign template tags
Mapping eSignature tags
FAQs
Formulas and Calculated Fields
Questions to ask yourself
Locating the Formulas feature
How to create a Formula
Formula Data Dictionary
FAQs
Front Page
Questions to ask yourself
Locating the Front Page feature
How to edit the Front Page
FAQs
Incentive Design
Questions to ask yourself
Locating the Incentive Design feature
How to design an Incentive
Incentive Options
FAQs
Single Sign On (SSO)
Azure AD
Okta IDP Configuration
SP Configuration
PowerClerk API
Custom API IDs
FAQ
API Documentation for Developers
Application & Process Automation
Getting Started
Common Usage Scenarios
Using Custom IDs
API Method Reference
Code Samples
Administration
Business Days
Questions to ask yourself
Locating the Business Days feature
Setting up Business Days
FAQs
Dashboards
Questions to ask yourself
Locating the Dashboards feature
How to create widgets in your Dashboard
Other Dashboard Actions
Data Import
Questions to ask yourself
Locating the Data Import feature
How to validate a Data Import
FAQs
Duplicate Check
Questions to ask yourself
Locating the Duplicate Check feature
How to use Duplicate Checks
FAQs
ePayments
Questions to ask yourself
Locating the ePayments History feature
How to add ePayments
FAQ
Import From V2
Questions to ask yourself
Locating the Import From V2 feature
How to Import From V2
FAQs
Operation Status
Questions to ask yourself
Locating the Operation Status feature
How to use the Operation Status feature
FAQs
Program Info
Project Inquiry
Questions to ask yourself
Locating the Program Info feature
How to edit the Program Info menu
Notification Banners
Billing Info
FAQs
Program Statistics
Questions to ask yourself
Locating the Program Statistics feature
How to use Program Statistics
FAQs
Reports
Questions to ask yourself
Locating the Reports feature
How to setup Reports
Multi-instance reports
Integrate scheduled Reports
Cross-Program Reports
FAQs
Test Environment
Questions to ask yourself
Locating the Test Environment feature
How to setup a Test Environment
FAQs
User Administration
Questions to ask yourself
Locating the User Administration feature
How to work with User Administration
FAQs
Web Adapter Factory
Questions to ask yourself
Locating the Web Adapter Factory
What are Web Adapters
Input and Output Fields
Connecting, Testing, and Enabling
Maintenance and Alterations
Web Adapter Message Format
FAQ
Program Reporting
Data Fields
Questions to ask yourself
Locating the Data Fields feature
How to work with Data Fields
Custom Lists and Data Field Groups
Table form element
PV System + batteries element
FAQs
Milestones
Questions to ask yourself
Locating the Milestones feature
How to define a Milestone
FAQs
Project List Columns
Questions to ask yourself
Locating the Project List Columns feature
How to use Project List Columns
FAQs
Project Summary
Questions to ask yourself
Locating the Project Summary feature
FAQs
How to edit the Project Summary
Project Views
Questions to ask yourself
Locating the Project Views feature
How to edit Project Views
FAQs
Settings
My Account
Questions to ask yourself
Locating the My Account feature
How to use the My Account feature
Setting up Multi-Factor Authentication
MFA Recovery Guidelines
FAQs
FormSense
Questions to ask yourself
Locating the FormSense feature
How to use the FormSense feature
FAQs
Grant Access
Questions to ask yourself
Locating the Grant Access feature
How to Grant Access to users
FAQs
Integration Guides
Integration Guide 001: How to configure a Web Adapter – ArcGIS Implementation
Integration Guide 002: How to configure Electric Power Research Institute’s (EPRI) DRIVE Connect software with PowerClerk
PowerClerk Video Guides
New User Video Guide
Setting up Business Days
Dashboards
Edit Forms - Tutorial #1
Edit Forms - Tutorial #2
Configuring Forms
FormSense
Build A Formula
Automation with Formulas in Action Rules
Formulas and Advanced Visibility Rules
Calculated Fields
Milestones
Project Summary
Roles and User Administration
Visualize Workflows
PowerClerk User Group Sessions (UGS)
PowerClerk Responsive Admin View

Test Environment

Save time and ensure quality delivery by using the Test Environment to develop and evaluate program changes without impacting your live program.

Test Environment feature


Questions to ask yourself about your Test Environment:

Who in your organization should have access to the Test Environment? Who needs to create Test Environments?
Which aspects of your current program need to be improved?
How do we commit Test Environment changes to our live or production program?

Locating the Test Environment feature

Anyone in a Role with the Create Test Environment privilege can access this feature by opening the ADMIN menu and clicking on Test Environment:

 

Locating the Test Environment feature

Figure 1: ADMIN >> Test Environment

 

How to setup a Test Environment

The Test Environment feature of PowerClerk allows you to create a copy of your current program to evaluate and implement changes to your live program without interruption.

 

The dialog shown in Figure 2 below offers you the option to include Roles from your existing program to allow them access to your new Test Environment. In addition, you can enter your own email-address, so any outgoing communication from this new Test Environment is exclusively sent to your inbox.

 

To start, give your new Test Environment a name and click the Create Test Environment button:

 

Create Test Environment

Figure 2: Create Test Environment


Once your new Test Environment has been created you will notice a yellow-grey banner indicating that you are working within a Test Environment. The overview of Program Changes lists any differences between your current main program and your Test Environment. Upon completion of your changes and thorough functionality testing, please visit PowerClerk’s Ticket System program and submit your commit request by selecting the option “I would like my Test Environment to be committed“. Alternatively you may select to discard your current Test Environment to start over with a completely new Test Environment:

 

Test Environment dialog

Figure 3: Test Environment dialog


Please note: Upon fulfillment of your commit request, all your edits within your Test Environment will be committed to your actual main program and this procedure is not reversible.

You can create only one Test Environment at a time and have to either discard or request the commit of your changes before creating a new Test Environment.

FAQs

Q: What is the process for the PowerClerk team to commit a Test Environment?
A: While in the Test Environment, please review the Test Environment report by navigating to Admin >> Test Environment and investigate any entries that state "Duplicate Detected". These duplicates represent commit conflicts between your live Production Environment and Production Test Environment that prevent the PowerClerk Support Team from committing your Test Environment. Most commonly, these duplicates appear by altering your Production Environment while your Test Environment was already established, and then re-creating the Production changes in your Test Environment with the exact same naming convention(s). You can fix most "Duplicate Detected" conflicts by renaming the respective PowerClerk element either in your production environment or Test Environment.   Once you have thoroughly tested all program changes of your current Test Environment and are ready to request the commitment of these changes to your Production Environment, please submit your commit request by clicking the button called New Support Request in PowerClerk's Ticket System program and then selecting the option "I would like my Test Environment to be committed" and completing the form before submitting your support ticket.   PowerClerk's Support Team guarantees to process your commit request within 5 business days, and most commit requests are processed within hours of ticket submittal. If you need to target a specific date for committing your program changes, please reach out to the PowerClerk Support Team ahead of time to ensure we can work with your time constraints.   Once your Test Environment has been committed, you will receive a commit confirmation email form the PowerClerk Support Team. Alternatively, the PowerClerk Support Team may contact you to remedy any commit conflicts that need to be addressed prior to committing your current Test Environment.
Q: When committing a Test Environment, will we keep all users that had already been registered in Production?
A: Yes, committing a Test Environment to Production will not overwrite your existing users in Production. Similarly, if you have Projects set up in the Test Environment, those Projects will not overwrite your existing projects in Production when committing the Test Environment to Production.

Have additional questions? Contact us to nominate your FAQ and help others find answers to your own questions concerning this feature.

Create A Support Ticket

Not finding your answer here?  Submit a question to our support team at the PowerClerk Ticket System and leverage the PowerClerk team’s expertise.