Simple Standard Workflow

When the Add Namespaces wizard is run in an environment without a templating variable named namespace already defined, you are given the opportunity to create the following workflow items:

  • A variable called namespace, to which the 'Add Namespaces' wizard will add a value for each namespace you choose to manage using this workflow.
  • A multi-version location called Library, mapping all components to L-format storage in Deltanji's home namespace. This will become your code repository.
  • A template system {namespace}, resulting in a dedicated system code for each managed namespace. This system code will typically also be used as the variant portion when naming the objects that will manage code in the namespace, e.g. Cinema.Film.CLS/SAMPLES.0
  • A template single-version location {namespace} controlling M-format storage in each namespace that you define as a value of the namespace variable, and managing BIN- and T-type components in the CSP directory associated with the namespace.
  • A template single-version location called {namespace}.Head which gives each namespace a latest-version view of its objects in the code repository.
  • A template multi-version location called {namespace}.Library which gives each namespace an all-versions view of its objects in the code repository.
  • A template location list {namespace} that groups and sequences the above three locations.
  • Templated transfer routes generating a simple workflow for each namespace:
    • REGISTER from {namespace} to {namespace}.
    • IN from {namespace} to {namespace}.Head.
    • OUT from {namespace}.Head to {namespace}.
    • OUT2 from {namespace}.Head to null, a retrospective checkout for use when code has already been changed in {namespace} without first being checked out.
    • GET from {namespace}.Library to {namespace}, allowing earlier versions to be retrieved.
  • A multi-version location called Temp, mapping all components to FX-format storage in a temporary file directory of the Deltanji host.
  • An EXPORT route from %ANY to Temp, enabling ad-hoc exports of code into XML files.
  • A null location for use by the OUT2 routes.
If any of the elements listed above already exist in your environment then setup of the simple workflow cannot proceed.