Everything vendor-specific lives in one adapter. The margin arithmetic and the evidence logic never learn which system produced an event.
Every customer-visible change, newest first. Each entry is written in the same commit as the release it describes and reviewed in the same diff, so the log and the product cannot drift apart. The same entries appear inside Attergo on the What's New screen, from this one source.
A connection to a dispensing system can now be switched off and back on from Settings, and its credentials are kept while it is off. Use this when a store is closed for a refit, or when a vendor is doing maintenance and you would rather not see errors. Removing a connection still throws the credentials away and means re-entering everything, so switching off is the reversible one.
When a file will not import, the report now groups the problems by cause, tells you how many rows each one affects, and says what to change. An NDC that is not in your catalogue names the NDC and offers the two ways to fix it. Amounts that arrived in dollars where cents were expected say so rather than being rounded. Rows that are already correct are unaffected.
Something you can now do that you could not, or something that behaves differently than it did. If a pharmacy owner would act on it or notice it, it is here. Library upgrades and internal refactors are not.
There are no version numbers. Attergo is one hosted system on one deployment, so everybody is on the current release at the same moment and there is nothing to compare a version string against. You are on this one.
Signed in, the same entries wait for you on the What's New screen, so a release reaches the people using it without anybody forwarding a link.
Read-only credentials you can revoke. We come back with the fills that went out under cost, the services you could have billed, and the fills an auditor would ask about.