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

Forms

Build Data Fields in Forms and collect the information you need to launch your program and empower your organization with critical data needed for business analytics, planning and operations.

Forms feature


Questions to ask yourself about Forms:

Which information is required, which is optional?
Do any data fields need input restriction?
What information needs to be collected in each Workflow step?
Should any part of the Form be conditionally visible?

Locating the Forms feature

Anyone in a Role with the Edit Forms privilege can navigate to the Form Editor by opening the PROGRAM DESIGN menu and clicking on Forms.

 

Locating the Forms feature

Figure 1: PROGRAM DESIGN >> Forms

 

How to create and edit Forms

To create a new Form, click the “New Form” button on the Forms screen:

 

Create new Form

Figure 2: Create new Form


Within the Form editor, name your new Form in the Description field as “Example Application”. PowerClerk will reference your new Form by this name. By clicking the top area of this new Form, please also enter “Example Application” as the title header for your new Form on the right-hand side:

 

Form name and title

Figure 3: Form name and title

 

Adding Data Fields to the Form

Add Data Fields to the Form by clicking and dragging any Field type item from the right-hand side menu tab Add a Field and drop the element onto your Form:

 

Add Data Field

Figure 4: Add Data Field


How does a program designer decide what fields should be added to this application Form? The best way to start configuring an application in your program is to take an existing paper or fillable PDF application and translate it into PowerClerk using the list of Data Field types available in the Add a Field section.

After you have set up this direct translation of a current Form, you can iterate on the Form in PowerClerk to make the application more efficient. PowerClerk Data Field properties such as making a field Required and setting up Conditional Visibility can be leveraged to make this new online Form much more powerful than what was used previously.

For example, one PowerClerk customer was able to combine 8 different interconnection applications into 1 Form in PowerClerk. What once took 8 different documents to administrate can now be collected in 1 Form, in 1 Workflow, in PowerClerk.
 
Field types (like “Single Line Text” and “Static Text” as shown in Figure 4) have importance to the kind of data that you’re looking to collect from your applicant.  Data Fields that require further calculations in the Formulas editor, for instance, will likely be set as “Integer” or “Decimal” fields.  PowerClerk will recognize the entries into these fields as data types that can be used in calculations.  In certain cases where you want the applicant to enter text (as in “Single Line Text”), you may also want to consider using Drop-down Lists or Multiple Choice field types so that you can present the applicant with a set number of options and avoid variations in data entry (like “Residential Service” versus “Residential” versus “Resi Service”).
 

Configuring Basic Data Field Properties

All Data Fields on Forms in PowerClerk have a small list of settings in common. You can configure these settings by clicking on that Data Field in the Form Editor and using the Field Properties menu.

 

Common settings

Figure 5: Common settings


(1) Label –what is displayed above the Data Field when a user is filling out the Form
(2) Required Field Checkbox –will prevent a Form from being submitted if this field is not filled out correctly
(3) Help Text –will display your specified text in a blue “?” bubble near the Label of the Data Field:
(4) Field Name –this is the database’s name for this Data Field. Note that the Label (what the applicant sees) and the Field Name (the name the database uses to store the data) can be different.

After you are done adding fields to the Form, click Save at the bottom of the Form Editor to save any changes.
 

Configuring the Form in the Workflow

Back on the Forms screen, please expand the new Form by clicking the “+” sign, and click the Configure Form button:

 

Configure Form

Figure 6: Configure Form


The Configure Form screen has several useful settings that will control which Roles can access the Form in which statuses, how this Form can trigger status changes, and how it can be integrated into administrative process:

 

 
Configuring the Form

Figure 7: Configure Form


(1) Selecting the Use for New Project Button checkbox for this Form will allow users to use this Form to enter the Workflow (and create a new, unique record). Note that multiple Forms can be configured to create a new project, allowing for programs with multiple, parallel Workflow paths. Every project in PowerClerk can have multiple Forms submitted throughout the Workflow, but only one of those Forms can be used to create the project in the first place.
(2) The Change status when submitting this form checkbox is used to cause a project to automatically change Status when the Form is submitted for a project. In this common example,when an applicant submits a brand new application, the project automatically changes to the Submitted Status. Another example would be if we created a Technical Review Form, and upon submission of that Form the project automatically moved to a Technical Review Completed Status. Note – this may be handled differently for programs that have been upgraded to Automations instead of Actions.
(3) The “In specific statuses” configuration option allows to define the statuses in which this Form is available, and which roles have access to the Form in those specific statuses. For example, when the project enters the Application Changes Needed Status, we could make this Form available to the Applicant so that they can come back to their application and make the appropriate edits. If we did not configure this Form to be available to the applicant in that Status, they would have read-only access to their application, and wouldn’t be able to make any changes to data that had already been submitted.

PLEASE NOTE: it is considered a best practice to give Administrators and Program Designers access to any Form in any status that another role has been given access. This follows the general theme that Administrators and Program Designers have global access to data in the program.
 
 

VersaForms™

VersaForms allows administrators to use PowerClerk forms on any website—no PowerClerk account registration required. With VersaForms, utilities can simplify enrollment, increase conversion and better manage workflows—all from a single platform.
 

  • Information submitted on a VersaForm is fed directly into PowerClerk workflows without requiring API configuration or other integration.
  • VersaForms are easily adapted to the look/feel of the landing page they are hosted on.
  • Forms can be created and modified in minutes by PowerClerk administrators, and easily embedded into utility-managed websites/landing pages.

Please note: The submission of a VersaForm™ creates a project. These projects count toward your utility’s (or agency’s) total application volume.
 
To enable VersaForms for your PowerClerk program, please file a new request in the Ticket System and choose the following option:
 

Request Embed ID

Figure 8: Request Embed ID

 
Once enabled you will be able to denote any of your Forms as a VersaForm by navigating to Program Design >> Forms >> expand the respective form and click the Configure Form button to enter the VersaForm configuration dialog as shown below:
 

Enable VersaForm option

Figure 9: Enable VersaForm option

 
VersaForms can be used in two distinct ways:

  1. Embed the VersaForm in your own website by copying two lines of code (e.g. for Energy Efficiency Rebate programs).
  2. Link to your VersaForm from a Communication Template send as an E-Mail.

 

VersaForm code snippet

Figure 10: VersaForm code snippet and direct link

 
See above samples for the code snippets, and respectively the direct link, which you can use in the context of your VersaForm scenario to embed your forms or direct your users with a link to your VersaForm.
 
 

VersaForms: custom font-size and font-family parameters

Two optional customization parameters allow you to set the font-size and font-family for embedded VersaForms: data-font-size-px and data-font-family. These parameters need to be added to the script tag used to embed a VersaForm:

  • data-font-size-px: the value of this parameter should be a number that represents the font size you wish to use. It should not include the px part.
  • data-font-family: the value of this parameter should be the name of the font family you with to use. It is the responsibility of the hosting page to make sure the actual font files are loaded as well.

Example:
<script type="text/javascript"
     data-font-size-px="17"
     data-font-family="sans-serif"
     src="<-- VersaForm script link -->" >
</script>

 
 

Form Field Elements

PowerClerk’s From editor allows you to create rich forms using a variety of Form Field Elements to capture the information and data relevant to your Workflow processes.
 

Integer- and Decimal form elements

Integer form elements allow you to capture whole numbers in comparison to Decimal form elements with a decimal point in it, like these: 1.5, 0.6, or 3.14. You can set a Default Value for these fields and also define the allowed number value range with the lower (Min Value) an upper (Max Value) value limit.
 
Field properties:

  • Label: A classifying phrase or name displayed above the integer form element
  • Default Value: The initial value of this form element, set by PowerClerk without user input.
  • Min Value: The lower value limit for this form element.
  • Max Value: The upper value limit for this form element.
  • Required Field: Enforces a value for this field. If none is set the form cannot be submitted.
  • Read Only: The value of this form element cannot be edited in the context of the current form.
  • Help Text: Guiding information on how to process or fill out this form element.
  • Help Link: Additional information retrievable from an external web source.
  • Conditional Visibility: This element will only be visible on the Form, if the condition for its visibility is met.
  • Field Name: The internal data field name, corresponding to the list of data fields presented under Program Design >> Data Fields.

 
As shown in Figure 11 the thousands comma separator for Integer- and Decimal form elements provides an option in the Form Editor and in Data Fields to enforce comma separators for large numbers to ease the display of numerical digits:
 

 
Thousands separator for Integer- and Decimal form elements

Figure 11: Thousands separator for Integer- and Decimal form elements



 
You also have the option to set the thousands separator for Integer- or Decimal form elements under Data Fields as shown below:
 

 
Thousands separator for Integer- and Decimal form elements under Data Fields

Figure 12: Thousands separator for Integer- and Decimal form elements under Data Fields



 
Please note: Editing this setting under the Data Fields functionality will affect all references to that field in any form where the field exists to enforce display with commas. This editing functionality under Data Fields only becomes available after at least one Form draft referencing the respective data field has been saved.
 

Sensitive Data Fields

PowerClerk allows you to add Sensitive Data Fields to capture sensitive user information, such as Social Security Numbers, which you want to protect against unwarranted disclosure. Administrators of your program working with Sensitive Data Fields are required to setup Multi-Factor Authentication (MFA) for their account access in PowerClerk. To setup your administrative PowerClerk account accordingly, please navigate to Settings >> My Account >> Set up Multi-Factor Authentication and visit our Support Center article for further information.

As shown in Figure 13, you can drag a Sensitive Data Field to your Form editor as any other data field:

 

 
Adding a Sensitive Data Field

Figure 13: Adding a Sensitive Data Field



 

When one of your program administrators with the permission to access Sensitive Data Fields navigates to a Form containing this kind of data field, they will be able to click the Show button to disclose the obfuscated information:
 

 
Show / Hide Sensitive Data Field

Figure 14: Show / Hide Sensitive Data Field


 

Attachment Fields

Attachment fields make it possible to upload project relevant document types such as .docx, .csv, .xlsx and .pdf file types for easy reference by Applicants or Administrators. Optionally you can request to specify additional acceptable file types and relax the existing 5 MB size limit currently applicable to this field type.
 
Configurable File Extensions: This option allows Program Designers to choose which file types are acceptable for each attachment field (e.g., .JPEG, .PNG, .CAD, etc.). You can define a variety of acceptable file formats with the exclusion of executable files like .exe or .bat:
 

 
Configure Allowed Files

Figure 15: Configure Allowed Files


Allow Large Files: The option to allow Large File sizes to be attached can be configured to enable attachments larger than the platform default. Please note: This option should only be used in circumstances explicitly requiring a deviation from the default value.
 

 
Allow Large Files

Figure 16: Allow Large Files


Feature Reference

Forms

Forms in PowerClerk are configurable by administrators, and can include logic that makes them dynamic and responsive based on user input. Data required in an application are entered into the application form by the applicant and are visible to the administrator upon submission. The application form is composed of fields, each uniquely labeled and positioned by the administrator or their designee. Many application processes have one application form; however, application processes with multiple application forms are also supported in PowerClerk, maximizing the flexibility to serve organizational needs to run programs.

Administrators define the fields contained in an online form, and the position of fields on the form via drag-and-drop. The Administrator drags each field from the list of options on the right side of the page, and drops the field onto the form as shown in Figure 12.

 

Editing Forms

Figure 12: Adding a Field to a Form in the Form Editor

 

Field Types

The following list describes the field types which can be included in a form. It is important to note that additional field types can be developed to accommodate additional technologies, and not all field types will be applicable to all program types.


Field Types
  1. Single Line Text: Free-form text entry field useful for a range of data entry requirements such as account number, etc.
  2. Static Text: Text embedded into the form such as general information, instructions, or other notes. Supports some HTML formatting, including the following tags:
    • “a”
    • “u”, “b”, “I”, “em”, “strong”, “big”, “small”, “pre”, “sub”, “sup”, “s”, “font”
    • “h1”, “h2”, “h3”, “h4”, “h5”, “h6”
    • “address”
    • “table”, “thead”, “tfoot”, “tbody”, “tr”, “td”, “th”
    • “caption”
    • “span”
    • “div”
    • “blockquote”
    • “br”, “ul”, “li”, “ol”, “p”
    • “hr”
    • “#text”
    • Please note: The following attributes are allowed with strict limitations to acceptable values for each:
      • “href” = URL
      • “border “= distance (a number suffixed with a unit from {“%”, “cm”, “ex”, “in”, “mm”, “pc”, “pt”, “px”})
      • “width” = distance
      • “height” = distance
      • “cellspacing” = distance
      • “cellpadding” = distance
      • “target” = “_blank” or “”
      • “name”
      • “colspan”, “rowspan”
      • “start”
      • “style” = semicolon-separated style values for any of the following:
        • “display”: “inline”, “block”
        • “padding”: “inherit”, “initial”, four distances separated by spaces (i.e. “0 1 2 3”)
        • “padding-left”: “inherit”, “initial”, distance
        • “padding-right”: “inherit”, “initial”, distance
        • “padding-top”: “inherit”, “initial”, distance
        • “padding-bottom”: “inherit”, “initial”, distance
        • “margin”: “auto”, “inherit”, “initial”, four distances separated by spaces (i.e. “0 1 2 3”)
        • “margin-left”: “auto”, “inherit”, “initial”, distance
        • “margin-right”: “auto”, “inherit”, “initial”, distance
        • “margin-top”: “auto”, “inherit”, “initial”, distance
        • “margin-bottom”: “auto”, “inherit”, “initial”, distance
        • “width”: “auto”, “inherit”, “initial”, distance
        • “height”: “auto”, “inherit”, “initial”, distance
        • “font-family”: “inherit”, “initial”, one of a long list of fonts that we allow. Many reasonable ones are included.
        • “font-size”: “medium”, “xx-small”, “xsmall”, “small”, “medium”, “large”, “x-large”, “xxlarge”, “smaller”, “larger”, “initial”, “inherit”, distance
        • “font-weight”: “normal”, “bold”, “bolder”, “lighter”, “initial”, “inherit”, distance
        • “color”: either a known color (e.g. “red”, “green”, “blue”, etc.) or a hexadecimal value (e.g. #00FFFF)
        • “background-color”: either a known color (e.g. “red”, “green”, “blue”, etc.) or a hexadecimal value (e.g. #00FFFF)
        • “list-style-type”: “lower-alpha”, “upper-alpha”, “lower-greek”, “lowerroman”, “upper-roman”, “square”, “disc”, “circle”
        • “text-align”: “justify”, “center”, “left”, “right”
        • “text-decoration”: “line-through”, “underline”
  3. Paragraph Text: Same as Single Line Text, but this free-form text field supports multiple lines of text.
  4. Check Box
  5. Integer: Whole numbers only; min and max can be specified.
  6. Decimal: Same as integer but allows decimal expressions. Min and max can be specified.
  7. Drop-Down List: List with entries specified by administrator. Forces user to choose a single response
  8. Multiple Choice
  9. Name
  10. Date
  11. Address
  12. Price: Similar to Decimal; limited to two decimal places and formatted as USD.
  13. Contact: Combination of: Name, Company, Address, Phone Number, and Email Address in one element.
  14. Summation (deprecated): Sum up Integer-, Decimal-, or Price elements present on the same Form. This element will only update its value if it is conditionally visible upon Form submission.
    Please note: The Summation element has been deprecated and will only update via Data Import or PowerClerk’s API if the underlying Form itself is also submitted during these processes. For more complex scenarios, where a calculation needs to be performed consistently across multiple Forms and Form versions, please use Formulas and Calculated Fields.
  15. Email Address
  16. Page Break: Separates the form into multiple pages, each can be given a unique name by the administrator
  17. Document Generation: Generate documents based on project data to simplify communications and contracts.
  18. PV System:
    • A complex control to receive detailed PV system specifications and calculate projected annual performance
    • Linked to CEC PV equipment lists and updated daily
    • Has the notion of multiple inverters and multiple arrays connected to an inverter
    • Contains the following fields:
      • Inverter Manufacturer
      • Inverter Model
      • Panel Manufacturer
      • Panel Model
      • Tracking System – None, Single-Axis, Dual-Axis
      • Tilt – defined per array
      • Azimuth – defined per array
      • Shading
    • Calculates DC rating and CEC-AC rating based on CEC equipment specs and orientation
    • Runs a PV simulation on their system in PowerClerk Interconnect using CPR’s SolarAnywhere® PV simulation technology and TMY3 insulation data
    • Calculates Design Factor (%), which is the ratio of estimated annual production of the system as configured by the user vs. production of the same equipment in the reference orientation and location. Reference zip code and reference tilt are specified by the customer and input by CPR for each program. It is assumed that reference azimuth is 180 degrees (south) and reference shading is none.
    • Show Battery Component: This setting needs to be enabled for the respective PV System data field group on the Data Field Groups tab of the Data Fields page to enable this setting. Please note: This setting cannot be disabled once it has been enabled.
  19. Energy Storage System: The Energy Storage System form element can be used to capture stand-alone energy storage system specifications, or as a separate field in AC-Coupled scenarios where PV + Energy Storage System specifications need to be captured. Please note: Please contact support@powerclerk.com to have this element enabled by a CPR Admin.
  20. Attachment: For upload of electronic attachments, generation of documents from templates specified by the administrator, as well as configuration of eSignatures. See “Document Generation” and “eSignatures” sections for more detail.
  21. User Selector: Provides a dropdown list containing names of all registered users in roles with Program Admin privileges.
  22. Signature Request: One instance of this control is required for routing of eSignatures and placed below Attachment fields
  23. Hyperlink
  24. Formula Result: Displays the result of the chosen Calculated Field.
  25. Table: Add a Table element to allow input of data in a tabular form element. This form element needs to first be setup under Program Design >> Data Fields >> Data Field Groups to become available in the form editor.
  26. Custom List: A Custom List can be any kind of hierarchical list of data, that you would like your applicants to be able to select pre-defined data from. This form element needs to first be setup under Program Design >> Data Fields >> Custom Lists to become available in the form editor.

The Administrator can generate a Preview of the form in its current state in a new browser window during the editing process without needing to commit changes. Changes to a form can be discarded with the Cancel button or committed with the Save button.
 

Field Properties

Most fields can be marked as required using a red asterisk. Integer and Decimal fields permit the administrator to specify minimum and maximum acceptable values; the field will reject entries outside of the acceptable range.


Conditional Visibility

Most fields can also be configured to be conditionally visible. Conditional visibility enables the administrator to specify the condition under which the field becomes visible/invisible to the applicant, and thus enables the form to adjust its requirements dynamically. Dynamic forms minimize applicant confusion by hiding fields that aren’t pertinent, thus reducing the overall length of the application, and the number of opportunities for an applicant to make a mistake.

In the example in Figure 14 below, the administrator is specifying that the Please Describe field is only visible when the applicant selects ‘Other’ in the preceding field: “Generation Type – Prime Mover.” Naturally, if the generation type was defined in a different entry in the drop-down list, the applicant wouldn’t need to specify the generation type in a text field.

 

Conditional Visibility

Figure 14: Conditional Visibility

 
Please note: If you intend to use a data field on two different forms and make one of the fields conditionally visible, then please review PowerClerk’s Conditional Visibility logic in the following video to better understand how PowerClerk would handle such Conditional Visibility configuration:

 

 
Please note: As an exception to the rule explained in the preceding video, Attachment field elements are the only form elements that are retained even if the attachment field is temporarily conditionally invisible. The reasoning for retaining uploaded attachments is to avoid uploading the attachment multiple times dependent on the underlying configuration for the field’s conditional visibility.
 

Additionally, the Administrator may specify Help Text and/or a Help Link for nearly every field type. Either will be visible to the applicant when clicking the blue help icon visible on a data field. See Figure 15 – Help Text and Help Link below.

 

Help Text

Figure 15: Help Text

Video Guides

Edit Forms – Tutorial #1

This video guide will show you how to insert key data fields into forms.  Capture key info from the form so that you have the necessary inputs to approve or reject applications.

 

Edit Forms – Tutorial #2

This video guide will show you how to adjust settings on key data field elements.  Set features like Conditional Visibility and PV or Custom List elements to capture key technical info.

 

Configuring Forms

This video guide explains how to Configure Forms in PowerClerk.

 
A full list of all Video Guides can also be found here.

FAQs

Q: I want to create a read only field to store the application fee amount, but prevent edits to this field, how can I do this?
A: The wrong way to go about this is to try and create a read-only field and assign a default value to this field. Such default values unfortunately are not saved upon form submission as read-only fields are intended for the purpose of displaying data that has been previously submitted.
The correct approach to accomplish what you are intending is to create a formula that contains the constant value, then save and enable that formula, and then connect the Formula Result element in your respective form field. This way the value for this field will be properly saved.
Q: Can I add HTML formatting to static text form fields?
A: Yes, within PowerClerk forms you can utilize a broad variety of formatting options to style your static text form elements according to your needs. Please click on this link for a list of available HTML formatting tags that you can add to static text form fields.
Q: How do I go about getting PowerClerk updated to reflect a new inverter that I cannot find in the current list?
A: PowerClerk uses the CEC-approved equipment lists for inverters (external link) and PV modules (external link) as the sources for its equipment option lists. We monitor those websites and when updates are made there, they are generally reflected in PowerClerk within one business day. However, we have no input or visibility into the approval process for any particular equipment items.
So it is up to the manufacturers to have their equipment models approved for inclusion on the CEC lists; instructions for that are available on the CEC website, including: http://www.gosolarcalifornia.ca.gov/equipment/documents/General_Listing_Request_Procedures.pdf.
Sometimes, the equipment item in question is actually in the option list but it is listed in an unexpected way so that it is not immediately found. Most often that’s due to a manufacturer name variation; here, in fact, there are two variations for this manufacturer, Northern Electric and Northern Electric & Power. But the model you inquired about it is not listed under either one.
Cases of unlisted equipment items like this happen quite infrequently, but some of our program admins have set up their form in such a way that an unlisted equipment scenario can be handled using conditional visibility of inputs. If you’d like some suggestions as to how you might do that, let us know.

WORK-AROUND One possible work-around for the issue with users selecting the “closest” model to their inverter is to set up the form with a “Technology Type” input that included Solar PV (Equipment not listed):
Label settings If Solar PV is chosen, then the standard PV System element is displayed, but if the “Solar PV (Equipment not listed)” option is chosen, then an alternative set of inputs could be displayed instead. For example:
List Fields
Q: If you have a set of fields on a form (e.g. Form 1) that are also utilized on other forms (e.g. Form 2), do we need to update the same field value on each form or just update the field on Form 1 in order reflect the same data in the same data field on Form 2?
A: You would only need to update the Data Field on Form 1 to have Form 2 reflect the same change in data. Please note that for this to work, the data field on Form 1 would need to have the same Field Name as the data field on Form 2 as shown below:
Field name configuration
Field name configuration
Q: How can I make a field's appearance conditional?
A: Most fields can be configured to be conditionally visible. Conditional visibility enables the administrator to specify the condition under which the field becomes visible/invisible to the applicant, and thus enables the form to adjust its requirements dynamically. Dynamic forms minimize applicant confusion by hiding fields that aren’t pertinent, thus reducing the overall length of the application, and the number of opportunities for an applicant to make a mistake.
In the example below, the administrator is specifying that the Please Describe field is only visible when the applicant selects ‘Other’ in the preceding field: “Generation Type – Prime Mover.” Naturally, if the generation type was defined in a different entry in the drop-down list, the applicant wouldn’t need to specify the generation type in a text field.
Conditional Visibility Settings:
Conditional Visibility Settings

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.