Skip to main content

Version 9.1.124 (21 October 2024)

Imports

Data file upload (#121204)

Problem

    When the ruleset does not use payroll connectors the import breaks when updating user data When the username has been accented the import of appointments fails When the job profiles are imported without a code, only the first job profile is imported into the sheets, and the import fails at the positions step.
    When the org codes are not provided the import uses the ruleset name as the root node rather than the org level 1 when constructing the org path and the position step fails because the org could not be found. When you save on the integration tab and the content server validation fails the other settings on the page are not saved.
    When the content server has a valid password and you save the validation fails because the password is not sent to the server.

     

    Solution

      Initialised payroll connector as null rather than new
      Sanitise the username in dapper queries when accents are present
      Add fallback to the title when the job code is empty when determining the unique jobs to create
      Use the org level 1 when creating the path

       

      Ruleset Management

      User Name Changes (#119426)

      Problem

        When you save on the integration tab and the content server validation fails the other settings on the page are not saved
        When the content server has a valid password and you save the validation fails because the password is not sent to the server

         

        Solution

          Change the order of the actions in the update so the content server is updated at the end
          Change the selector that retrieves the value of the password field

           

          Handle invalid ruleset error better (#120938)

          Problem

            A vague error message is displayed when the ruleset cannot be determined from the URL

             

            Solution

              Display a more appropriate message when the URL is incorrect

               

              HR Processes

              Claims Report (#120508)

              Problem

                On the Historical Requests tab, the display limit is currently 10 When clicking on Load More it does not appear to work and still only displays 10, when there are more than 10 items in the database The problem is with the container ID used for each tab ('Awaiting', 'Open', 'Historic') All 2 use the same partial to populate information This partial had a wrapper div with an id="process-requests-container." When clicking on the next displayed tab, it loads the partial into the next v-tab—"container," with the result being that there is more than 1 element with id="process-requests-container." When the Load More then tries to add the next batch of requests, it looks for #process-requests-container and adds the requests to the first element it finds which adds the historical records to the 'Awaiting' tab

                Solution

                  Changed the partial wrapper div id to be determined based on the selected tab, changed the page hidden fields to be class references to not have duplicate id elements present Changed the Load More functionality to look for the specific tab container ID and add the items to that to ensure the correct elements are used

                   

                  Performance Management

                  Add domain validation (#112141)

                  Problem

                    There is a rare occurrence where an L3 weight ends up being 0% which causes unwanted problems on the contract To address that it does not need to add domain-level validation to ensure that weights are always greater than 0% on a domain-level
                    However, with this change, an additional change needed to be made on the Templates with regard to the Hide Scores setting, which only flagged the first item as 100% and the rest as 0% since it did not matter at the time When the contract is created from the template and then submitted the weights are distributed

                    Solution

                      Add domain validation to ensure captured weights are greater than 0
                      Distribute weights on the template when hide scores are enabled

                       

                      Cannot Print Agreements (#121253)

                      Problem

                        When impersonating and clicking on View / Print an error is shown indicating the user does not have access to the contract, the impersonation is not getting sent through to the view/print pages.

                        Solution

                          Include the ImpersonateUserId on all the view / print links if available to allow the impersonator to view / print the contract. Fix the issue with auto weight distribution when hiding scores and allow perspectives off  Fix weights displaying on the template when hiding scores on  Fix add key competencies breaking when hiding scores on 

                           

                          Ratings (#120918)

                          Problem

                            For the next action and stage of the contract, the next action seems to display the correct translation.

                            Solution

                              Change the wording generically to:
                                Complete and submit the Manager Ratings

                                 

                                Data Warehouse

                                Claims Report (#120508)

                                  Corrected the update of ApprovalStatus 

                                   

                                   

                                   

                                   

                                   

                                  Back to top