Changelog #51

Release Notes

Planned Maintenance

Database Upgrade

We will be performing scheduled maintenance to upgrade our database on the weekend of 10/11/25. This upgrade improves performance and reliability across database transactions, and in the next changelog, we will communicate the impact of this change. This is one of the many more performance improvements coming to ION this fall.

• GovCloud & Public Environments: Saturday 10/11/25 at 11:59 PM PT
• EU & AUS Environments: Saturday 10/11/25 at 8:00 AM PT

During these windows, you may experience up to a few minutes of partial downtime or slower response times while the upgrade completes.

This upgrade is strictly infrastructural: there are no breaking changes to our API or to the data pipelines. All external connections and workflows will continue to function as expected once the maintenance is complete.

We expect the impact to be minimal and appreciate your patience as we continue to bring you a more performant platform.

Planned Rollouts and API Changes

BOM Demand and Reorder Points in Autoplan

We are making some important changes to Autoplan behavior over the next few business days. Currently, ION will override BOM demand with your reorder point driven demand even if BOM quantities are higher than your maximum reorder point.

ION will now treat the BOM demand as the source of truth, but will ensure the maximum reorder point is satisfied when generating planning results if supply is less than the minimum reorder quantity.

This approach allows Autoplan to take the MAX of BOM demand and the maximum reorder point to prevent part shortages due to assuming one is more accurate than the other.

Planned Rollout: Role-Based Procedure Approval

Procedures have been upgraded to a standard role-based approvals, allowing you to set the roles required to approve a procedure. You will now be able to set the minimum required approvals per role for procedures. For more information, click here.

These changes will begin going live starting Oct 13, 2025 on a rolling basis. When going live, you will notice that all new procedures created will use the role based approval but existing procedures will not use the role based procedures.

Planned Rollout: Canceled Step Changes

As communicated in the previous changelog, ION will automatically remove canceled steps from the dependency graph to prevent canceled steps from blocking downstream work. Successors will be rerouted to depend on the canceled step’s predecessors. For more information, click here.

These changes will begin going live starting Oct 13, 2025 on a rolling basis.

Other Notable Wins

Run ID on part inventory labels
The first Run ID can now be added to part inventory labels to improve traceability during audits and handoffs. Each inventory item, whether original or split, is linked back to its very first run, to make it easier to track runs and streamline scanning workflows. For more information click here.

Improved stability for parts inventory management
Deleting outdated custom attributes won’t wipe your history. Instead, “deleting” works like archiving: attributes disappear from the UI but stay preserved in your records. All past data remains available through analytics and data connections, helping teams grow without losing traceability or cluttering the interface. Learn more about attributes here!

Procurement cost override via GraphQL Allows procurement partners to set a PO line cost that supersedes inherited part cost, enabling precise pricing and fewer corrections in integrations.

We’re looking forward to the next batch of updates in two weeks!
Best,
First Resonance Product Team

Changelog 51 Notes

🎥 The New ION Experience:

Comes from Notion doc and manual

• Reference 49 and 50 for how this has been done in the past.

🚀 Upcoming API Changes

Comes from Engineering, need to ask #engineering

• Cancelled Steps
• Role Based Procedure Approval
• Min / Max Changes

📦 Other Notable Changes

Comes from #Product-Changelogs

• FOR-108: Improved stability of parts inventory by eliminating timeouts when removing custom attributes, ensuring consistent system performance.

• This functionality cleans up your ION environment without losing traceability of prior data. As manufacturers scale their processes do too. And with growth comes learnings and needs for new data. Old data is still valuable but you do not need it to clog up current day builds. As such the functionality allows you to archive attributes so they do not show up within ION but all historical data is still available through analytics and data connections.

• Value: streamline your UI, maintain traceability.

• FOR-475: Added a property on part inventories available for barcode templates that automatically links a run ID. The run ID is set to the earliest related run by creation date, or for split inventories, the earliest origin run.

• earliestRunId The earliestRunId property is available when generating barcode labels for part inventories. This property provides a direct reference to the first run associated with that inventory, ensuring consistent traceability from the point of origin.

• Primary Runs: If the inventory has one or more runs directly linked to it, earliestRunId is set to the run created first (based on creation date).

  • Split Inventories: If the inventory has been split one or more times, earliestRunId will reference the first run from the original inventory, again based on creation date. This design ensures that every inventory item, whether original or split, can always be traced back to the earliest run that established its lineage.

• Value: Improved run / part inventory traceability and tracking. Visibility of your production tied to physical inventory.