It's not always clearly distinct from the UI itself whether you're working in the sandbox Admin Center or production. It appears that the main way to check is by looking at the subdomain in your browser. For heavy sandbox users, this makes it easy to make mistakes in production because you thought you were in sandbox. This would alleviate an entire layer of disorientation from going back and forth when prepping for deployment.
It would be a massive protection to our work and users and environments to have a visual cue from the page itself other than always beginning each action on each page by checking the subdomain. While there could be an explicit callout on pages, it would be effective if there was just a subtle watermark to the sandbox page wallpaper. This would really announce itself as the environment that you're working in .
Example of need for differentiation
Similar to how existing emails in production are modified to be firstname.lastname@example.org , differentiation of assets like exports would also provide better management.
We recently needed to perform a massive field cleanup of fields created 2 years ago at launch that didn't or no longer follow patterns or naming conventions. There were a significant number of duplicative fields and forms and conditions that need to be revised, tested, and updated.
To track this, we exported the field list to excel, updated the fields in admin center, and tracked the new names in the excel file. These changes were in sandbox to prepare for testing. After finishing the edits, we exported the field list again to confirm the edits.
After opening the export we saw that none of the Field IDs matched any of the other ones, none of the edits seemed live and all of the unpatterned fields had the same names. After about 5 seconds we realized we'd exported the fields from production - wheeeewww.
To assist with tracking changes and preventing overlap and conflicts of effort, it would be helpful if file names had some append to identify the instance - ie 'ticket-fields.sandbox.xlsx' for sandbox rather than 'ticket-fields.xlsx' for production.
Por favor, entrar para comentar.