** We have AR System, alone, with a lot of custom forms.  Trying to create higher-level workflows that tie these forms together (such as an employee boarding process)  is proving to be a daunting task.  Do we need Atrium Orchestrator to achieve this in a supportable manner?  This post seems to suggest a resounding "YES".
AO is really intended to automate and accelerate the execution of broader IT services that are typically performed through a series of actions across these purpose-built applications.
If so, can we acquire *just* this AO component or do we need the other pieces like Atrium CMDB, etc.

What are the alternatives to doing orchestration, in general?  That is, how would you go about defining these higher-level services that encompass multiple forms within an AR System?  My first guess is you could just make a web page describing the higher-level process with a bunch of links to each individual form, and let a human be the orchestrator.  In other words, not bother?  :-)  Another way (which I've tried) is to make a "wrapper" form that defines the process and attempts to orchestrate the child-forms through a complex series of filters and extra fields on both the wrapper form the and child forms.  Not very understandable or flexible.  Now I am looking at Orchestrator which seems to be a monster of a product but sounds like it is the correct one, but is it overkill?

Thanks for any suggestions!

Brien
_Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_

Reply via email to