Release Date: 26th October, 2022

1. New Attributes: The tracking of a Custom Form process or the description of how the custom form process is used is now possible with the addition of a Description text entry field in the following entities:

• Portal Custom Page (port_custompage)
• Portal Custom Page Process (port_custompageprocess)
• Portal Page (port_portalpage)
• Custom Process Type (port_customprocesstype)
• Custom Process Step (port_customprocessstep)

Note: Configuration assistance is required.

2. Renaming Labels: In the Business License Class entity (reg_permitclass), the following attribute labels have been renamed:

• Fixed Application Period Opens (mm-dd) – Renamed to “Fixed License Period Start (mm-dd)”.
• Fixed Application Period Closes (mm-dd) – Renamed to “Fixed License Period End (mm-dd)”.
• Rolling Application Period Opens (Days) – Renamed to “Renewal Opens (Days)”.

3. Entity Creation / New Feature – Business Portal Structure – Determine Prerequisite License: Agency system administrators can now determine the prerequisite license for acquiring
businesses and associated facilities to enforce prerequisite requirements.

To facilitate the use of this new feature, the new “Prerequisite Business Parent License” entity (reg_prerequisitebusinessparentlicense) has been created with the following attributes:

• Parent License Class – The lookup to the parent license class in the Business License Class entity.
• Application License Class – The lookup to the application license class in the Business License Class entity.
• Name – The name of the prerequisite business parent license.
• Mandatory (Yes/No/Unset) – This indicates if the license class is mandatory if “yes” is selected in the portal.In the Platform:

• • Select “Yes” to indicate selecting an option for this field is required on the portal page.
  • Select “No” to indicate that selecting an option for this field is not required.
  • Select “Unset” to hide this option/field from the portal page.

Note: Configuration assistance is required.

4. Add lrn_profileid to lrn_professionaldevelopmentplan: As per the NLPB request, in the Continuing Education Plan entity (lrn_professionaldevelopmentplan) the missing Profile attribute has been added to link the profile to the Continuing Education Development plan.

Note: Configuration assistance is required.

5. Custom Process Step Unique Identifier: The order of the steps shown in a custom process is now entirely configurable. For example, this new feature will allow showing the declarations step much earlier in the process than would be done normally.

To facilitate the use of this new feature, a “Unique Identifier” optional text field has been added to the Custom Process Step entity (port_customprocessstep). This text field is similar to the one in the Portal Page entity and indicates that the step is connected to one of the standard pages that already exists for a custom process.

Note: Configuration assistance is required.

6. Entities and fields creation – for Managers: Several modifications have been made to accommodate required employee positions such as managers.

New Entities Added:

• The Employment Position License Type entity (reg_positionlicensetype) has been created to specify the required license types of required employee positions. For example, the manager must be in a registration class A status as “practicing”, or a registration class A status as “active”.
  The attributes are:

   

  • Name – The name of the employment position license type.
  • Employment Position – The lookup to the Employment Position entity.
  • Business License Class – The lookup to the Business License Class entity.
  • Registration Class – The lookup to the Registration Class entity.
  • Active (Yes/No/Unset) – This indicates the employment position license type is active when set to “Yes” in the portal.
    In the Platform:

     

    • Select “Yes” to indicate selecting an option for this field is required on the portal page.
    • Select “No” to indicate that selecting an option for this field is not required.
    • Select “Unset” to hide this option/field from the portal page.

Existing Entities Modified:

• The Employment Change Request entity (reg_employmentchangerequest) has a new attribute in the Employment Chang Details section:
  • Position – The lookup to the Employment Position entity.
• The Portal Configuration entity (port_site) has a new attribute in the Place of Practice Configuration section:
  • Use Employment Position List (Yes/No/Unset) – When this is set to “Yes” in the portal, the list of employment positions will be available to choose from.
    In the Platform:

     

    • Select “Yes” to indicate selecting an option for this field is required on the portal page.
    • Select “No” to indicate that selecting an option for this field is not required.
    • Select “Unset” to hide this option/field from the portal page.
• The Employment Position entity (reg_employmentposition) has the following new attributes:
  • Name String Resource – The name string resource key for the employment position.
  • Hide for Individual (Yes/No/Unset) – When “Yes” is selected in the portal, only businesses, and not an individual, can select the employment position. For example, an individual cannot designate their position as the manager, only a business can.
    In the Platform:

     

    • Select “Yes” to indicate selecting an option for this field is required on the portal page.
    • Select “No” to indicate that selecting an option for this field is not required.
    • Select “Unset” to hide this option/field from the portal page.
  • Ask to Specify (Yes/No/Unset) – When this is set to “Yes” in the portal, this is treated as “other” employment position where a new textbox appears in which the other position needs to be entered.
    In the Platform:

     

    • Select “Yes” to indicate selecting an option for this field is required on the portal page.
    • Select “No” to indicate that selecting an option for this field is not required.
    • Select “Unset” to hide this option/field from the portal page.

Note: Configuration assistance is required.

7. Entity Creation Request for Application Steps Configuration / Standard/custom process enhancements: As per a FSRA request, application steps for completing an application are now configurable. This means that both standard and custom pages can be displayed in a designated order or position in the Application Portal. Currently, this feature is only supported in the Individual Licensee application process.

To facilitate this new feature, there is a new entity called “Portal Process Step” (port_processstep), which has the following attributes:

Portal Process Step section

• Name – The name of the portal process step.
• Name String Resource – The name string resource for the portal process step.
• Display Ordinal – The number indicating the display order of this step in the portal process.
• Portal – The lookup to the Portal entity, which indicates the portal to which the step belongs.
• Portal Page – The lookup to the Portal Page entity, which indicates if the page is a standard or custom page.
• Conditions Metadata – Some pages only show conditionally based on configurations and/or user data. This field is used to store conditions in JSON format, which will be parsed and evaluated in the code.

Processes section

• Application Type – The lookup to the Application Type entity. This ties the step to the specified application type in the application process.

Note: Configuration assistance is required.

8. Add Radio configuration: In the Portal Configuration (port_site) entity, within the Business Information section, there is now a new radio button:

• Allow Key Contact Changes Without Request (Yes/No/Unset) – When this value is set to “Yes” changes can be made for key contacts without a request being sent for approval from the portal. When this value is set to “No” requests to change key contacts will be sent for approval.In the platform:
  • Select “Yes” to indicate selecting an option for this field is required on the portal page.
  • Select “No” to indicate that selecting an option for this field is not required.
  • Select “Unset” to hide this option/field from the portal page.

Note: Configuration assistance is required.

9. Add port_stringresource_key to tc_securityquestion: As per a request from CPATA, security questions have been modified to support translations in the Portal using the String Resource entity (port_stringresource). The attributes within this entity which facilitate the use of this functionality are:

• Customer Site – The lookup to the Portal Configuration entity for the customer’s site.
• Language Locale – The language locale used on the portal site.
• Name – The name of the string resources key.
• Value – The value stored by this string resource.
• Portal – The lookup to the Portal entity.

Note: Configuration assistance is required.

1. The invoice download issue reported by NLPB has been fixed. When attempting to download invoices in the Invoice Preview, after clicking on the Download button to view a pdf version of the invoice, the pdf version of the invoice will be downloaded, and the Thentia Cloud Platform will no longer become unresponsive.

2. After saving a registration record, the related data will now be synchronized with the Public Register.

3. Transaction codes will now populate on the Payment page in Thentia Cloud Version 2.0 systems that are using authorized.net as the payment processor.

4. When opening a record or creating a new record, the breadcrumb associated with the record will now appear immediately regardless of whether it is wrapped to the next line.

1. Custom page item type province should check the default country in port_site if a reference country lookup is not specified: When the country is not defined in a custom form, the custom province dropdown will now be automatically populated based on the default country.

2. Business Registration Class record missing abilities: This is a PEICP and NLPB request. In the Business License Class record the Platform user only had the ability to define the start and end dates of a fixed license registration period, as well as to define the number of days after the expiration date that the licensee is able to submit a late Renewal (Late Applications Accepted (Days)). Now with this request the ability to define the number of days prior to the expiration date that the licensee can start renewal in the portal for a Business License Class is now possible.

To facilitate the use of this new feature, within the Renewal Schedule section of the Business License Class entity (reg_permitclass) there is a new attribute called “Renewal Opens (Days)”. This new attribute will allow defining the number of days prior to the Expiration Date that the licensee or registrant is eligible to start renewal.

Note: Configuration assistance is required.

3. Custom Form Permission – Read Only if Value is Present: There is now the ability to prevent changes to certain values on forms to ensure information remains accurate. To accommodate this new feature, the fields that contain personal information will be defaulted to “read only” when the form data loads.

Some cases where the “read only” functionality will apply:

• On the Custom Personal/Business Information page the name and gender will be read-only, etc.
• When editing the Custom Insurance record, values will exist, and some shouldn’t be changed, such as the policy number and company.
• A file might have already been provided however historical files should not be deleted.

4. Business Portal Structure – Determine Parent/Child Relationship(s): Agency system administrators can now identify the parent/child relationships between businesses, facilities and permitted items. This was completed in the Sprint 9 via “Parent Ticket: Introducing Parent-child business relationship”.

To accomplish this in the portal Business Information page, do the following:

• Does this business have a parent business (Yes/No) – Select “Yes” to indicate that there is a parent business.
• Parent Business Name – Select the name of the parent business.

Business Portal Structure- View Business Employee Listing: Agency staff can get a comprehensive view of licensed business’ employees from within the existing Employment module in the portal.

Business Portal Structure – Determine Prerequisite License: Agency system administrators can now determine a prerequisites license for acquiring businesses and associated facilities to enforce prerequisite requirements. Similar to the facility application where a business license can be a prerequisite, a business license can now be a prerequisite for another business license. This functionality considers the parent-child business relationship.

5. Improvements for business application and business renewal flows: The business licensing and business renewal workflows have been modified to satisfy the requirements of the OKCH and LPGAS clients.

To facilitate the use of this new feature, the following changes were made:

• The Shareholder Change Request (SCR) option which was previously mandatory is now configurable. In the Business Information section of the Portal Configuration (port_site) the radio button “Allow Key Contact Changes without a Request” is used to determine whether a change request is required/not required for changing a shareholder or key contact.

To facilitate the use of this functionality, in the Portal Configuration do one of the following:

• • Select “Yes” to indicate selecting an option for this field is required on the portal page.
  • Select “No” to indicate that selecting an option for this field is not required.
  • Select “Unset” to hide this option/field from the portal page.
• Similar to the registration application approval process, a message prompt has been added to indicate that the Business License (e.g., “Business License #XYZ”) was generated when approving the business license applications.

6. The CPO and FSRA clients’ requests have been implemented.

Custom page enhancements:

There is now the ability to link data in a custom table with an application instead of with the user profile in a portal. When adding a new custom table record to an application in the portal, that data will be linked to the application only. If that application is cancelled, all custom table data will be removed as well.

Refer to the following link for more details on configuring a custom table:

• https://thentia.atlassian.net/wiki/spaces/TCP/pages/322043998/Table

Multiple Items Selection:
There is now a multi-select item type available for custom pages, which allows the selection of multiple items at once for a field in a custom page. For this Sprint, the multi-select feature is only enabled for Language combo fields or dropdown lists (e.g., “Select from countries”) in portals.

To facilitate the use of this new feature, the multi-select JSON data must be entered into the Page Metadata field in the Portal Custom Page entity (port_custompage) to enable the multi-select feature on a custom page. The “Language of Care” entity (reg_practicelanguage) is used to populate the languages multi-select field in a custom page.

Refer to the following link for more details on configuring the multi-select feature:

• https://thentia.atlassian.net/wiki/spaces/TCP/pages/446857230/Multi-Select

Note: Configuration assistance is required.

7. Allow optional supporting documents: There is now the ability to make uploading supporting documents optional for completing application processes. This is enabled in the portal when the Platform’s Application Required Document entity (reg_applicationrequireddocument) has the new radio button “Is Optional” set to “Yes” for the designated Document Type. In the portal, the affected document type will not be flagged as required and can be uploaded optionally.

Note: Configuration assistance is required.

8. Business Portal – no name: When a business is selected and it doesn’t have a name, N/A will be displayed in the top selection section of the left navigation menu.

9. Adding the manager concept to the product: The Manager position field has been added to the Add Staff page in the portal.

To facilitate the use of this new feature, the Employment Position License Type entity (reg_positionlicensetype) has been created to store the details of an employee’s position.
The attributes are:

• Name – The name of the employment position license type.
• Employment Position – The lookup to the Employment Position entity.
• Business License Class – The lookup to the Business License Class entity.
• Registration Class – The lookup to the Registration Class entity.
• Active (Yes/No/Unset) – This indicates if the employment position license type is active.

Note: Configuration assistance is required.

10. Decouple payment step from process submission: The Payment page (step) in a custom process for a license or application will no longer support the submission logic, which allows the page to be moved or displayed in any order in the portal.

All submission logic now happens on the Complete page at the very end of the Custom Process workflow. Revisiting the Payment page after a payment has been submitted will result in the user being redirected to the next step.

Also, an additional metadata configuration has been added to prevent the status from updating to the configured value (typically ‘Submitted’). This is useful in the event that the status of the custom process will be conditionally set via the custom page code. For example, a business Approves or Rejects an employee’s application before it is sent to the Regulator for final approval or rejection.

11. Payment Page FeeItems: All fees are now populating correctly for the following payment pages:

• Business Licensing Portal Custom Process Payment page
• Business Facility Renewal Payment page
• Business Renewal Payment page
• Business Application Payment page
• Business Application License Fee Payment page (2 step payment)
• Business Facility Application Payment page
• Business Facility License Fee Payment page (2 step payment)
• Business Authorization Application/Renewal Payment page
• Business Authorization Application License Fee Payment page (2 step payment)
• Licensee Portal Custom Process Payment page
• Licensee Portal Reinstatement Payment page
  Licensee Portal Renewal Payment page

12. Make “standard” steps modular so that their steps are no longer fixed: Process steps used in standard portal pages have been modified from being fixed to now being modular. This means that steps can now be positioned to display in a specific order on a page.

To facilitate this new feature:

• With the exception of the Start, Type Select (if configured), and Complete steps, all other steps can be ordered in any desired way. This is done by creating the steps under a Custom Process Type in the Platform’s Custom Process Step entity (port_customprocessstep).
• For Standard Pages, instead of attaching a Custom Page to the step, the Route of the custom page must be entered into the “Unique Identifier” field of the Platform’s Custom Process Step entity (port_customprocessstep).

• The portal will build the links and order of the custom process based on the Display Ordinal of all the steps.

Note: Configuration assistance is required.

13. Link UTL Improvements: The following modifications were made for handling links:

• When a user navigates to a future page URL, the user will now stay on the current page.
• Whenever validation fails on a page, the user will not be allowed to proceed to the next page.
• There is now a redirect lock in place for the following processes:
  • Application
  • Authorization App/Renewal
  • Business Application
  • Business Custom Process
  • Business Renewal
  • Facility Application
  • Facility Renewal
  • Reinstatement
  • Renewal
  • Licensee Portal Custom Process

14. Standard/custom process enhancements: As per FSRA’s request, the standard/custom process features will now support processes sponsorship applications, license upgrades/downgrades, and license surrenders.

Entity Creation Request for Application Steps Configuration (Platform): As per a FSRA request, application steps for completing an application are now configurable through the “Portal Process Step” entity (port_processstep). This means that both standard and custom pages can be displayed in a designated order or position in the Application Portal. Currently, this feature is only supported in the Individual Licensee application process.

Note: Configuration assistance is required.

15. Public Register custom profile, allow table data to show “exploded” lookups: Changes have been made to allow showing level 2 data on the Online Registry Profile page. These changes are present on:

• Tables – In tables the records that are immediate children of the subject records are displayed. For example, the Education Detail entity (reg_educationdetail) record can be the immediate child of the Profile (reg_profile) entity record. Metadata for a table column will need to be added to display information that is present on the record, connected to Education Detail entity (reg_educationdetail).
• Name Value Pairs – Each name value pair can pull data from subject records, as well as their immediate children. If displaying information present in records connected to immediate children is desired, then utilizing the newly added “nestedFieldConfig” is required. For example, this can be used to display employer and/or education information for the registrant.

Refer to the following link for more details on configuring the Online Registry Profile layout:

• https://thentia.atlassian.net/wiki/spaces/TCP/pages/426672129/Custom+Register+Profile+Layout

Note: Configuration assistance is required.

1. In the ASBBHE portal, all external links will now open in a new tab instead of in the same tab.

2. In the CPO environment, when a new application type (e.g., Eligibility Review – Supervised Practice: Psychologist, Eligibility Review – Supervised Practice: Psychological Associate) is created and declaration questions are added, the Declarations menu option will now appear on the portal.

3. When the details of a new application have been filled in, and after adding or editing a custom table page record, and then hitting the ‘Save and continue’ button, the reported network error will no longer occur.

4. In the PEICP portal, if an application is submitted when the Payment Method record has the “Is Acceptable” radio button not set to “Yes” for the credit card option, the Review & Pay button will be hidden on every Invoice & Receipt page.

5. In the OBA portal, when attempting to save an application, the application will now be saved with all dates in the correct format.

6. The issue reported by CPO has been fixed. Existing field values on custom forms will now be cleared when the value has been changed or hidden.

For example, when editing a new application in the portal to change the Education Level to another, the previously saved Education Level will be cleared, and the new selected Education Level will be stored on the saved record.

7. Clicking on the “Start New Application” button to start a new application, and then selecting the application type will now correctly display the application steps in the left navigation menu.

Bug – portal header banner on iPad view: In the iPad 9th generation, when a user selects the Profile dropdown menu from the portal header banner, the horizontal lines will now remain in position and will no longer shift to the left-hand side.

8. The issue reported by ASBBHE has been fixed. Authorization Attestations will now display in the correct order in the portal according to the number entered in the Online Display Ordinal field of the Authorization Attestation entity in the platform.

9. After submitting an application in the FSRA Portal, and then clicking on the Review button, the “This field is required” error text will no longer be displayed if the file has already been uploaded using the Upload Document (Choose File) functionality.

10. After an applicant has submitted an application and the application has been approved, the evaluation period will now start on the designated Start Date, instead of on the application approval date.

11. As per the NLPB request, the missing Profile attribute that links a profile to the Continuing Education Development plan has been added to the Continuing Education Plan entity (lrn_professionaldevelopmentplan).

12. After the custom code class modification, event triggers have been adjusted to correctly return the custom code in a wrapper function instead of returning the custom code directly.

13. When a new business account is created on the portal, a profile number will now be assigned to the created profile.

14. Placeholder text will now display correctly within the white area in the following locations:

• Licensee Portal > Authorizations (license Application)> Declarations/Attestations
• Licensee Portal > Authorizations (license Renewal)> Declarations/Attestations
• Licensee Portal > Custom Process> Declarations/Attestations
• Licensee Portal > License Renewal> Attestations
• Licensee Portal > License Renewal> Declarations
• Licensee Portal > Name change request
• Business Portal> Business License Application> Declarations/Attestations
• Business Portal> Business License Renewal> Declarations/Attestations
• Business Portal> Custom Process> Attestations
• Business Portal> Custom Process> Declarations
• School Portal> Name change request page

15. After creating a custom page to override a standard Complaint Form and the page includes the supporting document widget and the file upload feature, when the complaint is submitted with files uploaded, the uploaded files will now be saved.

16. The same license renewal approval process will now be completed regardless of whether the approval was done manually or automatically.

17. On Custom Pages, when there is an error related to the Upload Document (Choose File) functionality, the “This field is required” text will now always display in red, and the user will not be able to proceed to the next page if no file has been uploaded.

18. The proration amount can now be set to $0 based on configuration in the Fee Proration Condition entity and the correct proration fee will be used.

19. Selected items on the navigation menus in all portals will now remain highlighted (in their active state) making them distinguishable from non-selected items. Also, the color theme on mobile navigation bars has been adjusted based on the color configurations completed in Sprint 5.

20. When the locale is set to French, the fee items and string values will now correctly translate to French on invoices and receipts.

21. CPATA security questions have been modified to support translations in the Portal using the String Resource entity (port_stringresource).

22. On the LSBID Public Register page, the “Only show Licensees with discipline notices” checkbox has been removed as requested.