Previewing Library Management settings in a Staging environment | Community
Skip to main content
U
u00n7z
June 19, 2017
Solved

Previewing Library Management settings in a Staging environment

  • June 19, 2017
  • 2 replies
  • 824 views

I've recently inherited DTM from a previous employee and had a question about Library Management settings.  We currently use a Custom setting that points to an externally hosted version of the old s code file.  We'd like to move to App Measurement, but were told that this change would reflect in production immediately.  Is there a way to make this change in lower environments only?  Can this change be queued up for approval like any other changes (direct call rules, etc..)?

thanks in advance!

Jon

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by jantzen_b

    Hi Jon,

    I'm not sure who told you the change would be immediately reflected in production. No changes are sent from the UI into production without approval and publishing workflows. The only way this might be true would be if your production site had the staging library deployed instead of the production DTM library.

    Also, I believe you can even have multiple hosting options turned on at the same time. Any change in the UI would immediately be pushed to all staging libraries regardless of which embed code option you choose. Only approved and published changes would be added to the production libraries.

    Thanks,

    Jantzen

    2 replies

    jantzen_b
    Adobe Employee
    jantzen_bAdobe EmployeeAccepted solution
    Adobe Employee
    June 19, 2017

    Hi Jon,

    I'm not sure who told you the change would be immediately reflected in production. No changes are sent from the UI into production without approval and publishing workflows. The only way this might be true would be if your production site had the staging library deployed instead of the production DTM library.

    Also, I believe you can even have multiple hosting options turned on at the same time. Any change in the UI would immediately be pushed to all staging libraries regardless of which embed code option you choose. Only approved and published changes would be added to the production libraries.

    Thanks,

    Jantzen

    U
    u00n7zAuthor
    June 19, 2017

    Thanks much!

    I felt that was the case, but I wanted to make sure before saving any changes.  It didn't make sense to me that a change as substantial as that would be live immediately, but I didn't want to find out the hard way as I'm kind of feeling my way through this tool.

    Jon

      Terms & ConditionsAccessibility statement

      Loading footer...