Release Date: 31st August, 2023

Ability to include picture on letter certificate: Picture files that are related to portal users (e.g., a photo on a license) or system users (e.g., the signature of an inspector) can now be included on letter certificates.
 

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

• In the Document Template entity (tc_documenttemplate), image variables can now be added and must have the name prefixed with “img_”. The system treats “img” as case-insensitive, so an image named {{img_portrait}} or {{IMG_portrait}} is treated as the same image. 
  
  
• In the Data Mapping section on the left panel of the Letter Template entity (Comms – Letter Template), there are new attributes to accommodate image or picture files:
  • The “Connection Source Entity” dropdown list allows the user to select an entity to collect image information from for the primary and child entities outside a loop and a single child entity within a loop.
    
    
  • A filename can be specified for the image to display, along with the dimensions (width and height) of the image in pixels. The default dimensions are 80x80.
    
    
    • Image – The name of the picture file, minus the “img_” prefix (e.g., “photo”, “portrait”).
    • Width (px) – The width of the picture.
    • Height (px) – The height of the picture.
      
• The system uses the information provided for the image within the record of the specified entity to find an image file (e.g., jpeg, jpg, png, bmp, gif) that has a name starting with the entered string. If there are multiple files that match the criteria, the system will use the file that is uploaded first.

Note: Configuration assistance is required.

When a table is configured with a column to show a lookup name, the lookup value from the parent entity is being displayed by the lookup.

When registering for a new account in the portal, the Profile entity (reg_profile) is now saved without the first and last names of the portal user. This allows the new user to create and activate the new account from the portal and in the Workbench, an empty record will be generated with only the portal user connection filled in.

Register - Profile

Within the Task management panel in the Reviewer module, dropdown fields that have options with an “&” will now display the “&” instead of “&”.

In the Summary View, the table connection is now using the filter parameter from the configured View to display the correct information.

The Thentia Cloud usage logs, which utilize custom messages to add additional information about the event being captured, are now being properly cleared to ensure the correct logs are being stored for the current event.

Whenever API create or update calls fail, the related create or update functionality on workbench entities will now also fail.

Facilities are not shown after selecting a business: After selecting a business in the portal, clicking on “Facilities” in the left navigation menu will now display the list of facilities associated with the business on the Facility page.

Note: Configuration assistance is required.

Allow documents to be collected in a facility application: In the portal, during the facility application and facility renewal process there is now the ability to upload and submit supporting documents.

Custom Complaint Form: Respondent types are now being populated in a Respondent Type dropdown on the Complaint form in the portal to allow the user to select the type of respondent. Respondent Types will only be populated in the dropdown based on the following rules:

• If any respondent type is active according to the type shown in the dropdown.
  
• If no respondent type is active, then the Licensee field will be shown by default.
  
• If all types are active, then all Respondent Types are displayed in the dropdown.

The current types are “Business”, “Facility”, and “Licensee”.

To facilitate this new feature, in the Workbench, there is now a new entity called Complaint Respondent Type (com_complaintrespondenttype), which stores the various types of complaint respondents.
 

Ability for agency staff to request additional documents related to a complaint: Agency Staff are able to request additional documents related to a complaint. Once the request is made a complainant can add the documents via the Document Upload page in the portal.
 

The process flow:

1. The complainant opens the Complaint Portal.
   
2. The complainant submits a formal complaint.
   
3. The regulator reviews the complaint.
   
4. The regulator requests further documents from the complainant.
   
5. The complainant views the documents they need to upload when viewing the “Upload Document” page.
   
6. The complainant uploads the requested documents.
   
7. The agency staff views the submitted documents.
   
   

Attestations, declarations, and fees now display only for the application type on which they are configured.

Note: The renewal and reinstatement configurations are only controlled by the license type on the record.

When a logged in user is following the security steps and is on the Password Reset page, they will now be able to reset their password successfully, instead of their logged in session being terminated.

On custom pages, sentences will no longer display under the “Note:” label, instead all texts will display formatted in a paragraph.

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” that 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 also have the ability to reset the password to unlock a locked-out user.