This idea has been merged into another idea. To comment or vote on this idea, please visit PB-I-293 getting the log data of pagebuilder history.
Hi All,
I hope this message finds you well :-)
I'd like to put in a request to have all changes from API calls to UI updates tracked and made available in some type of log and/or notification that can be ingested by an external webhook.
Ultimately, we have very little visibility into what/who/why something changed and it makes triage, debugging, root cause analysis and other investigatory tasks either difficult or impossible.
What are the chances that we could have this introduced into ARC XP in the coming months?
Thanks in advance for considering this request.
Jack
Jack Foster
| Categories | Developer Tools, Developer Workflow, Editor, Feature Configuration, Other, Page Versions |
| I need it... | Yesterday (let's go already) |
Hi Jack,
This breaks into two areas with different answers.
For Composer, you can get this today via Arc XP IFX (Integration Framework). IFX sends real-time webhook events for virtually every content operation: story saves, publishes, updates, deletes, author changes, image and gallery operations, and more. The payloads include timestamps and source information, so the "who changed what and when" question is answerable. Check out the IFX documentation.
For PageBuilder, there's no equivalent today, and it makes sense to have same audit trail that you can pull from Arc XP. PageBuilder operates at a layout and configuration layer, not a content operations layer. We understand the triage pain, but nothing is planned for this in the near term. We currently have this idea submitted overlaps with what you asked on PageBuilder side, can you vote on this idea: https://arcxp.aha.io/ideas/ideas/PB-I-293