|
Repository Browser Overview
The 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 cases
In order to quickly get used with Repository Browser, let's list basic repository use cases:
General View
Repository Browser General View consists of the two parts:
Repository Tree and Project Element View
The 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 states
Project can be in one of the following states, which is shown by a corresponding icon in the Repository Tree:
Checked out
- Project is copied into local user workspace, can be modified by user and checked in later.
Opened
- Project is copied into local user workspace, is visible to WebStudio, but can not be modified by user.
Closed
- Project exists only in DTR.
-
Deleted
- Project is marked for deletion.
Local
- Project exists only in local user workspace.
Opened, locked
- Project is opened and can not be checked out because it is checked out by another user.
Closed, locked
- Project is closed and can not be checked out because it is checked out by another user.
Project elements
-
Folder
-
File
Project 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):
Deployment
Prepared 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:
- Create new deployment project.
Description: creates new empty deployment project with the given name. 
- Deploy project.
Description: copies projects from deployment set into production time repository.
- Open version.
Description: opens specific version of a deployment project.
- Close project.
Description: removes project from local user workspace. All changes made to project are lost.
- Check out project.
Description: copies deployment project from DTR into local user workspace for modification.
- Check in project.
Description: copies deployment project from local user workspace into DTR.
- Copy project.
Description: creates a copy of a project in DTR.
- Delete project.
Description: deletes project.
- Add/remove descriptors.
Description: adds and removes projects to/from deployment set.
After checking in deployment project, deploy button is get enabled and clicking it deploys project into production time repository.
|