How can I share feedback for the Sandbox Deploy Automations closed beta?

4 Kommentare

  • Liv

    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.

    0
  • David Hall
    Zendesk Product Manager
    0
  • Joey

    I'm trying to deploy a few automations but get the error This configuration has dependencies that aren’t supported, so it can’t be deployed.” with no indication what dependency is causing the error. There is also no link to the automation in production to quickly check.

    The fields exist in both so my assumption here is that the dynamic content is missing (can't search DC, so.), could this cause the error?

    The dependencies are definitely a headache creator, after changing three automations in sandbox I now have to go into production and change these three again.

    0
  • David Hall
    Zendesk Product Manager

    Hi Joey, thanks for the feedback.  You are probably on the right track about dynamic content being a blocker, as DC is not currently supported in deployments.  I see you've signed up for a face-to-face session with us, looking forward to digging into this in more detail with you.

    0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.

Powered by Zendesk