Objects created in AutoMate BPA Server, such as workflows, tasks, conditions and agents are automatically stored in a repository for re-use. This provides a centralized location in which to conveniently store newly created objects as well as access pre-existing ones. Storing objects in the repository does away with the tediousness of re-building tasks or re-creating conditions each time a new workflow is created. With this concept, a single task can be utilized in many workflows.

Repository objects can easily be administered, modified and quickly incorporated into new or existing workflows with just a few mouse clicks. If changes are made to an existing object that is currently used by several workflows, they are applied globally to all the workflows in which the object resides. For example, a Schedule event is used to trigger execution of 15 different workflows at exactly 1:00 am on a daily basis. If the schedule needs to be altered to 2:00 am for all 15 workflows, the change could simply be made to a single Schedule event and all workflows that use it will reflect the change. However, if the schedule needs to be altered for only 10 out of the 15 workflows, you can simply create a copy of the original Schedule event, give it a unique name, make appropriate changes and link the new event to the appropriate workflows, keeping the rest intact.

Each time an individual workflow object is created, it is stored in the repository and can be accessed via the SMC's Repository section under their respected folders. For example, all created tasks can be accessed via Repository-> Tasks.  Each time a new workflow is created, it too is stored in the repository and can be accessed from the SMC via the Workflows section. This allows for the addition of embedded workflows. Keep in mind that any new objects added to a newly created workflow will be saved to the repository as well. The repository can also be accessed from the Workflow Designer (WFD). For more details, see Designing Workflows. The ability to store objects in a central location enables them to be easily managed, conveniently accessed and effortlessly re-used in future workflows. For more details, see Repository Management.

NOTE: Non-licensed events and conditions will appear opaque when viewing them in the repository. Selecting an unlicensed object will generate an error.


Related Topics