What changed? Image fields in workflows now have an option to capture photos in-app, with latitude and longitude automatically watermarked on the image.
Why it matters: Proves where an inspection, task, or issue was recorded, which cuts down on disputed or fake field evidence and strengthens audit trails.
What changed? Sent POs can now be edited through a Revise PO option. Each revision goes back through approval, can be repeated until the PO is confirmed, and keeps a full revision history.
Why it matters: Before, any change in items or amount after sending meant cancelling and recreating the PO. Now changes are handled in place, stay controlled through approval, and remain fully traceable.
What changed? TPM modules have a new dedicated Approval Preference tab for approval settings.
Why it matters: Approval configuration is now in one predictable place per module, so admins can set it up and change it without hunting through other screens.
What changed? The Excel download now includes a Failure Code column, and the module gains Create, Import, and Import History options.
Why it matters: Failure types can be set up in bulk instead of one by one, import issues are traceable, and each failure type stays mapped to the correct parent Issue Type, which keeps failure data clean for reporting.
What changed? The Email Builder now supports a CC field with multiple recipients.
Why it matters: Stakeholders such as supervisors or managers get Schedule Maintenance email updates without being the primary recipient, so no one is left uninformed.
What changed? A first reminder is sent when a Work Order is created, then repeats at the configured interval until the Work Order is completed.
Why it matters: Open work orders keep getting follow-ups automatically, which reduces overdue and forgotten tasks and the need for manual chasing.
What changed? The Asset List has two new columns showing the last completed PM and the next planned PM for each asset.
Why it matters: PM status is visible at a glance per asset, so teams can spot overdue or upcoming maintenance without opening schedules or reports.
What changed? The ServiceNow integration now supports updating Work Requests through a PUT API, and data for Work Requests and Work Orders flows between ServiceNow and Cryotos.
Why it matters: Changes made on either side stay in sync without manual re-entry, and the Work Request-to-Work Order process runs smoothly across both systems, with fewer mismatches and delays.