Premium sandbox trigger categoriesRespondida
We use the categories feature for triggers pretty heavily. They are massively helpful looking at segments of different lines of business. In addition to other categories, the categories doing the biggest lifting are assignment, communications, and then line-specific triggers.
We also rely on the sandbox to test changes before deploying to live. Although the triggers get refreshed when you spin up a new sandbox, they don't carry over the respective categories and they all get lumped into one.
It would be very helpful to improve the parity between instances by carrying over the categories when creating a new sandbox - not only for ease of use, but also so that any admin can avoid triggers that might be mistaken for similar ones that would otherwise be under a different category in live.
Thanks for the feedback mfg. Just to confirm, when you spin up an instance none of the categories show up in the sandbox? If that is the case I can see that being a pain when trying to test things out before deployment. I have been working a little with the triggers modernization project this year so I will pass this information onto the product manager. We don't currently have anything on the roadmap for the sandbox side of triggers but I will categorize this and get it in front of the right people.
To confirm, we have 13 categories in Production, and only 1 in Sandbox. If there's some setting I'm missing please let me know, but this happens with any Sandbox we've created so far.
Wow that would be very frustrating. Thank you for sharing. I will copy the product manager on this to see if it is a setting, a bug, or just lacking functionality.
Por favor, entrar para comentar.