Keep the Notification Queue in the pilot database paused
Customizing and testing the new workflow in the pilot environment may trigger sending garbage notifications to real email addresses. In order to prevent unnecessary notifications, we recommend that you keep the Notification Queue in your pilot database paused. While the queue is paused, email messages accumulate in the queue (where you can safely review them) and remain there until you resume queue processing or force-send individual messages.
When you are ready to switch your pilot database to production, delete all notifications from the queue and resume sending notifications. We recommend doing this before starting Alloy Automation Server 2022 on your flipped production database (for details, see Delete test notifications and resume the Notification Queue).
IMPORTANT: If you keep the existing workflow
If you chose to keep the existing workflow, in addition to imported items and components the migration procedure creates new workflow items and components for the new functionality introduced in version 2022. You should review the resulting workflow and customize it as needed.
In this case we highly recommend leveraging our Professional Services team who are experts in workflow design and implementation and committed to delivering quality and perfection. You can contact Alloy Professional Services team at email@example.com.