A new release of our low-code platform Spiro has recently gone live. In version 2.23, we’ve significantly expanded the Action log functionality, bringing greater transparency and control over data changes. What this means and how it can benefit your business – more details in the article.
The more users work within the system, the more important it becomes to control changes. This is particularly relevant for companies that deal with large amounts of data on a daily basis, as any error can impact business processes or the customer experience.
Therefore, in release 2.23, we updated the action logging system, which allows tracking the change history applied to all objects in Spiro.
The logs store all changes made: the action and initiator, the object class, the date and time, as well as the previous and new values. For the logs within the entity view, we created a separate tab with a list of changes, filters, and an easy-to-use search function. Now, Spiro users can find information even for data that has been changed or deleted.
The action logging functionality covers all types of objects in the system: users, products, interactions, documents, pages, content, campaigns, configurations, and many others. In Spiro, all data changes are recorded, whether they are made manually by system operators or through the API – now you can track the full history, regardless of the source of the changes.
Action logs function as a critical tool for any ERP, CRM, PRM, or other systems with a large number of users and complex data structures. They serve several key functions:
System activity monitoring: the change history includes information on the time of action and the initiator. Chronological recording of each interaction with data allows for tracking the full lifecycle of an object in the system.
Audit and security: action logging helps identify errors or unauthorized actions, establish their source, and respond quickly to incidents.
Support for external integrations: logging changes that come through the API allows for full control over processes, even when part of the actions is performed by third-party services.
Let’s look at several examples of action logging functionality in different contexts:
Inventory management and tracking material movements between warehouses:
In case of material loss or incorrect write-off, the system allows tracking the chain of events and identifying at which stage the data discrepancy occurred, whether the action was a mistake, who performed the operation, and when.
Audit of the loan approval process by financial institutions:
With the action logging feature, the system records every stage of the loan process: from request processing to approval or denial. This ensures transparent oversight of compliance with standards and allows for quick identification of deviations from established procedures.
Tracking changes in order processing:
Recording changes in order status and details enables tracking all actions, such as adding or replacing items, updating address or contact information, adjusting quantities, or processing returns.
Thus, the Spiro 2.23 release with its enhanced action logging feature strengthens control over changes within the system and helps quickly identify the cause of any discrepancies in the data.
Looking to explore more about the platform's features and capabilities? Simply fill out the form with your contact details, and our manager will get in touch with you to provide detailed information on deploying projects with Spiro.