31 October to 6 November 2026
This week we made promoting a process to Production far clearer, fixed shared-process runs that were refused or ran the wrong version, introduced owner alerts when a bot's work doesn't match what was asked, added a full FICA customer due-diligence desk, and built a Policy register for governance teams.
Promoting a process to Production is now a straight ladder, not a guessing game
If you have ever pressed Promote and then wondered why Production still looked out of date, or why the orange dot never went away, this one is for you.
The promote screen used to list versions in a way that made it easy to send the same old version again, leaving Production quietly behind. We have rebuilt it from the ground up.
What is on screen is now always your working copy, the starting point. Above it, each environment shows exactly which version it is running and how far behind your screen it is. A single line under the ladder tells you what Production is still missing, for example "sub-process IQ Excel Macro changed", with a direct link to promote.
When you do promote, there is no more "What goes" step to puzzle over. You choose where you want it to run, and the form shows plainly what will happen to each environment. Promoting straight to Production now also updates Testing and Staging to the same version in one go, so nothing is left behind.
Smaller teams often have one person who both builds and approves. The new layout makes it obvious at a glance whether Production is current, and what is still waiting for an approver.
#Automize #ProcessAutomation #Operations #Workflow
Shared processes now run the right version and accept uploaded files from any company
Two frustrating failures hit teams that share a process across companies, and we fixed both this week.
The first: when a process belongs to one company and runs on another company's machine, "Run again" was refused with a message saying the process had never been promoted, even though it had been promoted four times. The problem was that the promotion check looked in the wrong place, under the machine's company instead of the process owner's. The process now runs the version the owner actually promoted, every time.
The second: if someone at a partner company started a run from the Launchpad and uploaded a file, pressing "Run again" later told them the file was not available, even though it was sitting there untouched. The check was looking for the file under the wrong company. It now looks under the company that started the original run.
Both fixes also cover the case where a designer at one company tests a shared process with their own uploaded file. That test used to fail on the first try. It no longer does.
#Automize #ProcessAutomation #DigitalWorkers #Operations
Process owners are told when a bot's completed steps don't match what was expected
A bot can finish a run, show a green tick, and still have done something slightly different from what was asked. Until now, that difference sat quietly on the run's page where nobody looked.
After each step, the bot reads back what it actually did and compares it with what the process asked for. If anything differs or failed that check, the process owner, anyone the process is shared with, and the company's admins now receive a notification.
The alert is sent at most once a day per process, so a busy process does not fill anyone's inbox. Test and debug runs are left alone. The message gives counts only, not field values, because those can contain client information and the notification also goes out by email, chat and webhook.
Email notifications follow each person's existing process notification setting, which is off by default, so you will only receive them if you have switched that on.
This matters because a difference that looks harmless, such as a number formatted differently by an application, can sometimes signal a real problem. Owners now hear about it the same day instead of finding it weeks later in an audit.
#Automize #ProcessAutomation #Automation #Operations
The FICA and Onboarding Clerk runs customer due diligence from upload link to sign-off
Gathering FICA documents from a new customer is slow, repetitive work. Emails go unanswered, wrong documents arrive, and someone has to chase every party by hand.
The FICA and Onboarding Clerk now handles the whole process. A firm hires the clerk, opens a customer record on the new FICA desk, and the customer receives a secure upload link. On that page they see exactly which documents are required for someone in their situation, with the accepted formats listed for each one. Every document they upload is virus-scanned, read by AI, and checked on the spot. A wrong format or an out-of-date proof of address is refused immediately, with a plain explanation.
The clerk identifies directors, trustees and beneficial owners holding 25 percent or more, and sends each of them their own upload request. Every party is screened against sanctions and politically exposed person lists through OpenSanctions. If a document is unclear, it goes to a person to review. The clerk chases every 48 hours with a fresh link, and a complete file goes to a nominated person for sign-off, never the person who opened the case.
Release notes and setup instructions are in the platform's documentation.
#Automize #FICA #Compliance #DigitalWorkers
A Policy register lets governance teams write, approve, distribute and track acknowledgements
Keeping track of which staff have read and acknowledged the current version of a policy is one of those tasks that falls through the cracks. Spreadsheets go stale, email threads get lost, and an audit question about who read version 2.1 is hard to answer.
We have built a Policy register, sitting alongside the existing Controls and Risks registers. A company can draft a policy, attach a PDF or Word document, and send it for approval. Someone other than the author must approve it before it goes out. Version numbers follow a simple rule: a material change moves to the next whole number, a wording change moves to the next minor number.
Once a version is in force, it can be sent to everyone or to one team, with a set number of days to acknowledge. Each person receives a task in their My Tasks list. Every acknowledgement is tied to the exact file that was uploaded, using a hash, so you can prove in an audit which document each person read and when.
A published policy is archived rather than deleted, so acknowledgement records are never lost when a policy is superseded.
This feature is off on every plan at the moment. Nothing changes for any customer until we switch it on.
#Automize #Governance #Compliance #RiskManagement