Skip to main content

Version 9.1.97 (1 July 2024)

Performance Management

PM dashboard - Resolve the large amount of unnecessary HTTP requests that are made on the dashboard (#116126)

Problem

  • Unnecessary HTTP requests are made on the dashboard

 

Solution

  • Move templates pull for review setup to dashboard load and send data to the modals. 
  • Move the user contract previous and subs load to only happen when the modal is opened. 

 

System Access

Updates to the Forget Password Login (#115694)

1. After forgot password has been selected, the same password is used as the previous one:

    • Change the message to:
      • ”This Password has been used already and you cannot reuse Passwords.  Please select a different Password.”

2. When the password and confirmation password do not match, show the text in white and bold instead of red.

3. Show a masked email address in the message to which the OTP was sent.

 

Languages

System menu Translations (#114922)

  • Change the menu heading text box to read-only
    • Store the translation key for the menu in the DB
    • Update ProductURL with the name as the translation key
    • Display the translation for the key if found.
  • Add a button next to the heading text box “Translate”
    • When clicking the button opens a new tab and loads the language tab for the current active culture e.g. en-Us
  • On Languages| Culture | Global
    • Add a new section called System Menu with a field for each system menu.
  • If the user changes the translation for the system menu where the translation is used, it will reflect that value.
  • The system menu cache will need to be busted when updating the translations of the system menu section.

 

Ruleset Management

Additional services access secret error occurred (TP#116387)

  • Add Tenant admin and ruleset admin global role to the CreateLegacyIntegrationClient request

 

Login

| Translations

Add a new Languages dropdown on the login page (TP#114924)

  • Add a drop-down in the top right corner of the page with the published languages for the current theme’s login
  • The preferred language forms the culture cookie if available must be set
  • The list of active languages must be cached per Ruleset.
  • After logging in, see if the user selected a preferred language (that would have been stored in the database).  If so, change the language to this value and update the cookie accordingly.
  • On the home controller before redirecting into the module confirm that the preferred language in the cookie is the same as the session cache of user details
Back to top