Thentia Cloud release notes: Version 1.29.0 (July 27, 2023)

Standard report - Billing based on active license: A new standard report has been created in the Analytics module to show the list of license types with the total number that have a status flagged as “billable”.
 

For example:

Classification | License Type | Total

Individual | Cosmetologist | 22330

Individual Authorization | Straight Razor Shave | 2333

Business | School License | 23333

Facility | Salon | 2323

Education Provider | Continuing Education | 435

The final line in the report displays a total count for all licenses by classification.
For example:

Classification | Total

Individual License | 32244

Individual Authorization | 23342

Staff user - Review and print my document: When working with a letter template, the following occurs:

• Clicking on the “Save & Print” button will generate the letter in a pdf file and save the file in the user’s local download folder, as well as in the Files section of the record from which the letter was generated.
  
• The generated pdf file is downloaded via the user’s current internet browser.
  

Note: Configuration assistance is required.

System admin - Preview my letter template: In the letter template, system admins can now do the following:

• Browse for and select a record from the target entity using the Data Source Entity dropdown list.
  
• Click on the new “Preview” section header in the left panel to expand it. The section is collapsed by default.
  
• Select a record letter to preview from the Preview Record Letter dropdown list. A preview of the letter can be viewed in the main panel with the data from the selected record.
  

Note: Configuration assistance is required.

System admin – Prepare or refresh a list of merged fields that I need to map to workbench fields: In the letter template, system admins can now do the following:

• Click on the new “Data Mapping” section header in the left panel to expand it. The section is collapsed by default. All the merge fields ({{ }}) on the letter template are available under this section.
  
• Click on the “Refresh Fields” button to refresh the data mapping list. This is used in the case when a new merge field is added on the main panel after the section is loaded.

Note: Configuration assistance is required.

Staff user - View and select a letter template that I can use to generate a document: Staff users can now view and select a letter template from the list of available preconfigured letter templates, depending on configuration, and then use that template to generate a document. Also, the letter template can be opened in a new tab for editing purposes and letters can be generated and previewed from the main panel.

Note: Configuration assistance is required.

System Admin - View letter template editor as I create or open an existing letter template record: The letter template entity has been enhanced with a new interface for configuring and viewing new and existing letter template records. Also referred to as the "letter template engine" or “enhanced letter generator”, it provides the capabilities to include a letterhead, footer, page number, background images, and more document formatting features similar to Microsoft Word. This engine also supports more data points for a letter document.

System administrators can configure letters that include information from multiple entities. For example, a letter to show license information (primary entity), profile information (parent entity), and License history (child entity).

Note: Configuration assistance is required.

Need billable (tc_billable) attribute on status entities: A new “Billable” (Yes/No/Unset) radio button has been added to the following entities to provide the option of marking a status as “billable” or “not billable”:

• Authorization Status (reg_authorizationstatus)
  
• Business License Status (reg_permitstatus)
  
• Education Provider Status (lrn_educationproviderstatus)
  
• Facility Status (reg_facilitystatus)
  
• License Status (reg_registrationstatus)
  
  

File limit error message: The single file size upload limit to the system is 300MB in order to avoid the server timeout. File size will be checked by the system before a file is parsed. This will prevent server timeouts for files larger than 300MB.
 

Also, when attempting to upload a file that exceeds the file size limit, an error message appears similar to the following: “The attachment size exceeds the allowable limit: 300MB”.

Fix of Security Vulnerability on Containment of Ability to Brute-Force Logins: Additional security features have been implemented to minimize “brute-force login” attacks on the workbench. Now, system admins can configure the number of failed login attempts allowed before a user, based on username, is locked out of the system. The “Time Out Duration” at which the user is locked out of the system due to failed login attempts can be set. Once a user is locked out of the system, an email is automatically sent to notify the user that the username has been locked. The user will then need to wait the allotted time until the username is unlocked in order to be able to log back into the system. System admins will have the ability to reset the password to unlock a locked-out user.

The Payment API is now returning sys_approved = “true” for the Payment processing: Accept payments anywhere Authorize.net payment transactions with a status of "Authorized/Pending Review".

The search feature in the Profile entity now correctly parses search criteria and displays the proper search results.

The Profile entity has been modified to ensure that only records with dates specified in the filter criteria are displayed. Date fields are also sorted correctly according to the sort criteria.

The rich text is now rendered properly after configuring and formatting a text field in Form view through the Reviewer Module.

The table source entity and attribute options are now displayed properly in portal custom pages. Now the options in the “Source Lookup Field Name” dropdown include the "Source Entity" and attribute lookups of the source entity.

Also, if “Source Entity” is selected from the “Source Lookup Field Name” dropdown, the options available for the “Field Name” are the source entity attributes whose types are not lookup. If a lookup is selected in “Source Lookup Field Name”, then attributes of the selected lookup are displayed in the “Field Name” dropdown. 

Business Entity Registration ending in odd years: The license expiration date of a business or facility can now be calculated with the addition of two new radio buttons in the Business License Type entity (reg_permitclass) and Facility Type entity (reg_facilitytype):

• License Period ends in even year (Yes/No/Unset) – If a license period is greater than a year, then this can be used to ensure the expiration date generated always matches the even year requirement. Select “Yes” to indicate that the license period ends in an even year. It does not end in an even year when set to “No”.
  
  For example, if the license period is 2 years, and licenses can only end in even years and I submit an application for a license in the year 2023, and it gets approved, then initially, the system adds the period of 2 years, so that it would expire in 2025. However, because of the requirement of even years only, it will subtract a year to satisfy the requirement, resulting in the license expiring in 2024. When I go to renew the license in 2024, it will now be the full period of 2 years expiring in 2026.
  
  
• License Period ends in odd year (Yes/No/Unset) – If a license period is greater than a year, then this can be used to ensure the expiration date generated always matches the odd year requirement. Select “Yes” to indicate that the license period ends in an odd year. It does not end in an odd year when set to “No”. For example, If the license expiration is calculated as January 2025 and the value for the “License Period ends in odd year” is set to “No”, then the license cannot expire in 2025. Instead, 1 year will be subtracted from the end date, setting the new license expiry to January 2024.
  

Note: If a license period is yearly, then this configuration should never be enabled, as a yearly period would always require alternating even and odd years.

Note: Configuration assistance is required.

Adding sponsor approved / rejected status for sponsor renewal workflow: The sponsor approval workflow has been modified to include the “approved” and “rejected” statuses to provide a business with the ability to mark submitted sponsor renewal applications as either “approved” or “rejected”.

Note: The invoice is currently still generated when a sponsored renewal application is submitted to the business.

Note: Configuration assistance is required.

Individual license - reinstatement config - ability to specify duration in months: The Individual license reinstatement process has been modified to support configuring the duration in days and months within the License Type entity.

Note: Configuration assistance is required.

Apply multiple fees for one Business Document Request Type: Multiple fee items records can now be configured for a single business document request type in the Document Request Fee Item entity (reg_documentrequestfeeitem).

Note: The Business Document Request Type change applies only for the fee items configured in the Document Request Fee Item entity for clients using portal Version 2.4.0 and higher.

In the portal, on the Document Request page, all the applicable fee items will be displayed, along with the total of all fee items as the final payment amount.

Note: Configuration assistance is required.

Need to add Business Address to Business Register: In the public registry, the business address column and information are now available in the custom Business Register search results. 

SSN/SIN input behavior - All Portal: In the portals that have the SSN or SIN field, the number is now masked. When entering each number in the SSN or SIN, the number will be briefly shown and then masked.

Initially, when entering the SSN or SIN, there will be two SSN or SIN fields to enter the number. The second field is used to re-enter the SSN or SIN to mitigate data entry errors and will be used to see if both fields are a match before allowing the user to save the record. Once the record is saved, only one SSN field will be displayed, and the numbers will be masked completely.

Note: After saving the SSN or SIN, if the value needs to be changed, the user will need to contact the regulator to make the change.