63 posts tagged with "Features"

Features​

Comment System Threaded comments on bookings, projects, quotes and invoices. Interact with your colleagues and be notified on updates.

Features​

Publishing bookings With a new permission and a new default setting, bookings can now be worked on in a "draft" state and only published when ready. This allows for a more controlled workflow, especially in larger teams where multiple staff members may be involved in the booking process. Only published bookings trigger notifications.

Enhancements​

• Webhooks: Added absence webhooks
• REST API: Added endpoints for client updates, client addresses and client contacts

Bugfixes​

• Permissions: We now ensure that any booking permission (e.g. status update) also comes with a view permission, as it's otherwise useless

Features​

orgAI log Added a new team-wide log for tracking orgAI use and token consumption across the team.

Enhancements​

• Team menu: Added direct links to changelog and orgAI log
• orgAI: Quick conversation switcher added

Bugfixes​

• Groups: The list of groups would fail to load in some places

Features​

Mass Duplication Bookings can now be mass-duplicated to multiple days (which some call "extended copy") while being created or afterwards. Skipped days are also taken into account while mass-duplicating.

Year Planner A new, read-only 12-month planner view is now available, allowing a broader facility overview.

Enhancements​

• Staff: Export is now more comprehensive

Bugfixes​

• Planner: In the vertical day planner, moving bookings between resources while keeping the time would not save the change
• Bookings: Collisions for non-available hours are now correctly prevented when "skip non-working days" is enabled
• SAML / SSO: Critical A user could force login to a foreign team. Note: This issue was found via a self-conducted penetration test and has been fixed. Our records show that it was never exploited.
• Departments: Duplicating a department with children would give the children the parent name
• Staff: "End employment" could fail in some circumstances
• Notifications: In some edge cases, booking & task notifications were not sent
• Bookings: Deleting one booking of a group that carried Goods&Services would delete the Goods&Services from the other bookings in the group
• Invoices: Creating multiple equally split invoices could lead to all being classified as the final invoice
• Cost tracking: A one-day booking on resources with weekly/monthly/yearly cost would not incur any costs
• Utilisation Analytics: Fixed an issue where the sum of days was incorrectly calculated on hourly bookings
• Absences: Cancellation requests for absences would not delete the absence correctly upon approval