System Requirements: Cobalt Certification 3.11 or higher
The default Certification functionality is "independent" where users can apply for and hold several Certifications each with their own unique Start Date, End Date, Expiration Date, Cycle Begin Date, and Cycle End Date. Because the Certifications have different dates, the recertification process and CEC cycle process occur independently and users will update each Certification as needed at varying times.
Joint Certification functionality was introduced in Cobalt Certification 3.11. The system can be configured for "joint" certification so that credentials collectively expire and can be renewed all at once. Certifications that are "joint" will receive the same End Date, Expiration Date, Cycle Begin Date, and Cycle End Date.
System Configuration
Configuring a system for Independent or Joint Functionality is something that should not be changed often. Once it is set, it should be left. There should be no flipping back and forth.
To turn on the Joint Certification Functionality, navigate to the Settings record. On the Cobalt Certification Dynamics Form, the “Collective Certification Expiration Behavior” field should be set to Joint. Save changes
Data Configuration
Once the system is configured for Joint Certification, there is some system data that will need to be configured. The system data will be used on the customer data that is generated during the initial certification application process. Once the system data is set, it can be adjusted as needed. However, adjustments might occur on an annual basis and it is not expected that changes would occur that often.
- Create at least two Certification Type records with the grace period value set.
- Create an Initial Certification Application Type for each Certification Type.
- Create an Initial Certification Application Fee for each Initial Certification Application Type.
Initial Certification Scenarios and Expected Behavior
Scenario 1: Applying for a first Certification
Use Case: A Contact is eligible to apply for/receive a Certification and does not have an existing active Certification already.
Expected Behavior:
Verify a Certification record is created and active with the following date values:
- Start Date = Today (the day the Initial Certification Application was completed and the Certification was created)
- End Date = set based on the duration logic on the Initial Certification Application Type
- Cycle Start Date = same as Start Date
- Cycle End Date = same as End Date
- Expiration Date = End Date + Grace Period set on the Certification Type
Scenario 2:
Use Case: A Contact with an existing active Certification (with the End Date in the future) applies for another Certification.
Expected Behavior:
Verify a Certification record is created and active with the following date values:
- Start Date = Today (the day the Initial Certification Application was completed and the Certification was created)
- End Date = matches the End Date of the existing active Certification
- Cycle Start Date = matches the Cycle Start Date of the existing active Certification
- Cycle End Date = matches the Cycle End Date of the existing active Certification
- Expiration Date = matches the Expiration Date of the existing active Certification
Scenario 3:
Use Case: A Contact with an existing Certification (with the End Date in the past, but Expiration Date in the future, aka within the grace period) applies for another Certification.
Expected Behavior:
Verify a Certification record is created and active with the following date values:
- Start Date = Today (the day the Initial Certification Application was completed and the Certification was created)
- End Date = matches the End Date of the existing active Certification
- Cycle Start Date = matches the Cycle Start Date of the existing active Certification
- Cycle End Date = matches the Cycle End Date of the existing active Certification
- Expiration Date = matches the Expiration Date of the existing active Certification