There are two scenarios where a PB publishing alert box would help prevent inadvertent changes from being published to the end user experience:
A JSON feed delivered from PB to trigger mobile push notifications: we want all users (either editorial, developers or QA) who has access to such page is aware of the impact to the user experience when they publish any change. A pop-up box to challenge the publishing action like "This will be sending the alert to all mobile users - are you sure" would help non-Editorial users be clearly aware if they are making any undesirable change to production
The same pop-up will also help digital editors publishing changes upon "Use Shared" first in their local workspace. In the scenario where a user is going to publish local change without "Use Shared", an alert message suggesting by doing that he/she will drop the other's edit would be generally helpful for teamwork and reduce verbal communication.
Guest
| Categories | Editor, User Workflow |
| I need it... | Quarter |
Hi Katherine,
Thank you for your reply, and please let me elaborate more on the first bullet:
We had utilized PageBuilder for publishing app notifications to the mobile app users. To do so we created a PB page has a special "Feature block" which will output JSON of the breaking headlines upon page publishing, subsequently our notification service picks it up and get it dispatched to mobile devices real-time. While this set up works for the purpose, we have experienced a production incident once that a testing message was inadvertently sent by our engineers to real app users.
Hence we think about the idea of a pop-up alert that would help prevent this from happening. The idea is to allow the PB user configure a special "publishing alert message" at Feature/Chain block level, and once they exist they be displayed in a pop-up box when any PB user hit the publish button.
In the aforementioned scenario, when our engineers try to publish a test message on production PB, right upon they hit the publish button, they would see a pop up message says "This will be sending the alert to all mobile users - are you sure" and then we would have a chance to cancel the publishing action.
I hope this clarifies.
Hi Joe, Thanks for posting this idea. For the first bullet point, is the thinking that if a custom field is updated that would impact the styling/display for end users who are viewing a page on a mobile device, it will inform the PB user that the update isn't mobile friendly via a custom message the organization can set? It would be helpful to learn more about the specific use case and workflow.
For the second item, if a user publishes their draft (Publish Draft action found under My Draft located under Draft Options in Publish Workspace), there is a modal for users to confirm the action and informs them that changes will not be applied to the Shared Draft (screen recording: https://share.getcloudapp.com/L1uWzq7v). We do see that a confirmation modal does not appear when a user clicks Share & Publish for the Merged Draft and will consider implementing a similar modal workflow for a consistent experience.