Repository Browser OverviewThe Repository Browser allows users to view and edit projects stored in design time repository (DTR). Before a project can be viewed or edited, it must be opened or checked out. Open and check out operations create a copy of a project in local user workspace. When finished with editing, project must be checked in to store changes in DTR. Local user workspace and design time repository (DTR) are two main project storages, which will be in the center of our attention. Use casesIn order to quickly get used with Repository Browser, let's list basic repository use cases:
General ViewRepository Browser General View consists of the two parts: Repository Tree and Project Element View ![]() Repository TreeThe Repository Tree provides tree-like view that allows users to browse projects and project elements. Each time you click a tree node only buttons corresponding to available operation are enabled. Project statesProject can be in one of the following states, which is shown by a corresponding icon in the Repository Tree:
Project elements
Project Element ViewProject Element View allows users to execute commands against project and its elements and view information about currently selected element. Element information may contain from 2 to 4 tabs (Properties, Versions, Elements, Dependencies):
DeploymentPrepared projects can be deployed into production time repository. It is a special project storage that makes projects available to external systems, such as Rule Service. Generally user creates a new deployment project, checks it out, adds rules projects to it by creating descriptors, checks in the new deployment project and finally deploys it to production time repository. Basic deployment use cases are the following:
|