Managing Add-ins

 1 Replies
 1 Subscribed to this topic
 68 Subscribed to this forum
Sort:
Author
Messages
Buckeye Bruce
New Member Send Private Message
Posts: 1
New Member

Our HR area originally had 6 super users running add-ins to S3 Human Resources but a year later later we are now at over 60 super users. There have been some data integrity issues stemming from poorly designed, un-tested add-ins being applied directly to production. We have been asked to identify best practices for managing, testing, documenting, and communicating "Changes" that are being made via the add-ins. Does someone have a best practices model, document or policy or procedures they could share?

Bob Canham
Veteran Member Send Private Message
Posts: 217
Veteran Member
We locked down uploads to our IT analyst team and 1 super user if they're very trusted to do specific tasks. When our IT team does uploads, we log it with our normal change management practice. Our policy allows for pre-approved changes where we document the reason, communication, and process for performing a task and then we just need to log when it happens. This way we have a tracking list of everything that is being loaded. Whenever we do the uploads, part of the process is to validate it in test virst.