Product Updates

Update 3.2.135: Attendance Export Order Details and AWR Exclusions

Release 3.2.135 brings order details to attendance exports, AWR client exclusions, hashed API keys, and key scheduling fixes.

Subscribe

Subscribe

Release date: September 23, 2026


New Features

Order Details in the Attendance Export

The attendance export now includes an Order tab gathering order details (order number and name, order manager, order ID, purchase order number, specification, status, start and creation date) plus the attendance's final invoice: invoice number, issue, due and paid dates, payment status, amounts with and without VAT, and pro forma invoice and credit note numbers. Attendance rows can now be matched against orders and invoices without a second export.

AWR Applicability per Client

Clients that AWR rules do not apply to can now be kept out of the AWR tracker. A new "AWR applicable" switch on the company profile, on by default, lets an admin turn it off, and the tracker leaves switched-off clients out of its listing; a "Show clients not applicable for AWR" filter checkbox brings them back when needed. Clients grouped under an umbrella company are always listed. Nothing is recalculated, so a client switched back on shows its full history right away.

Range Selection in Shift Closing

Staff members can now be selected by range in the shift closing form by holding the SHIFT key while selecting.

Shift selection in the Closing form

Default Pricing System on New Jobs

The job form can now start on the legacy pricelist category instead of the new ratelists. A new agency setting under Work defaults, "Use new ratelists by default when creating a job," decides which one is preselected, and the client order form follows the same setting. A job added into an order that is already priced offers only the pricing system that order uses.

Public API

Stronger Protection for API Keys

Public API keys are now stored more securely. Existing keys keep working unchanged, and the API key lists show the last four characters of each key so you can tell them apart.

Documented Embeds for List Endpoints

The Public API documentation now states which models each list endpoint can embed via with, and the Attendance and Contract response schemas list the StaffClockIn and Worker embeds.

More Reliable Filtering on Contract Types

GET /api/v1/contractTypes keeps the same response, filters, sorting and pagination, with stricter filter handling shared across list endpoints: a value that does not fit the field, an unknown operator, in mixed with another operator, or like on a date field now answer a 400 with a clear message instead of a server error; like on a numeric field works, an empty value on a field that cannot hold one answers a 400 instead of an unfiltered or empty list, and only documented fields sort. The ContractType schema marks its nullable fields and drops the unused with parameter.

Improvements

Requirements Hidden for Staff Already Signed Up

The shift detail in the staff portal no longer evaluates and lists the requirements of a shift the staff member is already signed up for, so a red requirement warning no longer appears next to the green confirmation of a sign-up an admin already made. The same applies to a connected position the staff member has joined, while positions they can still join keep their requirement check. Opening your own shift is also faster, since the checks are no longer run.

Bug Fixes

  • Inactive tags no longer pre-fill: Deactivating a tag now also removes it from the company defaults it was set on, so it no longer appears pre-filled as a bare number in the tags field of new shifts, or gets saved on newly published shifts. The company select in the tag form is cleared and locked while the tag is inactive.
  • Grouped sign-up no longer fails on an over-assigned position: Signing up as an applicant for a group of connected positions no longer fails with "position is full" when one of the positions already has more confirmed staff than its size. Only the applicant pool limits an applicant sign-up, so an admin's earlier assignment no longer blocks a later applicant.
  • Advance payments locked once an order is invoiced: Advance payments can no longer be added to, changed on or deleted from a pro forma invoice once the order has its final invoice, and such a pro forma cannot be deleted either. To correct an advance, delete the final invoice first.
  • Multi-edit transport End respects the actual trip start: In the shift closing form, the multiple-edit "End" of a transport in Duration mode now adds the typed hours to each staff member's own transport start (or the planned trip start when that is later), instead of always to the planned trip start.
  • Order-change email shows full details: The order-change email a client receives after an order is cancelled or restored again shows each position's profession, location and staff count with the previous values struck through, instead of a dash and a blank location.

As always, we welcome your feedback on these updates. Should you have any questions or run into anything unexpected, our support team is ready to help.

Similar posts

Subscribe to our Blog

Get workforce advice and OnSinch updates delivered straight to your inbox

Subscribe