Select a title in the table below to jump straight to that item further down this page.
We've fixed an issue where the “Schedule” button stopped working for existing KPI records after a recent update.
A recent update introduced a new type of KPI (measure-based KPIs) and, in the process, accidentally broke scheduling for existing KPIs — only the new KPI type could be scheduled afterwards. We've restored the original schedule button for existing KPIs and added a separate, dedicated button for the newer measure-based KPIs.
Nothing. Use the “Schedule” button as normal on existing KPIs, and the new dedicated button for measure-based KPIs.
We've fixed an issue where publishing an F20 notice could show a long list of confusing, repeated warning messages about lot numbers — even when there was no real problem.
When a lot was awarded to multiple suppliers, the system was checking lot numbers once per supplier instead of once per lot, and repeating the warning message every time — with the message text itself duplicated. This produced a wall of near-identical warnings. The check now runs once per lot, after all suppliers have been processed, so warnings only appear when there's a genuine duplicate.
Nothing. Publish F20 notices as normal — warnings will now only appear when there's an actual issue to review.
We've fixed an issue preventing UK6 notices from publishing when linked to a prior notice marked “Below threshold – unknown” and given a more specific below-threshold category.
This is a valid, expected combination — a “below threshold – unknown” prior notice is meant to be followed by a more specific below-threshold category on the linked notice. The system was incorrectly requiring an exact match between the two, which isn't how this rule is meant to work.
Nothing. If you were previously working around this by matching the procedure type exactly, you no longer need to.
We've fixed a display issue in the Supplier Portal where KPI due dates and statuses were shown in the wrong fields.
The Due Date field was showing the KPI's status, and the Status field was showing the due date — which could confuse suppliers reviewing their KPIs. Both fields now display the correct information.
Nothing. Existing and new KPI records will now display correctly in the Supplier Portal.
We've fixed an issue where UK7 notices could be wrongly blocked by an R509 error after a user removed the additional procurement category option.
Unchecking “Additional Category Below Threshold?” is meant to mean the additional category section is ignored entirely. Previously, the system kept reading the old category value in the background and would still flag it as matching the main category, blocking the notice from publishing even though the option had been switched off.
Nothing. Uncheck the additional category option as needed and publish as normal — the error will no longer appear.
We've fixed an issue where lots carried over from a linked UK3 or UK4 notice into a UK12 notice could be duplicated every time the notice was processed.
Lots weren't being reliably recognised as already copied across, so each processing pass added them again, building up duplicates. Lots are now matched correctly against the prior notice, so each one is copied across exactly once.
Nothing. If you were previously using a manual workaround to prevent duplicate lots, you no longer need to.
We've fixed an issue where the date range shown on Contract Saving records could display the wrong month or year. Saving records now show the correct start and end period every time.
Previously, the Period field on a Contract Saving record could show a date range that didn't match the actual dates entered. For example, a saving covering exactly 12 months could show an end date a year later than it should.
Nothing. This fix applies automatically. Existing Contract Saving records will now display the correct period the next time they are viewed.
We've fixed an issue where the automatically calculated “Estimated Annual Value” on contracts was incorrect for contracts running less than 12 months.
The calculation was applying a scaling formula intended only for contracts of 12 months or more, which inflated the value for shorter contracts. Contracts under 12 months now correctly show the Estimated Annual Value as equal to the Current Value.
Nothing. This applies automatically to contract records going forward.
We've fixed a permissions error that stopped users — including admins — from creating a new pipeline or programme from a template.
A newly added field wasn't included in the right permission sets, so the system blocked access to it even for users who should have full access. Access has been corrected so the field no longer gets in the way.
Nothing. Creating a pipeline or programme from a template should now work for all users with permission to do so.
We've fixed an error that could stop the feedback link inside the “Send Bidding Letters” pop-up from opening correctly.
The link relied on a fixed internal reference that didn't always match how the underlying page is labelled in every customer's account, causing a “page does not exist” error for some customers. The link now resolves correctly regardless of account setup.
Nothing. The feedback link will now open as expected.
We've increased the size of the “Send Bidding Letters” pop-up window.
The window was previously fixed at a small size, making the content feel cramped and requiring extra scrolling to use. It has been resized for a more comfortable, readable layout.
Nothing. You'll simply see a larger, easier-to-use window next time you use this feature.
We've rebuilt the internal code that runs whenever a supplier record is created or updated, using modern engineering standards.
This is a behind-the-scenes improvement: it reduces the risk of future defects and makes the system easier to maintain. It does not change how supplier records look or behave today.
Nothing. There is no visible change for users.
We've fixed a technical fault that could occasionally stop documents from uploading successfully to Contracts Finder.
The connection between our platform and Contracts Finder was using an incorrect method to authenticate, which could cause document uploads to silently fail. This has been corrected so uploads complete reliably.
Nothing. Document uploads to Contracts Finder should now complete reliably.
We've removed unintended object-level “Create” access to Action records that had been included in the “Atamis Fields (No Object Access)” permission set.
This permission set is meant to grant field-level access only, without giving users the ability to create records. Leaving Create access on Action records was a gap between what the permission set was meant to do and what it actually allowed.
Nothing. If your organisation assigns this permission set, users will no longer have Create access to Action records through it.
We've fixed a technical fault that could occasionally stop documents from sending for signature or completing successfully via DocuSign.
The connection between our platform and DocuSign was using an incorrect method to authenticate, which could cause a sign request or status update to fail intermittently.
Nothing. DocuSign sign requests and status updates should now complete reliably.
We've fixed an issue where procurement team members granted access to Contract Documents were not being given access to the associated Contract Document Folder.
A change made earlier this year altered the format of an internal reference used to match team members to their contract document folders, so the matching silently found no folders to share — team members with the correct permission could be missing folder access without any error being shown.
Nothing. Folder access will now be granted correctly going forward. If a team member should have contract document folder access but doesn't yet see it, updating their access level on the project will re-apply it.
We've fixed a security vulnerability, identified during a penetration test of the Supplier Portal, where content submitted through the messaging function was not fully sanitised before being displayed.
Without this fix, a message containing malicious script content could potentially run in another user's browser when viewed. This has been resolved to keep the messaging function safe to use.
Nothing. This protection applies automatically.
We've updated the validation rules on procurement contract records so they also check a configuration setting that automated, overnight processes use to bypass rules meant for manual data entry.
Validation rules — such as checking that a contract's end date isn't before its start date — are appropriate when a user is entering data by hand, but were also being applied to background system updates, which could cause automated processing to fail.
Nothing. This applies automatically to background processing going forward.
We've fixed an issue on the Supplier Portal where, once a supplier had entered a valid CDP share code, the “Edit Responses” button still allowed them to manually type over responses that had been automatically populated from the Central Digital Platform (CDP).
Auto-populated CDP responses are meant to reflect data pulled directly from the Central Digital Platform, so allowing suppliers to overwrite them manually undermined the reliability of that data for buyers relying on it. We've also fixed a related issue where entering an invalid share code was saved silently, without telling the supplier it was invalid.
Nothing. Suppliers can still complete and edit any requirements that aren't auto-populated as normal — only responses sourced from the CDP are now locked.
We've fixed an issue where, if a supplier's Central Digital Platform (CDP) record included a Legal Form of “Other” with details longer than 255 characters, the CDP responses failed to pull through into the supplier portal and generated a system error.
The character limit on that field wasn't being handled gracefully, so a long “Other” description could silently prevent an entire CDP share code submission from importing correctly, with no clear signal to the supplier or buyer about what had gone wrong.
Nothing. CDP share codes with a long Legal Form “Other” description will now import correctly.
We've updated the wording on the public contract search page so that it consistently refers to “Contracts” rather than “Opportunities” — including the page heading, search labels, and column titles.
The previous “Opportunities” wording was generic placeholder text left over from an earlier build, and didn't match how buyers and suppliers actually refer to public contract notices — which could read as confusing or off-brand to anyone browsing or searching the page.
Nothing. The updated wording applies automatically to the public search page.
Atamis R&D
Updated