# Version 9.1.238.3 (Support Release - 2 July 2026)

#### Imports

##### PaySpace cell number formatting and position effective date (#150845 & #146760)

**Problem**

- When employee details are pushed to PaySpace, two issues were causing records to be rejected:
- Cell phone numbers were sent in a format PaySpace/SARS would not accept. South African mobile numbers captured without their leading "0", and numbers belonging to other countries PaySpace supports, were not converted into the layout PaySpace expects, so the push failed.
- Newly created employee positions were rejected with "Effective date required" because the position was sent to PaySpace without an effective date. A related rejection, "Effective date cannot be before the employee's group join date", could also occur when the date used was earlier than the date the employee joined the group.

**Solution**

- Cell phone numbers are now tidied up automatically using a standard phone-number library that knows the rules for each country. South African numbers get their leading "0", and numbers from other countries are sent in the international "00 + country code" format PaySpace expects. Numbers that cannot be understood are still passed through cleanly rather than blocking the employee
- When a position is created for an employee, it is now always given a valid effective date, so PaySpace accepts the record. The date used is the current date, which always sits on or after the employee's group join date, so neither rejection occurs.

---

#### **Performance Management**

##### Wrapping SyncFusionPopover in td tag (#152177)

**Problem**

- Manager comments and employee comments are in the same column when their text exceeds the max length and SyncFusion styles are applied

**Solution**

- Wrap the SyncFusion Popover element in a td element to prevent a div tab from being added to the table body

---

#### **Job Management**

##### Optimising job profile query (#152112)

**Problem**

- Query runs too long on live, and this causes timeouts

**Solution**

- Optimising the query to reduce execution time to ensure that it does not time out

---

#### **Dashboards**

##### Adding known as profile name logic (#151968)

**Problem**

- On the Main Dashboard's My Colleagues widget, the "known as" name is not displaying as it does on People Management

**Solution**

- Add known-as display logic to the My Colleagues dashboard widget, same as previously done on People Management

---