PowerClerk Support Center

Program Design
Automations
Questions to Ask
Locating the Automations feature
How to create an Automation
Automation Triggers
Automation Action Rules
Validation Rules
Scheduled Triggers
Troubleshooting Automations
FAQs
Channels
Questions to ask yourself
Locating the Channels feature
What are Channels?
Types of Channels
Channel Type: Mark as Child
Channel Type: Make Successor
Channel Type: Create Related Project
Channel Type: Submit Related Project
Channel Type: Project Lookup
How to create a Channel
Channel Signals and Automations
FAQs
Communications
Questions to ask yourself
Locating the Communications feature
Creating Communication templates
Finding Data Tags
Bulk Communications via Data Import
Images in Communications
Project Attachments and Content Library Items
Smart Templates
Upgrading to Smart Templates
Upgrading when a Test Environment Exists
Broken Template Tags
Examples of Broken Template Tags
PowerClerk Bulk Email Communication Policy
FAQs
Connections
Questions to ask yourself
Locating the Connections feature
What are Connections
How to Create a Standard Web Adapter
Define Input and Output Fields
Connecting, Testing, and Enabling the Web Adapter
Creating a Standard Web Adapter Configuration
Utilizing Connections on PowerClerk
Maintaining and Editing the Web Adapter
Web Adapter Message Type Format
Supported Message Versions
Error Handling
Custom List Lookup
Create a Custom List Lookup
Utilizing Custom List Lookup
FAQs
Content Library
Questions to ask yourself
Locating the Content Library feature
Uploading content to the Content Library
Use with Communication Templates
Use for Front Page content
FAQs
Custom API IDs
Questions to Ask
Locating the Custom API IDs feature
How to edit a Custom API ID
FAQs
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
Deadlines
Questions to ask yourself
Locating the Deadlines feature
What are Deadlines
How to Create a Deadline
Deadline Automation Action Rules
Utilizing Project Admin Page for Deadlines
Communication Templates for Deadlines
Deadline Set/Satisfy Options
Program-Wide Deadline Actions
Reporting on Deadlines
Deadlines in Project List Columns
FAQs
Document Templates
Questions to ask yourself
Locating the Document Templates feature
How to define a new Template
How to define a new Merged Document
eSignatures
DocuSign template tags
Mapping eSignature tags
Smart Templates
FAQs
eSignature Envelopes
Questions to Ask
Locating the eSignature Feature
What are eSignature Envelopes?
eSignature Checklist: The Prerequisites to create a new Envelope
How to set up Advanced eSignature Envelopes Step-by-Step
How to add an eSignature Envelope to a form
eSignature Automation Trigger
Viewing Completed eSignature Envelopes
Resending eSignature Notifications
Canceling eSignatures
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
FAQs
Formulas and Calculated Fields
Questions to ask yourself
Locating the Formulas feature
How to work with Formulas and Calculated Fields
Formula Data Dictionary
Dynamic Formula References
Rules of Formula References
Advanced Visibility Rules
Video Guides: Formulas
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 create and edit Incentive Designs
Incentive Options for One-Time Incentive Type
Incentive Design Options
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
How to edit the Project Summary
FAQs
Project Views
Questions to ask yourself
Locating the Project Views feature
How to edit Project Views
FAQs
Roles
Questions to ask yourself
Locating the Roles feature
How to create and edit a Role
Access Groups
Access Groups and Automations
Access Groups and Data Imports
Access Groups and Reports
FAQs
Workflow
Questions to ask yourself
Locating the Workflow feature
How to create and edit the Workflow
Transitions
Workflow Example Overview
FAQs
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
Steps to Complete a Data Import
Data Import Configurations
Column Header Types
Automatic Data Imports via SFTP
FAQs
Duplicate Check
Questions to ask yourself
Locating the Duplicate Check feature
How to use Duplicate Checks
FAQs
Import Projects
Questions to ask yourself
Locating the Import Projects 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
Locating the Project Inquiry feature
How to edit the Project Inquiry Settings
Automating Communications for Project Inquires
Inquiry Summary
Questions to ask yourself
Locating the Program Info feature
How to edit the Program Info menu
Notification Banners
Usage 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
Sharing 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
Tools Menu
My Account
Questions to Ask
Locating the My Account feature
How to use the My Account feature
Setting up Multi-Factor Authentication
Missing, lost, or stolen mobile devices: resetting Multi-Factor Authentication
Disabling Multi-Factor Authentication
Recovery Guidelines for MFA Administrators
FAQs
FormSense
Questions to Ask
Locating the FormSense feature
How to use the FormSense feature
FAQs
Grant Access
Questions to Ask
Project Grants vs Broad Grants (i.e. "Grant Access")
Locating the Project Grant feature
Locating the Grant Access feature
How to use the Grant Access feature
FAQs
Integration Guides
ePayments
Questions to ask yourself
Locating the ePayments History feature
How to add ePayments
FAQ
PowerClerk API
Questions to Ask
What is the PowerClerk API?
What can the PowerClerk API do?
Integrating with the PowerClerk API
API Documentation for Developers
Single Sign On (SSO)
Questions to Ask
PowerClerk SSO Configuration
Azure AD Configuration (SAML)
Azure AD Configuration (OIDC)
Okta IDP Configuration (SAML)
SP Configuration
SSO for multiple programs
IDP Configuration Troubleshooting
FAQs
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
FormSense
Edit Forms - Tutorial #1
Build A Formula
Edit Forms - Tutorial #2
Automation with Formulas in Action Rules
Configuring Forms
Formulas and Advanced Visibility Rules
Calculated Fields
Milestones
Project Summary
Setting up Roll-up Reports
Roles and User Administration
Visualize Workflows
ArcGIS
API
SFTP Automatic Data Import
Standard Web Adapter Setup
PowerClerk Program Launch
PowerClerk User Group Sessions (UGS)
Learning Management System (LMS)

Channels: Mark as Child and Make Successor

Channel Type: Mark as Child

The Mark as Child Channel Type allows an admin to declare a project to be the child of another project. Relationships can be seen on the Project’s Admin page. No information is shared between the related projects. Multiple projects can become the children of one parent project. 
 
The Mark as Child Channel type assists Admin when a new project was created that is related to a different project, but still needs to undergo the workflow. Therefore, the new project may appear as a ‘duplicate’ and have matching data fields but is a viable project. 
 

    Attributes of the Mark as Child Channel Type:

  1. Both projects already exist.
  2. Multiple projects can be marked as a child to the same parent project.
  3. No data is copied from the parent project to the child project.
  4. No further Automation or Action needs to occur in the relationship.
  5. Manually relate the projects together on the Child Project’s Admin Page.
    Use-cases for this Channel Type may include:

  • Adding equipment and/or updating an existing system where the original is already a project.
  • An applicant submits multiple viable projects under the same account. For example, a program that has many types of applications.

 
Creating the Mark as Child Channel Configuration
If this is an interprogram set-up, establish which program is the Published Program and which program is the Linked Program. The Published Program is the program that will have the child projects. The Linked Program is the program that will have parent projects.
 
First, navigate to the Publishing Program. Then select “Publish New Channel” and select the Mark as Child Channel Type.
 

Create Mark as Child Channel

Figure 1: Create Mark as Child Channel

 
On the configuration page, you will select which data field(s) your Administrators can utilize to ensure the correct project is selected. PowerClerk will lookup the parent project’s data field values and return the result to your Administrators when they are marking the new project as a child to the parent project. It acts as a check for the Administrators. An example may be the Account Number of the Applicant.
 

Lookup Project Configuration

Figure 2: Lookup Project Configuration

 
To configure the data field lookups, you will first select the Data Field Type and Data Field Alias. The Alias acts as a label for you to understand what data you are attempting to lookup. You cannot change the Data Field Type and the Alias once the Channel has been published.
 
You will also select the Specific Data Field that should be mapped to the Data Field Alias. This is the Data Field you wish to pull information from this Program. If you are connecting two programs, you will select the Data Field in the linked program as well when you link this Channel. This can be edited after the Channel is published.
 
You can add multiple data fields to return for lookup.
 
Once you are ready, save the Channel Configuration.
 
Publishing The Channel
Publish the Channel by clicking on your new Channel. Select the Group and Save.
 

Publish Channel to Group

Figure 3: Publish Channel to Group

 
Link the Channel
If this Channel is within the same program, tab over to “Linked Channels” and press “Link to Channel”. Select the proper Group and Channel and select “OK”. Then “Enable” the Channel.
 
If this Channel is between multiple programs, navigate to the other program’s Channel page. Tab over to “Linked Channels” and press “Link to Channel”. Select the proper Group and Channel and select “OK”. Then “Configure” the Channel and select the proper Data Fields to map the Lookups data fields. “Enable” the Channel.
 

Link Channel

Figure 4: Link Channel

 
Add Channel to your processes
This Channel only relates projects together and does not share information or take action on related projects.
 
To use this Channel, an Administrator can mark a project as a child on the Project’s Admin Page. You will select “Mark Project as Related” and enter the Project Number of the targeted project that will become the Parent. Then select “Check” to expose the Lookup Data. Once you have confirmed that these projects should be related, select “OK”.
 

Mark Project as Child to Parent

Figure 5: Mark Project as Child to Parent

 
The relationship will appear on the Project’s Admin Page. It will not appear on the Project’s View/Edit Page.
 

Relationship on Project Admin Page

Figure 6: Relationship on Project Admin Page

 
We suggest using this feature in conjunction with the Duplicate Check feature to easily locate projects that share the same Lookup information. We also suggest exposing the Lookup data fields in the Project’s Admin Page Project Summary for ease.
 
You may consider adding a checkbox or Multiple Choice to your Review Form to help remind your Administrators to check for parent projects.
 

Use Automatic Duplicate Check

Figure 7: Use Automatic Duplicate Check

 

Channel Type: Make Successor

The Make Successor Channel Type allows an admin to declare a project to be the successor of an existing project. It will copy data from the predecessor project, mark the current project as the successor, and send a Signal back to the predecessor project to take action.
 
The Make Successor Channel type is similar to the Mark as Child. A new project was created that is related to a different project, but still needs to undergo the workflow. In this use-case, data needs to be copied from the predecessor project to this current project. Action may need to be taken on the predecessor project (for example, moving it to an Archived status).
 

    Attributes of the Make Successor Channel Type:

  1. Both projects should already exist.
  2. Data can be copied from the predecessor project to the successor (as a one-time data copy).
  3. Further Automation Actions can occur on the predecessor project once it has been related.
  4. Manually relate the projects together on the Successor Project’s Admin Page.
    Use-cases for this Channel Type may include:

  • Move in/move out process where you want to copy information over and/or take action on the original project
  • Updates to an existing system where you want to copy information over and/or take action on the original project.

 
Creating the Make Successor Channel Configuration
If this is an interprogram set-up, establish which program is the Published Program and which program is the Linked Program. The Published Program is the program that will have the successor projects. The Linked Program is the program that will have predecessor projects. If interchangeability is desired, you can create two parallel Channels that are reversed.
 
First, navigate to the Publishing Program. Ensure that you have a Channel Group set-up by a CPR-Admin. Then select “Publish New Channel” and select the Make Successor Channel Type.
 
Select Data/Attachments to Copy
On the configuration page, select any data fields and attachments that you want copied from the predecessor project to the successor project. This will be copied the moment the relationship is created as a one-time copy. For example, in a move in/move out process, you may wish to copy the PV System Specs and One-Line Diagram.
 
Select the Data Field Type and Data Field Alias. The Alias acts as a label for you to understand what data you are attempting to copy. You cannot change the Data Field Type and the Alias once the Channel has been published.
 
Select the Specific Data Field that should be mapped to the Data Field Alias. This is the Data Field you wish to store the information in this program. You will select the Data Field in the linked program to pull the information from when you link this Channel. This can be edited after the Channel is published.
 
Establish a Signal
When you make a project a successor, you can send an Automation Signal back to the Predecessor project and take action. You can change the status of the Project, set data fields, etc. A common example is changing the status of the Predecessor Project to “Archive”.
 
Create a clear signal name to utilize in your configuration.
 

Configure Make Successor Channel

Figure 8:Configure Make Successor Channel

 
Lookup Project Configuration
Just like the Mark as Child Channel Type, you will select at least one data field to return for lookup and confirm the correct project was selected. See the Mark as Child Channel Type above for more information.
 
Once you are ready, save the Channel Configuration.
 

Configure Lookup Project Configuration

Figure 9:Configure Lookup Project Configuration

 

Publishing the Channel
Publish the Channel by clicking on your new Channel. Select the Group and Save.
 

Link the Channel
If this Channel will stay within the same program, tab over to “Linked Channels” and press “Link to Channel”. Select the proper Group and Channel and select “OK”. “Configure” the Channel. Map the data field aliases to the proper data fields for the data exchange and project lookup. These can be the same data fields from the Published ones, or unique ones. Then “Enable” the Channel.
 
If this Channel is between multiple programs, navigate to the other program’s Channel page. Tab over to “Linked Channels” and press “Link to Channel”. Select the proper Group and Channel and select “OK”. “Configure” the Channel. Map the data field aliases to the proper data fields for the data exchange and project lookup. Then “Enable” the Channel.
 

Configure Lookup Project Configuration

Figure 10: Configure Lookup Project Configuration

 
 

Map Data Fields in Linked Configuration

Figure 11: Map Data Fields in Linked Configuration

 
Add Channel to your processes
This Channel relates projects together, shares information from the Predecessor to the Successor, and can take action on the Predecessor.
 
Set Up Signal
See below on how to set up Channel Signals in Automations. A common use-case is moving the predecessor project to an “Archive” status and setting a data field to indicate why. Please note that for this channel, the signal will only be received at the moment the relationship is created.
 

When a signal is received from the published channel

Figure 12: When a signal is received from the published channel

 
Mark the Projects as Related
To use this Channel, an Administrator can make a project a successor on the Project’s Admin Page. You will select “Mark Project as Related” and enter the Project Number of the targeted project that will become the Predecessor. Then select “Check” to expose the Lookup Data. Once you have confirmed that these projects should be related, select “OK”. The data will immediately be copied over.
 
The relationship will appear on the Project’s Admin page. It will not appear on the Project’s View/Edit page for applicants to see.
 
We suggest using this feature in conjunction with the Duplicate Check feature to easily locate projects that share the same Lookup information. We also suggest exposing the Lookup data fields in the Project’s Admin Page Project Summary for ease.
 
You may consider adding a checkbox or Multiple Choice to your Review Form to help remind your Administrators to check for predecessor projects.
 

Creating Relationship on Project Admin Page

Figure 13: Creating Relationship on Project Admin Page

 

 

Information Shared as see in Project Data History

Figure 14: Information Shared as see in Project Data History

 

Video Guides

Would a video guide help to better explain Channels? Contact us and let us know.
 
A full list of all Video Guides can also be found here.

FAQs

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.