Activity Log / Audit Trail / Booking History report
C
Cam Szarapka
It's important that changes users make in Event Temple are tracked & can be reported on. The current Activity List report is too limited. I'd like to see things such as who changed booking details and when. Also who updated Contact or Account information.
Event Temple
Merged in a post:
Action log in bookings
I
Ida Hanssen
We would like for Event Temple to have action log for changes made in bookings.
Unfortunately, now we do not have access to see which users have implemented changes for booking dates, added new products/menu items etc.
This could help us understand what users need more training, or should only have "ready only" access.
Event Temple
Merged in a post:
History of Changes on Bookings
C
Cam Szarapka
We have many users and its important to know when and who made a change to our bookings, events and documents. We need some way of being able to see the history of changes.
Katie Knight
Merged in a post:
Missing Action Log
C
Conference QH Borås
I would be so happy if there were anyway to see who has made changes and what changes were made. Like the action log i mews. Where you can go back and backtrack what's happened. It would sometimes be easier to go to the source if something is wrong or if you have questions about the change made.
M
Miriam Cordero
Dear Event Temple Development Team,
I hope this message finds you well. I would like to discuss an important suggestion to enhance your software. During my experience with Event Temple, I have noticed a lack of specific functionality related to the activity history. I believe it is crucial to have a detailed breakdown of activities within the program, especially in situations where multiple vendors and events are marked as "lost" despite having signed contracts and deposits.
Having a comprehensive activity history would allow for more efficient tracking of past transactions and events. This would provide a clear view of each vendor's responsibilities and help prevent confusion or loss of contracts and deposits. Additionally, it would facilitate the identification of problems or misunderstandings and enable timely corrective measures.
Therefore, I strongly recommend incorporating this feature in future updates of the Event Temple software. I firmly believe it would be a significant improvement for users and help ensure the integrity of activity records.
I appreciate your attention to this suggestion and your dedication to software improvement. I am available to provide any additional information you may need.
Best regards,
Miriam Cordero
Hotel el Guajataca
N
Nimesh Bhudia
This would really help us too, great suggestion.
B
Ben Ostro
This has 108 bumps - is this something that will ever be done? It's really important to be able to reference document changes...especially in organizations with multiple users
R
Rachel Heller
Merged in a post:
Pipeline Stage History for a Booking
E
Emily Jolly
When we move couples from one stage of the pipeline to the other it would be great if we could have a historical trail. We will like to be able to track if someone goes from new lead to tour arranged cancels the tour and goes back to stage two. It will also be helpful to report on these changes so we can check for trends.
R
Rachel Heller
Merged in a post:
Warning when changing Stage
S
Scott Chester
We seem to have issues with bookings getting moved between stages in the pipeline when they shouldn't. Without an audit log, we don't know who is doing it or when this is occurring, but there are some that we know for certain were in other stages. I don't know if it happens when they are dragged on the main page, or if someone is accidentally clicking on a stage on the booking page. Maybe we only need a warning if going backwards, but while I love how easy it is to change the stage, it is too easy and happening when we don't want it.
S
Scott Chester
I agree on the need for an audit trail.
In the event of moving backwards, adding a note would be helpful to explain why it moved backwards. Maybe any change in pipeline should be presented with a pop-up to add notes and confirm the change.
S
Scott Chester
Ideally each and every field change would have a corresponding audit log entry. Who changed the stage? Who added that payment? When did the xyz items get added? Who discounted that item? When did that field get changed?
These are all questions that can't be answered today.
Load More
→