Release Date: 9th August, 2022

2. Accent-insensitive search on the public register: In the Online Register, it is now possible to conduct a smart search that ignores accents in text, such as in a person’s name like “François” or “Mathéo”. All records matching the search criteria, including variations in spelling, will now be displayed.

3. Authorization Document Template: The ability to download certificates in Authorizations has been implemented. The template used to download the certificate may be different depending on the authorization class.

To facilitate the use of this new feature, the Authorization Document Template entity has been created (reg_authorizationdocumenttemplate) to link the authorization document template to the authorization class and status.

The attributes are:

• Name – The name of the authorization document template. This is required.
• Authorization Class – The lookup to the Authorization Class entity. This is required.
• Authorization Status – The lookup to the Authorization Status entity.
• Document Template – The lookup to the Document Template entity. This is required.
• Display Ordinal – The number indicating the display order for this authorization document template. This is required.
• Disable Download – When this is set to “Yes”, the ability to download Authorization certificates will be disabled. Certificates can be downloaded when this is set to “No” or “Unset”.

Note: Configuration assistance is required.

4. Mobile Logo Configuration: In the Portal Logo section of the Portal Configuration entity (port_site), the Mobile Logo configuration has been implemented for use on mobile devices.

To facilitate the use of this new feature, the following attributes have been added:

• Mobile Logo Width – The maximum width of the portal logo on mobile devices. For example, if the width is 75 pixels, enter 75.
• Mobile Logo Width Unit – The unit of measure used for the portal logo width on mobile devices. For example, if the unit is pixels, enter px.

Note: Configuration assistance is required.

5. Portal Azure AD B2C Integration: To facilitate the Portal Azure AD B2C Integration and other integrations, new entities and attributes have been created.

Existing Entities Updated

• Authentication Provider (port_authenticationprovider)
  The new attribute is:

   

  • Name – The name of the authentication provider. This is required.

New Entities Added

• Authentication Provider Configuration (port_authenticationproviderconfig)
  The attributes are:

   

  • Auth Provider – The lookup to the Authentication Provider entity. This is required.
  • Configuration Name – The name for the authentication provider configuration. This is required.
  • Configuration Value – The value assigned to the authentication provider configuration. This is required.
• Portal Authentication (port_portalauthentication)
  The attributes are:

   

  • Name – The name of the portal authentication provider. This is required.
  • Portal Configuration – The lookup to Portal Configuration entity. This is required.
  • Portal – The lookup to the Portal entity.
  • Authentication Provider – The lookup to the Authentication Provider entity. This is required.
  • Active (Yes/No/Unset) – This indicates that this is an active portal authentication provider, when “Yes” is selected.

Note: Configuration assistance is required.

6. A custom process has been implemented to handle application and name change requests, as well as accommodate certain approval actions, which can be defined in the metadata. This custom process is currently only supported for the Business Licensing and Licensee Portals.

The workflow is:
Application Questions > Upload Documentation > Pay Fee > Regulator Approval                (platform) > Print Wallet Card (Business Licensing portal)

The custom process works in combination with custom pages and standard pages. Standard pages include start, supporting docs, declaration, attestation, payment, and complete pages. The Start and Complete pages will always be displayed as the initial and end steps of the custom process. Supporting docs, declaration, attestation, and payment pages will be determined based on whether there is existing configuration.

To facilitate the use of this new feature, several entities have been updated to support the custom process module:

Existing Entities Updated

• Submitted Document (reg_submitteddocument)
  This entity stores the answer record to the supporting document and is connected to the record in the Custom Process Record entity.
• The new attribute in the Related section is:
  • Custom Process – The lookup to the Custom Process entity.

New Entities Added

• Custom Process Type (port_customprocesstype)
  This entity defines the custom process types.
• The attributes are:
  • Name – The name of the custom process type. This is required.
  • Portal – The lookup to the Portal entity. This is required.
  • Metadata – This text field stores the condition metadata defined for this process type.
  • Single Process at a time (Yes/No/Unset) – This indicates a process is re-doable when set to “No”.
  • Number Manager Name – The name of the number manager for this process type.
  • Parent Custom Process Type – The lookup to the parent process type, which indicates this is the parent process type.
  • Active (Yes/No/Unset) – This indicates the custom process type is active, when set to “Yes”. This is required.
• Custom Process Step (port_customprocessstep)
  This entity defines the custom page steps for the custom process type.
• The attributes are:
  • Custom Process Type – The lookup to the Custom Process Type entity for this custom process step. This is required.
  • Name – The name of the custom process step. This is required.
  • Display Ordinal – The number indicating the display order of the Custom Page. This is required.
  • Custom Page – The lookup to the Custom Page entity for this custom process step.
  • Condition Metadata – The condition metadata defined for this process step.
• Custom Process Record (port_customprocess)
  This entity stores the answers to all the questions, on standard pages (i.e., supporting docs, declarations, attestations).
• The attributes are:
  • Custom Process Type – The lookup to the Custom Process Type entity. This is required.
  • Profile – The lookup to the Profile entity.
  • Business – The lookup to the permit holder in the Business entity.
  • Name – The name of the custom process record. This is required.
  • Entity Name – The source record entity name.
  • Entity Record Id – The source record id for the entity.
  • Declaration Issue (Yes/No/Unset) – This indicates the record is associated with a declaration issue, when “Yes” is selected.
• Custom Process Fee Item (port_customprocessfeeitem)
  This entity defines the fee item for a certain process type. If there is no fee item added for a certain process type, the payment page will be skipped.
• The attributes are:
  • Custom Process Type – The lookup to the Custom Process Type entity. This is required.
  • Name – The name of the custom process fee item. This is required.
  • Fee Item – The lookup to the pay product in the Fee Item entity. This is required.
• Custom Process Required Document (port_customprocessrequireddocument)
  This entity is used to associate supporting documents to a certain process type. This works similar to the regular application process. If there is document added for a certain process type, the Supporting Documents page will be skipped.
• The attributes are:
  • Name – The name of the custom process required document. This is required.
  • Custom Process Type – The lookup to the Custom Process Type entity. This is required.
  • Document Type – The lookup to the Document Type entity. This is required.
  • Display Ordinal – The number indicating the document display order. This is required.
  • Upload Online (Yes/no/Unset) – This indicates whether the “upload online” option is enabled.
• Custom Process Declaration Question (port_customprocessdeclarationquestion)
  This entity defines the declaration questions for a certain process type. This works similar to the regular application process. If there is no declaration added for a certain process type, the declarations page will be skipped.
• The attributes are:
  • Name – The name of the custom process declaration question. This is required.
  • Custom Process Type – The lookup to the Custom Process Type entity. This is required.
  • Declaration Text – The declaration question text. This is required.
  • Text String Resource Key – The string resource key of the declaration text.
  • Correct Answer (Yes/No/Unset) – This indicates the correct answer for the custom process declaration question, when “Yes” is selected. This is required.
  • Section Display Ordinal – The number indicating the section display order of the question. This is required.
  • Requires Upload (Yes/No/Unset) – This indicates the custom process declaration question requires a document upload, when “Yes” is selected.
  • Active (Yes/No/Unset) – This indicates an active custom process declaration question, when “Yes” is selected. This is required.
• Custom Process Declaration (port_customprocessdeclaration)
  This entity stores the answer record to the declaration, it will be connected to the Custom Process Record entity.

• The attributes in the Declaration section are:
  • Name – The name of the custom process declaration. This is required.
  • Custom Process – The lookup to the Custom Process entity, which links the answer to the process record. This is required.
  • Profile – The lookup to the Profile entity.
  • Business – The lookup to the permit holder in the Business entity.

• The attributes in the Declaration Answer section are:
  • Declaration Question – The lookup to the Declaration Question entity, which links the answer to the declaration question. This is required.
  • Answer (Yes/no/Unset) – This indicates the answer to the declaration, when “Yes” is selected. This is required.
  • Answer Details – The answer details for the declaration question.
• Custom Process Attestation Question (port_customprocessattestationquestion)
  This entity stores the attestation questions for a certain process type. This works similar to the regular application process. If there is no attestation added for a certain process type, the attestation page will be skipped.
• The attributes are:
  • Name – The name of the custom process attestation question. This is required.
  • Custom Process Type – The lookup to the Custom Process Type entity. This is required.
  • Attestation Text – The attestation question text. This is required.
  • Text String Resource Key – The text string resource key for the attestation question.
  • Section Display Ordinal – The number indicating the section display order of the attestation. This is required.
  • Active – This indicates an active custom process attestation question.

• Custom Process Attestation (port_customprocessattestation)
  This entity stores the answer record to the attestation, it will be connected to in the Custom Process Record entity.

• The attributes in the Attestation section are:
  • Name – The name of the custom process attestation. This is required.
  • Custom Process – The lookup to the Custom Process entity, which links the answer to the process record. This is required.
  • Profile – The lookup to the Profile entity.
  • Business – The lookup to the permit holder in the Business entity.

• The attributes in the Attestation Details section are:
  • Attestation Question – The lookup to the Attestation Question entity. This is required.
  • Answer (Yes/No/Unset) – This indicates the answer to the attestation question, when “Yes” is selected. This is required.
  • Answer Details – The answer details for the attestation question.

Note: Configuration assistance is required.

1. When an individual registration application is submitted, it will now be correctly linked to the registrant’s profile and remain attached to the registrant’s profile when searching through Profiles.

1. A custom process has been implemented to handle application and name change requests, as well as accommodate certain approval actions, which can be defined in the metadata. This custom process is currently only supported for the Business Licensing and Licensee Portals.

The workflow is:
Application Questions > Upload Documentation > Pay Fee > Regulator Approval
(platform) > Print Wallet Card (Business Licensing portal)

Note: Configuration assistance is required.

2. Certificates will now be generated based on Authorization data whenever an Authorization application is staff accepted and if the current Authorization is successfully renewed. The related certificate will be available for download at any time by those with “active” Authorizations.

To facilitate the use of this new feature, the Authorization Document Template entity has been created (reg_authorizationdocumenttemplate) to link the authorization document template to the authorization class and status. When the Disable Download radio button is set to “No” in this entity, the Certificate button will be available in the Authorizations section of the Licensee Portal page and clicking the Certificate button will download the authorization certificate.

Note: Configuration assistance is required.

3. Work Queue item generated per Supervision Experience submitted: For every submitted Supervision Experience that is approved by a supervisor, a new Work Queue item will now be generated so that staff are notified. Once the provisional licensee has been approved as having completed supervision, the provisional licensee will then be eligible to submit an application for full licensure.

4. Azure Active Directory B2C integration: This integration is currently only implemented for the Online Complaint portal users to manage identities within Thentia Cloud portals. Future implementations will handle various portal users, which could include the general public, applicants, licensees, or business owners.

Note: Configuration assistance is required.

5. Accent-insensitive search on the public register: In the Online Register and Platform, it is now possible to conduct a smart search that ignores accents, such as in a person’s name like “François” or “Mathéo”. All records matching the search criteria, including variations in spelling, will be displayed.

6. Dynamically hide declaration and attestation pages in all applicable processes: Attestation and Declaration pages will now be skipped (disabled/hidden) depending on configuration if attestations or declarations are not required to complete a process.

To facilitate the use of this functionality, the following two attributes have been added in the “Visible to” section of the Declaration Question entity (reg_declarationquestion):

• Application Process (Yes/No/Unset) – Indicates the declaration question is visible to the Application Process when set to “Yes” and hidden from the process when set to “No”.
• Renewal Process (Yes/no/Unset) – Indicates the declaration question is visible to the Renewal Process when set to “Yes” and hidden from the process when set to “No”.

Note: Configuration assistance is required.

7. Custom Page Enhancement – Button: The ability to add button items or functionality to custom pages is now available. The custom page button will require custom code to be added.

Note: Configuration assistance is required.

8. A secure Online Complaint Portal has been implemented as requested by MVP. After logging in, a user will be able to do the following:

• Update their personal information, which pulls from the same profile as other portals
• Create new complaints
• Save complaints as drafts
• Resume complaints saved as drafts
• Submit complaints

1. In the Application Review/Print page, buttons will no longer be displayed with an outline.

2. After submitting any application type, the Application Documentation page will now correctly display the chosen application type, instead of the application status, under the Application Type column.

3. When using portal version >= 2.8.0, and adding an application record manually, the Application Number will now be automatically generated based on the number manager. Other fields, like the Invoice Number, that are linked to number managers will also now generate those numbers automatically.

4. After starting a new application, the application type name will now be automatically displayed under the Application Type in the left navigation menu of the portal.

5. When authorization declaration questions are configured in the Authorization Declaration Question entity (reg_authorizationdeclarationquestion), the content of the Declaration Text field will now be displayed correctly on the portal.

6. When making a payment for an application and the wrong credit card information is entered, an error message will now be displayed to inform the applicant of the issue.

7. From the Application Payment page, when processing a payment for an application, the applicant will now be redirected to the correct payment authorizer’s page to make the payment.

8. After removing a payment for a particular application type and then submitting the application, the “Application Review” page will now be generated, regardless of whether there is a payment page.

9. In the Application Review/pdf download of the review, the “Professional and Fraternal Organization Membership” and “References” pages will now display the “Edit” and “Delete” buttons with the correct images and format.

10. Two issues have been fixed:

• The total submitted hours (i.e., Total Submitted this CE Period) has been fixed on the Continuing Education Summary page and will now reflect the correct total number of hours submitted for all program records.

• On the User Accounts page of the Business Licensing Portal, after clicking on the button “Add New Records”, the page will now load properly, and the page contents will be available for use.

11. In the Registration/Licensee Renewal pages, after the submission of a renewal for an active registration/license:

• The username will now be correctly displayed at the top right of the page.
• In the left navigation menu, all options that were displayed prior to the renewal submission will remain displayed after the renewal is submitted.

13. The ability to restrict the number of decimal places in the Number field on custom forms/pages is now available by adding the number of decimal places (e.g., 3) to the key “roundToPlaces” (e.g., “roundToPlaces”: 3) in the metadata of the custom form/page.

14. The Supporting Documents page will no longer be presented as a step in the license renewal process, if the license class does not have the supporting documents requirement configured.

15. When the mobile device (e.g., iPhone 9 series or iPad) screen/viewport is too small, the Print button is intentionally hidden. If the Print button is disabled on the screen, the printer is most-likely not selected. The print option in this case is controlled by the web browser and not the Thentia Cloud application.

On a mobile device, such as an iPad, after logging into any portal that has invoices, select Application Receipts, and then click on the Print button to print the invoice.

The favicon will now be present on mobile devices (e.g., iPad, Tablet) when using different browsers.

16. Whenever the login screen of any Portal is loading, the correct value of the string resource, e.g., “Powered By”, will be displayed on the screen.

17. The Thentia Cloud logo has been modified to display more legibly and in entirety on Mobile devices.

18. When logged into various portals on desktop and mobile devices, the contact phone number will now be hyperlinked. Also, the registration type and registration number will no longer be truncated.

Also, after downloading the wallet card, the entire name of the registration type will now be displayed, instead of being truncated.

19. When using a mobile device:

• If logged into the School Administration Portal, the name of the school and username will now correctly appear at the top right of the screen.
• If logged into the Inspector Portal, select the “Assigned to me” section, and then expand the ‘Business’ section, the assigned Inspections list/grid will now display the correct headings:
  • Inspection Number
  • Inspection Created Date
  • Facility Name
  • Inspection Category
  • Inspection Type

20. The Thentia Cloud logo will now display at the correct size in comparison to the rest of the invoice page when printing invoices.

21. On the Renewal Payment page, after switching the method of payment (e.g., e-transfer to cheque and vice versa) to process a payment for a renewal, the page will refresh to correctly reflect the selected method of payment.

22. When configurable navigation is turned on/enabled for a portal through the platform configuration, the custom pages will now remain displayed on the portals to which they are linked.