Skip to main content

Version 9.1.148.2 (Support Release - 3 March 2025)

Imports 

Error on Employee Automated import (#128700)

Problem

    When the end date received from Payspace is equal to the start date, as is the case with enrolments, the record is rejected. When the termination reason is not available in the case of the above case the record is rejected. When an appointment is updated in Payspace the user receives a new position id which causes a new position to be created in Signify for each appointment update.

     

    Solution

      Remove the end date >= start date pre-import validation Remove the termination required when the end date is provided pre-import validation Change the position code to a concatenation of the organisation title and the employee id. This creates a position with a name per employee rather than per appointment change. This means that positions will not be reused should the employee transfer to a new position in Payspace .

       

      Performance Management

      Evaluation Summary not available after Final Approval (#129000)

      Problem

        When users view their contract and employee evaluation is on and has a due date, regardless of the phase, the button cannot be seen.

         

        Solution

          Add the button to the check for the user approved to always display in the rating phase
          Add the button to the default fallback also

           

          Unable to include the Value Survey score (#128772)

          Problem

            Saving a contract survey gave SQL Dapper an error because new columns were added to the query object used on an unrelated query causing it to break here.
             

            Solution

              Made the query model used by the Survey creation distinct from the other usages.

               

              People Management

              User error (#128950)

              Problem

                When multiple processes materialised in the same people group at the same time the people group calculation fails due to duplicate insert
                The performance management consumer for the reporting line consumes other reporting line types than LM and PM resulting in unnecessary errors

                 

                Solution

                  When inserting confirm that the entry is not part of the people group
                  Filter the reporting line types used in the consumer and do not process the other types

                   

                  Error after appointing a new person (#128545)

                  Problem

                    When appointing a new user the people groups are not busted in time of the profile page load due to eventual consistency

                     

                    Solution

                      Move the busting to the job profiler service to bust the materialised cached in the service first and then all the rest of the services.

                       

                      Termination reasons (#128535)

                      Problem

                        Inactive termination reasons are shown in the dropdown

                         

                        Solution

                          Only show active termination reasons. You still cannot delete a termination reason if it has been used, regardless of whether it is active or not.

                           

                          Back to top