Enjoy Greater Flexibility and Increase Your Productivity With More BEO Options

Streamline your workflow with new Change Log capabilities

Take control of your change management in a whole new way. 

iVvy now offers granular control over BEOs, allowing you to trigger the Change Log on an individual session. This is particularly helpful for larger bookings that have some sessions finalised, and others still pending. 

New features:

  • Removal of the 'Finalise BEO' button: The ‘Finalise BEO’ button is no longer on the booking documents tab.
  • Change log trigger logic based on document status: Know when your documents are up-to-date. Our Change Log trigger logic now uses document status, allowing you to control when the Change Log is enabled. Now you can track changes in each session or booking with ease.
  • Auto-assign BEO: Our Change Log now automatically knows which BEO(s) a change is associated with, so users no longer need to manually select each one. When any activity affects multiple document entities, the log will include all relevant entries.
  • Update to Change Log API: Make changes faster and easier with our newly updated Change Log API endpoint. Now you can quickly access an array of BEO IDs associated with the change request.

Take your booking management to a new level with enhanced Change Log functionalities:

Firstly, we've removed the "Finalise BEO" button, which previously triggered the Change Log. Instead, the new Change Log will be enabled based on the document status. This means you can have a booking in a partially finalised state, with some sessions finalised and some not, and still have the ability to log changes as needed.

To enable the Change Log for a booking, simply set an all-day booking BEO to finalised, or select all BEOs and change the document status to finalised. If a session BEO is finalised and a change is made within that session, or if a booking BEO is finalised and a change is made within a session contained within the booking, the Change Log dialogue will automatically appear.

We've also made changes to the way changes are logged against BEOs in the Change Log popup, removing the need for the user to select a BEO.  Now, if a session belongs to multiple BEOs, the change will be logged against all associated BEOs, and in the Change Log itself, all associated BEO numbers will be displayed.

Finally, we've updated the Changelog API to allow for multiple BEOs to be associated with a single change log item.

We believe these changes will greatly improve your experience using the Change Log in iVvy, giving you more control and flexibility when logging changes. 

If you have any questions or feedback, please don't hesitate to get in touch with our support team.