Please find details below of the items included in this update

Service Geeni is introducing Single Sign-On (SSO) authentication to streamline access for users within client organizations. This feature allows back office and admin users to seamlessly log in to the Service Geeni platform using their organization’s SSO credentials like Microsoft, Google etc., eliminating the need to maintain separate login credentials.

Following customer feedback “TCC’s” are being renamed as “Forms”. We have updated the terminology throughout the application to replace “TCC” with “Form”, where applicable. This system wide change in terminology will reduce confusion and more accurately align with user expectations.

To further enhance the web portal users ability to document work, we now support a wide range of file types as attachments, including .pdf, .xlsx, .doc, and more. This improvement allows for richer, more detailed documentation, offering greater flexibility and efficiency. Users can now include various formats to better capture the scope and specifics, ultimately leading to improved record-keeping and communication. Image files can now be previewed directly within the web portal, while other file types display a default thumbnail indicating the file type, along with a download icon.

We have updated the Job Sheet and Job Invoice documents that the user can edit from Settings → communication Centre to include the Activitytype field from the bookings dataset. This enhancement ensures that the activity type selected by the user is accurately displayed for each labour and travel booking.

An issue where when the user tried to raise a new job and the “Add to Existing Job” popup was incorrectly displaying jobs from other sites when raising a new job with only a site task added. Now, the popup correctly filters and shows jobs from the added site only, ensuring accurate job selection and improved user experience.

When adding a kit to a job, the delivery note incorrectly listed all individual items within the kit instead of the kit itself. This issue has been resolved, ensuring that the delivery note now correctly displays the kit as a single item line.

Scheduling a job to two engineers via the diary screen incorrectly displayed both engineers as having the job issued even if the job was issued to one of them. Despite both engineers showing the “Un-issue” job option, only one engineer had the job issued in the system. Now, when a job is scheduled to multiple engineers and the user clicks “Issue job” from one engineer’s diary slot, a popup will appear with options to issue the job to the selected engineer or all engineers. If the user selects the first option, the status of both the job and engineers will be checked before any status colour changes, ensuring accurate job assignment and display.

Users found that locking a job in the diary only locks the first task item, leaving the other tasks unlocked. This issue occurs when a repair job with multiple tasks is added to the diary. Locking the main job item (non-task specific) should lock all associated tasks, but currently, only the first task is affected. We have updated the locking mechanism to ensure that when a job group (with all tasks) is locked in the diary, all associated tasks are locked as well. This ensures consistent and complete locking of multi-task jobs, improving task management and workflow efficiency.

Users of the subcontractor portal reported that the subcontractor PO line created for labour roundoff was not calculated correctly, resulting in incorrect pricing for several jobs. This issue affected both chargeable and non-chargeable hours, leading to discrepancies in job pricing We have fixed the calculation logic for subcontractor PO lines to ensure accurate roundoff for both chargeable and non-chargeable hours.

Users experienced an issue where opening the “Add Quotation” page from both the quotation screen and the JobDetails screen resulted in multiple tabs being opened for adding quotations. This caused the JobDetails quote page to overwrite the session details for the quotation, leading to a null reference error when returning to the quotation screen and performing any operations.We have implemented tab locking for the popups to prevent multiple tabs from being opened when adding quotations. This ensures that when a new quote is added from the JobDetails page, the session details remain intact, and users no longer encounter null reference errors.

The Date due back field on Contracts was not very clear. This confusion arose because there was no tooltip explaining that the DateDueBack field determines the period during which the equipment is active and invoiced. Once the DateDueBack is reached, invoicing stops even if the contract remains active. We have added a tooltip to the DateDueBack field on the contract page. This tooltip clearly explains that the equipment will only be invoiced until the DateDueBack date, helping customers understand the invoicing period and preventing future confusion.

Users encountered an SQL error when manually typing a date into a Records → Contracts → Edit date on service sequence. This issue arises particularly when entering dates before approximately 1972, causing the system to fail. We have implemented validation to check the date duration. If a user enters a year before 1972, a message will now appear to inform them of the invalid date. Additionally, the validation will only trigger once the full date is edited and the user moves the mouse away from the field, ensuring a smoother user experience.

When attempting to add a Form (previously TCC) to a task in the “Service Call -> Raise Job” section, users encountered a JavaScript error that prevented the process from progressing. This issue has now been resolved, allowing users to successfully add forms without any errors.

Users encountered two issues when clicking the document icon in the Customer Portal:

Users experienced an issue in Stock → Purchase Invoice posting → Process purchase invoice where the loading symbol would not disappear when selecting a Purchase Order (PO) during purchase invoice posting. This was caused by a JavaScript error leading to a disrupted workflow. Now, the page loads when a PO is selected, ensuring a smooth and uninterrupted purchase invoice posting process.

Users reported that selecting the “All” option for invoicing caused the system to hang, displaying a spinning geeni for several minutes before stopping without any message. While individual invoices processed correctly, attempting to process all invoices at once led to this issue, disrupting the invoicing workflow. We have optimized the invoicing process to handle bulk selections more efficiently.

Users encountered query errors when accessing the reports in the SSR Standard Dashboard in Business Intelligence → Self Service. This issue has been resolved, ensuring that the reports now generate correctly without any errors.

Users encountered an issue in Equipment → Forms enquiry → Edit Form where setting the notification values for the “Further Work Required” internal note resulted in a pop-up error indicating unpopulated fields, despite the fields being correctly filled. This prevented email notifications from being sent to selected users, disrupting their workflow. We have identified and fixed the validation logic that incorrectly flagged the fields as unpopulated. Now, users can set the notification values and send email notifications without encountering any errors.