How can I share feedback for the Sandbox Deploy Automations closed beta?
How to give feedback?
This Community forum is the best place to share your feedback, so other customers can join in the conversation and add their own perspectives.
When you have feedback to give, have a look at the existing posts in this forum and see if you can benefit or contribute to the feedback that others are discussing. If no existing posts seem relevant, then feel free to create a new post.
Suggested guidelines for giving feedback
We value your feedback, no matter what it is. We encourage you to tell us what you like, dislike, and where you could see improvements. We'd like to see a healthy forum for discussion, but we can't do that without just a little bit of effort from everyone.
Here are a few pointers that will really help us understand your feedback and work with you to make the sandbox experience even better:
- When you see something you dislike or see something you'd like improved, write it down and think about it for a little while
- Try to be as clear as possible in your feedback; explain why you like/dislike something, and how it could be improved. If you can do screenshots easily, we'd love to see them
- Be patient when waiting for responses from Zendesk
- Don't use sarcasm, be rude to other customers or staff, and don't use strong language. We will moderate forum posts where we think reasonable
Ultimately, we want the feedback forums to be a place where any customer can come and give feedback.
Reporting bugs
As this feature is in beta, the best way to report a bug is to do so here in this forum, rather than raising a ticket. This is especially helpful if you're reporting a minor bug or a bug that is not directly impacting your customers. As this is a beta, the response times may be longer than they typically would be going through the normal support channels.
-
When deploying from the sandbox to production, the tool appears to use the naming descriptions for dependencies. Would it be possible to understand how the tool matches configurations, is it through naming descriptions?
I only ask, as we deploy from sandboxes to production on a regular basis and sometimes the naming conventions may not always be the same. They may be updated in production at a later date.
The deployment tool within the admin center, when a dependency issue is found, and you have the option to create the dependency in production, it would also be helpful to be able to match to an existing one, maybe by using the name or ID.
-
Hi Kerry, thanks so much for a the feedback.Yes that's correct, when dependencies need to be matched we look for the same type of entity with the same name (e.g. a Ticket Field of type
dateand the nameRenewal Date). It's a case-sensitive match.Re how this relates to names changing over time, there are a few different possible scenarios:When the Sandbox is first created we copy across Triggers, Automations, and dependencies and we establish a link between the equivalent entities (a mapping of their IDs). For these entities, we no longer need to do a name check because a definitive link already exists.
- From then onwards, changing the name in either environment won't break that mapping. However, please note that if the name of a Trigger or Automation is updated in Production but not the Sandbox, when you make a deployment the old Sandbox name will overwrite the new Production one (i.e. it's not currently possible to maintain different naming of equivalent Triggers and Automations through Deployments)
- For new Triggers and Automations that are created in the Sandbox and then deployed to Production (creating a new Trigger or Automation in Production), the deployment process creates the ID mapping, and that same behaviour will apply from then on.
- For new Triggers and Automations that are created in the Sandbox and then manually created in Production, we do not currently attempt to match them up by name. A subsequent deployment of that business rule from the Sandbox will create a duplicate in Production.
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
2 Kommentare