Workflow and ServiceDesk Community

 View Only
  • 1.  Workflow Repositories

    Posted Oct 20, 2011 10:05 AM

    I'm after information and best practises on how to use the Workflow Repositories in Workflow 7.1. I'm setting up Dev, UAT and Production workflow servers and want to know how/if I should be using the workflow repository to move developed workflows from dev to UAT to production.

    What sort of folder structure is recommended? Any other hints or tips?



  • 2.  RE: Workflow Repositories

    Posted Oct 20, 2011 11:26 AM

    I have no real guidelines to offer as far as repo structure... however, one thing I would do is not hardcode anything environment-specific (like database connection strings) into the components of your flow. I'd use either a project property that can be changed on deploy, or an application profile value stored in PM.



  • 3.  RE: Workflow Repositories

    Posted Oct 24, 2011 11:46 AM

    One tip that I have is not to put your integration components into the repository this doesnt work too well. But definitely stick with application properties etc for the Workflow, makes it easier to do any blanket changes in case you swap anything over.



  • 4.  RE: Workflow Repositories

    Posted Oct 27, 2011 02:29 PM

    If you have multiple SMP servers keep the repository on the production server and make your other servers unmanaged so you can deploy directly to them. When you're ready to promote something to production commit it to the repo with notes then deploy.

    If you use integration projects it's a little more tricky. You need to add the integration project to the repository and then add the reference to the project from the repository (when you add a reference you'll see Repository on left). This will ensure that during deployment the integration library is also published.

    As far a folder structure, I guess that can be anything that makes sense for your projects.