We are running Remedy under a new department now and the rules are changing. Previously when we finished testing something in development we would just move the workflow over (via Panacea) after hours. Now they want us to document our changes and have production control do it.
How do you folks handle moving workflow into production. And wow - the message window I'm typing this into is tiny.

LOL! I'll look into the forum configuration to see why that window is so tiny...

Secondly, documenting it is simply a matter of listing all forms and workflow objects, as well as relevant data changes. Moving it can be manual (Admin tool, exporting/importing .def files), automated (Migrator, Panacea, etc.), and, obviously, by recreating (tweaking the objects on the target system rather than moving them into place). It's all really a matter of what is best for you and your organization. Migrator, and I believe Panacea, too, offer the backup option where it allows you to retrieve the previous objects in case you need to roll your change back. Pretty nice when you need to document a backout plan.

Good luck!

Thanks Matt, for your reply. It wasn't really what I was asking, though. What I'm wondering is if anyone else has rules where they are not allowed to touch the production boxes. What this change amounts to is that only production control may make workflow changes. To me this is a nightmare, as if we miss a minor modification change and ProdCon puts the change through at night we could potentially have Remedy go down for a significant amount of time, whereas if I make the change myself and forget something I'll whack myself in the head for forgetting, fix the problem, and that's the end of it.