3 Replies Latest reply on Jun 10, 2014 6:55 AM by CSTeam

    Test to Live - any solutions for processes that are not ready?

    Apprentice

      We are new to the LDSD and are just getting prepared to move Change Management to production.  We are still developing many of the other processes and don't want to pend the availability of the Change Management component as they have a very manual process now.  Since LDSD does not currently have a way to filter what is pushed from test to live, does anyone else have recommendations for "hiding" processes that we want to wait to push until it meets our strategic timeline?  We have talked about not publishing or creating shortcuts so to accomplish this.  We have also talked about the possibility of adding an extra step to each process that would auto close and send a notification to a staff person if we didn't want them to actively be entering tickets until we were ready. 

        • 1. Re: Test to Live - any solutions for processes that are not ready?
          Expert

          Not publishing the short cuts is probably the easiest.  Another option is permissions.  You can separate permissions for Change, Request, Incident, etc.  For us every analyst uses Incident and then they need to be in another group to do Change.  Then you have exact control over what your people can do.  The easiest thing is just don't publish the incident short cut bar, only admins will have access.  Publish to specific users to allow others to use and test as you want.  Then when your ready to open up to everyone publish to groups.

          1 of 1 people found this helpful
          • 2. Re: Test to Live - any solutions for processes that are not ready?
            Specialist

            One solution that we are looking to implement for similar issue of developing new items is to add a 3rd server to the mix. So we will have a dev server that syncs with test and the test sync to production. That way we can fix and update in test and save our dev stuff from going to production during he syncs form test

            1 of 1 people found this helpful
            • 3. Re: Test to Live - any solutions for processes that are not ready?
              Apprentice

              Thanks for responding so quickly to the question.  After a bit of additional research, we determined that the quickest and most effective solution for us was going to be removing all of the shortcuts (links, gadgets, tabs w/flyouts, service catalog items) before we pushed Change Management to production.  Following implementation of Change Management, then we will rebuild all of those items we removed for Incident and Request management.  We determined we should only have to do this once if we were more diligent about what was added based on our implementation timeline.  Thanks again for your recommendations.