All locations in a Deltanji environment should fall into one of the following categories: working location, library-view location, virtual location, generic location and NEW location. Each location type serves its own particular purpose, which affects how users interact with those locations.
Working Locations and Library-View Locations
These two location types are the most common, and can be described in contrast to each other.
A working location can be identified by its yellow folder icon: . When an object exists at this kind of location, the user is able to access its components, execute them, and perhaps modify them too. Essentially, this kind of location is designed to let the user do something to the objects. More specifically, this kind of location maps at least some of its objects' components to a physical storage space that isn't the library.
In contrast, a library-view location only maps its objects' components to the library. As such, this kind of location is designed to let the user know something about the objects it contains. They can be identified by their blue folder icon: .
For example, three locations have been grouped into a location list called 'SAMPLES':
- 'SAMPLES.Head' is a library-view location showing the user a list of the latest version of all objects that comprise the SAMPLES codebase.
- 'SAMPLES' is a working location because it maps onto a physical storage space that this developer can access. It is set up so that the user can check objects out to it, at which point they can modify and execute them.
- 'SAMPLES.Library' is a multi-version library-view location (notice the multiple tabs on its folder icon) in which the user can browse all checked-in versions of the SAMPLES codebase, including old ones.
Note: It is important to understand that an object version can exist at multiple locations. Just because an object version is at a library-view location does not mean that it cannot be executed, because it may also exist at a working location.
A virtual location does not map to any physical storage spaces. They can be identified by their white folder icon: .
When an object version is transferred to it, no components will physically be transferred. However, the statuses of the object version will be updated in accordance with the transfer route. This kind of location cannot be used as the source location for another transfer if that route needs to handle the actual components.
A virtual location is suitable for transfers which indicate the next step in the development cycle, without the need for components to be retrievable from the location. An example is a transfer from a 'ready for testing' step to 'approved'.
While virtual locations share some characteristics with library-view locations, it is recommended that library-view locations are used unless there is a strong reason for using virtual locations instead. When objects are in a library-view location, their components' contents can be viewed and compared. Users cannot view the contents of an object's components at a virtual location because the components do not map to any physical storage space.
Generic locations are built-in entities which can be used to simplify the setting up of transfer routes, particularly when a route is likely to be copied or replicated. They are pre-defined during the installation of Deltanji and should not be modified or deleted. There are three generic locations that can be used:
- %ANY - a generic location which functions as a wildcard for all existing locations. It can be used in the 'from location' and the 'to location' field of a transfer route.
- %FROM - a generic location which represents the 'from location' of a transfer route. It can be used in the dependent locations, new active locations and message fields of a transfer route.
- %TO - a generic location which represents the 'to location' of the transfer route. It can be used in the dependent locations, new active locations, new master location and message fields of a transfer route.
%FROM and %TO can be used in the definition of any transfer route, simplifying reuse after a route is copied. They are particularly useful when %ANY is used in either the 'from location' or the 'to location' field.
They only appear in the Locations folder under Setup, where they use the same white folder icon as virtual locations do: .