PowerClerk Support Center

Test Environment

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

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.

Cookie	Duration	Description
CloudFlare CDN	4 weeks	The cookie is set by CloudFare to identify individual clients behind a shared IP address and apply security settings on a per-client basis. It does not correspond to any user ID in the web application and does not store any personally identifiable information.
CookieLawInfo Checkbox Necessary	11 months	This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category ‘Strictly Necessary’.
CookieLawInfo Checkbox Performance	11 months	This cookie is set by GDPR Cookie Consent plugin. The purpose of this cookie is to check whether or not the user has given the consent to the usage of cookies under the category ‘Performance’.
CookieLawInfo Checkbox Personalization	11 months	This cookie is set by GDPR Cookie Consent plugin. The purpose of this cookie is to check whether or not the user has given the consent to the usage of cookies under the category ‘Enhancements & Personalization’.
Viewed Cookie Policy	11 months	This cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
Website Search Interaction	Session	This cookie is set by Site Search 360, our search engine for all Clean Power Research websites, to record search session preferences and performance.
Website Search Session ID	11 months	This cookie is set by Site Search 360, our search engine for all Clean Power Research websites, to record search session preferences.

Cookie	Duration	Description
Google Analytics Data Limiter	1 minute	This cookie is installed by Google Universal Analytics to throttle the request rate to limit the colllection of data on high traffic sites.
Google Analytics Page Visits	1 day	This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the wbsite is doing. The data collected including the number visitors, the source where they have come from, and the pages visted in an anonymous form.
Google Analytics Random Identifier	2 years	This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site’s analytics report. The cookie stores information anonymously and assigns a randomly generated number to identify unique visitors.
Marketo Tracking	2 years	This cookie is associated with an email marketing service provided by Marketo. This tracking cookie allows the website to link visitor behavior to the recipient of an email marketing campaign, to measure campaign effectiveness.

Cookie	Duration	Description
Wistia Videos	11 months	Set by Wistia to support video functionality that may be found throughout the website. In addition to keeping track of the website visitor's position in a video should playback be interrupted, this cookie also notes user behavior regarding the video itself.
Wistia Videos Data	10 months	This cookie collects visitor interaction data regarding Wistia video content so that such content can be made more relevant to the visitor.