Migration Announcements
Commonly, businesses with NetSuite will want to inform their fellow workers of any new changes occurring on any crucial systems used daily. For one particular client I worked with, no official process was in place to broadcast anticipated system changes or enhancements to NetSuite business users. All existing methods were via email communications which lacked structure and were difficult to manage when searching through mailboxes for historic migration emails. This solution aimed to audit all system changes and migrations occurring across multiple NetSuite environments in NetSuite directly, whilst also enabling the automation of email announcements to the appropriate business users.
Details
- Pre-migration, post-migration, roll-back, emergency and cancellation announcements were addressed in this solution.
- Tickets & files related to the migration announcement were also audited on the system. The tickets could be of either data, script or configuration.
- All announcements were uniquely identifiable, as well as the tickets themselves.
- All business users who received the announcement would be audited.
- Pre-migration, post-migration, roll-back, emergency and cancellation announcements were addressed in this solution.
- Tickets & files related to the migration announcement were also audited on the system. The tickets could be of either data, script or configuration.
- All announcements were uniquely identifiable, as well as the tickets themselves.
- All business users who received the announcement would be audited.
Steps to use this Functionality
- Users would navigate to a custom Suitelet from the main menu. This would take them to the migration scheduling page.
- From here, users would need to specify the TYPE of announcement they want to broadcast, then add the related tickets of this announcement to the item table on the Suitelet.
- Next, users would need to also specify the user roles relevant to the announcement. This would automatically run a saved search of all employees linked to the selected roles. These employees are the workers who will be emailed with the announcement.
- Lastly, to schedule the announcement, the user would hit the SUBMIT button. Now, the next action could work in two different ways: 1) If the announcement was being sent to under 50 users in the business, the Suitelet can process the whole action because it would have sufficient governance units to do so. 2) Beyond this, the script would alternatively send the request to a separate scheduled script, which can handle a far bigger load than a Suitelet.
