Copyright: Repository Mgmt Online Help - V9.0.4.4  Copyright © 1995, 2004, Oracle Corporation  All Rights Reserved


Navigator - Return to Object Reference
   Return to Object Reference (Navigator Menu)

Related Topics

Returns to the repository object from which you located a referenced object.


Navigator - Expand All
   Expand All (Navigator Menu)

Related Topics

Expands the selected node or nodes on the Navigator, to show all the levels of branches below.

This option is available only when a selected node or nodes can be expanded. The [image] icon is displayed next to all nodes that can be expanded.

To expand only a single level below a selected node, click the [image] icon.


Navigator - Collapse All
   Collapse All (Navigator Menu)

Related Topics

Collapses the selected node or nodes and all the levels of nodes below them on the Navigator. The Navigator does not store any information about the levels to which nodes are expanded.

This option is available only when a selected node has been expanded. If a node can be collapsed, the [image] icon is displayed next to it.

To collapse a node or nodes so that they can be expanded back to the same level, click the [image] icon.


Navigator - Set Mark
   Set Mark (Navigator Menu)

Related Topics

Places a bookmark on the currently selected repository object. The Navigator can have only one bookmark at a time. At a later stage, if you want to return to the bookmark, you can use Navigator→Goto Mark.


Navigator - Go to Mark
   Go to Mark (Navigator Menu)

Related Topics

Automatically scrolls the Navigator to the location of the bookmark. This option is available only if a bookmark has been set using Navigator→Set Mark.


Navigator - Go to Object Definition
   Go to Object Definition (Navigator Menu)

Related Topics

Navigates to a repository object that is referenced by a selected repository object.

For example, if a table has a foreign key defined, you can use this option to navigate to the definition of the table containing the primary key referenced by the foreign key.


Window - New Window
New Window (Window Menu)

Creates a new diagram window containing the active diagram. You can use this new window to display a different part of the active diagram.


Window - Cascade
Cascade (Window Menu)

Arranges all your open windows so that they overlap and each window's title bar is visible.


Window - Tile Horizontally
Tile Horizontally (Window Menu)

Arranges all your open windows so that they fit horizontally in the main window. The title bar and a portion of the tool remain visible for each window. The windows are displayed at the largest possible size that will fit into the tool window without overlapping each other or the icons of minimized tool windows.


Window - Tile Vertically
Tile Vertically (Window Menu)

Arranges all your open windows so that they fit vertically in the main window. The title bar and a portion of the tool remain visible for each window.


Window - Arrange Icons
Arrange Icons (Window Menu)

Arranges your window icons so that they line up neatly and do not overlap.


Window - Window Name
1, 2, 3... Command (Window Menu)

Switches to the window and makes it active. A check mark is displayed next to the name of the active window.


Window - Arrange Windows
Arrange Windows (Window Menu)

Displays all open windows so that they do not overlap.


Help - Help Topics
Help Topics (Help Menu)

Related Topics

Displays a list of the main subject areas in the online documentation system.


Help - Show Keys
Show Keys (Help Menu)

Displays the shortcut keys for the current tool.


Help - How to use Help
How to Use Help (Help Menu)

Related Topics

Displays general information on how to use the Microsoft Windows help.


Help - About
About (Help Menu)

Displays copyright and version number information about this application. You might need to know the version number for product support purposes.


Help - Customer Support
Customer Support (Help Menu)

Displays an Oracle Support Problem Report (displayed in your default ASCII text editor) that you are requested to complete before contacting Oracle Support for assistance. The report asks for details about you, your environment setup and details about the problem, including any steps to reproduce the problem. By completing this form prior to contacting Oracle Support, you will aid the processing and response to your request.

A default text editor is set up for ASCII text based on the settings in the Windows Registry. You can specify an alternative editor by using Options→Text Editor Options.


Context-Sensitive Help button
   Context-Sensitive Help

Related Topics

Provides access to context-sensitive help information about the menu options, standard toolbar and drawing toolbar buttons.

Selecting this button, or pressing SHIFT+F1, and then selecting a menu option, standard toolbar button or palette button, displays help information for the chosen item.


Properties - Expand All
Expand All (Properties Menu)

Related Topics

Expands all groups of properties in the Property Palette. Related properties are arranged in named groups after the non-related properties. For example, the element type Table Definition has named groups such as Volumes, Storage, Documentation, Visual Basic/C++ and Audit.


Properties - Collapse All
Collapse All (Properties Menu)

Related Topics

Collapses all groups of properties in the Property Palette. Related properties are arranged in named groups after the non-related properties. For example, the element type Table Definition has named groups such as Volumes, Storage, Documentation, Visual Basic/C++ and Audit.


Properties - Pin Palette
      Pin Palette (Properties Menu)

Related Topics

Causes the properties displayed in the Property Palette to remain unchanged even if you select another repository object from the Navigator. This action is known as "pinning" the Palette.

The Palette is the "pinned" state when the Property Palette toolbar button is [image].


Properties - Object Set
   Object Set (Properties Menu)

Related Topics

Displays the editable properties of two or more selected repository objects as a set on the Property Palette. The selected objects need not be of the same type. By default, when multiple repository objects are selected from the Navigator, the objects automatically become members of the object set (i.e. this menu option is not available).

In this type of display, properties for which all selected objects have the same value defined have the actual value displayed. Properties for which all selected objects have a value but the values are different have the value displayed as ######. To display the properties of individual members of the object set, use Properties→Next Object and Properties→Previous Object.


Properties - Next Object
   Next Object (Properties Menu)

Related Topics

Displays the properties of the next repository object in a set of two or more selected objects. The selected objects need not be of the same type. You can use this option to quickly move forwards through the members of a set.


Properties - Previous Object
   Previous Object (Properties Menu)

Related Topics

Displays the properties of the previous object in a set of two or more selected repository objects. The selected objects need not be of the same type. You can use this option to quickly move backwards through the members of a set.


Properties - Locate Object Definition
Locate Object Definition (Properties Menu)

Related Topics

Navigates to a repository object that is referenced by a selected repository object. For example, if a table has a foreign key defined, you can use this option to navigate to the definition of the table containing the primary key referenced by the foreign key.


Property Details dialog box

Displays various internal details about a selected property and the element to which it relates. These details are mostly of interest to developers writing code against the repository Application Programming Interface (API).

Object Details

Short Name

The short name of the element, preceded by the short name of its supertype. The supertype codes are:

CEL - container element

NSHR - 'non-shareable' element

PAC - primary access controlled element

SAC - secondary access controlled element

SHR - 'shareable' element

Name

The full name of the element type.

Base Table

The name of the repository table in which elements of this type are defined.

Caution:	Developers should not write code to access these tables directly. Instead, they should use the corresponding API view. For example, workarea definitions are stored in the base table named I$SDD_WORKAREAS, but user-written code should access the corresponding API view named SDD_WORKAREAS.

Object ID

A 38-digit numeric code that uniquely identifies the element. This code is sometimes known as the IRID.

Object IVID

A 38-digit numeric code that uniquely identifies this version of the element, even if the element has not been brought under version control. If the element is not versionable (for example, a workarea) this value is 0.

Version Label

The version label of the element, if it is under version control. It is this label, rather than the IVID, that is displayed by the various repository tools, such as the Version History Viewer.

Properties Details

Base Table Column

In the repository base table for this element type, the name of the column that stores data for the selected property. See the cautionary note above regarding the use of API views rather than base tables.

View Column

The name of the column in the API view for this element type that stores data for the selected property.

Mandatory

Indicates whether this is a mandatory property (that is, it must always have a value).

Maximum Length
DataType

The combination of these two values indicates the maximum length of the value that this property can have. For example, a maximum length of 256 and a datatype of VARCHAR2 means that the property value can be up to 256 characters in length.

Range

The range of values that this property can take.

Internal Value

The value for this property as it is stored internally in the repository.

Display Value

The value for this property as it is displayed in the repository tools.

Domain Name

The name of the domain, if any, to which this property belongs.

Model

Displays the type definition from the repository model for this element type. This includes details of the element short name, view name, versioning structure, uniqueness criteria, deletion rules, summary of changes since the previous release, and properties (both displayed and non-displayed).

API

The CDAPI function specification for this element type, giving details of the standard PL/SQL procedures provided for the element type (e.g., insert, update, delete etc.).


Edit - Create Object
   Create Object (Edit Menu)

Related Topics

Creates a new repository definition of the same type as the currently displayed definition(s). If in default view, the Property Palette switches to spreadtable view. To be able to create a new object, you must have INSERT access for the workarea and container in which you are creating the object. Use the Repository Object Navigator to check your access permissions.


Edit - Delete Object
   Delete Object (Edit Menu)

Related Topics

Deletes the selected object definition from the workarea and places it in the wastebasket. To be able to delete an object, you must have DELETE access rights to the workarea and the container that owns the object. Use the Repository Object Navigator to check your access permissions.


Edit - Copy Properties
   Copy Properties (Edit Menu)

Related Topics

Copies all properties to the Properties Clipboard.

This option overwrites any previously copied properties on the Properties Clipboard.

You can paste the copied properties into other objects in the Navigator by choosing Edit→Paste Properties.

Note:	You can check the contents of the Properties Clipboard by choosing Edit→View Copied Properties.


Edit - Paste Properties
   Paste Properties (Edit Menu)

Related Topics

Inserts copied properties into a selected object.

You use this option when the Properties Clipboard contains a set of properties that were copied from a previous selection. You can paste the contents of the Properties Clipboard as many times as required.

Note:	You can check the contents of the Properties Clipboard by choosing Edit→View Copied Properties.


Edit - View Copied Properties
View Copied Properties (Edit Menu)

Related Topics

Displays the object properties, if any, that have been most recently copied to the Properties Clipboard. This is useful as a check when you are about to paste copied properties into an object.


Edit - Clear
Clear (Edit Menu)

Related Topics

Clears the details of a selected property. This menu option does not place the contents of the selection to the Properties Clipboard. Use Edit→Cut to remove the details of the selected property to the Properties Clipboard.


File - Save Uncommitted Data
   Save Uncommitted Data (File Menu)

Related Topics

Commits any outstanding changes made in the Property Palette to the repository.


File - Revert Uncommitted Data
   Revert Uncommitted Data (File Menu)

Related Topics

Cancels unsaved changes made to properties in the Property Palette.


View - Normal Size
Normal Size (View Menu)

Related Topics

Resets the magnification of the diagram in the active window to the magnification it was displayed when opened or created.


View - Zoom In
   Zoom In (View Menu)

Related Topics

Increases the magnification of the diagram in the active window. The new view of the diagram is centered around the same position as the view on which the magnification is based.


View - Zoom Out
   Zoom Out (View Menu)

Related Topics

Decreases the magnification of the diagram in the active window. The new view of the diagram is centered around the same position as the view on which the reduced magnification is based.


View - Fit to Area
   Fit to Area (View Menu)

Related Topics

Increases the magnification of a selected area of the diagram so that it fits the active window.


View - Fit to Selection
   Fit to Selection (View Menu)

Related Topics

Adjusts the magnification of items selected on the diagram in the active window so that they are displayed at the maximum size that can fit into that diagram window.

This option is available only if one or more items are selected on the diagram.


View - Fit to Diagram
   Fit to Diagram (View Menu)

Related Topics

Adjusts the magnification of the whole diagram in the active window so that it is displayed at the maximum size that can fit into that window.


View - Toolbar
Toolbar (View Menu)

Related Topics

Shows or hides the standard toolbar below the menu bar.


View - Tool Palette
Tool Palette (View Menu)

Related Topics

Shows or hides the tool palette.


View - Status Bar
Status Bar (View Menu)

Related Topics

Shows or hides the status bar at the bottom of the application window.


View - Spreadtable View
      Spreadtable View/Default View (View Menu)

Related Topics

The Property Palette can display properties in one of two views: spreadtable view, and default view.

Spreadtable View   [image]    In spreadtable view,  you can list more than one set of properties in the spreadtable. For example, you can select two or more tables from the Navigator and compare their property values on the spreadtable.

Default View  [image]    In default view, the Property Palette is displayed as a two-column grid, with the property names listed vertically and their values listed alongside.


View - Intersection View
      Union View/Intersection View (View Menu)

Related Topics

The Property Palette can show a set of properties in one of two views: union (the default) and intersection. The union/intersection view applies to conflicts of property types (e.g., Name, Length) and not to conflicts of property values (e.g., HEADQUARTERS, 10). Thus the setting of this button is not relevant when the selected repository objects are of the same type because in this case they have the same set of property types.

If there is a property type that has been given different values for different repository objects, then that property value is displayed in the Property Palette as a set of hashes (#####) regardless of the Union/Intersection button.

Union View    [image]   In Union View, the Property Palette lists the combined property types, i.e., all the property types of the selected object types.

Intersection View   [image]   In Intersection View, the Property Palette lists only the common property types, i.e., the property types that appear in all of the selected types.


View - Grid
Grid (View Menu)

Related Topics

Shows or hides the grid in the active window.


Tools - Navigator
Navigator (Tools Menu)

Related Topics

Opens a new Navigator if none is open, or makes the Navigator window the active window if the Property Palette is active.

Navigator windows use a tree structure to represent the repository definitions that are recorded  in the repository, and the associations between those definitions.


Tools - Property Palette
Property Palette (Tools Menu)

Related Topics

Opens a new Property Palette if none is open or if the present palette is pinned, or makes the latest Property Palette the active window if the Navigator window is active.

Property Palettes display the properties of definitions, e.g. table definitions, that are recorded in the repository.


Edit - TextPad
   TextPad (Edit Menu)

Related Topics

Opens the TextPad, which enables you to attach textual information to the selected text property.


Edit - ASCII Editor
   ASCII Editor (Edit Menu)

Related Topics

Opens the ASCII editor, which enables you to attach ASCII text to the selected multi-line text property.


Edit - HTML Editor
   HTML Editor (Edit Menu)

Related Topics

Opens the HTML editor, which enables you to attach HTML text to the selected multi-line text property.


Tools - Process Modeler
Process Modeler (Tools Menu)

Related Topics

Invokes the Process Modeler with the same database connection and workarea as the current tool.


Tools - Dataflow Diagrammer
Dataflow Diagrammer (Tools Menu)

Related Topics

Invokes the Dataflow Diagrammer with the same database connection and workarea as the current tool.


Tools - Repository Reports
Repository Reports (Tools Menu)

Invokes the Repository Reports tool, which enables you to run reports about the contents of the repository.


Tools - Entity Relationship Diagrammer
Entity Relationship Diagrammer (Tools Menu)

Related Topics

Invokes the Entity Relationship Diagrammer with the same database connection and workarea as the current tool.


Tools - Function Hierarchy Diagrammer
Function Hierarchy Diagrammer (Tools Menu)

Related Topics

Invokes the Function Hierarchy Diagrammer with the same database connection and workarea as the current tool.


Tools - SQL Plus
SQL*Plus (Tools Menu)

Opens a SQL*Plus window.


Tools - Repository Object Navigator
Repository Object Navigator (Tools Menu)

Invokes the Repository Object Navigator with the same database connection as the current tool.


Tools - Dependency Manager
Dependency Manager (Tools Menu)

Related Topics

Invokes the Dependency Manager, from which you can examine dependency information stored in the repository. You can also use the Dependency Manager to edit some repository information.


Tools - Matrix Diagrammer
Matrix Diagrammer (Tools Menu)

Invokes the Matrix Diagrammer with the same database connection and workarea as the current tool.


Tools - Design Editor
Design Editor (Tools Menu)

Related Topics

Invokes the Design Editor with the same database connection and workarea as the current tool.


Options - Customize Property Palette
Customize Property Palette (Options Menu)

Customizes which properties are displayed on the Property Palette.

Dialog box options

Show

Show Owning Folder

Displays or hides the name of the owning container for an element.

Show Version Label

Displays or hides the version label property in the Property Palette.

Show Audit Properties

Displays the audit properties (date created, date changed etc.) in the Property Palette.

Property Clipboard

Include Multi Line Text Properties

Includes or excludes multi-line text properties in the Properties Clipboard, used when copying properties.

Automatically switch to spreadtable mode on multi insert

If active, automatically switches the Property Palette to spreadtable view when creating more than one element in a single operation.


Options - Text Editor Options
Text Editor Options (Options Menu)

Related Topics

Defines Text Editor options. This enables you to specify which text editor to use for the values of repository definition properties that are stored in ASCII or HTML format.

Default text editors are set up for ASCII text and HTML text based on the settings in the Windows Registry. You can specify alternative editors for either or both of these kinds of text.

Dialog box options

Text Editor

Select command to run the ASCII editor

The command that runs the ASCII text editor. Ensure that the filename is followed by the characters <SPACE>%1 in order for the command to function correctly.

Browse button

Locates the .EXE file for the ASCII text editor. Selecting this button displays the Browse dialog box.

HTML Editor

Select command to run the HTML editor

The command that runs the HTML editor. If you specify Netscape Navigator as the editor, ensure that the filename is followed by the characters <SPACE>"%1" for the command to function correctly.

Browse Button

Locates the .EXE file for the HTML editor. Selecting this button displays the Browse dialog box.


Options - Broadcast Options
Broadcast Options (Options Menu)

Related Topics

Defines broadcast options.

Dialog box options

Broadcast Notifications

Disabled

Turns off the broadcasting mechanism, i.e., the user does not receive (or send) notification messages.

Desktop only

Broadcasts all changes made in the current tool to all tools running on this machine.

Network

Broadcasts all changes made in the current tool to all users participating in the network broadcasting mechanism.


Options - Diagnostics
Diagnostics (Options Menu)

Allows you to set diagnostic file and trace settings. This feature should not be used unless requested to do so by your Oracle customer support representative. If you inadvertently set any of the diagnostic options you may find that the tool's performance is affected. If you do find any degradation in performance, click the Disable Option button to switch off the diagnostics facility.


Font dialog box

Allows you to specify the details of the font to be used for a text item.

Dialog box options

Font

Specifies the font to be used. You can choose a font from the list.

Font Style

Specifies the style for the selected font. You can choose a style from the list. Available styles are: regular, italic, bold and bold italic.

Size

Specifies the size in points of the font for this text item. A point is 1/72nd of an inch.

Sample

Shows an example of how this text item will appear with the current font options.

Script

Specifies the character set to be used for the selected text item.


The TextPad

Related Topics

The TextPad is a convenient method for entering and storing text for multi-line text properties. You can also use the TextPad to save text in a file and to assign text from a file to a multi-line text property.

The TextPad window contains a toolbar and a main text writing area:

For information on a TextPad toolbar button, click [image] in the main toolbar, then click the toolbar button.


Multi-line text properties

Related Topics

Many element types in the repository have text properties, such as Description, Notes or Comment. Some of these text properties (e.g., Description and Notes) are multi-line text properties, meaning that they can consist of more than one line of text.

Multi-line text properties are listed under the heading "Text" in the Property Palette, and are indicated by a [image] icon next to the property name.

You can edit a multi-line text property either by using the TextPad, or by using an ASCII or HTML editor if one is available.


File menu options for TextPad


File - Close (Textpad)
Close (File Menu - TextPad)

Related Topics

Closes the TextPad without attaching the current text to the selected property.

To close the TextPad and attach the text to the selected property, choose File→Exit.

If you do not want to attach the text to the property, but want to keep a copy of the text, then save the text as a text file.


File - Include File (Textpad)
   Include File (File Menu - TextPad)

Related Topics

Includes a specified file at the current position in the TextPad.

You can use File→Write to File to save the current text to file and come back to it later. In this way, it is possible to write some boilerplate text that you can attach to some selected properties.

Dialog box options

Use the context-sensitive help facility in the this dialog box for information on individual components.


File - Write to File (Textpad)
Write Text to File (File Menu - TextPad)

Related Topics

Saves the current text in the TextPad to a specified file.

Dialog box options

Use the context-sensitive help facility in the this dialog box for information on individual components.


File - Save Uncommitted Data (Textpad)
   Save Uncommitted Data (File Menu - TextPad)

Related Topics

Commits to the repository any unsaved TextPad changes you have made to the selected property.

Note:	Any changes that have been made to properties on the Property Palette, prior to invoking the TextPad are also committed to the repository.


File - Revert Uncommitted Data (Textpad)
   Revert Uncommitted Data (File Menu - TextPad)

Cancels any unsaved TextPad changes you have made to the selected property and closes the TextPad.

To cancel unsaved TextPad changes without closing the TextPad, click the [image] button.

Note:	Any unsaved changes that have been made to properties on the Property Palette, prior to invoking the TextPad are also canceled.


File - Print (Textpad)
Print (File Menu - TextPad)

Related Topics

Prints the contents of the TextPad. This option enables you to specify the range of pages to be printed, the number of copies, the destination printer and other printing options.

Dialog box options

Use the context-sensitive help facility in the this dialog box for information on individual components.


Edit menu options for TextPad


Edit - Undo (Textpad)
   Undo (Edit Menu - TextPad)

Cancels the effect of the last operation performed in the TextPad. For example, you can use this option to discard any unsaved TextPad changes you have made, without closing the TextPad.

Choosing this option a second time restores the effect of the canceled operation.


Edit - Copy (Textpad)
   Cut (Edit Menu - TextPad)

Related Topics

Removes the selected text from the TextPad and places it on the Clipboard.

The Clipboard stores the selection that you cut from the TextPad until the next time you cut or copy something. Each time you cut or copy text, this overwrites the Clipboard contents.

You can insert the contents of the Clipboard into the TextPad using the [image] button. You can also paste text from the Clipboard into other Windows applications.

To remove selected text from the TextPad without placing it on the Clipboard, choose Edit→Clear.


Edit - Undo (Textpad)
   Copy (Edit Menu - TextPad)

Related Topics

Places a copy of the selected text on the Clipboard.

The Clipboard stores the selection that you copy from the TextPad until the next time you cut or copy something. Each time you cut or copy text, this overwrites the Clipboard contents.

You can insert the contents of the Clipboard into the TextPad using the [image] button. You can also paste text from the Clipboard into other Windows applications.


Edit - Paste (Textpad)
   Paste (Edit Menu - TextPad)

Related Topics

Places the contents of the Clipboard at the insertion point in the TextPad.

The Clipboard contains the subject of the most recent cut or copy. The Clipboard contents can be pasted as many times as required.

To place text on the Clipboard, highlight the text and click the [image] or [image] button. You can also cut or copy text from other Windows applications and paste them in the TextPad.


Edit - Clear (Textpad)
Clear (Edit Menu - TextPad)

Removes the selection from the TextPad without placing it on the Clipboard.

To place a copy of the removed text on the Clipboard, click the [image] button.


Edit - Find (TextPad)
Find (Edit Menu - TextPad)

Related Topics

Searches for a text string in the TextPad.

The TextPad window is searched to find the next text string that contains a match for the specified characters. You can specify the direction of the search and whether or not the search is case-sensitive.

Dialog box options

Find What

The text string that you want to search for in the TextPad. By default, this field contains the current selection in the TextPad.

Match Case check box

Indicates whether the search is case-sensitive.

Up option button

Indicates that the search operates upward from the current cursor position.

Down option button

Indicates that the search operates downward from the current cursor position.

Find Next button

Finds the next occurrence of the string in the Find What field. This button is dimmed if no string has been specified.


Edit - Replace (Textpad)
Replace (Edit Menu - TextPad)

Related Topics

Finds and replaces occurrences of a specified text string in the TextPad.

The TextPad window is searched to find the next text string that contains a match for the specified characters. You can specify whether or not the search is case-sensitive.

Dialog box options

Find What

The text string that you want to be replaced in the TextPad. By default, this field contains the current selection in the TextPad.

Replace With

The text string that you want to replace the occurrences of the text string in the Find What field.

Match Case check box

Indicates whether the replace operation should search for only those text strings that match the case of the string in the Find What field.

Find Next button

Selects the next occurrence of the text string in the Find What field.

Replace button

Replaces the found text string with the string in the Replace With field. If no text string is currently selected, then this button searches for the next occurrence of the string in the Find What field.

Replace All button

Replaces all occurrences of the string in the Find What field with the string in the Replace With field.


Edit - Repeat (Textpad)
Repeat (Edit Menu - TextPad)

Related Topics

Finds the text string that was specified (under Find What) in the most recent search or replace operation.


Edit - Select All (Textpad)
Select All (Edit Menu - TextPad)

Selects all text in the TextPad.


Edit - WordWrap (Textpad)
WordWrap (Edit Menu - TextPad)

Enables or disables the word wrap feature for text.

When word wrap is enabled (this is the default), text that cannot be fitted on one line is displayed on the next line in the TextPad. When word wrap is disabled, this additional text is displayed on the same line and you must scroll horizontally to see it.

Note:	If you set the text to unwrapped, then you will be permitted to enter as much text as you want in one line. When you commit the text to the repository, the text is automatically wrapped to use as many lines as is necessary.


Edit - Text
Text (Edit Menu)

Related Topics

Attaches free format multi-line text for the text types (e.g. Description and Notes) associated with this selected element.

Dialog box options

Element Name

Displays the name of the element.

Text Type

The types of text, e.g., Description, Notes. The changes made in the Text Area apply to the type of text displayed in this box.

Text Area

The text for the element. Text can be cut, copied and pasted from this area by using the hot-keys Ctrl+X, Ctrl+C and Ctrl+V.

Note:	A maximum of 80 characters can be entered per line for PL/SQL text types.

Text Editor

Opens the ASCII editor, which enables you to attach ascii text to the selected multi-line text property.

HTML Editor

Opens the HTML editor, which enables you to attach HTML text to the selected multi-line text property.


Utilities - Resequence
Resequence (Utilities Menu)

Related Topics

Allows you to change the order in which some types of selected elements are ordered in the Navigator. For example, you can resequence columns in a table definition.

Elements that can be resequenced are indicated in the Navigator window by [image].

Dialog box options

List box

Lists the repository definitions that you can resequence. This list box allows single selection only. Use the resequence buttons to move a selected definition up or down the list box.

Resequence buttons

Specifies the order in which the definitions are to be displayed on the Navigator window and diagrams.

Tip:	Instead of using the Resequence buttons you can hold down the CTRL key and press the Up and Down arrows.


Utilities - Select in Other Tools
Select in Other Tools (Utilities Menu)

Related Topics

Selects the same repository objects, as currently selected on the active tool, in other tools (providing that the other tools are open in the same context).


Utilities - Update Columns in a Domain
Update Columns in a Domain (Utilities Menu)

Related Topics

Updates all the appropriate columns/Oracle object type attributes with the property details of the selected domain. You might use this, for example, when you make a change to a domain and want to propagate these changes to all the columns/type attributes that use that domain.

This utility overwrites any properties in a column/attribute that conflict with the same property in the column's/attribute's domain. Null values in the domain replace any non-null values. The exception to this is the Default Values property, which is overwritten only if the corresponding column/attribute property has a null value.


Utilities - Force Delete
Force Delete (Utilities Menu)

Related Topics

Invokes the Force Delete or Force Purge wizard. These wizards remove selected repository objects or secondary access controlled (SAC) elements, regardless of any delete constraints that may have been defined for the corresponding object type. About

Each wizard is a predefined set of screen forms that takes you step by step through the force delete or force purge process.

Note:	It is possible to undo a force delete operation. Objects removed in this way are placed in the workarea wastebasket, from where they can be recovered. However, it is not possible to recover references or child elements of force-deleted objects.

It is not possible to undo a force purge operation.

The Force Delete Wizard is invoked if the selection is a non-versioned object or a SAC element of any kind of object. In this case the selection is removed to the workarea wastebasket. If the selection is a checked-out versioned object, Force Delete has no effect. You can use the Force Delete Wizard only if you have the FORCE system privilege, and DELETE access rights to the workarea and the owning container.

The Force Purge Wizard is invoked if the selection is a checked-in versioned object. The version visible in your workarea is completely removed from the repository and cannot be recovered. You can use this wizard only if you have the FORCE or PURGE system privileges, and DELETE access rights to the owning container.


Force Delete/Force Purge: Objects Selected

Lists the objects that you have selected for the force delete or force purge operation.

If the list is incorrect, click Cancel and reselect the objects, otherwise click Next.

Path

The hierarchical path of the object in your workarea.

Element Type

The repository element type for this object.


Force Delete/Force Purge: Purged Objects
Force Purge: Purged Objects

Lists the objects that will be purged (that is, have all object versions removed).

Status

A value of OK indicates that the purge operation can continue for this object. If an object is checked in, this is indicated; you will need to select the object and check it out before the operation can continue.

An example of when an object in the list might be checked in would be when purging a domain that is referenced by a column. In this case the column will be cascade deleted. However, if the table to which the column belongs is checked in, it must be checked out before the column can be deleted and the operation can continue.

Path

The hierarchical path of the object in your workarea.

Element Type

The repository element type for this object.

Check Out

Checks out a selected item in the list that is marked as checked in, so that the operation can continue.


Force Delete/Force Purge: Deleted Objects

Lists the objects that will be deleted.

Status

A value of OK indicates that the delete operation can continue for this object. If an object is checked in, this is indicated; you will need to select the object and check it out before the operation can continue.

An example of when an object in the list might be checked in would be when deleting a domain that is referenced by a column. In this case the column will be cascade deleted. However, if the table to which the column belongs is checked in, it must be checked out before the column can be deleted and the operation can continue.

Path

The hierarchical path of the object in your workarea.

Element Type

The repository element type for this object.

Check Out

Checks out a selected item in the list that is marked as checked in, so that the operation can continue.


Force Delete/Force Purge: References

Lists reference properties for the objects that you are deleting or purging. These references will be nullified. Note that, although deleted objects (but not purged objects) can be restored from the wastebasket, the references cannot.

Status

A value of OK indicates that the operation can continue. If an object is checked in, this is indicated; you will need to select the object and check it out before the operation can continue.

Property

The element type of the reference property.

Referencing Element/Element Type

The element (and its type) that references the object selected for delete or purge. For example, if you are deleting a domain that is referenced by a column, this field shows the column name and its path in the repository.

Referenced Element/Element Type

The element (and its type) that is referenced by the element in the previous pair of fields. For example, if you are deleting a domain that is referenced by a column, this field shows the domain name and its path in the repository.

Check Out

Checks out a selected item in the list that is marked as checked in, so that the operation can continue.


Utilities - External References
External References (Utilities Menu and Configuration Wizard)

Related Topics!Alink(COM_Listing_external_references, , , )

Enables you to check whether repository objects in a selected workarea, container or configuration make reference to objects outside that workarea, container or configuration. You can then include any of these externally referenced objects in the workarea, container or configuration.

Dialog box options

For

The name and (if under version control) the version label for this workarea, container or configuration.

List Mandatory Only

When this check box is selected, clicking the List button causes the display to show only the mandatory external references for this workarea, container or configuration.

Recurse Sub Folders

When this check box is selected, clicking the List button causes the display to also show external references for child objects of this workarea, container or configuration (for example, sub-folders of a folder).

Name

The name of an object for which an external reference exists.

Type

The type of object listed.

Reason

The reason why the reference to this object is classed as an external reference:

Lost + Found	The object resides in the Lost+Found area, i.e. it has no owning container
No Access Rights	You do not have access to the container that owns this object
Not in Folder	This object is not in the selected container
Not in Workarea	This object is not in the selected workarea
Not in Repository	This object is not in the repository; this message indicates a problem that requires resolution, e.g. by creating the required object
Wrong Version	The referenced version of this object has no record of the reference; you can use Change Version to choose a different version
Status

Indicates whether the object is checked in, checked out or not under version control. If an object is not checked in, you cannot include it in a workarea.

Mandatory

Indicates whether this is a mandatory reference.

Version

The version label for this object (if it is under version control).

Include Iteratively

When this check box is selected, selecting objects from the list and clicking the Include button causes these objects to be iteratively included in the selected workarea, container or configuration. This means that any objects referenced by the externally referenced objects are also included, as well as any objects referenced by those extra objects, and so on until all referenced objects are included. Example

Show Latest on Branch

Appears only if workarea or configuration selected. For objects under version control, this enables you to list objects from a checkin branch other than the default.

List

Redisplays the list based on the status of the List Mandatory Only and Recurse Sub Folders check boxes.

Select All

Selects all the objects in the list of references. Used in conjunction with the Include button.

Include

For objects selected in the list, includes these objects in the container identified by the For: field.

Change Version

If the For field shows a workarea or configuration name, then for a selected object in the list, this allows you to list a different version of that object (if the object is under version control).

List References

For a selected object in the list, shows the objects that reference it and the kind of reference they make to it.


Include iteratively - example
Iterative inclusion - example

Assume that a container called Folder1 has an entity, ENT_A, which has a relationship to ENT_B in a different container, Folder2. ENT_B, in turn, has references to ENT_X, ENT_Y and ENT_Z in other containers. You select Folder1 and list its external references. You see only ENT_B in the list. You want to include ENT_B in Folder1, so you select ENT_B in the list.

If you clicked Include at this point, you would include only ENT_B in Folder1. However, you want to include not only ENT_B but any other objects that it references, and any other objects that they reference, and so on. To do so, you select the Include Iteratively check box and click Include.


Utilities - Extended Copy
Extended Copy (Utilities Menu)

Related Topics

Copies one or more selected PAC elements within a workarea, enabling you to specify what to do about references to other objects. The copies are renamed with a system-generated or a user-defined name.

This option invokes the Extended Copy Wizard, a series of screens that takes you step by step through the copy process.


Extended Copy Wizard:  Copy List

Specifies the complete set of objects to be copied.

Target Container

(Mandatory)  The container to which the objects are to be copied.

Objects to Copy

Lists the set of objects that are to be copied.

Path

The complete repository path specification of an object to be copied.

Element Type

The element type for this object.

Add

Enables you to include further objects in the set to be copied.

Remove

Removes selected objects from the copy list.

Copy Dependencies

When checked, copies any dependency information created for the objects by the Dependency Manager tool. When cleared, no dependency information is copied.


Extended Copy Wizard:  References

Lists all objects referenced by those in the copy set. You can choose to copy the referenced objects, leave them as they are, nullify the reference properties or remap the references to different objects.

Type

Type of object identified by Name.

Name

The name of a referenced object.

In Target ?

Indicates whether the referenced object is owned by the target container.

Copy

Copies the referenced object as well as the referencing object, and updates the reference properties to point to the new copy of the object.

Leave

Specifies that the referenced object is not copied, nor are the reference properties updated. This applies only to those objects that are known as "shareable" (that is, they can be referenced from a container other than their own). The exceptions are listed here.

Null

For optional references only, sets the reference properties to null in the new copy of the object. Does not apply to mandatory references.

Remap

Enables you to change the reference properties to point to a different object. Checking this box displays a screen from which you can choose a different object.

Remap to

If Remap is checked, this field identifies a likely candidate for the remap (an object with the same name and type) in the target container, if such an object exists. If you choose a different object, it is shown here.

Details

For a selected object in the referenced objects list, indicates which objects reference it.

Set Remap

Changes the reference properties to point to the object indicated in the Remap To field.


Extended Copy Wizard:  Reference Details

For a selected object in the referenced objects list, indicates which objects reference it.

Type

The type of object that references the object shown at the top of the screen.

Name

The name of an object that references the object shown.

Property

The property through which the object is referenced.

Mandatory

Indicates whether this is a mandatory reference.


Extended Copy Wizard:  Name Change

Enables you to specify a new name for a copied object. Lists all the objects to be copied.

Original Path

The repository path and name of the object being copied.

Copy Name

The name you want the copy to have. By default the name of the copy is name_1, where name is the name of the original object. You can specify a different name for the copy here.


Utilities - Publish Diagrams
Publish Diagrams (Utilities Menu)

Related Topics

Publishes diagrams to a file or to the Repository Object Browser (ROB).

This option opens the Publish Diagrams dialog.


Publish Diagrams dialog

Enables you to publish Designer diagrams to the Repository Object Browser (ROB) or to save them as files to a file system directory.

Available Diagrams pane

Shows the diagrams within the current workarea.  If you want to publish a subset of these diagrams, click the diagram or diagrams that you want to publish.

Single right arrow

Click to move the diagrams highlighted in the Available Diagrams pane to the Selected Diagrams pane.

Single left arrow

Click to move diagrams highlighted in the Selected Diagrams pane to the Available Diagrams pane.

Double right arrow

Click to move all diagrams in the Available Diagrams pane into the Selected Diagrams pane.

Double left arrow

Click to move all diagrams in the Selected Diagrams pane to the Available Diagrams pane.

Selected Diagrams pane

Diagrams listed in this pane will be published when you click the OK button.  If a diagram was active in the Design Editor when you opened the Publish Diagrams dialog, it will automatically be listed in this pane.

File Name text box

This is enabled only if the "Publish to File" option is chosen (see below). This text box displays the target file name for the diagram currently highlighted in the Selected Diagrams pane. By default the target file name is the same as the diagram name in the repository.  You can change the target file name by overtyping the text in this box.

Destination group

Use the options in this group to specify the destination for publishing.

Publish to Repository Object Browser option

Choose this option to publish the diagrams to the Repository Object Browser.

Publish to File option

Choose this option to publish the diagrams to files.

Directory text box

This text box shows the file system directory to which the files containing the diagrams will be written.  A directory will be suggested, which will be one of the following:

-	the mapped directory of the application system, if the selected diagrams belong to one application system

-	the directory chosen during the previous publish operation

-	the system temporary directory.

You can change the suggested directory by overtyping the text in this box, or by using the Browse button.

Browse button

Click to open a browse dialog, though which you can choose an existing directory.

Publish Format text box

Choose a format for the published diagrams from the drop-down list.  You can choose from PNG, GIF, TIFF, JPEG and BMP.


File - Close
Close (File Menu)

Closes the active window without quitting the tool. To quit the tool use File→Exit.


File - Summary Information
Summary Information (File Menu)

Related Topics

Displays information about the active window and enables you to record additional information about the window.

The database connection and the current workarea cannot be changed using this menu option, but can be changed using File→Change Connection and File→Change Workarea.

Dialog box options

When the active window is a diagram, the dialog box has the following tabs:

Summary Details

Text

Otherwise, the Summary Information (without tabs) dialog box is displayed.


Summary Information - Summary Details

The Show checkbox adjacent to each field determines whether or not the information in the field is displayed in the print legend on the active window.

Note:	Summary information cannot be saved against a diagram unless that diagram has already been saved in the repository.

When a diagram is copied, i.e., you open a read-only copy of a currently open diagram, the summary information about that diagram does not get copied.

Diagram

The name of the active diagram.

Title

The title of the active window. The title can be used for displaying additional information on the window.

Created

The date and time on which the contents of the active window was created.

Last Modified

The date and time on which the contents of the active window was last modified.

Author

The author of the contents of the window.

Container

The name of the container that you are currently using.

Username

The username for the Oracle database that you are currently using.

Connect String

The connect string for the Oracle database that you are currently using.

Workarea

The name of the workarea that you are currently using.


Summary Information - Text

Related Topics

Used to enter free format multi-line text for the text types associated with the active diagram, such as notes and description.

Note:	Multi-line text can be entered only for named diagrams.

Text Type field

Defines which text type you want to enter multi-line text for. A list of currently defined text is available.

Text Editor button

Opens the ASCII editor, which enables you to attach ASCII text to the selected multi-line text property.

HTML Editor button

Opens the HTML editor, which enables you to attach HTML text to the selected multi-line text property.


Summary Information dialog box

Related Topics

Displays information about the Navigator. The checkbox adjacent to each field determines whether or not the information in the field is displayed in the print legend.

Workarea

The name of the workarea that you are currently using.

Username

The username for the Oracle database that you are currently using.

Connect String

The connect string for the Oracle database that you are currently using.


File - Change Connection
Change Connection (File Menu)

Related Topics

Changes the Oracle database to which the current tool is connected.

Connect dialog box


Connect dialog box

Specifies or changes the Oracle database to which the current tool is connected.

Username

The name of the user that must be specified to gain access to the database account.

You can specify the full connect string in this field, in the format:

username/password@database_alias

For example, to connect to a database with the alias HQ8 using the username and password scott, you would enter:

scott/scott@HQ8

Note:	If you specify the full connect string here, you do not need to complete the Password and Connect fields.

Password

The password for the given username. The password is displayed as asterisks.

Connect String

The database alias required to access the database account. You must ensure that the database alias is specified in the TNSNAMES.ORA file in your Oracle home directory, usually d:\oracle_home\NET80\ADMIN.


File - Change Workarea
Change Workarea (File Menu)

Related Topics

Changes the workarea for the current tool and provides access to the Workarea Wizard which allows you to create new workareas.

Note, you must have the repository management privilege before you can create workareas.

Workarea dialog box


Workarea dialog box

Specifies or changes the workarea for the current tool, and enables you to create a new workarea.

Workarea list box

Lists the workareas that you can choose, together with various details about them. You can choose a workarea by selecting it and clicking OK.

Workarea

The names of the workareas that have been defined in the repository.

Owner

The username of the repository user who created the workarea.

Type

Indicates whether this is a private or shared workarea. Private workareas can be accessed only by the user who created them. Shared workareas can be accessed by any user to whom the owner grants access.

Check In Branch

(Versioned repositories only) The default branch, if any, to which versioned objects are checked in if they are updated via this workarea.

New

Enables you to create a new workarea. Clicking this button starts the Create Workarea Wizard, a predefined set of screen forms that takes you step by step through the process of creating a workarea.


Create Workarea Wizard: Options

The Create Workarea Wizard: Options screen provides the following four options for creating a workarea:

Option	Description
Create a default workarea	Simplest option - just enter the workarea name
Copy a workarea	Copies an existing workarea, but allows you to modify workarea details in the copy
Create a workarea based on a file-stored workarea specification	Uses rules and configurations stored in a file to create the workarea; you can modify these and other details
Create a custom workarea	Provides greatest choice - you can manually define all the details of the workarea
Note:	To edit an existing workarea, select the workarea and choose Edit→Edit Workarea.

Additional fields are displayed from each of the four available options. These allow you to name the workarea, provide a suitable description for the new workarea and, where appropriate, name a workarea to copy from.

Once you have made your selection, the wizard takes you step by step through the process of creating the workarea.

When you create a workarea, it is initially a private workarea, meaning that only you can access it. Subsequently you can, if you wish, grant one or more other users access to it, thus making it a shared workarea. If you later revoke access to the workarea from all other users, the workarea becomes private again.

For all except a default workarea, you can specify a default checkin branch if the automatic branching policy is enabled. You can also change the rules and configurations that make up the workarea specification.

A basic workarea specification, consisting merely of the rule LATEST (MAIN), is applied to all new workareas by default. This rule specifies that each time the workarea is refreshed it will display details of the latest version of all objects to which you have access on the MAIN branch. It is not necessary for a workarea to have any other rules or any configurations specified for it, but if you want to refine the workarea specification, you can do so using the wizard.


Application System dialog box

Specifies or changes the application system for the current tool.

Application System entry box

Identifies the name of the application system you want to use. If an application system is selected in the list box, then the name of that application system is displayed in this field.

Application System list box

Lists the names and owners of all the application system that you may use. If you select an application system from this list, its name is displayed in the application system entry box.


File - Print
   Print (File Menu)

Related Topics

Prints the contents of the active window. This option enables you to specify the range of pages to be printed, the print quality, the number of copies, the destination printer and other printing options.

Dialog box options

Printer

The name of the current printer. The current printer can be changed using the Setup button. If the current printer is the system (that is, the default) printer it is stated in this field.

Print Range

All

Prints all pages. All is the default print range value.

Pages

Prints a range of pages specified by the From and To fields. For example, entering 2 in the From field and 6 in the To field prints pages 2 to 6 inclusive.

Print Quality

Specifies the print density. The higher the print density, the better the print quality, but higher-quality copies may take longer to print.

Copies

The number of copies of the print job that you want to print.

Print to File

Determines whether or not the print job is printed to a specified file instead of being sent to the printer. When checked, the Print to File dialog box is displayed.

Page Numbers

Determines whether or not page numbers are printed at the bottom of each page of the print job.

Print to ASCII

Prints the textual content of the Navigator window to a text file. If this box is checked, a dialog box is displayed for you to specify the name and location of the text file. Note this option is available from the Repository Object Navigator only.

Page Title

Determines whether or not the title is printed at the top of each page of the print job.

Page Boundaries

Determines whether or not indicators are displayed showing the outermost edges of the printable area of the page.

Scale to Pages

X:

Determines the number of pages in the horizontal axis on which the data will be printed.

Y:

Determines the number of pages in the vertical axis on which the data will be printed.

Fit to Page

Determines whether or not the data is printed so that it fits onto one sheet of the currently selected paper size.

Setup button

Allows you to view or change the configuration of the current printer, or to choose a different printer if more than one is available. Selecting this button displays the Print Setup dialog box.


File - Print Preview
Print Preview (File Menu)

Related Topics

Displays the contents of the active window as it will appear when printed, and provides options for navigating through, and for changing the magnification of, the pages within the Print Preview window. The contents of the active window can also be printed directly from this preview window.

Print preview buttons

Print button

Displays the Print dialog box, allowing you to specify how and where the data is printed, and to initiate the print job. Selecting this button cancels the Print Preview window.

Next Page button

Shows how the next page of the data will appear when printed.

Prev Page button

Shows how the previous page of the data will appear when printed.

One Page/Two Page button

Specifies whether one or two pages are previewed at a time.

Zoom In button

Enlarges part of the page preview display.

Zoom Out button

Reduces the magnification of the page preview display.


File - Print Setup
Print Setup (File Menu)

Related Topics

Configures printer settings such as the destination printer, the paper size and the paper orientation. Advanced document properties set within an application can also be set. These settings will override the default settings made in Windows.

Dialog box options

Printer

Determines whether you want to use the default printer or one of the other currently connected printers. A dropdown list of currently connected printers is available. The default printer can be changed, and other printers connected, from the Settings option on the Windows Start menu.

Orientation

Determines whether the printout will appear in portrait or landscape format. Selecting the appropriate option button changes the image of the page accordingly in this field.

Size

Determines the paper size for the printer.

Source

Determines the source of the paper for the printer.

Options button

Displays the Options dialog box for the currently selected printer, allowing you to set some of the more advanced document printing options. Third party printer help is available for the Options dialog box.


File - Recent File
Recent file (File Menu)

Opens any of the four most recently opened files (diagrams or logic text) in the current workarea. Diagrams or logic files in other workareas which have been opened recently may also be listed, but cannot be opened using this option.


File - Exit
Exit (File Menu)

Exits from the tool.


Browse dialog box

Directories

The directory where the file that you want to embed or link to is located.

Drives

The drive where the file that you want to embed or link to is located.

Network... button

Locates a file on the network. For more information, select the Help button on the Connect Network Drive dialog box.


Print to File dialog box (Description not used by Designer in 2.1)

Related Topics

Allows you to specify the name of the file to which a print job is to be saved.

File Name

Specifies the name of the file (maximum of eight characters, plus a three-letter extension), including its path, to which you want to print the diagram.

Attention:	The filename must be different from the original filename, or the diagram must be saved to a different drive or directory.

Note:	If no file of this name currently exists, one will be created.

All the files of the specified type in the specified directory are listed below the File Name field.

Save File as Type

Specifies the file extension for the file. It also filters the File Name list so that only files of the specified type are listed.

Drives

Select the drive on which you want to store the file.

Directories

Select the directory where you want to store the file.

Network button

Opens the Connect Network Drive dialog box so that you can make a connection to a network drive. For more information, choose the Help button in that dialog box.


Utilities - Table to Entity Retrofit
Table to Entity Retrofit (Utilities Menu)

Related Topics

The ‘Table to Entity Retrofit’ utility transforms (or 'reverse engineers') repository-held relational table definitions into entities, attributes, relationships and unique identifiers.


Table to Entity Retrofit dialog box

Related Topics

The ‘Table to Entity Retrofit’ utility transforms (or 'reverse engineers') repository-held relational table definitions into entities, attributes, relationships and unique identifiers.

Use this dialog to specify the table definitions from which entity definitions are to be created.

Table Name

The names of the tables to be transformed. Only tables that do not currently implement entities can be selected.

Entity Name

Mandatory, 30 character
The name of the entity definition to be created. This field defaults to the table name with any underscore characters present in the name replaced with spaces. If the wording is not acceptable, you can type over this entry.

Entity Short Name

Mandatory, 10 character
The short name of the entity definition to be created. This field defaults to the table name. If the wording is not acceptable, you can type over this entry.

Entity Plural

Mandatory, 100 character
The name of the entity plural to be created. This field defaults to the table name with any underscore characters present in the name replaced with spaces. If the wording is not acceptable, you can type over this entry.

Update relationships for existing entities

With this box checked, the utility will create relationships for foreign keys that have been added to tables that implement existing entities.

Update unique identifiers for existing entities

With this box checked, the utility will create unique identifiers for primary and unique key constraints that have been added to tables that implement existing entities. Also, the utility will replace attribute unique identifier entries with relationship entries or create new relationship entries, where the primary or unique key implementing the unique identifier shares columns with a foreign key of the table.

Candidate Tables button

Displays a Candidate Tables dialog box listing all the tables in the current application system that can be transformed into entities. Tables previously used to implement entities are not displayed in the list. A Filter field is available to locate specific tables in the list.

Retrofit button

Transforms the table definitions displayed in the Table to Entity Retrofit dialog into entity definitions.

Grid Save button

Saves the current widths of grid columns.

Grid Reset button

Resets grid columns to their default widths.


Candidate Tables dialog box

Related Topics

This dialog lists all the tables in the current application system that can be transformed into entities. A Filter field is available to locate specific tables in the list. Choose the tables you require and press OK.


Version - View Version Details
View Version Details (Version Menu)

Related Topics

Displays the Details dialog box, enabling you to view details about the contents of the selected object.

The version of the selected object for which the details are displayed is the version that is currently visible in your workarea.

	Displays only the icon and names of the repository items in column lists, ordered vertically.
	Displays only the icon and names of the repository items in multiple column lists, ordered horizontally.
	Displays various general details about the items in the list: name, object type, the date when the item was created, who created it, when it was modified, who last modified it and the number of times the item was modified.
	Displays version details about the items in the list: name, object type, the branch and version number, version label, status, rule or configuration that caused the object to be included in the workarea, and (if currently checked out) the date the object was checked out and by whom.
	Selects the level above the current level in the repository hierarchy.
	Causes the details displayed in the Details dialog box to remain unchanged (pinned) even if you select another repository object from the Navigator. The Details dialog box is in the pinned state when the button is [image].


Version - Compare Other Version
Compare Other Version (Version Menu)

Related Topics

Enables you to compare a version of an object with another version of the same object, and displays the results of the compare operation in the Compare window.

The version of the object currently in the workarea view is indicated by an arrow in the Version History Viewer display area, if this tool is active for the object.


Version - Edit Branch Labels
Edit Branch Labels (Version Menu)

Related Topics

Displays the Branch Labels dialog box, enabling you to add new or edit existing branch labels. A branch is always identified by its label.

Label details

Label

The name of the branch label you are editing.

Notes

Any notes attached to the branch label.

Created By

The repository user who created the branch label.

Date Created

The date on which the branch label was created.

Modified By

The user who last modified the branch label.

Modified

The date on which the branch label was last modified.

No. Modifications

The number of times that the branch label has been modified.

Buttons

Add

Displays the Add Branch Label dialog box, enabling you to add a new branch label.

Edit

Displays the Edit Branch Label dialog box, enabling you to edit the selected branch label. You cannot edit a branch label if it is currently being used by any object version.

Delete

Deletes the selected branch label. You cannot delete a branch label if it is currently being used by any object version.

Used by

Displays the Branch Usage dialog box listing all the objects that use the selected branch.


Version - Edit Policies
Edit Policies (Version Menu)

Related Topics

Allows you to set defaults for any or all of the repository-wide policies for:

•	Version control

•	File system files

•	Object dependencies

Policies can be set only by a user with the Set Policy privilege.  About

Versioning

Automatic branching

When selected, if a default checkin branch is set for a workarea, all checked-out objects for the workarea will check in to that branch.

Automatic version labeling

When selected, each new object version is automatically assigned a version label on checkin.

Strict locking

When selected, prevents any version of an object being checked out from a branch when one version is already checked out on that branch.

Names of files and folders

Case-sensitive uniqueness checking

When selected, activates case sensitivity checking for the names of new file system files and their containers when these are created in the repository.

Dependencies

The following options control the default setting for what happens to dependency data, if any, for repository objects when they are copied or when new object versions are created. In either case the default can be overridden at the time of the operation. Dependency data is created using the Dependency Manager tool.

Copy on versioning

When selected, causes dependency data to be copied by default when a new version of an object is created.

Copy on copying

When selected, causes dependency data to be copied by default when an object is copied.


Utilities - Compare
Compare (Utilities Menu)

Related Topics

Enables you to compare a version of an object with a version of another object of the same type, and displays the results of the compare operation in the Compare window.

The compare operation indicates:

•	additions to one version that are not in the version with which it is being compared

•	deletions from one version that are not deleted in the version with which it is being compared

•	changes to existing data in one version that are not changed in the version with which it is being compared


Version - Merge
Merge (Version Menu)

Related Topics

Enables you to merge the changes that have occurred independently in two versions of the same object.

The merge operation takes two contributor object versions (target and source), compares them to a common ancestor version, and uses internal rules to create a result version based on changes found in all three versions.  About

Any differences and conflicts encountered by the merge operation are displayed in the Merge window.


Version - Edit Lock Status
Edit Lock Status (Version Menu)

Related Topics

Enables you to view and edit the lock status of a checked-out object version.  How

When a checked-out object version is locked, other users can still check out a version of that object unlocked, but are prevented from either locking it or from checking it back in to the same branch until the lock is removed.  About

This option applies for the currently selected object and is valid only for objects that are already checked out. You can edit the lock status of a checked-out object only if a strict locking policy is not in force, and the object is checked out in the context workarea.

Workarea Context

The workarea that includes the currently selected object.

Object

The currently selected object; the object for which you are viewing and editing the lock status.

Status

The status of the currently selected object.

Locked by

If the object is locked (as indicated by the Locked checkbox), the name of the user who locked the object.

In Workarea

If the object is locked (as indicated by the Locked checkbox), the workarea from which the object was checked out.

Locked

Indicates whether or not the object is currently locked, and, depending on the current state of the object, enables you to lock or unlock the object.


Add / Edit Branch Label dialog box

Related Topics

Enables you to create a new branch label or edit an existing branch label.

Label

The name of the branch label you are creating or editing.

Notes

Any notes associated with the branch label. You can enter new notes or edit any existing notes.


Branch Usage dialog box

Related Topics

Enables you to view a list of the objects associated with the selected branch.

Branch Label

The name of the selected branch label.

Used By

The container type and object identifier of any objects that use the selected branch.


Configuration Wizard - Welcome

Related Topics

Enables you to specify whether you want to create a new configuration or a new version of an existing configuration.

If you choose to create a new version of an existing configuration that is checked in, the configuration will be checked out automatically for the revisions to be applied.

Create a new configuration

Configuration name

The name of the configuration.

Description

A short description of the configuration.

Create a new version of an existing configuration

Configuration name and version

The name and version of the existing configuration on which you want to base the new version.

Browse

Displays the Select Configurations dialog box for you to locate the configuration on which you want to base the new version.


Configuration Wizard - Rules Specification

Related Topics

When you base a configuration on a predefined specification such as a workarea or a template file, the configuration uses any rules and/or configurations included in that specification.

The Rules Specification dialog box displays all rules and configuration specifications associated with the workarea or template file on which your configuration is based.

You can edit the specification by adding or removing rules and configurations.

Specification display area

Displays rules and configurations included in this configuration.

Edit

Displays the Edit Specification dialog box, enabling you to edit the current specification or add rules and/or configurations to your configuration.


Configuration Wizard - Options

Related Topics

Displays a list of configuration options to choose from. The contents of the list depend on whether you chose, on the previous page, to create a:

•	New configuration

•	New version of an existing configuration

New configuration

Initialize configuration using a file template specification

Initializes your configuration with a specification file that has already been created.  How

The specification file contains rules and configurations and must have a .cws file extension.

Template specification file

The name of the specification file. Use the Browse button to locate the file.

Create configuration from a workarea

Uses a specified workarea as the basis for your new configuration.

Workarea

The name of the workarea. Use the Browse button to locate the workarea.

From current contents

Determines whether the configuration is based on the currently visible contents of the selected workarea. If the workarea has not been refreshed for some time, the current contents may differ from those defined by the workarea specification.

From specification

Determines whether the configuration is based on the specification of the selected workarea. The specification defines which objects are visible in the workarea.

Create configuration from the latest versions on a branch

Uses the latest versions on a specified branch as the basis for your new configuration.

Branch Name

The name of the branch. Use the Browse button to locate the branch.

Create a custom configuration

Creates a custom configuration consisting of object versions from a variety of sources by specifying rules and configurations, choosing members, and incorporating externally-referenced object versions.

Specify combinations of rules and configurations

Displays the Edit specification dialog box, enabling you to select rules and configurations on which to base the new configuration.

Just select objects from the repository

Displays the Members dialog box, enabling you to select objects from the repository to include or exclude from the configuration.

New version of an existing configuration

Reinitialize configuration using a file template specification

Reinitializes your configuration with a specification file that has already been created.  How

The specification file contains rules and configurations and must have a .cws file extension.

Template specification file

The name of the specification file. Use the Browse button to locate the file.

Re-create configuration from a workarea

Uses the contents of a specified workarea as the basis for your new configuration version.

Workarea

The name of the workarea. Use the Browse button to locate the workarea.

From current contents

Determines whether the configuration is based on the currently visible contents of the selected workarea. If the workarea has not been refreshed for some time, the current contents may differ from those defined by the workarea specification.

From specification

Determines whether the configuration is based on the specification of the selected workarea. The specification defines which objects are visible in the workarea.

Re-create configurations from the latest versions on a branch

Uses the latest versions on a specified branch as the basis for your new configuration version.

Branch Name

The name of the branch. Use the Browse button to locate the branch.

Re-create a custom configuration

Re-creates a custom configuration consisting of object versions from a variety of sources by specifying rules and configurations, choosing members, and incorporating externally referenced object versions.

Specify combinations of rules and configurations

Displays the Edit specification dialog box, enabling you to select rules and configurations on which to base the new configuration.

Just select objects from the repository

Displays the Members dialog box, enabling you to select objects from the repository to include or exclude from the configuration.

Refresh all existing members with their latest versions

Creates a new version of a configuration by refreshing the contents of an existing configuration with all the latest object versions.

Preview refresh list

Displays the Refresh List dialog box, enabling you to choose which members of the configuration you want to refresh. If you choose not to preview the refresh list, all existing members in the configuration are refreshed automatically.

Refine existing configuration

Enables you to create a new version of a configuration by adding new objects to an existing configuration. You can also delete objects or select different versions of objects in the configuration.


Configuration Wizard - Members

Related Topics

Displays the content of your configuration, and enables you to add repository objects to, or remove repository objects from, the configuration. You can also change the version of objects included in the configuration.

If you initialized the configuration with the contents of a file template specification or you based the configuration on a workarea or branch, the contents of these sources are displayed in this dialog box.

Members display area

List

Displays the configuration members in list format.

Name

The name of the object.

Version

The version of the object.

Version Label

The version label of the object.

Type

The type of the object.

Tree

Displays the configuration members in a tree structure.

Add Member

Displays the Add Configuration Members dialog box, enabling you to add objects to your configuration.

Remove Member

Removes the selected member from the configuration.

Change Version

Displays the Select Object Version dialog box, enabling you to choose an alternative version of the configuration member.


Configuration Wizard - External References

Related Topics

Enables you to display the List External References dialog box, listing any objects included in your configuration that reference objects that are currently not included in the configuration.

If the configuration does contain external references you can choose to include them using the External References utility.

List External References

Displays the List External References dialog box, listing any objects included in your configuration that reference objects that are currently not included in the configuration.


Configuration Wizard - Save

Related Topics

Allows you to choose whether you want to save and check in the configuration, or whether you want to just save the configuration.

Save and check in configuration

Displays the Check In dialog box, enabling you to save and check in the configuration.

Just save configuration

Saves the configuration.


Configuration Wizard - Save
Configuration Wizard - Summary

Related Topics

Displays a summary of the members of the configuration you have just created.

Configuration Name

The name of the configuration.

Configuration Members

Displays a list of the configuration members together with their details.

Name

The name of the object.

Version

The version of the object.

Version Label

The version label of the object.

Type

The type of the object.


Version - Purge Versions
Purge Versions (Version Menu)

Related Topics

Displays the Purge Versions dialog box, enabling you to do any of the following for a selected object:

•	purge a specific version

•	purge all insignificant versions

•	purge all insignificant versions from a particular branch

•	purge all versions

Object versions can be purged only if they are not visible in any other workarea. About

You can use the Version History Viewer to view which workareas use a particular object version.

Purge versions of this object from the repository

Indicates the object selected for purging.

Purge specific version

Removes only the object version that you select from the list.

Purge all insignificant versions

Removes all insignificant versions of the object from all branches.

Purge insignificant versions on branch

Removes all insignificant versions of the object from a branch that you select from the list.

Purge all versions

Removes all versions of the object from the repository. Use this option with caution, as it will destroy all evidence of the object.

Purge

Begins the purge operation.


Tools - Configuration Wizard
Configuration Wizard (Tools Menu)

Related Topics

Starts the Configuration Wizard, enabling you to create a new configuration or create a new version of an existing configuration. The Configuration Wizard is a predefined set of screen forms that take you step by step through the process of creating the configuration.

Configurations, like other repository objects, can be placed under version control. When you have completed the configuration you can choose to save and check in the configuration immediately, or just save the configuration.


Generic version selection dialog box

Displays details for each version of the selected object, and enables you to select the object version you want to use.

Version

The checkin branch and version number of the object, for example, MAIN:1.

Version Label

The version label of the object, for example, 1.3.


Refresh List dialog box

Related Topics

When you choose to create a new version of an existing configuration by refreshing all existing members with their latest versions, you have the option to preview the contents.

The Refresh list dialog box is displayed if you choose to preview the contents, enabling you to select the objects you want to be refreshed.

Configuration

The name of the existing configuration for which you are creating a new version.

Name

The name of the object in the configuration.

Version

The checkin branch and version number of the object, for example, MAIN:1.

Version Label

The version label of the object, for example, 1.3.

Refresh

Refreshes the selected objects in the configuration with their latest versions.

Select All

Selects all the objects in the list.


Options Menu

Related Topics

The Options menu contains options for customizing the display of the Version History Viewer. This menu is accessible only when running the Version History Viewer from the Command Line Tool.

Node Colors	Allows you to select the types of node to highlight in the version diagram and change the node colors to suit your personal preferences.
Hide Insignificant Nodes	Hides or shows the insignificant versions of the object. Insignificant versions include those that are not root or tip versions, are not branch parent versions, are not target or source versions in a merge operation, are not common ancestor versions, or are not the source of a checkout.
Show All Notes	Displays all notes associated with the version history diagram including branch labels and checkin notes.
Show Major Node Notes	Displays all notes associated with major nodes in the version history diagram including branch labels and checkin notes.
Hide Notes	Hides all checkin notes and branch labels.
Zoom Minimum	Changes the size of the nodes to the minimum size.
Zoom Maximum	Changes the size of the nodes to the maximum size.
Zoom Default	Changes the size of the nodes back to the default set by the tool.


Version - Check In
   Check In (Version Menu)

Related Topics

Checks in all the selected objects. You can specify checkin options and enter notes that you want to associate with the objects.

This option is valid only if the objects selected are either checked out or are not yet under version control. Checking in an object that is not yet under version control adds this object to version control.

Choosing this option displays the Check In dialog box.  About


Check In dialog box

Related Topics

Checks in all the selected objects. You can choose the branch to which you want to check in the objects as well as specifying checkout options and entering notes that you want to associate with the objects.  How

Objects selected for check in

Lists all objects selected for check in. These can include objects not under version control, objects mapped to a repository container but not uploaded to the repository, and checked-out objects.

Note:	All objects listed here, whether they are highlighted or not, will be checked in when you click OK.

(Not applicable when using the Version History Viewer as this tool operates within the context of only one object.)

Options for object_name

Current checkin branch

(Display only)  The name of the current checkin branch for this object. You can change the checkin branch in the Use branch field.

Use branch

For existing objects, enables you to check in this object to a branch other than the one from which you checked out the object. If the object was checked out locked by another user from a branch, you cannot check in your object version to that same branch.

For new objects, lists the branch to which the object will be checked in:

•	If no default checkin branch is set, the object is checked in to the MAIN branch.

•	If a default checkin branch is set, the object is checked in to the default checkin branch in addition to the MAIN branch.

(Not applicable when using the Version History Viewer as this tool operates within the context of only one object.)

Version label

The version label attached to each object when checked in. Depending on the repository policy, this version label can be generated automatically by the system, or defined by the user.  About

Use checkout notes

Determines whether you want to use the same notes for checkin that you specified for checkout.

Check out after checkin

Determines whether you want to check out the objects again immediately after checkin. This enables you to continue working on the object after ensuring that the latest version is available to other users.

If the objects were initially checked out with a lock, they will be checked out again with locks.

Check in even if unchanged

Determines whether the objects are checked in even if they have not changed since they were checked out.

Checkin notes

Any notes you enter here will apply to all the selected objects in the Objects selected for check in list.


Version - Check Out
   Check Out (Version Menu)

Related Topics

Checks out all the selected object versions. You can specify checkout options and enter notes that you want to associate with the objects.

This option is valid only if the selected object versions are checked in.

Choosing this option displays the Check Out dialog box.  About


Check Out dialog box

Related Topics

Checks out all the selected object versions. You can specify checkout options and enter notes that you want to associate with the objects.  How

Objects selected for check out

Lists the objects you have chosen to check out.

(Not applicable when using the Version History Viewer as this tool operates within the context of only one object.)

Options for object_name

Lock

Determines whether the object is locked when it is checked out. Locking the object prevents anyone else from checking in another version onto the same branch until the lock is removed.

If a strict locking policy is in force, you cannot change this option as the strict locking policy ensures that every checkout is automatically set to locked.

Check out latest

Determines whether the latest version of the object is to be checked out, regardless of the version that is selected. This option is dimmed if the latest version is already selected.

(Not applicable when using the Version History Viewer as this tool operates within the context of only one object.)

Version dependencies

Determines whether the dependency links to any objects referenced by this object are to be versioned as well (but not the referenced objects themselves).

Checkout notes

Any notes you enter here will apply to all the selected objects in the Objects selected for check out list.


Version - Check Out Contents
Check Out Contents (Version Menu)

Related Topics

Checks out all the object versions within a specified context (checks out the 'contents' of the context element).

Depending on the type of sub-context you can specify various options, including whether to recurse subcontainers, and whether to check out the context element itself. Examples of context elements are workareas and containers.

Selecting the Recurse subcontainer option checks out all subcontainers and their contents as well as the top level contents of the context element. Selecting the Check out sub-context itself option checks out the selected context element itself, as well as its contents.

For

Workarea

The name of the selected workarea. Use the Browse button to select an alternative workarea.

Sub-context

Enables you to select one of the following sub-context types:

•	Entire Workarea

•	Container

•	Configuration

•	Diagram

•	User-Defined Set

Enter the name of the selected sub-context in the adjacent field, for example, the name of the container for which you want to check out its contents. Use the Browse button to locate and select the sub-context element.

Recurse subcontainers

Determines whether all subcontainers for a selected container, together with their contents, are checked out.

This option is not applicable for workareas; if checking out the contents of a workarea, all objects within that workarea, regardless of which container they are in, are always checked out.

Preview checkout list

Determines whether the Preview Checkout dialog box is displayed before the checkout operation. This dialog box enables you to refine the selection of objects for check out by specifying which of the objects within a group of objects (sub-context) you want to check out.  About

Check out sub-context itself

Determines whether the sub-context element itself is checked out in addition to its contents.

This option is not applicable for workareas.

Check out system folder

Only applicable for workareas, this option determines whether the system folder is also checked out.


Version - Compare Previous Version
   Compare Previous Version (Version Menu)

Related Topics

Compares a version of an object with its immediately previous version, and displays the results of the compare operation in the Compare window.

The version of the object currently in the workarea view is indicated by an arrow in the Version History Viewer display area, if this tool is active for the object.


List Checkouts dialog box

Related Topics

Lists all the repository objects in a selected context that are checked out, are not under version control or are new file system files. Other details are also displayed where applicable, for example, object type, checkout and checkin dates and other version details. The selection of objects displayed is determined by the selection criteria you chose previously in the List Checkouts: Criteria dialog box.  About

From this dialog box you can also:

•	check in all or selected objects

•	undo a checkout

•	add new objects to version control (by checking in the objects)

•	compare an object version with its previous version

For

(Display only) The name of the selected workarea and sub-context (entire workarea, container type, configuration, diagram or user-defined set), and the default checkin branch (if any).

Object details

The following object details are displayed:

Name	The name of the object.
Predecessor Version	For objects already in version control, the details of the version from which the checkout was performed.
Version Label	The version label attached to the object version. Depending on the workarea rules, this version label may have been generated automatically by the system, or defined by the user.
Status	The object status: this can be Checked Out, Not Versioned or New File System File.
Type	The type of the object.
Date Checked Out	The date when the object was last checked out.
Checked Out By	The name of the user who last checked out the object.
New Query

Redisplays the List Checkouts: Criteria dialog box, enabling you to change the criteria determining which objects are displayed in the List Checkouts dialog box.

Check in

Checks in any objects selected in the list.

Undo Checkout

Undoes the checkout of any checked-out objects selected in the list.

Compare

Compares, with its previous version, a checked-out object selected in the list.

Select All

Selects all objects in the list.


Version - List Checkouts
List Checkouts (Version Menu)

Related Topics

Displays the List Checkouts: Criteria dialog box, enabling you to determine which of the objects within a selected context will have their details displayed in the List Checkouts dialog box.  About

For

Workarea

The name of the selected workarea. Use the Browse button to select an alternative workarea.

Sub-context

Enables you to select one of the following sub-context types:

•	Entire Workarea

•	Container

•	Configuration

•	Diagram

•	User-Defined Set

Enter the name of the selected sub-context in the adjacent field, for example, the name of the container for which you want to list checkouts. Use the Browse button to locate and select the sub-context element.

Show

Checked-out objects

Determines whether all checked-out objects for the selected workarea and sub-context are displayed in the List Checkouts dialog box.

Non versioned objects

Determines whether repository objects that have not been added yet to version control are displayed in the List Checkouts dialog box.

Non repository files

Determines whether objects mapped to a repository container but not uploaded to the repository are displayed in the List Checkouts dialog box.

Recurse subcontainers

Determines whether all subcontainers and their contents are displayed in the List Checkouts dialog box, in addition to the top level contents of the context element.

Checked out / Created

By me

Determines whether only those objects that are checked out by you, or created by you (but not added yet to version control), are displayed in the List Checkouts dialog box.

By anybody

Determines whether all those objects that are checked out by anybody, or created by anybody (but not added yet to version control), are displayed in the List Checkouts dialog box.


Preview Checkout dialog box

Related Topics

Displayed if you selected the Preview checkout list option on the Check Out Contents dialog box, this dialog box enables you to refine the selection of objects for check out by specifying which of the objects within a group of objects (sub-context) you want to check out.

For

(Display only) The name of the selected workarea and sub-context (entire workarea, container, configuration, diagram or user-defined set), and the default checkin branch (if any).

Object details

The following object details are displayed:

Name	The object name and path in the repository.
Version	The branch and version number for the object.
Version Label	The version label attached to the object version. Depending on the workarea rules, this version label may have been generated automatically by the system, or defined by the user.
Latest On Branch	Indicates whether the object version is the latest on the branch.
Type	The type of the object.
Check Out

Checks out any objects selected in the list.

Select All

Selects all objects in the list.


Version - Undo Checkout
   Undo Checkout (Version Menu)

Related Topics

Abandons (undoes) the checkout of all selected object versions. This reverts the object to the state it was in prior to being checked out.  About

List

The selected object versions for which you want to undo the checkouts.

(Not applicable when using the Version History Viewer as this tool operates within the context of only one object.)

Save filesystem changes (saved to <filename>.KEEP)

Displayed only if the selected object is a mapped file, this option saves any changes made since the object was checked out. By default, when you undo a checkout, any changes made since the object was checked out are lost. However, if a selected object is a mapped file, this option allows you to preserve the changes in a separate file. The file is called <filename>.KEEP, where <filename> is the name of the original file.


Version - View Version Events
View Version Events (Version Menu)

Related Topics

Displays the Version Event Viewer in which you can view event details of an object and its versions.  How

For each event you can view information including:

•	the type of event (checkin, checkout, locked, branched or merged)

•	the version label

•	the name of the object

•	the branch on which the version resides

•	the date the event occurred

•	the user who initiated the event

•	notes about the event


Version Event Viewer window

Related Topics

The Version Event Viewer displays details of all events that have occurred for an object.

You can re-sequence the information displayed and choose to display only selected information.  How

Note:	Any refinements of the details displayed are not reflected in the Event Viewer window until you click the Rescan button.

Event History for

The name of the object for which the events are displayed.

Start date field

The start date for any events displayed in the window. To activate this field, enable the Start date checkbox.

End date field

The end date for any events displayed in the window. To activate this field, enable the End date checkbox.

Start date checkbox

Activates the start date field, enabling you to specify a start date for any events displayed in the window.

End date checkbox

Activates the end date field, enabling you to specify an end date for any events displayed in the window.

Exclude Checkouts

Excludes any checkout event details. Checkout details are overwritten each time the object is checked in, so checkout details are only shown if the object currently has a checked-out version.

Report Key panel

Enables you to rearrange the report display and to include or exclude selected information from the display.

Display list

Displays a list of the details currently displayed in the report, including the order in which they are displayed and whether they appear in the left or right columns.

To add any additional details to the report, select the chosen detail from the drop-down list and click Add.

To remove or reorder any details, select the detail from this display list and click the appropriate button.

Drop-down list

A list of all possible event details that can be displayed in the report.

To add any additional details to the report, select the chosen detail from the drop-down list and click Add.

Add

Adds the detail selected from the drop-down list to the report.

Remove

Removes the detail selected in the display list from the report.

Higher

Moves the detail selected in the display list one position higher up in the order of details in the same column.

Lower

Moves the detail selected in the display list one position lower down in the order of details in the same column.

move Left

Moves the detail selected in the display list to the end of the left column.

move Right

Moves the detail selected in the display list to the end of the right column.

Rescan

Refreshes the display with the specified details.

Tabular list of events

Displays the specified details for each event in a tabular form.


Version - View Version History
  View Version History (Version Menu)

Related Topics

Displays the Version History Viewer in which you can view the version history of an object displayed in a graphical representation.  How

As well as viewing the full version history of an object, you can also:

•	check in object versions from, and check out object versions to, the context workarea

•	compare object versions

•	merge object versions

•	change the visible version of an object in the workarea


Version History Viewer window

Related Topics

The Version History Viewer displays the version history of an object in a graphical representation.  About

The Version History Viewer window contains the following:

Display Area	Displays a diagram made up of a number of nodes that correspond to each object version.
Status Panel	Shows information about the selected node.
Toolbar	Used to customize the display and provides shortcuts to the functionality available from the menus.


Generic Select dialog box

Displayed from the Browse button or automatically displayed when additional information is required for the current activity.

The title of the dialog box will depend on the context in which it is displayed.

Some features of the dialog box are displayed only if they are required in the particular context. For example the Select All button is displayed only if more than one object can be selected in one operation.

Look In

Displays the label for the area you are currently viewing and, where appropriate, enables you to move to another location in the hierarchy.

  Up One Level

Selects the level above the current level in the repository hierarchy.

  List View

Displays only the names of the repository objects in a multi-column list.

  General Details View

Displays the following general details about the objects in the list:

Name

The name of the object.

Type

The type of the object.

Attributes

The attributes (properties) of the object:

CI	checked-in
CO	checked-out
R	read-only
Modified

The date when the object was last modified.

Modified By

The username of the repository user who last modified the object.

  Version Details View

Displays the following version details about the objects in the list:

Name

The name of the object.

Type

The type of the object.

Attributes

The attributes (properties) of the object:

CI	checked-in
CO	checked-out
R	read-only
Version

The checkin branch and version number of the object, for example, MAIN:1.

Version Label

The version label of the object, for example, 1.3.

  Hierarchical View

Displays all the repository objects below the selected level. Objects are displayed with their path in the repository indicated.

  Flat View

Displays only the repository objects at the selected level in the repository hierarchy. In this view, double-clicking the name of a workarea or container displays the objects at that level.

Find elements that match these criteria

Available on some variants of this dialog box, these options enable you to move to a selected object. You can filter the list of objects displayed by name, type and version.

Name

The name of the selected object.

Type

The object type.

Version

The version of the selected object.


Set Context Workarea dialog box

Displayed when a checkout operation is performed from the Version History Viewer but the repository cannot determine the context workarea, this dialog box enables you to select a context workarea to which the object will be checked out.

All the workareas to which you have access are listed.

Select workarea

Enables you to select a workarea to make that workarea the context workarea.


Which configurations include this version dialog box

Related Topics

Available from the Version History Viewer,  [image]  displays the Which configurations include this version dialog box, listing all the configurations that include the selected object version.

Configurations

A list of all the configurations that include the selected object version.

Show version labels

Determines whether you want to display the version label for each configuration in the list.

When this option is not selected, the branch label is displayed for each configuration in the list.


Which workareas include this version dialog box

Related Topics

Available from the Version History Viewer,  [image] displays the Which workareas include this version dialog box, listing all the workareas that include the selected object version.

Workareas

A list of all workareas that include the selected object version.


Version History Viewer toolbar

Related Topics

The following toolbar buttons are available from the Version History Viewer:

Button	Description
	Updates the display area with any new information.
	Opens a dialog box displaying the version properties of the selected object version.
	Opens a dialog box displaying a summary list of configurations containing the selected version.
	Opens a dialog box displaying a summary list of workareas containing the selected version.
	Checks out the selected object version.
	Checks in the selected checkout.
	Undoes a checkout.
	Hides or shows the insignificant versions of the object. Insignificant versions include those that are not root or tip versions, are not branch parent versions, are not target or source versions in a merge operation, are not common ancestor versions, or are not the source of a checkout.
	Shows or hides the status panel at the bottom of the screen to allow more space for the version tree.
	Displays all notes associated with the version history diagram including branch labels and checkin notes.
	Displays all notes associated with major nodes in the version history diagram including branch labels and checkin notes.
	Hides all checkin notes and branch labels.
	Allows you to select the types of node to highlight in the version diagram and change the node colors to suit your personal preferences.
	Changes the size of the nodes and consequently the size of the entire diagram.


Version Properties dialog box

Related Topics

 opens the Version Properties dialog box for the selected version in the Version History Viewer.

Version name

The object name, branch name and position of the version on the branch.

Date created

The date and time the object version was created.

Created by

The username of the person who created the object version.

Status

The current status of the object version: checked in or checked out.

Notes

Notes that were added when the object version was checked in.


Checkout Properties dialog box

Related Topics

Displays the properties of the checkout selected in the Version History Viewer.

Original name

The object name, branch name and position on the branch of the original object version from which the selected version was checked out.

Date

The date and time when the object version was checked out.

Created by

The name of the user who created the object version

Notes

Any notes that were added when the version was checked out.


Version History Viewer display area

Related Topics

The Version History Viewer display area shows the version tree, a graphical representation of an object.  About

The version tree is made up of a number of nodes, each representing a single object version. Nodes are connected to other nodes by lines (or edges). The version tree includes all versions of the object and any branches and merges that may have taken place during development.

Notes entered at checkin or checkout are displayed beneath the node. They can be toggled on and off from the toolbar.

Depending on the version labeling policy, the name or the label assigned to each version is displayed inside the node. About

Version tree node colors

The following diagram illustrates the default node colors in the Version History Viewer. These colors can be customized to suit your personal preferences.  How

	Blue nodes represent the checked-out versions of this object. Red nodes are the leaf (or tip) nodes and are at the tip of each branch. They represent the latest version for that branch. Yellow nodes are major nodes. A major node is a node that corresponds with either the root of the branch, the parent node of a branch, or is a merge result node. The selected node is indicated by the blue cornered highlight selector. The node that is selected by this user’s workarea is marked with an arrow. The red triangle on the top left hand corner of node 1.3 indicates a marked node. Nodes are marked when they are being used in a compare or merge operation.  How


Version History Viewer Status panel

Related Topics

The Version History Viewer status panel at the bottom of the Version History Viewer window displays information associated with the selected node.

The status panel can be hidden from the display using the [image] button, so that more space is available for the display area.

Branch

The name of the branch to which the selected node belongs.  About

Version Label

The version label, which can be automatically generated or defined by the user.  How

Notes

These are optionally added to an object version when a checkout or checkin operation is performed. The note is a text string of a maximum 2000 characters. Full details of the note are available from the Version Properties dialog box.  How

Date Created

The date the object version was checked in to the repository.

Status

The three recognized states of a node are Checked in, Checked out, and Locked.


Compare window

Related Topics

The Compare window displays the results of a compare operation.

A compare operation involves a base object version and a contributor object version. The base object version is the version with which the contributor object version is compared.

The compare window consists of two panes separated by a resizing splitter. The left pane displays the contents of the base object version; the right pane displays the contents of the contributor object version.

Expanding or collapsing branches on the right pane will cause the corresponding branch on the left to expand or collapse.

You can scroll the screen vertically and horizontally using the scroll bars. Scrolling is synchronized so that corresponding items can be examined side by side.

Identifying differences between object versions

The compare display provides three ways in which differences between object versions can be identified:

•	Different text colors to represent additions, deletions and modifications.

•	Vertical bars to the left of each section of the object version to highlight what is being compared. The color of the block marker corresponds with the text color.

•	Icons to indicate the nature of the difference that exists between object versions:

Icon	Difference
	Added - An item has been added to the contributor version but not to the base version with which it is being compared.
	Deleted - An item has been deleted from the contributor version but not from the base version with which it is being compared.
	Update - An item is included in both the contributor and the base versions but the item is different in each version.


Merge window

Related Topics

The Merge window displays the results of a merge operation. A merge operation takes two contributor object versions (target and source), compares them to a common ancestor version, and uses internal rules to create a result based on changes found in all three versions.  About

The Merge window displays the differences and conflicts encountered by the merge algorithm. It also shows selections made by the algorithm, and lets you override those selections before the result is produced.

The Merge window appears in the following circumstances:

•	You attempt to do an automatic merge, and the merge algorithm encounters conflicts.

•	You explicitly ask for the Merge window to be displayed.

Difference blocks

The Merge window displays any differences in a series of difference blocks. A difference block shows the form that an item of data has in the contributor versions (source and target) and the common ancestor version, and indicates whether the item has been added, removed, or modified in one or both of the contributors with respect to the common ancestor. The difference might be:

•	A simple difference: a difference that the algorithm has been able to resolve using its own rules. In this case, the version containing the form of the item that the merge has selected to go forward to the result has its box selected. You can override the selection made by the algorithm by choosing an alternative form.

•	A conflict: a difference that the algorithm has been unable to resolve using its own rules. In this case, no contributor has its box selected. You must resolve the conflict by choosing the form of the item that you want to go forward to the result. If the conflict is for a file or for multi-line text, you can select more than one form of the comparison to go forward to the result; if the conflict is for structured repository object types, you can select only one.

Use the following menus to perform merge tasks:
File
View
Navigate
Merge
Help

The arrow toolbar buttons enable you to navigate through the lists of differences and conflicts.


Object Visibility dialog box

Related Topics

Displayed when you create an object in a checked-out container and check in the object for the first time, this dialog box warns you that the object being checked in may not be visible to other users until you check in the owning container.

To ensure that other users will be able to see the new object in their workareas (provided that the workarea specifications allow this), click OK and then check in the container.

Do not show this message again

Enables you to prevent the dialog box from being displayed every time you create and check in an object for the first time. Note that selecting this option hides the dialog box not only in the current working session, but also in all future working sessions.


Select Paths for Inherited Classes dialog box

Related Topics

Displayed when comparing or merging Oracle Forms (files with the .fmb, .olb or .mmb extension) that use subclassing or referenced objects, this dialog box enables you to define:

•	the scope: the workarea or configuration in which the Form versions participate

•	the path: the Forms path for the Form you want to compare or merge

Note that when comparing or merging Oracle Forms that use subclassing or referenced objects, you must ensure that:

•	each of the Form versions you are comparing or merging is in a different workarea or configuration

•	the Forms path exists in every workarea or configuration used for the comparing or merging operation

•	the files on the paths are uploaded into the repository  How

The options displayed in the dialog box differ according to whether you are comparing or merging Oracle Forms.

• Comparing Oracle Forms	The options enable you to enter the scope and path for the contributor and base object versions.
• Merging Oracle Forms	The options enable you enter the scope and path for the target, source and ancestor object versions.
Options displayed when comparing Oracle Forms

For

The name of the Form for which you are defining additional information.

Contributor Form

Information about the contributor Form version for this compare operation.

Workarea

Indicates whether or not the scope of the compare operation is for a workarea in which the contributor Form version participates.

Configuration

Indicates whether or not the scope of the compare operation is for a configuration in which the contributor Form version participates.

Name

The name of the workarea or configuration in which the contributor Form version participates. Select the name of the workarea or configuration from the list of those in which the contributor Form version participates.

Path

The Forms path for the contributor Form version. The path defaults to one previously used by the Form, but can be changed by the user. Paths should be defined relative to the root. Specify the path without any version information, and use a semicolon for separating multiple paths.

Base Form

Information about the base Form version for this compare operation.

Workarea

Indicates whether or not the scope of the compare operation is for the workarea in which the base Form version participates.

Configuration

Indicates whether or not the scope of the compare operation is for the configuration in which the base Form version participates.

Name

The name of the workarea or configuration in which the base Form version participates. Select the name of the workarea or configuration from the list of those in which the base Form version participates.

Path

The Forms path for the base Form version. The path defaults to one previously used by the Form, but can be changed by the user. Paths should be defined relative to the root. Specify the path without any version information, and use a semicolon for separating multiple paths.

Options displayed when merging Oracle Forms

For

The name of the Form for which you are defining additional information.

Target Form

Information about the target Form version for this merge operation.

Workarea

Indicates whether or not the scope of the merge operation is for the workarea in which the target Form version participates.

Configuration

Indicates whether or not the scope of the merge operation is for the configuration in which the target Form version participates.

Name

The name of the workarea or configuration in which the target Form version participates. Select the name of the workarea or configuration from the list of those in which the target Form version participates.

Path

The Forms path for the target Form version. The path defaults to one previously used by the Form, but can be changed by the user. Paths should be defined relative to the root. Specify the path without any version information, and use a semicolon for separating multiple paths.

Source Form

Information about the source Form version for this merge operation.

Workarea

Indicates whether or not the scope of the merge operation is for a workarea in which the source Form version participates.

Configuration

Indicates whether or not the scope of the merge operation is for a configuration in which the source Form version participates.

Name

The name of the workarea or configuration in which the source Form version participates. Select the name of the workarea or configuration from the list of those in which the source Form version participates.

Path

The Forms path for the source Form version. The path defaults to one previously used by the Form, but can be changed by the user. Paths should be defined relative to the root. Specify the path without any version information, and use a semicolon for separating multiple paths.

Common Ancestor Form

Information about the common ancestor Form version for this merge operation.

Workarea

Indicates whether or not the scope of the merge operation is for the workarea in which the ancestor Form version participates.

Configuration

Indicates whether or not the scope of the merge operation is for the configuration in which the ancestor Form version participates.

Name

The name of the workarea or configuration in which the ancestor Form version participates. Select the name of the workarea or configuration from the list of those in which the ancestor Form version participates.

Path

The Forms path for the ancestor Form version. The path defaults to one previously used by the Form, but can be changed by the user. Paths should be defined relative to the root. Specify the path without any version information, and use a semicolon for separating multiple paths.


Merge Confirmation dialog box

Related Topics

Lists the source and target for the merge operation, and enables you to choose whether you want to preview the merge results in the Merge window, or perform an automatic merge if there are no conflicts.

If merging binary files other than Oracle Forms, the merge operation does not compare the source and target versions but instead copies the contents of the source over the contents of the target. When merging binary files, this dialog box does not therefore display the Use Merge window and Perform automatic merge options but instead displays a message informing you that the merge will copy the source file over the target file.

Source

The source object version for the merge operation: the version which is merged with the target.

Target

The target object version for the merge operation: the version into which changes made in the source are to be merged.

Use Merge window

Displays the Merge window listing the differences and conflicts encountered by the merge algorithm and the selections made by the algorithm, and letting you override those selections before the result is produced.

Perform automatic merge

Performs an automatic merge if there are no conflicts. The Merge window is displayed only if there are conflicts between object versions, so enabling you to resolve the differences; otherwise the Merge window is not displayed.


File Menu

Save

Merges the selected data into an updated form of the target and saves the result.

Exit

Exits from the tool.


View Menu

Toolbar

Shows or hides the standard toolbar below the menu bar.


Navigate Menu

Previous Difference

Navigates to the previous difference in the window.

Next Difference

Navigates to the next difference in the window.

Previous Conflict

Navigates to the previous conflict in the window.

Next Conflict

Navigates to the next conflict in the window.


Merge Menu

Select Source

Selects the source from the difference block currently in focus.

This menu option will be only be available when a difference block is currently in focus in the Merge Window.

Select Target

Selects the target from the difference block currently in focus.

This menu option will be only be available when a difference block is currently in focus in the Merge Window.

Select Common Ancestor

Selects the common ancestor from the difference block currently in focus.

This menu option will be only be available when a difference block is currently in focus in the Merge Window.


Help Menu

Help Topics

Displays a list of the main subject areas in the online documentation system.

About

Displays copyright and version number information about this application. You might need to know the version number for product support purposes.


Edit - Undo/Redo
Undo/Redo (Edit Menu)

Related Topics

Undoes the last action performed on the active window. Only certain actions can be undone. If the last action was performed using Edit→Undo, and the action can be redone, the menu option changes to Edit→Redo.


Edit - Cut
Cut (Edit Menu)

Related Topics

Removes the selection and places it on the Clipboard. Any text and graphics that you place on the Clipboard remains there until you replace it with a new item. The contents of the Clipboard can be pasted back using Edit→Paste. This option does not remove data from the repository.

Note:	When working in the Property Palette, the changes you make are not immediately stored in the repository. The changes will only be committed to the repository when you change the focus (by making another window active in the application) or by saving recent property changes.


Edit - Copy
Copy (Edit Menu)

Related Topics

Copies the selection onto the Clipboard. Text or graphics that you copy to the Clipboard replaces the previous contents. The contents of the Clipboard can be pasted back using Edit→Paste.


Edit - Paste
Paste (Edit Menu)

Related Topics

Inserts the contents of the Clipboard at the insertion point, replacing any selection if the selected text or graphic can be replaced. To place items on the Clipboard use Edit→Copy or Edit→Cut.


Edit - Edit Workarea
Edit Workarea (Edit Menu)

Related Topics

This option enables you to perform various workarea operations. About

Note:	In the Repository Object Navigator, this option is available when you select the name of the workarea in the Navigator window, or when you select an object visible in that workarea.

You can:

•	edit the workarea properties (name, description)

•	edit the workarea specification (the rules and configurations that determine which objects appear in the workarea)

•	specify a default checkin branch for versioned objects in a particular workarea

In either case, the menu option starts the workarea wizard at the appropriate point.


Edit - Refresh Workarea
Refresh Workarea (Edit Menu)

Related Topics

Enables you to reapply the workarea specification rules, updating the display of the workarea contents as a result.

This option displays a dialog box from where you can:

•	synchronize the repository with a file system

•	preview the changes that will be made before refreshing

Refreshing re-evaluates the workarea contents according to the workarea rules specified. For example, if a rule specifies that the workarea is to include the latest object versions on a particular branch and a user has updated an object on that branch, refreshing the workarea will show the new version of the object.

Dialog box options

Synchronize

Synchronize mapped folders/files after refresh

Synchronizes the repository with a file system to which a container in the workarea is mapped. Selecting this box performs the synchronization when the workarea is refreshed.

Include (create) files new to the repository

If synchronization would normally result in the creation of new files in the repository, selecting this box causes this to happen. Clearing the box prevents creation of new repository files (i.e., only files that have been changed will be refreshed). This box is activated only if you select the previous one.

Preview

Preview changes before refreshing

Select this box if you want to see the effect on the workarea of the refresh operation before it is performed, otherwise leave the box clear. The preview lists which objects will be added to, updated in, and removed from, the workarea when it is refreshed.


Preview Changes in Workarea Before Refreshing dialog box

Related Topics

Dialog box options

Changes in repository

If you chose on the previous screen to preview changes in both the repository and the file system, you can choose between the two options here.

New

Lists the objects that will be added to the workarea when it is refreshed.

Changed

Lists the objects that will be updated in the workarea when it is refreshed.

Removed

Lists the objects that will be removed from the workarea when it is refreshed.


Edit - Requery All
   Requery All (Edit Menu)

Related Topics

Compares all the elements displayed in the active window with their repository elements and, if there are differences, makes the display consistent with the repository.


Edit - Requery Selection
   Requery Selection (Edit Menu)

Related Topics

Compares one or more selected elements in the active window with their repository elements and, if there are differences, makes the diagram consistent with the repository. This option is dimmed if no elements are selected in the active window.


Edit Workarea Wizard: Properties

Enables you to rename a workarea and change the workarea description.

The workarea you are currently working in is the one selected for editing.

Note: 	You cannot select an alternative workarea to edit using this window.

If you choose to rename your workarea, the new name must be unique in the repository.

Dialog box options

Name

The name of the workarea selected to edit. You can enter a new unique name to rename the workarea.

Description

The description of the workarea selected to edit. You can enter a new description.


Create / Edit Workarea Wizard: Rules Specification

Displays the rules, configurations or both that make up the current workarea specification.

Using this dialog you can:

•	load an existing workarea specification from a template file in your file system

•	edit the workarea specification

•	save the workarea specification to a file

If you are creating a new workarea by using a specification file or by copying an existing workarea, any included rules and configurations are displayed.

If you are creating a custom workarea and have not specified any other workarea or specification file as its basis, the default rule LATEST(MAIN) is displayed.

If you are editing an existing workarea, any rules and configurations associated with the workarea are displayed.

Dialog box options

Load from file

(Edit Workarea Wizard only) Enables you to load an existing specification from a file. Specification files are given the .CWS extension by default.

Edit

Displays the Edit Specification dialog box for you to edit the current specification by:

•	adding new rules and/or configurations to the specification

•	deleting rules and/or configurations from the specification

•	rearranging rules and/or configurations within the specification

Save to file

Allows you to save the specification to a template file in your file system. The file is assigned the .CWS extension unless you choose otherwise.


Edit Specification dialog box

A workarea specification or a configuration can be built from objects from a variety of sources. For example, you may base a configuration on the contents of a workarea and then include an existing configuration together with additional rules and specific versions of individual objects.

The Edit Specification dialog box allows you to do the following to the selected workarea specification or configuration:

•	add or remove rules

•	add or remove configurations

•	reorder the list of included rules and configurations

•	include or exclude specific objects

Dialog box options

For

Displays the name of the workarea or configuration whose specification you are editing

Rules tab

Enables you to select a rule to include in the list of member rules and configurations.

The fields displayed on the Rules tab depend on the selected rule. About

Configurations tab

Latest version

When checked, displays only the latest version of the configurations to which you have access. When clear, displays all versions of all configurations.

Configurations

Displays all configurations under version control that you have access rights to.

Filter

Allows you to enter search criteria to locate specific configurations. You can use wildcard characters, for example "%" to specify "any character".

	moves selected rule or configuration into the Member rules and configurations list
	moves selected rule or configuration out of the Member rules and configurations list
Member rules and configurations

Lists the rules and configurations currently associated with the workarea or configuration.

	moves the selected rule or configuration up one position in the member rules and configurations list
	moves the selected rule or configuration down one position in the member rules and configurations list
	includes objects in the workarea or configuration
	excludes objects from the workarea or configuration


Create / Edit Workarea Wizard: Default Checkin Branch

Displays all branches available to you, and enables you to set the default checkin branch.

The value <None> causes objects to be checked in by default on the branch from which they were checked out. In some cases, described below, the wizard sets this value automatically and you cannot change it.

If you want to use a branch other than those listed, create a new branch. How

If you are creating a default workarea or a workarea based on a specification file, the wizard selects the value <None>.

If you are creating a workarea based on an existing workarea, the default checkin branch for the workarea you are copying is selected.

If you are editing a selected workarea, the current default checkin branch for that workarea is selected.

Before setting the default checkin branch, the wizard checks the repository automatic branching policy. If the automatic branching policy is not enabled, the wizard selects the value <None>.

Dialog box options

Select the workarea default checkin branch

All available checkin branches for the repository are listed. Select the one you want to use as the default.

Remind me to merge objects to the new checkin branch

(Displayed for Edit Workarea only) Invokes the Merge Wizard at the end of an edit workarea operation. If you are changing the default checkin branch, you can use the wizard to merge changes from object versions on the old branch with versions on the branch to which you are changing.


Edit - Requery
Requery (Edit Menu)

Refreshes the version tree for the object currently displayed in the Version History Viewer, enabling you to see any recent changes that have been made.


Listing external references

For certain operations it is very useful to know details of which objects in a particular context (a workarea, container or configuration) make reference to objects outside that context. For example, when exporting a set of objects that make up a configuration, you may want to check whether external references exist in the set, so you can ensure that the exported set is complete.

You can check whether external references exist for an object in its current context and, if necessary, include the referenced objects in that context.

To list external references:

1.	Select the workarea, container or configuration for which you want to list the external references, depending on the current tool.

2.	Choose Utilities→External References.

3.	If you want the display to show only the mandatory references, select List Mandatory Only and click List.

4.	If you want the display to also show external references for child objects of this workarea, container or configuration (for example, subfolders of a folder), select Recurse Sub Folders.

5.	If you want to include one or more listed objects in the context workarea, container or configuration, select those objects and click Include.

If you want to include all the listed objects, click Select All, then click Include.

Alternatively, if you want to include an object and all objects referenced by it (and so on until all references are exhausted):

a.	Select the object in the list.

b.	Select the Include Iteratively check box.

c.	Click Include.

6.	If the context is a workarea or configuration and you want to list objects from a checkin branch other than the default, choose the branch from Show Latest on Branch (this does not appear if the context is a container).

7.	If the context is a workarea or configuration and you want to display a different version of a listed object:

a.	Select that object in the list.

b.	Click Change Version.

c.	In the Select Object Version dialog, select the version you want to display and click OK.

8.	If you want to know which objects reference a listed object and the kind of reference they make to it, select the object in the list and click List References.


Updating columns/attributes in a domain

You can update all the columns/attributes in a selected domain with the property details of that domain. You may want to do this when you edit a domain and want to update all the columns/attributes that use that domain.

This utility overwrites any properties in a column/attribute that conflict with the same property in the column's/attribute's domain. Null values in the domain replace any non-null values. The exception to this is the Default Values property, which is overwritten only if the corresponding column/attribute property has a null value.

To update columns/attributes in a domain:

1.	Select the domain for which you want to update columns or attributes.

2.	Choose Utilities→Update Columns/Attributes in a Domain.

Note:	From the Repository Object Navigator, choose Utilities→Designer→Update Columns/Attributes in a Domain.

The columns/attributes in the domain that you select will be updated with the values held in that domain.


Publishing diagrams

Use these procedures to publish Designer diagrams to the Repository Object Browser (ROB) or to save them as files.

To publish diagrams to the ROB:

1.	From the Design Editor, choose Utilities→Publish Diagrams.

The Publish Diagrams dialog opens.  The diagrams available for publishing are listed beneath the directories in the Available Diagrams pane.

2.	Use the arrow keys to populate the Selected Diagrams pane with the diagrams that you want to publish.

3.	In the Destination group, choose Publish to Repository Object Browser.

4.	From the Publish Format drop-down list, choose a file format for the published diagrams.

5.	To publish the selected diagrams to the ROB, click OK.

A progress dialog appears, showing the name of the diagram currently being published.  If you want to cancel the publish diagrams operation, click Cancel.  The operation will be cancelled after the current diagram is published.

The time taken to publish a diagram will be the same as the time taken by a diagrammer to open the diagram.

At the end of the process, the selected diagrams will be published to the ROB in the specified format.

To publish diagrams as image files:

1.	From the Design Editor, choose Utilities→Publish Diagrams.

The Publish Diagrams dialog opens.  The diagrams available for publishing are listed beneath the directories in the Available Diagrams pane.

2.	Use the arrow keys to populate the Selected Diagrams pane with the diagrams that you want to publish.

3.	In the Destination group, choose Publish to File.

The File Name text box is enabled, and shows the default file name of the diagram that is currently highlighted in the Selected Diagrams pane.  Selecting a diagram in the Selected Diagrams pane will show its default file name in the File Name text box.  You can change a default diagram name by overtyping it.

The Directory text box is enabled.  Type in the name of the directory to which you want the diagrams to be published, or use the Browse button to choose an existing directory.

4.	From the Publish Format drop-down list, choose a file format for the published diagrams.

5.	To publish the selected diagrams as files, click OK.

A progress dialog appears, showing the name of the diagram currently being published.  If you want to cancel the publish diagrams operation, click Cancel.  The operation will be cancelled after the current diagram is published.

At the end of the process, the selected diagrams will be published to the chosen folder in the specified format.


Copying elements with new languages

Related Topics!Alink(COM_Copying_elements, , , )

When you have created module definitions in the repository, you may want to use them as the basis for new elements of a different language. For example, you may want to use an Oracle Forms module, as the basis for a Visual Basic module.

The Copy With New Language utility helps you to create new elements with different languages, by automatically removing information that is not relevant for the target language.

With the introduction of reusable module components (which can be made private), The use of the copy utility to create copies of module components is now redundant. If you need to copy a common definition of a module component to different modules, then make the module component reusable. However if you wish to diversify that definition then make the inclusion of the reusable module component private.

To copy an element with a new language:

1.	Select the module that you want to copy.

2.	Choose Utilities→Copy With New Language.

3.	Specify the name and language of the new module that is to be created.


Mapping unbound items to database columns

During application design you can record details about the items that are to be displayed and used by a generated application. You can record details about items that map directly to a single database column, by creating bound items in the repository. You can also record details about items whose values cannot be derived from a single database column, by creating unbound items in the repository.

You can change an unbound item into a bound item, by mapping the unbound item to a database column.

Note:	You cannot change a bound item into an unbound item.

To map unbound items to database columns:

1.	Select one or more unbound items.

2.	From the Select Binding for Unbound Items dialog box , use the Column dropdown lists to identify the database column to which each unbound item will be mapped.


Utilities - Copy with new language
Copy with New Language (Utilities Menu)

Related Topics

Creates a new module definition as a copy of an existing definition. The new module component must be based on a different language to the element from which it was copied. For example, you can create a Visual Basic module that is based on an existing Oracle Forms module.

Note:	This utility is specifically for creating copies of definitions with different languages. To copy a definition without changing the language, choose Utilities→Copy Object.

Dialog box options

Short Name

A display only field that identifies the short name of the module that you want to copy. The definition must be a module.

Language

A display only field that identifies the language of the definition that you want to copy.

New Short Name

Identifies the short name of the new definition that is to be created.

New Language

Identifies the language of the new definition that is to be created. The list shows the languages from which you can choose. Notice how the language of the definition from which you want to make the copy is not shown in the list.


Utilities - Map Unbound Items
Map Unbound Items (Utilities Menu)

Related Topics

Changes unbound items into bound items. Unbound items are those which are not mapped directly to a database column.

The database columns are identified using the module component table usage alias and the column name, for example Dept.Deptno, where Dept is the table usage alias and Deptno is the column name. Additionally, the type and length of the database column are displayed in brackets after the name, for example Dept.Deptno (VARCHAR2 240).

Dialog box options

Unbound Items

Lists all of the unbound items for a selected module component.

Columns

Lists the database columns to which each unbound item can be mapped. This list is derived from the underlying columns of the tables that are used by the module component. For example, if a module component has a base and a lookup table usage, the columns for both of those table usages are listed.

This list is empty if no table usages have been defined for the module component.

If <NULL> is shown as the column value, then the unbound item will not be mapped to a column.


Viewing the Navigator window

Selecting objects in the Navigator

Navigating to a named object

Navigating to and from a referenced object

Expanding objects in the Navigator

Collapsing objects in the Navigator

Setting bookmarks


Dragging and dropping repository objects

When used in the Navigator window, the Windows drag-and-drop feature enables you to

•	copy an object from one container to another

•	move an object from one container to another

•	delete an object from a container

•	create a shortcut from one container to another

•	upload files or directories from a file system to the repository

Note:	Apart from upload, drag-and-drop can be used only on objects within the same workarea.

Method	Effect
Drag-and-drop between containers	Creates a shortcut (identified by the [image] icon) in the destination container to an object in the source container
SHIFT+drag-and-drop between containers	Moves an object from the source container to the destination container
CTRL+drag-and-drop between containers	Copies an object from the source container to the destination container
Drag-and-drop from container to wastebasket	Deletes an object, removing it from the container (the object can be restored from the wastebasket)
Drag-and-drop from Windows Explorer to Navigator window	Uploads files or directories to the repository


Finding objects or properties by name

To find a text string in the Navigator window or Property Palette, you can search for the next or previous occurrence of that text string (not case-sensitive). Note that you cannot search a TextPad window.

The first item that contains the text string starting at any character position is highlighted. Thus, for example, if you specify the string "def", expecting to find the word "definition", you could find that a node or property containing "indefinite" is highlighted first.

Note:	In the Navigator window, the search is effective only on items that are currently visible or which have been expanded in the current session.

An alternative method is to search the entire repository.  How

To search for objects or properties by name :

1.	Select the window in which you want to search (Navigator or Property Palette).

2.	Indicate the start point of the search by selecting an item (for example, when searching up, the last node in the Navigator window, or the last property in the Property Palette).

3.	Choose Navigator · Find.

4.	In the Find text box enter the text string for which you want to search.

5.	Choose the direction of the search by selecting Up (to search from the start point to the top of the window) or Down (to search from the start point to the end of the window).

6.	To find the first occurrence of the text string in the specified direction click Find Next. To find the next occurrence of the text string (depending on the search direction you have chosen) continue to click the Find Next button.

To search from the main toolbar:

1.	Select the window in which you want to search (Navigator or Property Palette).

2.	Indicate the start point of the search by selecting an item (for example, when searching up, the last node in the Navigator window, or the last property in the Property Palette).

3.	In the toolbar text box (just to the left of the [image] button), begin entering the text string for which you want to search. The first match for the specified text string is selected automatically as soon as possible.

4.	To find the next occurrence of the text string, click the [image] button. Alternatively, continue typing more of the string in the text box.

5.	To find the previous occurrence of the text string, click the [image] button.


Searching the repository

Related Topics

You can search for any repository object across the entire repository, within a particular workarea, or within a particular container in a workarea.

You can perform simple searches, for example by object name, or more advanced searches using complex search conditions. You can also restrict the search to repository objects of a particular type, for example, column, index and so on. It is possible to search for a particular object by name, or to search for all objects with one or more properties that correspond to specified conditions.

The results of the search are displayed in a separate window, which shows brief details about the objects found. The Search Results window also allows you to locate the objects in the Navigator window by means of the right mouse menu.

To search the repository:

1.	In the Navigator window:

a.	(Optional) Select a workarea or a container in which to search.

b.	Click [image] in the main toolbar.

2.	In the Repository Search dialog box, choose Entire Repository or Workarea to set the scope of the search.

3.	If you choose Workarea, type the name in the adjacent field (or use the Browse button to locate and select a workarea).

4.	(Optional)  If you want to restrict the search to a particular container and did not select one in step 1, type its name in the Folder Path field (or use the Browse button to locate and select a container).

5.	Choose an option button under For Types. To search for:

•	uploaded files, choose the Files option button

•	objects by one or more element types, enter these types in the Type Names field (or use the Browse button to locate and select one or more element types)

•	objects under one or more categories, choose Categories and select one or more of the check boxes About

Note:	In the Type Names field, if you are searching on a single element type you need enter only enough letters of the element type name to distinguish it uniquely from the other available types. If you are searching on more than one element type, enter each type name enclosed in double quotation marks and separated by a space character.

6.	Set any further search criteria, all of which are optional:

•	To search for an object by name, complete the Name field. You can use the % wildcard to search on a partial name.

•	To search for an object by short name, complete the Short Name field. You can use the % wildcard to search on a partial short name.

•	To search for an object using its internal globally unique identifiers (GUIDs), select the Search on GUIDs check box, then complete either or both of the IRID (object identifier) and IVID (version identifier) fields that are displayed as a result. You can use the % wildcard to search on a partial identifier.

•	Select the Match Case check box if you want a case-sensitive search to be performed on the values in the Name and Short Name fields, and the data fields in the dialog boxes displayed by the Version, Audit and Advanced buttons.

•	Select the Display GUIDs check box if you want the Search Results window to display the value of the internal object identifiers that match the specified search conditions.

•	Select the Search Subfolders check box if you want the search to extend to any subcontainers of containers named in the Folder Path field.

•	To search on version details of an object, click Version and specify the version details. You can search on the version status (checked in, checked out or not versioned), on the version label or on the checkin branch.

•	To search on the audit properties of an object, click Audit and specify the audit properties. You can search on: date created, date last modified, date format, user who created the object, user who last modified the object, and the number of times the object has been modified.

•	To perform an advanced search based on precisely specified conditions, click Advanced and specify the conditions. How

•	Click the Count Hits button to see the number of matches, if any, for the search conditions. With a large repository, this can indicate whether you need to refine the search conditions before executing the query.

•	Click the SQL button to display the SQL statements that are generated by the search conditions. Optionally modify these and click Execute to perform the search.

7. 	Click Search to display details of the objects that match the search conditions.

In the Search Results window, you can:

•	click a heading to display the entries organized alphabetically by that heading

•	select an object to display its properties in the Property Palette

•	select an object, then choose "Locate object in Navigator" from the right mouse menu to display that object in the Navigator window


Specifying repository search or filter conditions

Objects are selected by a search or filter operation if they match specified conditions. You specify conditions based on one or more properties.  About

To specify conditions for a search or filter:

1.	In the Condition field of a property you want to use, type the property value. Use wildcard characters as desired.

Note:	Conditions are case-sensitive, so for example the condition "ABC" is not the same as "abc".

2.	If you want to specify more than one condition for the same property, see "To specify alternate conditions for a property" later in this topic.

3.	If you want to use more than one property value in the search or filter conditions:

a.	Click the name of the next property you want to use, so that the line is highlighted.

b.	Optionally click [image] or [image] on the toolbar to specify the logical operator. If this field is blank, AND is assumed.

c.	In the Condition field, type the property value.

d.	Repeat steps a. to c. for any further properties you want to use in the search or filter operation.

To specify alternate conditions for a property:

1.	In the Condition field of the property you want to use, type the first value. Use wildcard characters as desired.

2.	Click [image] in the toolbar.

3.	Click the name of the duplicate property, so that the line is highlighted.

4.	Optionally click the [image] or [image] on the toolbar to specify the logical operator. If this field is blank, AND is assumed.

5.	In the Condition field of the highlighted line, type the next value. Use wildcard characters as desired.

6.	Repeat steps 2 to 5 for any further conditions you want to specify for this property.

To group properties together:

1.	Grouped properties must be adjacent. If necessary, move a property up or down the list as follows:

a.	Click the name of the property you want to move.

b.	Click the [image] or [image] buttons as many times as required.

c.	If necessary, repeat a. and b. for other properties.

2.	Click the name of the first property in the group.

3.	Hold down the SHIFT or CTRL key and click the name of the last property in the group.

4.	Click [image] in the toolbar.

The characters "(" and ")" enclose the first and last properties to indicate the extent of the group.

To clear a condition:

1.	Click anywhere on the line containing the condition you want to clear.

2.	Click [image] in the toolbar.

To clear a property group:

1.	Click the Property field of the first property in the group.

2.	Hold down the SHIFT or CTRL key and click the Property field of the last property in the group.

3.	Click [image] in the toolbar.


More about search or filter conditions

Case sensitivity

Conditions are case-sensitive, so for example specifying the condition ABC is not the same as specifying abc.

Wildcard characters

You can use wildcard characters in the selection conditions. For example, to select all items of the specified type whose name begins with A, type A% in the Condition field against the Name property.

Comparison operators

You can use comparison operators in the conditions. For example, to select objects that have been created since 1st January 1999, type >1-JAN-99 in the Condition field against the Creation Date property. To select objects that have been created in the last week, type >(SYSDATE-7) in the Condition field against the Creation Date property.

Logical operators

If you base the selection on more than one property, you use the logical operators AND and OR to specify how the selection is to proceed. For example, to select an item of which either the name or the short name is ABC, type ABC under Condition for both the Name and Short Name properties, and specify OR in the AndOr field against Short Name.

Condition groups

You might need to group conditions together if you are specifying particularly complex conditions. This is because the conditions generate a SQL query, which might require parentheses in order to run correctly. Grouping conditions together ensures that the parentheses are generated.

Use of SQL for greater precision

If you need a greater degree of precision in the search than is allowed by the dialog box fields, you can click the SQL button and customize the query to your needs. Doing so allows you, for example, to use other comparison operators such as [NOT] BETWEEN x AND y or IS [NOT] NULL.


Object search categories

The categories that you can specify when performing a search operation are:

Category	Includes
Object types	All repository element types
Named child types	All named references and secondary access controlled (SAC) elements
Built in types	All standard (factory-supplied) element types
User types	Not used in this release


Search Results

The results of your search operation are displayed in this window. You can:

•	click a heading to display the entries organized alphabetically by that heading

•	select an object to display its properties in the Property Palette

•	select an object, then choose "Locate object in Navigator" from the right mouse menu to display that object in the Navigator window

 (Icon View)

Displays the names of the repository items in a multi-column list.

 (List View)

Displays the names of the repository items in a single column list.

 (Details View)

Displays various general details about the items in the list:

Path

The path of this object in the repository hierarchy.

Type

The element type for this object.

Name

The object name.

Version

For a versioned object, the object version displayed in the format
branch_name;version_number.

Version Label

For a versioned object, the version label of the object.


Showing or hiding type headings

You can control whether element type headings are displayed for objects shown in the Navigator window. You can choose whether to display all the headings, never display them, only display them for objects if objects of that element type appear in the Navigator window, or only display them for a container if the container has objects of more than one element type.

You can also choose whether to display ancillary details such as usages (whether an object is referenced by another object) or inclusions (for example, whether an object is included in a workarea or configuration).

To display or hide the type headings:

1.	Choose Navigator · Show/Hide.

2.	From the dropdown list, choose the category for which you want to show or hide the headings:  objects (primary access controlled (PAC) elements), folders (containers) or child elements (secondary access controlled (SAC) elements, usages etc.)

3.	Choose the option button corresponding to how you want the headings to be displayed or hidden.

4.	Repeat steps 2 and 3 for any other categories you want to amend.

5. 	(Optional) Select or clear the check boxes according to how you want inclusions, usages and files in mapped containers to be displayed.


Setting the options file

User-defined data such as filters, customized groups and customized views are stored in a file known as the options file. By default, this file is named CKMETA61.OPT and is stored in the working directory (by default, this is the Oracle_home\BIN directory, where Oracle_home is the directory where the Oracle software is installed).

You can choose a different options file if desired. For example, someone at your site may have defined a set of options that are to be made available to all users.

To set the options file:

1.	Choose Options→General Settings.

2.	In the General Settings dialog box, enter the name of the file in the Options File field, or use the Browse button to locate the file.


Setting the date format (Repository Object Navigator)
Setting the date format

You can set the format in which dates are displayed in the Property Palette for items such as the audit properties.

To set the date format:

1.	Choose Options→General Settings.

2.	In the General Settings dialog box, enter the desired format in the Date Format field, for example, DD-MON-YY or MM-DD-YY.


Including objects in a workarea

If you are using version control, you can include checked-in versioned containers or repository objects in a selected workarea from anywhere in the repository. About

Note that you cannot include items that are not under version control.

To include objects in a workarea:

1.	In the Navigator window, select the name of the workarea in which you want to include the objects.

2.	Choose Edit→Include in Workarea.

3.	In the Include Container or Object Version in the Workarea field, enter the names of the versioned containers or objects that you want to include, enclosing each name in double quotation marks and separating them with spaces.

Alternatively, use the Browse button to locate versioned containers or objects for inclusion, repeating as necessary.

4.	If you do not want to refresh the workarea immediately, uncheck the Refresh Workarea Now? box. Refreshing the workarea makes the newly included objects visible in the workarea.

5.	Click OK. If you chose to refresh the workarea immediately:

a.	(Optional) To synchronize the repository and the file system when you refresh the workarea, select Synchronize.

b.	(Optional)  To see the effect of refreshing the workarea before you perform the operation, select Preview Changes Before Refreshing. You can choose to see the effect simply on the repository, or (if the repository contains uploaded files) the effect on both the repository and the file system.


Excluding objects from a workarea

If you are using version control, you can exclude checked-in versioned containers or repository objects from a selected workarea. About

Excluded objects still exist in the repository, but are no longer visible in the selected workarea.

To exclude objects from a workarea:

1.	In the Navigator window, select the versioned containers or objects that you want to exclude from the workarea in which they appear.

For multiple object selection, hold down the SHIFT key to select adjacent objects; hold down the CTRL key to select non-adjacent objects.

2.	Choose Edit→Exclude from Workarea.

3.	If you do not want to refresh the workarea immediately, uncheck the Refresh Workarea Now? box. Refreshing the workarea removes the newly excluded objects from view.

4.	Click OK. If you chose to refresh the workarea immediately:

a.	(Optional) To synchronize the repository and the file system when you refresh the workarea, select Synchronize.

b.	(Optional)  To see the effect of refreshing the workarea before you perform the operation, select Preview Changes Before Refreshing. You can choose to see the effect simply on the repository, or (if the repository contains uploaded files) the effect on both the repository and the file system.


Creating containers

You create the different types of container in the same way. About

Note:	You must have the Containers repository privilege before you can perform this operation. The repository owner can assign this privilege to you.

To create a container:

1.	In the Navigator window, select a workarea name.

2.	Click [image].

3.	In the Select Type dialog box, select the type of container you want to create and click OK.

4.	Type the container name.

5.	Click [image].


Mapping containers to file systems

You can associate a container in a workarea with a directory in any file system to which you have access. This operation is known as folder mapping. About

Note:	You cannot map a subcontainer; you can map only a container that has no parent.

A mapping provides a default specification for upload and download operations. In addition, a mapping is required before you can synchronize that file system with the repository. A mapped container is denoted by the  icon in the Navigator window.

To map a container to a file system:

1.	In the Navigator window, select the container that you want to map. You must select the container under the Private Workareas or Shared Workareas node, not the All Containers node.

2.	Choose Utilities→Map Folder to File System.

3.	In the Map Folder foldername to OS Path field, enter the full pathname of the file system directory you want to use for the mapping (or use the Browse button to locate and select the directory).

4.	(Optional) Click Apply to display this mapping, then optionally define other mappings.

5.	Click OK to return to the Navigator window.

6.	To see the effect of the mapping:

a.	With the container name selected in the Navigator window, click [image].

b.	Double-click the Files node to see the files in the mapped container. The file names are initially displayed in a different color, indicating that they are in a mapped container but have not been uploaded to the repository.

To delete the mapping for a container:

1.	In the Navigator window, select the container whose mapping you want to delete.

2.	Choose Utilities→Map Folder to File System.

3.	In the Map Folder(s) dialog box, click Delete Mapping, then click OK.


Editing repository objects

If a repository object is under version control, you can edit it only when it is checked out. You can edit other repository objects at any time.

To edit a repository object:

1.	Locate the object you want to edit. How

2.	If the object is under version control and does not display a [image] icon, check it out. How

3.	Select the object in the Navigator window. How

4.	Make any changes that you want.

5.	Click [image].


Moving repository objects

You can move a repository object from one container (the source container) to another (the destination container) in the same workarea. When you move an object, the destination container becomes the new owning container for the object.

You cannot move an object from one workarea to another. The set of objects that are visible in a workarea is defined by the workarea specification.

Moving versioned objects is possible, but is not recommended owing to ownership problems that can arise.

Note:	If you move objects of certain element types, you might encounter problems when viewing earlier versions of these objects with some diagramming tools. The element types concerned are those that are known as "non-sharable". About

If you move a PAC element from any container to a versioned container, the destination container is checked out. If you undo this checkout, the element disappears and can only be recovered from the Lost+Found folder by means of the Command Line Tool (see below).

To move a repository object (mouse method):

1.	If the destination container is under version control, check out the container. How

2.	In the Navigator window, select the object you want to move.

3.	Hold down the SHIFT key and use the mouse to drag the object to the destination container, so that a dotted box appears around the container name.

4. 	Release the mouse button first, then release the SHIFT key.

If you see the Move dialog box:

•	select Auto Checkout if you are moving a checked-in versioned object and you want it to be checked out immediately after the move

•	select Don’t Show This Dialog Again if you want your check box selections to apply every time you move an object

To move a repository object (keyboard method):

1.	If the destination container is under version control, check out the container. How

2. 	In the Navigator window, select the object you want to move.

3. 	Choose Edit→Cut (or press CTRL-X).

4. 	Select the destination container.

5. 	Choose Edit→Paste (or press CTRL-V).

If you see the Move dialog box:

•	select Auto Checkout if you are moving a checked-in versioned object and you want it to be checked out immediately after the move

•	select Don’t Show This Dialog Again if you want your check box selections to apply every time you move an object

To recover a PAC element from the Lost+Found folder:

1.	Start the Command Line Tool (from the Repository Object Navigator, choose Tools→Command Line Tool).

2.	Remove any workarea setting by entering:

set wa ""

3.	List the contents of Lost+Found showing the version identifiers (IVIDs) and element types:

lslaf -iv -ty

4.	Set the workarea context:

set wa workarea_name

5.	Checkout the destination container:

co container_name

6.	Reattach the element to the destination container, identifying the element by means of its IVID:

reatt ivid container_name -iv

7.	Commit the changes:

commit


Deleting references

You can delete any reference in the current container, provided that you have DELETE access rights to the container.

About references

About access rights

Caution:	You cannot undo this operation.

To delete a reference:

1.	Select the reference in the Navigator window.  How

2.	Click [image] in the tool palette to the left of the Navigator window.

3.	In the Confirm Delete dialog box, check that you are deleting the correct reference and click Delete.


Deleting shortcuts

A repository object can be owned by a container other than the one from which you are accessing it. The link between the two is known as a shortcut, and is denoted in the Navigator window by a [image] icon. Deleting the shortcut does not affect the original object. You must have DELETE access rights to the container that displays the [image] icon.

Caution:	You cannot undo this operation.

To delete a shortcut:

1.	In the Navigator window, select the object name that has the [image] icon next to it.

2.	Click [image] in the Navigator tool palette.

3.	In the Confirm Delete dialog box, check that you are deleting the correct shortcut and click Delete.


Using the Navigator

Selecting objects in the Navigator

Navigating to a named object

Expanding objects in the Navigator

Collapsing objects in the Navigator

Setting bookmarks in the Navigator

Navigating to and from a referenced object


Selecting objects in the Navigator

Related Topics

To select a single object in the Navigator, click on it. The entry is highlighted to show that it is selected. Any previous selection in the Navigator is lost.

To select a range of objects, select an object to identify the start of the range, then hold down SHIFT and select an object to mark the end of the range. All the objects between the two selected objects are selected.

To select several objects that are not within a range, hold down the CTRL key and select the nodes individually.


Navigating to a named object

If you want to locate an object by name, you can navigate to it directly by using the text box in the toolbar.

Note:	The object must have been previously displayed in the Navigator window in the current session.

To navigate to a named object:

1.	Start typing the name of the object in the text box in the toolbar:

As you type, the system selects the first object that matches the name you have typed so far.

2.	If the selected object is not the one you want, do one of the following:

•	Type more of the name to narrow the search.

•	Click [image] in the toolbar repeatedly until you find the object you want.

Note:	You can click [image] to go back to the object that was last found in the search.


Expanding objects in the Navigator

Related Topics

You can expand all or part of the Navigator to view the objects. You can expand an object only when its Collapse/Expand Icon is in its collapsed state.

When you expand a node by one or more levels, the level to which the node is expanded is determined by how it was previously collapsed. A node is expanded by one level unless the Navigator→Collapse option was used to collapse it. This collapse option stores information about the level to which a node is expanded, so that, when the Navigator→Expand option is used, the node is expanded to its previous level.

When you fully expand a node, the Navigator displays all the objects below it, until no more nodes can be opened.

Note:	When the Navigator is expanded and filters have been set, only objects that fit the filter criteria are shown. In the Repository Object Navigator use Navigator→Filter. In other tools, use Options→Customize.

To expand objects in the Navigator:

Do one of the following:

•	Double-click a collapsed node. The node is expanded and selected.

•	Click the Collapse/Expand icon of a collapsed node. The node is expanded but not selected.

•	Select the objects that you want to expand and do one of the following.

−	To expand the object to the next level, choose Navigator→Expand.

−	To expand all objects under the selected entry, choose Navigator→Expand All.


Collapsing objects in the Navigator

Related Topics

You can collapse all or part of the Navigator to hide objects that were visible in the expanded state. When you collapse an object, the Navigator stores the level to which the object was expanded. You can expand the object to its previous level using the Navigator→Expand option. In this way, you can easily collapse and expand part of the Navigator.

To collapse objects in the Navigator:

Do one of the following:

•	Click the Collapse/Expand icon of a expanded node. The node is collapsed but not selected.

•	Double-click an expanded node. The node is collapsed and selected.

•	Select the object that you want to collapse in the Navigator and do one of the following:

−	To collapse the selected node, choose Navigator→Collapse.

−	To collapse all nodes under the selected node, choose Navigator→Collapse All.


Setting bookmarks in the Navigator

Related Topics

You can use the Set Mark and Go to Mark commands to mark an object in the Navigator and then return to that object later on. Once a mark has been set, you can work in the Navigator and in other windows as desired. Only one bookmark can exist on the Navigator at any one time.

A bookmark remains set until:

•	you set a new mark

•	you delete the marked object

•	you change views in the Designer

•	you quit the tool

To set a bookmark, position the cursor on the desired entry and click the [image] button.

To jump to a bookmark, click the [image] button. The marked object is selected.


Navigating to and from a referenced object

Where a repository object references another object, you can navigate to the referenced object from the original object. For example, if a table has a foreign key defined, you might want to navigate to the definition of the table containing the primary key that is referenced by the foreign key.

Subsequently you can navigate back to the original object from the referenced object.

To navigate to a referenced object:

1.	In the Navigator window, select the name of the object that references the other object.

2.	Click [image].

To return to the object reference:

1.	In the Navigator window, select the name of the referenced object.

2.	Click [image].


Issuing repository commands from the command line

Related Topics

You can perform a large number of repository operations from the repository Command Line Tool.

It is possible to run the Command Line Tool from the Start menu in Windows, or from the Repository Object Navigator. Running it from the Repository Object Navigator avoids the need to issue a connect command, as the connection to the current repository is already active.

For information about the Command Line Tool, including full specifications of all the commands access the Command Line Tool Reference Guide (from the Start button menu)

Note:	When the Command Line Tool is active, you can enter help to list all the available commands. Enter help command_name for help about a particular command.

To run the Command Line Tool from the Start menu:

1.	From the Start button menu, access the Repository Command Line Tool.

2.	At the REPCMD> prompt, enter the following:

connect username/password@alias

The parameters are the username, password and database alias (connect string) that you normally use to connect to the repository.

3.	At the REPCMD> prompt, type a command and press ENTER.

To run the Command Line Tool from the Repository Object Navigator:

1.	Choose Tools→Command Line Tool.

2.	At the REPCMD> prompt, type a command and press ENTER.


Running repository tools from the command line

Related Topics

You can run any of the repository tools from a command line on a Windows workstation. There are two methods:  one uses the MS-DOS command prompt window, while the other uses the Command Line Tool supplied with Oracle Repository.

The method you use depends on the tool you want to run:

Tool	Method
Dependency Manager	Command prompt *
Matrix Diagrammer	Command prompt
Repository Administration Utility	Command prompt
Repository Object Navigator	Command prompt
Repository Reports	Command prompt
Version Event Viewer	Command Line Tool
Version History Viewer	Command Line Tool
* You can create dependency analysis data from the Command Line Tool, but you cannot run Dependency Manager from that tool.

To run a tool from a command prompt:

1.	Choose Start→Command Prompt or Start→Programs→Command Prompt, depending on how your workstation is configured.

2.	Enter the following:

d:

cd d:\oracle_home\bin

where d: and oracle_home identify the drive and directory to which the Oracle software is installed.

3.	Enter the tool command as shown below:

Tool	Command Format
Dependency Manager	ckdm61 [username/password@database]
Matrix Diagrammer	awm61 [username/password@database]
Repository Administration Utility	ckrau61 [username/password@database]
Repository Object Navigator	ckron61 [username/password@database]
Repository Reports	ckrpt61 [username/password@database]

where username and password are the username and password, and database is the database alias, for the repository you want to use.

If you omit any part of the username/password@database combination, the Connect dialog box displays for you to enter this information.

To run a tool from the Command Line Tool:

Note:	The names of repository workareas, containers and objects are case-sensitive.

1.	Start the Command Line Tool. How

If you start the Command Line Tool from the Repository Object Navigator, you will automatically be connected to the repository and the context workarea will be set, so continue from step 4.

2.	Connect to the repository by entering the following at the REPCMD> prompt:

connect username/password@database

3.	If you are using a repository that supports version control (whether you use this feature or not), you must set the context workarea (the one you want to work in).

To list the workareas to which you have access, enter:

lswa

To set the context workarea, enter:

set workarea workarea_name

4.	At the REPCMD> prompt, enter one of the following commands:

Tool	Command Format
Version Event Viewer	vev object_path
Version History Viewer	vhv object_path

where:

name or pattern identify the objects whose dependencies are to be analyzed, and options are described in the Command Line Tool Reference Guide, which you can access online.  How

object_path is the location of the object in the repository (from the current context), for example \container_name\object_name.

To see a list of containers in the context workarea, enter:

lsf

To set a particular container as the context container, enter:

cf container_name


About the Repository Object Navigator

The Repository Object Navigator is a versatile tool for creating and maintaining repository objects.

There are several kinds of tasks that you can perform with the Repository Object Navigator:

•	administrative

•	maintenance

•	access control

•	version control

Administrative tasks include creating, editing and deleting workareas, containers and configurations, and setting repository-wide policies.

Maintenance tasks include creating, editing and deleting repository objects, and performing file upload, download and synchronization between the repository and a file system.

Access control tasks include granting and revoking access by other repository users to workareas, containers and configurations.

Version control tasks include checking repository objects in or out, viewing the version history of an object, and comparing and merging object versions.


About the Repository Object Navigator display

The Repository Object Navigator display consists of the title bar, menus, toolbars, Navigator window, Property Palette, TextPad and the status bar.

Component	Function
Navigator window	Shows the repository object hierarchy at the selected level, and lists the object definitions at this level and below
Property Palette	Allows you to view or edit properties of repository objects or references
TextPad	Used to enter values for multi-line text properties
Status bar	Displays hint lines and status information about the repository


About Navigator views

Related Topics

You have the following sets of choices for how you display the contents of the Navigator window:

•	group tabs or no group tabs

•	list view or hierarchy view

•	split window or no splitting

Group tabs or no group tabs

Group tabs view

When the Navigator window is set to group tabs view, the window displays a set of tabs at the top, labeled with the names of element type groups.  In group tabs view, the Navigator window displays only the elements from the group selected by the tab. About

The groups correspond to different stages in the process of database or application modeling and design. About

You can customize these groups, for example, to show just the element types that are relevant for a particular task. How

You can also define your own groups and use these in the display. How

No group tabs

If you want the Navigator window to display all element types that are visible in a workarea, you can turn off the group tabs. How

List view or hierarchy view

For some element types, it is possible to create instances and arrange them in a hierarchical fashion. About

For example, you might want to define entities that have sub-entities, or business units that comprise other business units in the form of sub-divisions.  How

List view

By default, the Navigator window shows element definitions as a list that you can expand to see any references between objects. This view is known as list view. You can expand any element definition in the Navigator window to see its references, which are displayed under a node named Usages. About

In list view, elements that have been defined in a hierarchy are shown at the same level in the Navigator window. An example of an entity hierarchy in association view looks like this:

Hierarchy view

You can choose to display a hierarchical set of element definitions in hierarchy view. How
In hierarchy view, our example set of entities initially looks like this:

When the hierarchy is fully expanded, it looks like this:

Note:	The [image] icon indicates that hierarchy view is active for that particular node.

Split window or no splitting

By default, the Navigator window displays its contents in a single, undivided window. You can split the Navigator window either horizontally or vertically into two independently scrollable divisions. How


About element type groups

Related Topics

When the Navigator window is set to group tabs view, the window displays a set of tabs at the top, labeled with the names of element type groups.  In group tabs view, the Navigator window displays only the elements from the group selected by the tab. About

The groups are as follows.

Fun/Evt Model

In this group, the element types are those related to the definition of events, which can act as triggers to one or more business functions.

Server Model

This group enables you to create the definitions of various elements relating to a database that you are designing. For example, you can create definitions of tables, views, snapshots, sequences, clusters and PL/SQL definitions.

Modules

These element types are for use when defining the screen form, menu or library modules which actually implement the functions that have been defined. You can define components of modules as being reusable (that is, available for use by more than one module). You can also define preference sets, which allow the same set of preferences to be shared across element types and applications.

DB Design

In this group, the element types enable you to create the definitions for Oracle or other databases that are used by the application you are designing. For documentation purposes only, you can also record details of nodes and network server communities.

Files

This group shows files and directories that have been uploaded to the repository from a file system.

Ref Data

This group contains element types for defining reference information relating to an application. For example, you can define the terminology you use in your business, and any domains that you want to use to validate values that are entered subsequently.

Enterprise Model

These element types allow you to define information about the enterprise or business in which your organization is engaged. For example, you can record details of the various business units that form your organization. You can also define your business objectives and other influencing factors, such as critical success factors or problems that might prevent achievement of the objectives.

E/R Model

In this group, the element types permit the definition of entities and relationships for use in entity models of your business. This group also lists any entity relationship diagrams that have been created.

DataFlows

The element types in this group enable you to model the flow of data between business functions, datastores and externals. A flow of data that is modeled in this way is known as a dataflow.


Repository Loader reference

Related Topics

The Repository Loader utility provides a way of importing data from a text file (called a loader data file) into the repository, and of exporting repository data to a text file. You can use the utility to transfer data from one repository to another (both must be repositories created with this release).

The input to the utility is the loader data file. Output files are the error log file, which records details of any errors encountered, and the redo log file, which lists the operations that need to be repeated when error conditions have been resolved.

Loader data file format

The loader data file is formatted as a series of data declaration blocks. Each block comprises a series of commands of the form:

keyword argument1 argument2 ...

The keyword and arguments are delimited by spaces. The number of arguments in the command depends on the keyword used.

Command keywords

Command arguments

Note:	You can make comments in the loader data file by inserting a number sign (#). Text appearing after a number sign is ignored by the Repository Loader. Blank lines in the loader data file are also ignored.

Rules for loading repository data

The contents of a loader data file are loaded into the repository in Insert mode. (Note that Update mode is not supported in this release.)

In Insert mode, elements in the loader data file are created in the repository. If the element already exists in the repository, the block is not committed, details of the error are written to the error log file and details of the element are written to the redo log file.


Command keywords

Repository Loader recognizes the following command keywords:

Note:	Use the number sign (#) to make comments in the loader data file. Text appearing after a number sign on the current line is ignored. Blank lines are also ignored.

Example loader data file

Commands to Repository Loader are given in uppercase characters. In the syntax descriptions below, italic characters signify variable parameter values.

C - Commit

C

Indicates that the current block (that is, the set of keyword commands entered since the last C command) is to be processed by Repository Loader.

Data is processed when a C command is encountered in the input file when it is being interpreted. After a C command, references no longer apply to the elements that they were defined as identifying. The C command, therefore, delimits logical units of work in the output file, and its positioning is very important.

A slight performance improvement can be made by using fewer C commands (that is, by having a greater number of commands in each commit block), though doing so will require a larger rollback segment.

D - Delete

D type *reference

Deletes the element of the given type that is identified by reference.

E - Define Unnamed Element

E type &reference

Defines an unnamed element (for example, a table entity usage) of the given type, introducing the reference by which it can later be identified within the context of the current block.

F - Folder

F [container]

Specifies the container into which the data is to be loaded. This can be changed only by a subsequent F command.

If included, container is the full pathname of the container in the repository; this pathname is case-sensitive. You must use '\'  as the separator character, for example, "Workarea1\Folder1".

Issuing an F command without container specifies that subsequent data is to be loaded into the container identified in the parameters of the Repository Loader utility itself.

G - Get

G type name {E|I} &reference [container]

Retrieves an element of the specified type and name. If the element does not exist in the repository, the value E causes an error condition to occur, while the value I causes the element to be inserted with the given reference.

If included, container is the full pathname of a repository container to query (for PAC elements only), for example the SYSTEM folder. This pathname is case-sensitive. You must use '\'  as the separator character, for example, "Workarea1\Folder1".

H - Define Diagram (Hexadecimal) Data

H GRAPHICAL_DATA *reference hex_value

Used to encode diagram segments for the diagram identified by reference. Sets the current row of the diagram to the hexadecimal value specified in hex_value.

I - Insert Named Element

I type name &reference

Inserts an element of the specified type and name, and defines the reference by which the element is to be identified in other commands in the current commit block.

J - Fetch Unnamed Element

J type &reference [container]

Retrieves an unnamed element (for example, a table entity usage) of the given type and identified by reference.

If included, container is the full pathname of a repository container to query (for PAC elements only), for example the SYSTEM folder. This pathname is case-sensitive. You must use '\'  as the separator character, for example, "Workarea1\Folder1".

K - Define Foreign Key Relationship

K type *reference1 relationship column_name *reference2

Defines a foreign key relationship from the element identified by reference1 to the element of the specified type that is identified by reference2. The type of relationship is identified by relationship, and the relationship uses the foreign key identified by column_name.

M - Define Property

M property *reference value

Assigns the specified value to the given property of the element identified by reference.

N - Define SAC Element

N type name *reference1 &reference2

Inserts or retrieves a secondary access controlled element, identified by reference2, within the context of its primary access controlled element, identified by reference1.

O - Specify Whether Container Context Needed

O {Y | N}

Specifies whether the loader data file requires a container context for import. An import operation fails if the import file requires a container context and one is not set.

Value Y indicates that a container context is mandatory. Value N indicates that a container context is optional. If this command is not specified, the Loader assumes that the container context is optional.

R - Define Relationship-End Association

R *reference1 *reference2

Defines an association between two relationship ends (identified by reference1 and reference2) as two ends of the same relationship.

T - Define Text

T type *reference text_type "text"

Defines a line of multi-line text of type text_type to be entered against an element of the specified type that is identified by reference.

U - Define Utility Command

Defines a utility command that causes specific processing at the point in the loader file where the command is encountered. Format:

U "DebugLevel" level

Sets the specified diagnostic level. This turns diagnostics on or off at a particular point in the processing of a loader file in order to control the quantity or quality of the messages.

X - Exit

X

Terminates the run of the Loader if the current block fails during loading. If a block without an X command fails, the failure is recorded in the error log file and the loading process continues.

Y - Yank

Y type "element_identifier" &reference

Locates a specific element in a repository. Used in conjunction with other commands and in cases where an element name may have changed (e.g. where an element has been checked out), the Y command locates an element by its element identifier rather than by its name. The element is assigned the specified reference.

Z - Confirm Nulls

Z *reference

Explicitly sets null values for all undefined properties of the element identified by reference. If this command is not given, undefined properties are not updated in the target repository.


diagnostic level

Can be one of the following:

FUNCT_FLOW

FUNCT_HIGH_LEVEL

FUNCT_LOW_LEVEL

FUNCT_TRACE

NONE

RM_DEBUG

SQL_BIND

SQL_CLIENT

SQL_SERVER

TRANSACTIONS

USER_MESSAGES


element identifier

A numeric identifier of a repository element. This is the value of the IRID column in the CI_eltype view of the repository, where eltype identifies the element type (for example, the view for entities is CI_ENTITIES).


named element type

Examples of named element types are DFL, DOM, DST, ENT, EVT, FUN and RELEND.


reference

References act as pointers to repository elements. A reference can consist of any ordering of alphanumeric and underscore characters.

Reference declarations are preceded by an ampersand (&) and signify that the specified character string is to be used to reference the element in subsequent commands in the current commit block.

Reference usages are preceded by an asterisk (*) and identify an element that has a previously declared reference. The element can be identified by the given reference until the next C command or until another reference of the same name is introduced.


unnamed element type

Examples of unnamed element types are DFLATT, DSTATT, ENTUIE, FUNATT, FUNENT and FUNEVT.


Command arguments

Arguments in Loader commands can be grouped into the following types:

•	reference declarations

•	reference usages

•	element type names

•	association type names

•	property names

•	text type names

•	property values

Note:	You can find the name (that is, the internal repository name) for any given element type or association type by viewing summary information on a property of an element or association of the required type. How

The internal name for the element type or association type is displayed in the Name field of the Property Details dialog box that is displayed. The internal name for the property is displayed in the View Column field.

Example loader data file

Reference declarations

Element references act as pointers to the repository elements. Reference declaration arguments are preceded by an ampersand (&) and signify that the specified character string is to be used to reference the element in subsequent commands. The character string for the reference can consist of any ordering of alphanumeric characters and underscore characters.

Reference usages

Reference usages are preceded by an asterisk (*) and reference an element that has a previously declared reference. The element can be identified by the given reference until the next C command or until another reference of the same name is introduced.

Element type names

Element type names specify the type of element being referenced.

Association type names

The association type argument specifies the type of association between two elements.

Property names

Property names are used in the M command to specify which property of the referenced element is to be set to the given value.

Text type names

The text type argument appears only as the third argument of the T command. Valid text types are the types defined in the repository and include user-defined text types.

Property values

Property values are assigned to a property with an M or T command. All property values, numeric or otherwise, must be entered within double quotation marks ("").


Insert mode

The following tables summarize the outcome when certain combinations of elements are loaded into the repository in insert mode.

In the tables, 'Y' indicates that the element or association existed in the target repository before the load and 'N' indicates that it did not. An outcome of 'Error' indicates that the conflict is recorded in the error log and the load process continues. An outcome of 'N/A' indicates that the given situation could not arise.

PAC elements

The basic rules for loading PAC elements in insert mode are:

Element	Outcome
Y	Error
N	Insert

The basic rules for loading super-types and sub-types of PAC elements are:

Super-Type	Sub-Type	Outcome
Y	Y	Error
Y	N	Insert sub-type
N	Y	Error
N	N	Insert
SAC elements

The basic rules for loading a SAC element and the owning PAC element (e.g., an entity and its attribute) are:

PAC Element	SAC Element	Outcome
Y	Y	Error
Y	N	Error
N	Y	N/A
N	N	Insert

The basic rules for loading a SAC element and an associated PAC element (e.g., an attribute and the domain it is in) are:

PAC Element	SAC Element	Outcome
Y	Y	Error
Y	N	Insert SAC element
N	Y	Error
N	N	Insert
Associations

In the following table, Element1 owns the association between the two elements. For example, given a Summary Table Usages association, Element1 would be a module and Element2 would be a table.

The basic rules for loading associations are:

Element1	Element2	Association	Outcome
Y	Y	Y	Error
Y	Y	N	Error
Y	N	Y	N/A
Y	N	N	Insert
N	Y	Y	N/A
N	Y	N	Insert
N	N	Y	N/A
N	N	N	Insert


Example loader data file

The following example is an extract from a loader data file. The effect of this extract is to insert two modules into a container, a Web PL/SQL module and an Oracle Forms module.

The O Y command specifies that a container context is mandatory, that is, the destination container must be specified in some way.

The F commands identify the destination container to be used. Because no parameters are specified in the commands, the destination container identified in the utility parameters is used.

The C command commits the current block of data to the repository.

The first I command inserts into the repository an object of element type GEM (the internal name for a module) with the name WEB001. The & sign specifies that the number that immediately follows it is to be used to identify the element. The number is actually the internal repository identifier (IRID), which uniquely identifies the object in the repository. The second I command inserts an Oracle Forms module.

The M commands define the properties and their values for the object with the IRID shown.

The G commands retrieve an object of element type LAN (the internal name for a language), and the K commands associate the language with the object by defining a foreign key relationship from the object to the language.

O Y

F

C

I GEM "WEB001" &2347838728368108140819112663368656797

M SHORT_NAME *2347838728368108140819112663368656797 "WEB001"

G LAN "Web PL/SQL" E &1754353890218008865044785482249553977 "SYSTEM FOLDER"

K LAN *2347838728368108140819112663368656797 GEM_LAN LANGUAGE_REFERENCE *1754353890218008865044785482249553977

M MODULE_TYPE *2347838728368108140819112663368656797 "GEM"

M PURPOSE *2347838728368108140819112663368656797 "."

M CANDIDATE_FLAG *2347838728368108140819112663368656797 "N"

M PREVENT_GENERATION_FLAG *2347838728368108140819112663368656797 "N"

M TOP_LEVEL_FLAG *2347838728368108140819112663368656797 "N"

M GENERAL_MODULE_TYPE *2347838728368108140819112663368656797 "DEFAULT"

M COMPLETION_STATUS *2347838728368108140819112663368656797 "NOT STARTED"

C

F

C

I GEM "FORMS001" &2347838732391413268496598556790810525

M SHORT_NAME *2347838732391413268496598556790810525 "FORMS001"

G LAN "Oracle Forms" E &1754353890217952196646991046506989625 "SYSTEM FOLDER"

K LAN *2347838732391413268496598556790810525 GEM_LAN LANGUAGE_REFERENCE *1754353890217952196646991046506989625

M MODULE_TYPE *2347838732391413268496598556790810525 "GEM"

M PURPOSE *2347838732391413268496598556790810525 "."

M CANDIDATE_FLAG *2347838732391413268496598556790810525 "N"

M PREVENT_GENERATION_FLAG *2347838732391413268496598556790810525 "N"

M TOP_LEVEL_FLAG *2347838732391413268496598556790810525 "N"

M GENERAL_MODULE_TYPE *2347838732391413268496598556790810525 "DEFAULT"

M COMPLETION_STATUS *2347838732391413268496598556790810525 "NOT STARTED"

C


The Navigator window

Related Topics

The Navigator window contains a list of the repository contents, arranged in a tree structure, for example:

The actual contents of the display depend on how you are using the repository, and on the level of the tree structure selected when the window was opened.

Opening a Navigator window

You can open any number of Navigator windows. How

Each Navigator window can be open at any one of the following hierarchy levels:

•	the entire repository

•	private workareas

•	shared workareas

•	a single workarea

•	all configurations

•	a single configuration

•	all containers

•	a single container

For example, if you are using version control and you open the window at the level of the entire repository, you see the following:

Repository

This shows the name (or the alias) of the database where this repository resides.

Private Workareas and Shared Workareas

The area named Private Workareas, when expanded, lists all the workareas that you own and which are not currently accessible to other users. Shared Workareas shows all the workareas that either you or other users have made available for shared access. About

Configurations

A configuration is a grouping together of specific versions of specific repository objects, and is typically used when constructing a build of a particular application. About

Configurations are shown in the Navigator window with the configuration name first, with different versions of the configuration nested under it, like this:

In this way you can see all the versions of the configuration in the repository. If a configuration is not under version control, only one nested name is shown, with no version number.

All Containers

Expanding All Containers in the Navigator window lists all the containers to which you have access, regardless of their workarea.

The area named Lost+Found provides access to repository objects that do not currently reside in a container. This can occur, for example, if a folder (but not its contents) was inadvertently deleted.

Contents of the Navigator window

The Navigator window displays a tool palette to the left of the tree structure.

Each item in the Navigator window is called a node and represents a workarea, an element type heading, a repository object or a reference. You can specify how you want the nodes to be arranged by choosing from a number of view options. About

If you start the Repository Object Navigator from another tool, you may find that the Navigator window is opened at the level of the workarea you are already using:

Here, the node named Folders, when fully expanded, lists the various containers of this type that are visible in this workarea. About

The node named Wastebasket refers to the workarea wastebasket. This is a storage area that contains repository objects which have been marked for deletion from the current workarea. These objects have not been physically removed from the repository, and can be either restored or destroyed. Each workarea has a wastebasket, and there is also a global wastebasket (under the All Containers node). About


Icons in the Navigator window

Nodes in the Navigator window have an icon displayed next to them. Each icon indicates what the corresponding node represents, for example:

At the highest level of the tree structure are the workarea and container icons:

	Workarea
	Folder
	Mapped container
A mapped container is one that has been associated with a particular file or directory in a file system (i.e., outside the repository). Mapping is used for uploading and downloading files to and from the repository. About

At the next level are the element type icons. Each element type has its own icon, for example:

Besides these, there are other icons that have a particular meaning:

	Checked-out object
	Shortcut
	Collapse/expand
	Referenced element


Names in the Navigator window

The top-level node indicates the level in the repository hierarchy at which the Navigator window was opened. For example, if you open the Navigator window at the Private Workareas level, you see a list of workareas like this:

If you expand a workarea node, immediately below the workarea name you see the various containers that have been created and which are visible in that workarea:

When you expand a container, you see the element types for which there are instances in that container (provided that element type headings are displayed):

Expanding an element type shows you the names of individual repository objects of that element type that are owned by the current container:

In repository terms, each of these names identifies the primary access controlled (PAC) element of the repository object.

Expanding a PAC element name displays various secondary headings:

The first group of secondary headings shows the possible secondary access controlled (SAC) elements that can be defined for the current PAC element of the object. The headings that are displayed differ depending on the PAC element type; for example, for a domain you can create only Allowable Values and Sub Domains. SAC elements are dependent on the PAC element from which they derive, and cannot exist in their own right.

Every repository object can also display the secondary headings Inclusions and Usages, and some have the headings Security or Preferences (or both) as well. It is possible to hide the Inclusions and Usages headings, so you may not see these even if data is defined for them.

Inclusions shows you the configurations, workareas and other items in which an object is included, as well as any containers in which the object is referenced:

Usages shows you the types of reference that are possible for a particular PAC or SAC element of an object, together with any instances of those references. The possible types of reference are different for each element type. In our example of a domain, the usages look like this:

Security indicates the repository users who have access to the current object, either directly or through the granting of roles:

Preferences shows the preference sets or non-default preferences that have been defined for the current object. About


Group tabs view

Related Topics

In group tabs view, the Navigator window has a set of tabs at the top. The tab labels describe element type groupings that correspond to different stages in the process of database or application modeling and design. When you select a particular tab, only the objects of element types in that group are displayed in the Navigator window.  About

You can add your own group tabs to the Navigator window, to display your own selection of element types (or user-defined views of element types). How

If you want to see all the element types, turn off group tabs view.

Note:	If a group tab does not appear in your Navigator window, you may need to select it for display using Options→Customize Navigator Groups.


The status bar

Related Topics

The status bar is made up of two parts:

•	•	hint line

•	•	message windows

The contents of the hint line depend on the context. If the cursor is over a menu option or toolbar button, the hint line indicates what that option or toolbar does.

If an object is selected in the Navigator window, the hint line shows the repository path for that object (that is, the location of the object in the repository hierarchy).

If a property is selected in the Property Palette, the hint line provides a brief description of that property.

If an operation (such as a Save) is in progress, the hint line indicates what the Repository Object Navigator is currently doing.

The message windows are as follows:

Message	Indicates
UPDATE	The status of the active Navigator window
CHANGES	You have made changes that you have not committed to the repository
ERRORS	One or more object definitions have uncorrected errors. The incorrect objects are shown in the Navigator window in the color defined for errors (default is red).


File - Open
   Open (File Menu)

Related Topics

Enables you to open a new Navigator window at a selected level in the repository hierarchy.

The corresponding dialog box shows a list of various items in the repository. From this list, you can choose the level at which to open the Navigator window.

Dialog box options

Look In

Shows the level at which the Navigator window will be opened.

 (Up One Level)

Selects the level above the current one in the repository hierarchy.

 (List View)

Displays only the names of the repository items in a multi-column list.

 (General Details View)

Displays various general details about the items in the list:  name, element type, attributes (e.g. read-only, checked out etc.), the date when the item was last modified and the user who last modified it.

 (Version Details View)

Displays version details, if any, about the items in the list:  name, element type, attributes (e.g. read-only, checked out etc.), version label, branch and version number.

 (Hierarchical View)

Displays only the repository objects at the selected level in the repository hierarchy. In this view, double-clicking the name of a workarea or container displays the objects at that level.

 (Flat View)

Displays all the repository objects at or below the selected level. Objects are displayed with their path in the repository indicated. This view can be useful, for example, when specifying the Language property for a module or module component, as it avoids having to navigate to the System Folder to display the languages.

List box

If you select General Details View or Version Details View, displays details of the items at the repository hierarchy level immediately below that indicated by the Look In field.

Name

The name of the item.

Type

The type of item, e.g. workarea, application system, folder, configuration.

Attributes

For a repository object, indicates various attributes:

CI - checked in

CO - checked out

R - read only

Modified

(General Details View only) The date when this object was last modified.

Modified By

(General Details View only) The username of the repository user who last modified the object.

Version

(Version Details View only) The checkin branch and version number of a versioned object, for example, MAIN:1.

Version Label

(Version Details View only) The version label of a versioned object, for example, 1.3.

Find elements that match this criteria

Enables you to open a Navigator window at the level of a selected object. You can select the object in the list area (you may need to navigate down the hierarchy until you see the object in the list). Alternatively you can enter the object name in the Name field.

Name

The name of the object to which you want to navigate.

Type

The element type. You can use this field to filter the list of objects displayed.

Select All

Selects all the objects in the list. Use this if you want to open a window for each object.


File - Save Uncommitted Data
   Save Uncommitted Data (File Menu)

Related Topics

Saves any outstanding changes that you have made to the repository.

Changes you make to an object from the Navigator window (such as creating or deleting objects) are committed to the repository as soon as you choose this option or select another object.

When you edit properties in the Property Palette, the changes you make are committed as soon as you choose this option, or when you make another window active.


File - Revert Uncommitted Data
   Revert Uncommitted Data (File Menu)

Related Topics

Cancels unsaved changes you have made to the repository in the current Navigator window.

In the Navigator window toolbar, this button cancels the effect of all unsaved changes to the current repository object.

In the Property Palette, this button cancels the effect of all unsaved changes to the object properties.


File - Search Repository
   Search Repository (File Menu)

Related Topics

Enables you to search for objects across the entire repository, within a particular workarea, or within a particular container in a workarea.

You can perform simple searches, for example by object name, or more advanced searches using complex search conditions. You can also restrict the search to repository objects of a particular type, for example, column, index and so on. It is possible to search for a particular object by name, or to search for all objects with one or more properties that correspond to specified conditions.

The results of the search are displayed in a separate window, which shows brief details about the objects found. The Search Results window also allows you to locate the objects in the Navigator window by means of the right mouse menu.

Dialog box options

Context

Sets the context for the search: either the entire repository, or a particular workarea.

Entire Repository

Performs the search across the entire repository. Note that for a large repository, this could be very time-consuming.

Workarea

Restricts the search to a particular workarea.

Workarea Name

The name of the workarea in which you want to search. Enter the workarea name, or use the Browse button adjacent to this field to select a workarea.

Folder Path

The name of a container, in the selected workarea, in which you want to search. Enter the container name, or use the Browse button adjacent to this field to select a container.

For Types

Specifies the kind of object to search for.

Files

Searches for files that have been uploaded to the repository.

Specific

Searches for objects of a specific type.

Type Names

The element type of the objects for which you are searching. Enter the element type, or use the Browse button adjacent to this field to select one or more element types.

If you are searching on a single element type you need enter only enough letters of the element type name to distinguish it uniquely from the other available types. If you are searching on more than one element type, enter each type name enclosed in double quotation marks and separated by a space character.

Categories

Searches for objects according to one or more specified categories. About

Search Specification

Enables you to enter more specific details of what to search for.

Name

The object name. You can use the % wildcard to search on a partial name.

Short Name

The short name of the object. You can search on short names if the element type supports them.

IRID

(Displayed only if the Search on GUIDs check box is selected) The value of an IRID (a repository object identifier) you want to search for.

IVID

(Displayed only if the Search on GUIDs check box is selected) The value of an IVID (a repository object version identifier) you want to search for.

Search on GUIDs

Enables you to perform a search based on the internal globally unique identifiers (GUIDs) of an object. You can search on the object identifier or the version identifier.

Display GUIDs

Displays the value of the internal globally unique identifiers that match the search conditions in the Search Results window.

Match case

If selected, causes a case-sensitive search to be performed on the values in the Name and Short Name fields, and the data fields in the dialog boxes displayed by the Version, Audit and Advanced buttons. If clear, the search is not case-sensitive.

Search subfolders

If selected, extends the search to subcontainers (if any) of the container shown in the Folder Path field, if used. If clear, only the container shown in Folder Path is searched.

Version

Displays a further dialog box enabling you to specify version details. You can search on the version status (checked in, checked out or not versioned), on the version label or on the checkin branch.

Audit

Displays a further dialog box enabling you to search on the audit properties of an object (date created, date last modified, date format, user who created the object, user who last modified the object, and the number of times the object has been modified).

Advanced

Displays a further dialog box enabling you to specify advanced search conditions based on object property values.

Search

Starts the search operation.

Count Hits

Displays the number of matches, if any, for the search conditions. With a large repository, this can indicate whether you need to refine the search conditions before executing the query.

SQL

Displays the SQL query that will be executed by the current search conditions. You can edit this query before executing it.


File - Access Rights - View Access Rights
Access Rights - View Access Rights (File Menu)

Related Topics

Displays the access rights that you or another repository user have for a selected workarea, container or configuration. About

Note:	If you do not have the Manage User repository privilege and do not have Administrate access rights to the selected item, access rights for other users will not be shown.

Dialog box options

Object

Enables you to choose a workarea, container or configuration for which to display access rights.

Owner

Indicates the owner of a selected item in the Object list.

Users

A list of the users who have access rights to the selected item in the Object list.

Access Rights

The access rights that a selected user has for the selected item in the Object list. If multiple users are selected, this shows the combined set of access rights that they have.

A user may be shown as having access rights for a container. However, if that user does not have access rights to a workarea in which that container is visible, the user will not be able to perform operations corresponding to those access rights on objects in the container. The container itself will be visible to that user only via the All Containers node in the Navigator window.

Apply public and workarea rights

If the selected item is a container, checking this box applies the workarea access rights, together with those defined for the PUBLIC role, to the container.

If the selected item is a shared workarea or a configuration, checking this box applies the access rights defined for the PUBLIC role to the item.

If the selected item is a private workarea, this check box is disabled.

Grant Access

Displays a further dialog box showing the complete set of access rights for the selected item, allowing you to grant or revoke these rights.


Access Rights

Related Topics

You can grant or revoke a number of access rights to a selected workarea, container or configuration. The access rights are:

Access right	Allows user to...
Administrate	Grant, revoke or delete access rights on a repository object
Compile	Refresh a workarea
Delete	Delete an object (or perform force delete or purge if they have the necessary repository privileges)
Insert	Create an object
Select	Query an object
Update	Modify an object
Update Spec	Redefine a workarea
Version	Check out/check in an object
Repository privileges, such as those for force delete or purge, are set by the repository owner using the Repository Administration Utility.

If a user does not have the Version access right, that user can still modify an object under version control provided that the object is checked out.


File - Access Rights - Grant Access Rights
Access Rights - Grant Access Rights (File Menu)

Related Topics

Enables you to grant or revoke the access rights for yourself or other users to one or more selected containers, configurations or shared workareas. You must either own the items yourself or have the Administrate access right to them. About

You can also use this option to transfer ownership of a workarea, container or configuration that you own to another user.

You must select at least one workarea, container or configuration in the Navigator window before using this option.

Dialog box options

Objects

The list of workareas, containers or configurations that you selected.

Owner

Indicates the owner of a selected item in the Objects list.

Users

A list of the repository users who have been defined. You can select one or more users from this list and grant or revoke access rights for them.

Access Rights

A list of the access rights that you can grant or revoke. About

To Grant

When checked, indicates that the corresponding access right is to be granted to the selected users for the items selected in the Objects list.

To Revoke

When checked, indicates that the corresponding access right is to be revoked from the selected users for the items selected in the Objects list. You cannot revoke Administrate or Select access for an item if you are its owner. You can revoke an access right on an item from another user only if you originally granted the access right, or if you own the item.

Recurse Sub-Containers

When checked, indicates that the access rights to be granted or revoked for a selected container in the Objects list are also to be granted or revoked for any subcontainers it might have.

Grant

Grants the access rights specified.

Revoke

Revokes the access rights specified.

Ownership

Enables you to transfer ownership of one or more selections in the Objects list to another user.


File - Recent Windows
Recent windows (File Menu)

Opens any of the four most recently accessed windows in the Repository Object Navigator.


Edit - Undo
Undo (Edit Menu)

Related Topics

Undoes the last edit operation performed.

If the last operation cannot be undone, this option is disabled.


Edit - Paste Reference
Paste Reference (Edit Menu)

Related Topics

Inserts the contents of the Clipboard as a reference from an object selected in the Navigator window. For example, if you have placed a table definition on the Clipboard, pasting it as a reference from a module component enables you to create a module component table usage.

To place an item on the Clipboard for pasting as a reference, use Edit→Copy.

Note:	Edit→Paste Reference creates an object reference, whereas Edit→Paste creates an object copy.


Edit - Create
   Create (Edit Menu)

Related Topics

Creates a new item in the repository. The kind of item created depends on which node is currently selected in the Navigator window:

Current selection	Effect
Private Workareas heading Shared Workareas heading Workarea name	Invokes Workarea Wizard for creating new workarea
Configurations heading	Invokes Configuration Wizard for creating new configuration
Container type heading (e.g. Folders)	Creates container of that type
Container name	Creates new container of that type
Element type heading (e.g. Files)	Creates new object of that element type
SAC element type SAC element name	Creates new SAC element of that type
Compare this option with the Create Child option, which also creates repository objects but is available only in specific circumstances.


Edit - Create Child
   Create Child (Edit Menu)

Related Topics

Creates an item that is one level lower in the repository hierarchy than a selected item. The kind of item created depends on which node is currently selected in the Navigator window:

Current selection	Effect
Workarea name	Displays list of container types for creating a container
Container name (must be checked out if under version control)	Displays list of element types for creating a repository object
Configuration name (must be checked out)	Enables you to add members to the configuration
Compare this option with the Create option, which also creates repository objects but at the same hierarchical level as the selected item.


Edit - Create Reference
   Create Reference (Edit Menu)

Related Topics

Creates a reference from a selected repository object to another object. For example, you can record the usage of a particular entity by a particular business function.

Dialog box options

Look In

Enables you to select the level in the repository hierarchy at which the objects available for reference are displayed.

 (Up One Level)

Selects the level above the current one in the repository hierarchy.

 (List View)

Displays only the names of the available repository items in a multi-column list.

 (Details View)

Displays various general details about the items in the list:  name, element type, attributes, the date when the item was last modified and the user who last modified it.

 (Version Details)

Displays version details, if any, about the items in the list:  name, element type, attributes, version label, branch and version number.

List box

Lists the objects at the current hierarchy level that are available for referencing.

Find elements that match this criteria

These fields enable you to filter the list of objects displayed.

Name

The name of the object. You can use wildcards; for example, entering "c%" and clicking OK causes the list to include only those objects of the selected type whose names begin with the letter C.

Type

The element type. You can choose a type from the dropdown list.


Edit - Delete
 Delete (Edit Menu)

Related Topics

Deletes one or more selected repository objects, containers, non-versioned configurations or workareas. About

Caution: 	You cannot restore a deleted workarea.

Where a repository object (other than a configuration) is under version control, this option removes the container membership for that object version. The object version is retained in any previous versions of its container, but is no longer visible either in the current workarea or in any workareas that use subsequent versions of the container.

You cannot use this option to delete an object that has external references in other containers. You must either delete all external references first, or use Utilities→Force Delete.

This option does not delete a configuration that is under version control. To do so, or to delete one or more versions of any repository object, use Version→Purge Versions.

Dialog box options

List box

Lists the items that have been selected for deletion.

Recursively delete subfolders?

Select this box if you are deleting a container that has subcontainers defined. Deleting recursively causes deletion of the selected container and all its contents, including any subcontainers and all their contents.

Delete mapped file system files/folders

(Displayed only when deleting a repository container, or file owned by a container, that is mapped to a file system.) When selected, deletes the corresponding file or directory in the file system as well as the selected repository file or container. Use this option with care. If you inadvertently delete file system files or directories, restore them from the wastebasket and then synchronize the repository and file system.

Delete

Deletes all listed items.

Remove From List button

Deselects any items that do not require deletion.


Edit - Delete Reference
 Delete Reference (Edit Menu)

Related Topics

This option marks the selected reference for deletion from the repository. References are denoted in the Navigator window by a [image] icon.

Dialog box options

List box

Lists the references that have been selected for deletion.

Delete

Deletes all listed references.

Remove From List button

Deselects any references that do not require deletion.


Edit - Include in Workarea
Include in Workarea (Edit Menu)

Related Topics

Enables you to include checked-in versioned containers or repository objects in the selected workarea. You can include these items from anywhere in the repository, provided that you have access rights to them. Note that you cannot include items that are not under version control.

Dialog box options

Workarea

The name of the selected workarea.

Include container or object version in the workarea

The names of the containers or objects you want to include in this workarea. You can specify these items by name, enclosing the names in double quotes ("") and separating them with spaces, or you can use the Browse button to locate these items and select them.

Refresh workarea now?

Before you can see these items in your workarea you must refresh the workarea. If this box is selected, the workarea is refreshed as soon as you click OK. If the box is cleared, the items will become visible the next time you refresh the workarea.


Edit - Exclude from Workarea
Exclude from Workarea (Edit Menu)

Related Topics

Enables you to exclude checked-in versioned containers or repository objects from the selected workarea. Excluded objects still exist in the repository, but are no longer visible in the selected workarea.

Dialog box options

Workarea

The name of the selected workarea.

Exclude these object versions from the workarea

The names of the containers or objects you have chosen to exclude from this workarea.

Refresh workarea now?

Before you can remove these items from view in your workarea you must refresh the workarea. If this box is selected, the workarea is refreshed as soon as you click OK. If the box is cleared, the items will be removed from view the next time you refresh the workarea.


Edit - Empty Wastebasket
Empty Wastebasket (Edit Menu)

Related Topics

Removes from the repository all objects in the selected wastebasket.

Caution:	You cannot undo this operation. Repository objects removed in this way cannot be restored.

To empty a workarea wastebasket, you must have DELETE access to that workarea.


Edit - Restore from Wastebasket
Restore from Wastebasket (Edit Menu)

Related Topics

Restores the selected objects in the wastebasket to the repository. Objects are restored to the workarea from where they were deleted.


View - Show Group Tabs
Show Group Tabs (View Menu)

Related Topics

Switches the Navigator window to display a set of tabs at the top of the window. When group tabs are displayed, the Navigator window lists only the objects from the group selected by the tab. About

The tabs are labeled with the names of element type groups that correspond to various stages in the process of database or application modeling and design.


View - Hide Group Tabs
Hide Group Tabs (View Menu)

Related Topics

Turns off the display of element type group tabs at the top of the Navigator window.

When group tabs are hidden, the Navigator window is no longer restricted to displaying only those repository objects from the group defined by a selected tab. Instead, the window displays all objects at the selected level in the repository hierarchy.


View - Element Hierarchy View
Element Hierarchy View (View Menu)

Related Topics

For a selected element type, displays parent and child elements of that type as a hierarchy. A [image] icon is displayed next to each element to indicate that hierarchy view is selected for the adjacent node.


View - Element List View
Element List View (View Menu)

Related Topics

For a selected element type, displays all elements of that type at the same level, together with their associations.


Navigator - Show/Hide
Show/Hide (Navigator Menu)

Related Topics

Shows or hides element type headings in the Navigator window.

Dialog box options

Show Type Headings

For

The kinds of item for which you want to display the headings:

Objects	primary access controlled (PAC) elements
Folders	containers
Child elements	secondary access controlled (SAC) elements, usages etc.
Always

Headings are always displayed for the selected items.

Never

Headings are never displayed for the selected items.

Only for non empty nodes

For the selected items, headings are displayed only for those objects of which a node in the Navigator window includes at least one instance. For example, if a container has no instances of table definitions, the heading Table Definitions does not appear in the Navigator window for that container when the container is fully expanded.

Only for nodes containing more than one type

For the selected items, headings are displayed for a node in the Navigator window only if the node contains objects of more than one type. For example, if a container contains only table definitions, the heading Table Definitions does not appear; only the individual object names are listed.

Show Inclusions

When selected, displays the containers, configurations and workareas in which the selected types of item are included.

Show Usages

When selected, displays the references to other objects for the selected types of item.

File System files outside repository

When selected, displays files that reside in mapped containers but which have not been uploaded to the repository.


Navigator - Filter
Filter (Navigator Menu)

Related Topics

Enables you to customize the Navigator window in several ways.

For workareas, containers or configurations, or for repository objects of a selected type, you can include in the Navigator window only those items with properties that correspond to one or more specified conditions. This is useful, for example, where a repository has a large number of objects of a particular type but you do not want to display all of them in the Navigator window.

You can perform simple filters, for example by object name, or more advanced filters using complex filter conditions. You can also:

•	change the display order within an element type

•	display object properties in the Navigator window (besides those in the Property Palette)

Dialog box options

For Object Type

The type of object to which the customization is to apply.

Data

Applies the customization to the object data displayed in the Navigator, e.g., the object names.

Headings

Applies the customization to the element type headings in the Navigator.

Note:	If you want to apply customization to both data and headings, do so in separate operations.

The following tab is selected initially:

Filter Conditions

The dialog box also has these tabs:

Sort Sequence

Show Properties

Apply button

Applies the changes immediately in the Navigator window. If you display the Navigator window and the dialog box side by side, you can see the effect of your changes as you make them.

Save as Default button

Saves the changes as the default display for objects of this type.

Save as View button

Saves the changes as a user-defined view. You can then add this view to the Navigator window. How


Filter/Search Conditions tab
Filter Conditions tab
Search Conditions tab

From the Filter Conditions or Search Conditions tab, you can specify various conditions for a filter or search operation. You base these conditions on property values of objects of the selected type. Only objects of the selected type whose properties satisfy the conditions will appear as the output of the filter or search operation. About

	AND condition	Sets an AND condition for the selected properties (both this condition and one or more others must be satisfied)
	OR condition	Sets an OR condition for the selected properties (either this condition or one or more others must be satisfied)
	Group	Groups selected properties together for filtering purposes
	UnGroup	Cancels grouping for selected properties
	Duplicate Property	Copies a property to enable you to set alternative conditions involving this property
	Clear Condition	Clears a filter condition for a selected property
	Move Up	Moves a property up the list, for grouping purposes
	Move Down	Moves a property down the list, for grouping purposes
AndOr

AND indicates that you have set an AND condition involving this property.

OR indicates that you have set an OR condition involving this property.

Property

The name of the property to be used for the filter or search operation. You can filter or search using any number of object properties.

Condition

The condition that must be satisfied for objects to be displayed. For example, if the Name property has Condition set to A%, only objects of this type whose name begins with A will be displayed.


Sort Sequence tab

From the Sort Sequence tab, you can change the order in which objects of the selected type are output by the filter or search operation.

	Move Up	Moves a property up the list, for sorting purposes
	Move Down	Moves a property down the list, for sorting purposes
Order By

When selected, specifies that you are sorting the objects based on values for this property (for example, in ascending order of Name). You can sort objects by more than one property; in this case, objects are sorted by the highest specified property in the list, then by the next highest, and so on.

Property

The name of the property to be used for sorting. You can sort using any number of object properties.

Descending

When selected, specifies that descending order is to be used for the sort with this property (default is ascending order).


Show Properties tab

The Show Properties tab enables you to display selected properties in the output from the filter or search operation.

By default, the output lists object definitions by name. You can display other properties as well as (or instead of) the name, for example the short name.

	Move Up	Moves a property up the list
	Move Down	Moves a property down the list
Show

When selected, specifies that the corresponding property is to be displayed for objects of the selected type.

Property

The name of the property. You can display any number of object properties in the output.


Navigator - Sort
Sort (Navigator Menu)

Related Topics

Enables you to change the display order in the Navigator window for the contents of workareas, containers or repository objects of a selected type.

You can base the sort on any property, or any combination of properties, of the element type. For example, you can sort objects by creation date, name, and so on, in either ascending or descending order.

You can also:

•	show or hide objects of the selected type

•	display object properties in the Navigator window (besides those in the Property Palette)

Dialog box options

For Object Type

The type of object to which the customization is to apply.

Data

Applies the customization to the object data displayed in the Navigator, e.g., the object names.

Headings

Applies the customization to the element type headings in the Navigator.

Note:	If you want to apply customization to both data and headings, do so in separate operations.

The following tab is selected initially:

Sort Sequence

The dialog box also has these tabs:

Filter Conditions

Show Properties

Apply button

Applies the changes immediately in the Navigator window. If you can display the Navigator window and the dialog box side by side, you can see the effect of your changes as you make them.

Save as Default button

Saves the changes as the default display for objects of this type.

Save as View button

Saves the changes as a user-defined view. You can then add this view to the Navigator window. How


Navigator - Display Properties
Display Properties (Navigator Menu)

Related Topics

Enables you to choose which properties to display in the Navigator window for the contents of workareas, containers or repository objects of a selected type.

By default, the Navigator window displays objects by name. You can display other properties as well as (or instead of) the name, for example the short name.

You can also:

•	show or hide objects of the selected type

•	change the display order within an element type

Dialog box options

For Object Type

The type of object to which the customization is to apply.

Data

Applies the customization to the object data displayed in the Navigator, e.g., the object names.

Headings

Applies the customization to the element type headings in the Navigator.

Note:	If you want to apply customization to both data and headings, do so in separate operations.

The following tab is selected initially:

Show Properties

The dialog box also has these tabs:

Filter Conditions

Sort Sequence

Apply button

Applies the changes immediately in the Navigator window. If you can display the Navigator window and the dialog box side by side, you can see the effect of your changes as you make them.

Save as Default button

Saves the changes as the default display for objects of this type.

Save as View button

Saves the changes as a user-defined view. You can then add this view to the Navigator window. How


Navigator - Clear Selected Filters
Clear Selected Filters (Navigator Menu)

Related Topics

Clears any Navigator window display filters for the selected element types. The display reverts to the default display for these element types.


Navigator - Clear All Filters
Clear All Filters (Navigator Menu)

Related Topics

Clears all Navigator window display filters. The display reverts to the default display for the Navigator window.


Navigator - Find
Find (Navigator Menu)

Related Topics

Finds a text string in the active Navigator window or Property Palette. The search starts from the current selection in the Navigator window or Property Palette.

Dialog box options

Find

The text string for which to search.

Direction

Identifies whether the direction of the search is Up or Down from the current selection. If nothing is selected the search starts from the top of the active window.

Find Next button

Searches the active window for the next occurrence of the string entered in the text box. The direction of the search is determined by the Direction option.


Utilities - Designer - Database Design Transformer
Designer - Database Design Transformer (Utilities Menu)

Related Topics

Runs the Database Design Transformer, which transforms an entity model into a database design in the repository. The utility creates tables to record instances of each entity, columns to store the attributes, and constraints to implement the relationships between entities. It also creates constraints to enforce any unique identifiers that you have defined, and indexes to support your foreign keys.


Utilities - Designer - Application Design Transformer
Designer - Application Design Transformer (Utilities Menu)

Related Topics

Runs the Application Design Transformer, which transforms function and business unit definitions into an application system design in the repository. The utility converts functions into candidate modules, which can then be implemented as screens, reports, manual procedures, or utilities. The Transformer also converts function data usages to module data usages, which define how a module uses the tables and columns in the database. The utility then uses the module-to-business-unit association to create candidate menu modules and menu structures.


Utilities - Designer - Table to Entity Retrofit
Designer - Table to Entity Retrofit (Utilities Menu)

Related Topics

Runs the Table to Entity Retrofit utility, which enables you to derive entity definitions from tables in an existing database. You normally do this as part of a comprehensive database design capture process, which enables you to incorporate legacy data in a repository.


Utilities - Designer - Create Function Attribute Matrix
Designer - Create Function Attribute Matrix (Utilities Menu)

Related Topics

Creates default function attribute usages for all attributes of entities used by a business function.


Utilities - Designer - Create Default Module Data Usages
Designer - Create Default Module Data Usages (Utilities Menu)

Related Topics

Creates default data usages (such as module components with table usages and data bound items) for a selected module.

Note:	The Language property of the selected module must be defined, e.g. Oracle Forms.

This utility uses relationships between business functions, entities, tables and modules to create data usages for a module. The diagram below shows the information that must be recorded in the repository for the selected module, before running this utility.

Usage objects	Typically created by ...
A - Module function usages	Application Design Transformer
B - Function entity usages and function attribute usages	Application Design Transformer
C - Table entity usages and column attribute usages	Database Design Transformer
D - Module component data usages	Default Module Data Usages Utility
When A, B and C exist in the repository for a given module, the Default Module Data Usages utility will create D, the module component data usages (for example, module components with table usages and data bound items).

An example of when you may need to use this utility is if you used the Application Design Transformer to create default module definitions in the repository, before using the Database Design Transformer to create table definitions based on entities. When run in this order, the Application Design Transformer creates module definitions with no module components (or data usages). Before running the Default Module Data Usages utility to create the missing data usages, you must ensure that table entity usages and column attribute usages exist. You can do this by running the Database Design Transformer for the appropriate entities.

Re-running the Default Module Data Usages utility

You may want to change the entity model, the function hierarchy, or the relationship between them. The table below describes how this utility processes such changes:

If you...	When you re-run the utility...
Add a new entity and attribute usage to a function that is already mapped to a module.	A new module component, table usage, and bound item are created for the new table and column which map to the new entity and attribute.
Add a new attribute usage to a function that is already mapped to a module.	A new bound item is created. The bound item will be created in the table usage that corresponds to the attribute's owning entity.
Add a module function usage for an existing module to point to a new function.	New module components, table usages, and bound items are created for the entities and attributes that the function uses.
Add a mandatory column to a table which is mapped to an entity, which is used by a function on which a module is based.	A new bound item is not created. This must be added manually.
Update the properties of function entity usages, or function attribute usages.	Neither bound items or module networks are updated to reflect the new usages. These must be changed manually.
Delete function module usages, function entity usages, function attribute usages, or table entity usages.	Corresponding module components, table usages, and bound items are not deleted. The Default Module Data Usages utility does not delete module elements.
Dialog box options

Client/Server

Indicates whether processing is currently taking place at the client or the server.

Progress message

Records progress of the utility while gathering the information required to generate default module data usages.

List box

Lists the actions performed by the utility, for example the repository objects that have been created.

Cancel button

(Displayed during generation only). Cancels the process.

Close button

Closes the dialog box.

Copy button

Copies the contents of the List box to the Clipboard.


Utilities - Designer - Update Attributes in a Domain
Designer - Update Attributes in a Domain (Utilities Menu)

Related Topics

Updates all the appropriate attributes with the property details of the selected domain. You might use this, for example, when you edit a domain and want to update all the attributes that use that domain.

This utility overwrites any properties in a column or attribute that conflict with the same property in the domain to which the column or attribute belongs. Null values in the domain replace any non-null values. The exception to this is the Default Values property, which is overwritten only if the corresponding property of the column or attribute has a null value.


Update Columns/Attributes in a Domain dialog box
Designer - Update Columns/Attributes in a Domain dialog box

Related Topics

Updates all columns and attributes in the selected domain with any changes that have been made to that domain.

This utility overwrites any properties in a column or attribute that conflict with the same property in the domain to which the column or attribute belongs. Null values in the domain replace any non-null values. The exception to this is the Default Values property, which is overwritten only if the corresponding property of the column or attribute has a null value.

Container

The name of the owning container for the domain definition.

Domain

The name of the domain in which the columns or attributes have been placed.

Auto-checkout

This check box is enabled only if the owning entity (for an attribute in the domain) or table (for a column in the domain) is currently under version control and checked in. When selected, it causes the entities or tables to be checked out so that the update can take place. If the check box is cleared, entities or tables under version control and checked in are ignored by this utility.


Utilities - Force Delete
Force Delete (Utilities Menu)

Related Topics

Invokes the Force Delete Wizard. This removes selected non-versioned repository objects, or secondary access controlled (SAC) elements of any kind of object, regardless of any delete constraints that may have been defined for the corresponding element type. About

The wizard is a predefined set of screen forms that takes you step by step through the force delete process. Objects removed in this way are placed in the workarea wastebasket, from where they can be recovered. However, it is not possible to recover references or child elements.

You can use the Force Delete Wizard only if you have the FORCE repository privilege, and DELETE access rights to the workarea and the owning container.

Note:	To forcibly remove checked-in object versions, use Force Purge.


Utilities - Force Purge
Force Purge (Utilities Menu)

Related Topics

Invokes the Force Purge Wizard. This removes a selected checked-in object version, regardless of any delete constraints that may have been defined for the corresponding element type. About

The wizard is a predefined set of screen forms that takes you step by step through the force purge process. Object versions removed in this way cannot be recovered, nor is it possible to recover references or child elements.

You can use the Force Purge Wizard only if you have the FORCE or PURGE repository privileges, and DELETE access rights to the owning container.

Note:	To forcibly remove non-versioned repository objects, or secondary access controlled (SAC) elements of any kind of object, use Force Delete.


Utilities - Export
Export (Utilities Menu)

Related Topics

Enables you to export data from the repository to a file. You can export repository data to:

•	•	a file in Oracle database export format

•	•	an export file in text format

This option starts the Export Wizard, a predefined set of screen forms that takes you step by step through the export process.


Utilities - Import
Import (Utilities Menu)

Related Topics

Enables you to import data into the repository from a file. You can import repository data from:

•	•	a file in Oracle database export format

•	•	an export file in text format

This option starts the Import Wizard, a predefined set of screen forms that takes you step by step through the import process.


Utilities - Download Files and Folders
Download Files and Folders (Utilities Menu)

Related Topics

Copies selected files or containers from the repository to a file system directory.

Dialog box options

Source

Download from repository path

If you selected files or containers to download before the dialog box was displayed, this shows the repository path of these items.

File(s) / Folder(s)

The names of the files or containers you want to download. Enter any multiple names in double quotes ("") and separated by a space. The Browse button enables you to locate and select a file or container.

Recurse into sub-directories

When selected, indicates that any subcontainers of the selected container, and their contents, will also be downloaded. When clear, indicates that only the contents of the selected container will be downloaded.

Destination

To OS path

The full pathname of the file system directory to which you are downloading. If a mapping has been defined for the destination directory, this field shows the mapping, but you can change this value. If no such mapping is defined, the field shows the last destination specified, if any, otherwise it is blank. The Browse button enables you to locate and select a directory.

Options

Enables you to convert downloaded text (but not binary or Unicode) files from MS-DOS format to UNIX format or vice versa.


Options dialog box

Enables you to convert text (but not binary or Unicode) files from MS-DOS format to UNIX format or vice versa.

The difference has to do with the end-of-line (EOL) indicator. In MS-DOS (or Windows), end of line is indicated by a carriage return + line feed combination, whereas in UNIX only a line feed character is used.

Use mapping defaults

(Displayed only for synchronization) Causes a default translation specified during folder mapping to be used.

Do translation

Causes the selected type of text file translation to take place.

Translate files in MS-DOS format to UNIX format

Use this option if you are mapping, synchronizing or downloading to a UNIX file system.

Translate files in UNIX format to MS-DOS format

Use this option if you are mapping, synchronizing or downloading to a Windows file system.


Utilities - Upload Files and Folders
Upload Files and Folders (Utilities Menu)

Related Topics

Copies one or more files or directories from a file system into a repository container.

Once files have been uploaded, you can perform operations on them from within the repository. For example, you can open or edit an uploaded file using a program appropriate to the file type. The right mouse menu on a selected file indicates the operations you can perform. Uploaded files can also be brought under version control.

Dialog box options

Source

Upload from OS path

The full pathname of the file system directory from which you are uploading. If a mapping has been defined for the destination repository container, this field shows the mapping, but you can change this value. If no such mapping is defined, the field shows the last destination specified, if any, otherwise it is blank. The Browse button enables you to locate and select a directory.

File(s) / Folder(s)

The names of the files or directories you want to upload. The Browse button enables you to locate and select a file.

Recurse into sub-directories

When selected, indicates that the contents of any subdirectories of a selected directory will also be uploaded. When clear, indicates that only the contents of a selected directory will be uploaded.

Destination

To repository path

The container (and its workarea) to which you want to upload files.

Overwrite changed files

If you select this check box, changed file system files that already exist in the repository are overwritten on upload if they are checked out or are not under version control.

Check in after upload

If you select this check box:

•	All uploaded files and directories are checked in after the upload. Files that are skipped because they have not changed, or because you decided not to overwrite existing files, are not checked in. New or non-versioned files and directories are brought under version control.

•	If you select a directory and choose Recurse into sub-directories, the directory and all its subdirectories are checked in.

•	If you select a file and choose Recurse into sub-directories, the parent directory of the file is not checked in.


Utilities - Map Folder to File System
Map Folder to File System (Utilities Menu)

Related Topics

Associates a selected repository container with a directory in a file system to which you have access. You can also use this option to delete such an association.

Note:	You cannot map a subcontainer; you can map only a container that has no parent.

A mapping provides a default specification for upload and download operations. In addition, a mapping is required before you can synchronize that file system with the repository. You must requery the selected repository container before you see the effect of mapping, or mapping deletion, in the Navigator window.

A mapped container is denoted by  in the Navigator window of the Repository Object Navigator.

Dialog box options

Map folder name to OS Path

The full pathname of the file system directory you want to map. The Browse button enables you to locate and select a directory.

Delete Mapping

Deletes the association between the selected container and the file system indicated by Mapping path.

Options

For files in a mapped container or file system, enables you to convert text (but not binary) files from Windows (MS-DOS) format to UNIX format or vice versa.

Current folder mappings in workarea

Lists the current associations between containers and file systems in the current workarea.

Folder name

The name of a container in the current workarea.

Mapping path

The name of the file system directory with which this container is associated.

Text conversion

Indicates the type of conversion, if any, specified for text files in a particular mapping.

Apply

Creates the mapping, enabling you to select another container name to map.


Utilities - Synchronize Files and Folders
Synchronize Files and Folders (Utilities Menu)

Related Topics

Enables you to update files in a selected repository container to make them identical to the corresponding files in a mapped file system, or vice versa. For example, if a file is changed in the file system, synchronization ensures that the same changes are made to the corresponding file in the repository.

If you select a container that has not been mapped to a file system, this option requires you to perform the mapping first.

A mapped container is denoted by  in the Navigator window of the Repository Object Navigator.

Dialog box options (unmapped container)

Map Folder to OS Path dialog box

Dialog box options (mapped container)

Recurse into sub-folders

When selected, indicates that the contents of any subcontainers of the selected container will also be synchronized. When clear, only the contents of a selected directory will be synchronized.

Include (create) files new to the repository

When selected, uploads any files in the mapped file system that have not yet been uploaded to the repository (for example, files newly created in the file system).

Leaving this unselected (default) ensures that no new files are uploaded during synchronization. This prevents you from accidentally uploading unwanted files, e.g., intermediate build files and temporary files.

Synchronize

Updates files in the repository with the contents of the corresponding files in a mapped file system or vice versa, depending on which is the later version.

Options

Enables you to convert synchronized text (but not binary) files from Windows (MS-DOS) format to UNIX format or vice versa.


Utilities - Edit File Registry
Edit File Registry (Utilities Menu)

Related Topics

Displays details from the file registry, which determines how a particular file type is treated when it is stored in the repository. The display shows how a particular filename pattern is associated with a particular rule. The rules define whether a file is treated as a text or a binary file, or whether it is stored in compressed or uncompressed format.

The dialog box also enables you to create or update file registry details.

Dialog box options

Pattern and platform options

Pattern

Lists the patterns that have already been defined.

A file type is typically identified by its extension. For example, %.EXE indicates a Windows executable binary file, while %.TXT indicates a text file. The "%" character is the Oracle wildcard character (the equivalent of the "*" character in Windows or UNIX file specifications).

More precise patterns can be used for specific cases. The higher a pattern is in the list, the greater its precedence. Examples

Patterns are case sensitive, so for example you could have different rules for "%.txt" and "%.TXT". However, their effect is determined by the setting of the repository case-sensitive uniqueness checking policy. If this policy is active, the different rules both apply. If the policy is deactivated, only the rule that is higher in the list applies. About

Platform

The type of operating system under which files with the pattern set above are used:

Unix	UNIX systems
Win32	Windows 95/98/NT/2000 systems
All	both of the above
Important:  If you set the platform type to "Unix" for a particular rule then the Windows release of Oracle SCM will ignore this rule and continue scanning the rule set for a matching rule (one that matches both file pattern and platform).  If no matching rule is found then the file is assumed to be a binary file and you will not be able to run the Oracle SCM diff/merge utility.

Rule

Indicates how files with the corresponding pattern and platform are stored. About

The available options are Binary, Text, Compressed and Uncompressed.

Each entry in the file registry can define only one rule at a time. If you want to specify more than one rule for the same pattern (for example, to specify binary and compressed), you need to define two separate registry entries.

If mutually exclusive rules are inadvertently defined for the same pattern (for example, binary and text), the rule that is higher in the display takes precedence.

Description

A text description of the file type.

Top

Moves a selected pattern to the top of the list.

Up

Moves a selected pattern one place higher in the list.

Down

Moves a selected pattern one place lower in the list.

Bottom

Moves a selected pattern to the bottom of the list.

New rule

Enables you to define a new rule for a particular pattern. The new rule is added at the bottom of the list.

Delete rule

Deletes the rule for a selected pattern.

Edit rule

Enables you to edit any part of the rule for a selected pattern.


Examples of file registry use

Example 1

You have a particular file, named "myfile.doc", which you want to be treated as a binary file. However, your file registry is set up so that files with the pattern "%.doc" are treated as text files, and you want to preserve this setting.

To achieve this, you define a new rule (strictly speaking, a new entry in the file registry) that associates the pattern "myfile.doc" with the rule "Binary file". The new rule is added at the bottom of the displayed list. You then move it above the pattern "%.doc" in the list, as follows:

Pattern	Rule
myfile.doc	Binary file
%.doc	Text file
If you fail to move the new rule to this position, it will be overridden by the rule for "%.doc". This is because the file registry evaluates the rules in the order in which they appear in the list. Now, "myfile.doc" is treated as a binary file, but any other file with the extension ".doc" is treated as a text file.

Note that the file registry entries are case-sensitive. Thus, if you think your file is named "myfile.doc" when it is actually named "MyFile.doc", it will still be treated as a text file in this example.

Example 2

You want most files to be stored in compressed format, but you want to store files with the extension ".zip" as uncompressed files.

To do this, you define two rules, as follows:

Pattern	Rule
%.zip	Uncompressed
%	Compressed
Provided that you move the rule for "%.zip" above the rule for "%" in the list, this will achieve the result you want.

Note that mistakenly defining the rules like this:

Pattern	Rule
%	Compressed
%.zip	Uncompressed
would result in all files being compressed, as the "%.zip" rule is below the more general "%" rule.


File Registry Rule dialog box

Enables you to create or edit a rule in the file registry. This determines how a particular file type is treated when it is stored in the repository.

Pattern

The filename pattern that identifies the file or files to which the rule applies. You can use the wildcard character "%" to mean "any character".

Properties

Rule

Specifies the way you want files matching this pattern to be stored in the repository. The available rules are: Text file, Binary file, Compressed file and Uncompressed file.

If you inadvertently define mutually exclusive rules for the same pattern (for example, binary and text), the rule that is higher in the Edit File Registry display takes precedence.

Platform

Specifies the type of operating system under which files with this pattern are used:

Unix	UNIX systems
Win32	Windows 95/98/NT/2000 systems
All	both of the above
Description

A text description of the file or file type to which this pattern applies.


Tools - Navigator
Navigator (Tools Menu)

Related Topics

Changes the focus to the Navigator window if the Property Palette is currently in focus.


Tools - Workarea Wizard
Workarea Wizard (Tools Menu)

Related Topics

Starts the Workarea Wizard. This is a predefined set of screen forms that take you step by step through the process of creating a workarea.


Tools - Configuration Wizard
Configuration Wizard (Tools Menu)

Related Topics

Starts the Configuration Wizard. This is a predefined set of screen forms that take you step by step through the process of creating a new configuration, or creating a new version of an existing configuration.


Tools - Merge Wizard
Merge Wizard (Tools Menu)

Related Topics

Starts the Merge Wizard, enabling you to merge versions of multiple objects. The Merge Wizard is a predefined set of screen forms that take you step by step through the process of specifying the merge information and instigating the merge operation.

When you have completed the necessary information, the Merge Wizard processes each selected item in turn; if appropriate, in each case the Merge window is displayed for you to preview the selections made by the merge algorithm, and to make selections to override them if necessary.


Tools - Command Line Tool
Command Line Tool (Tools Menu)

Provides access to the command-line interface.

This option opens a window containing a command-line prompt, REPCMD>, enabling you to issue any of a wide variety of commands to perform operations on the repository.

At the REPCMD> prompt, you can enter the HELP command to see a list of available commands. For help on a particular command, enter HELP command_name at the prompt.


Tools - Explorer
Explorer (Tools Menu)

Opens Windows Explorer from within the Repository Object Navigator.

This option can be useful for locating files when uploading and downloading between the repository and a file system.


Tools - Color/Font
Color/Font (Options Menu)

Related Topics

Specifies the text color and font options for the Repository Object Navigator.

You can specify the:

•	color in which various types of text are displayed.

•	fonts used in the Navigator window, Property Palette and Textpad.

Dialog box options

Text Color

The type of item for which you want to change the text color. About

Note:	The current color setting for the selected text type is displayed in the Preview box to the right of this field.

Fonts

Identifies whether the font is to be set for the Navigator, Property Palette or Textpad.

Note:	The current font setting for the selected window is displayed in the Preview box to the right of this field.

Color Palette

Displays a further dialog box from which you can choose the required color.

Font Dialog

Displays a further dialog box from which you can choose the required font.


Options - General Settings
General Settings (Options Menu)

Related Topics

Sets general options within the Repository Object Navigator other than those for colors and fonts.  The settings shown in this dialog box are used as defaults each time this user invokes the tool.  For example, you can specify whether the Welcome Screen should be displayed each time you run the tool, or which date format you want to use.

Note:	To set text colors and fonts, choose Options→Color/Font.

Dialog box options

Show

Welcome Screen

When selected, specifies that the Welcome Screen is to be displayed when the tool is invoked.

Confirm dialog on Copy

When selected, specifies that a confirmation dialog box is displayed when you attempt to copy repository objects.

Confirm dialog on Move

When selected, specifies that a confirmation dialog box is displayed when you attempt to move repository objects.

Version

Determines the format of the object versions.

Version Label

Displays object versions with their version label. A version label is a string that uniquely identifies each version of an object, e.g. 1.3.1.0.

Branch ; Version Number

Displays object versions with their branch names followed by their version numbers, e.g. MAIN;7.

General

Options File

The name of the file that stores the details of user-defined filters, Navigator groups and Navigator views. Use the Browse button to choose a different file.

Date Format

Sets the format in which dates are displayed in the Property Palette for items such as the audit properties (date created, date changed and so on).


Options - Customize Property Palette
Customize Property Palette (Options Menu)

Related Topics

Customizes which properties are displayed on the Property Palette.

Dialog box options

Show

Show Owning Container

Displays or hides the name of the container that owns a repository object.

Show Version Label

Displays or hides the version label property. In a non-versioned repository, this property has no significance.

Show Audit Properties

Displays or hides the audit properties (date created, date changed etc.).

Show BPR Properties

Displays or hides the business modeling properties (under the heading BPR) for those element types that support them, e.g. business functions.

Property Clipboard

Include Multi Line Text Properties

Includes or excludes multi-line text properties in the Properties Clipboard, used when copying properties.

Automatically switch to spreadtable mode on multi insert

When selected, causes the Property Palette to switch automatically to spreadtable view when you create more than one object of the same type.

In spreadtable view, you can list the properties of more than one object at the same time. By contrast, the default view displays the Property Palette as a two-column grid, with the property names listed vertically and their values listed alongside.


Options - Customize Navigator Groups
Customize Navigator Groups (Options Menu)

Related Topics

Customizes which repository objects are displayed in the Navigator window.  For example, if you want to see only the objects associated with database design, you can hide all the other groups. In addition, you can create and delete your own object groups.

Dialog box options

Show/Hide

Enables you to display or hide various groups of repository objects. Note that any changes you make here do not become effective until the next time you use the View→Show Group Tabs option.

Show

When selected, indicates that the corresponding object group is to be displayed in the Navigator window. When clear, the corresponding object group is not to be displayed.

Tab Heading

The name of the object group tab that you want to show or hide in the Navigator window.  About

Description

A description of the object group.

Customize

Allows you to create and delete object groups, and specify which element types the groups are to contain.

List boxes

The left hand panel shows the object groups that you have created, and the element types they contain.  The right hand panel lists all the element types available for inclusion under the selected object group.

Add

Adds an element type to the selected group.

Remove

Removes an element type from the selected group.

MoveUp

Moves a selected element type up the display list in a selected group.

MoveDown

Moves a selected element type down the display list in a selected group.

Add Group

Opens a further dialog box that allows you to enter the name of a new object group, or to copy or modify an existing one.

Delete Group

Deletes a selected user-defined object group.


Create New Navigator Group dialog box

Creates a user-defined object group, and optionally allows you to copy or modify the element types of an existing group.

Dialog box options

Name

The name you want to give the new object group.

Copy Group

Lists the existing object groups that you can copy or modify.


Options - Customize Navigator Views
Customize Navigator Views (Options Menu)

Related Topics

Enables you to define customized views of repository element types. You can then add these views to the display list in the Navigator window.

For example, you might want to create a view that contains only candidate modules, so that you can easily locate them for generation.

Dialog box options

This dialog box has a number of tabs. These do not become active until you define a view name using the Add View button. The tabs are:

Filter Conditions

Sort Sequence

Show Properties

Add View

Displays a further dialog box where you define the view name and the element type upon which it is based.

Delete View

Deletes the selected view from the repository.


Text search buttons

Related Topics

The text search facility allows you to find a text string in the active Navigator window or Property Palette. You enter the string in the text box in the main toolbar at the top of the screen.

•	Text box

This box allows you to enter a text string and begin searching.

•	Find Next button

Searches the active window for the next occurrence of the string entered in the text box. The search for the next occurrence of a text string starts from the selected item and continues to the last item.

•	Find Previous button

Searches the active window for a previous occurrence of the string entered in the text box.


   Find Next button

Related Topics

Finds the next definition that matches the text string in the toolbar text box. The text box is situated to the left of the Find Next button.

0	In the Navigator window, the search starts from the selected node and continues down to the bottom of the window. When the search reaches the bottom of the window, the search continues again from the top. If no matching definitions are found, a message is displayed.

1	In the Property Palette, the search starts at the top of the window and continues to the bottom.


   Find Previous button

Related Topics

Returns to the last item found in a search operation that was initiated by the Find Next button.

0	The Find Previous button is unavailable if the Find Next button has not been previously selected.


   Context-sensitive help button

Provides access to help information about items in the Repository Object Navigator.

0	Clicking this button, or pressing SHIFT+F1, and then choosing a menu option, toolbar button, item in the Navigator window or property in the Property Palette, displays the help topic for the chosen item.

Note:	This facility is very useful for providing immediate information on an object or a property definition.


Collapse/Expand icon

Indicates whether a node has been expanded or collapsed.

0	A Collapse/Expand icon appears to the left of every Navigator window node for which definitions exist in the repository. If a node has no icon next to it, no definitions of that type exist in the repository.

1	The icon can be in one of two different states:

Icon	Meaning
	Collapsed node - definitions at the next level are not displayed
	Expanded node - definitions at the next level are displayed
Clicking the [image] icon expands the node to the next level.

12	Clicking the [image] icon collapses the node.


Shortcut icon

Related Topics

Indicates that the object is referenced from a container other than the current one in the current workarea.

 Shortcut icon

Double-clicking the Shortcut icon navigates to the referenced object. Subsequently clicking the [image] button returns to the original object.


Referenced Object icon

Indicates that the node is a reference to an object that exists elsewhere in the repository.

 Referenced Object icon

Typically a reference indicates a usage by one object of another type of object. For example, an entity attribute that is used by a particular business function will have a reference to that business function under the Usages node for the attribute:

0

1	If you click the Referenced Object icon, the Navigator window shows the referenced object, with its name highlighted and its properties displayed in the Property Palette.

2	Click the [image] button to return to the original display.


Conditions toolbar

	Button	Effect
	Group	Groups two or more selected properties together. You might need to do this to generate the correct SQL statement. 3 To select properties for grouping, click the name of the first property, then hold down the SHIFT or CTRL key and click the name of the second property. Click this button. The () characters are displayed to denote the extent of the grouping.
	UnGroup	Removes grouping from selected properties. 6 To remove grouping, click the name of the first property, then hold down the SHIFT or CTRL key and click the name of the second property. Click this button. The () characters disappear to indicate that grouping has been removed.
	Duplicate Property	Duplicates a selected property. Doing so enables you to specify AND or OR conditions for a property.
	Clear Condition	Blanks out a selected condition value. Click the appropriate Property or Condition field, then click this button.
13	Move Up 14 Move Down	Moves a selected property up or down the list, for grouping purposes. Click the property name, then click the appropriate button as often as desired to move it up or down the list.


Welcome to the Repository Object Navigator

This screen gives you a choice of tasks that you can perform with the Repository Object Navigator.

Where would you like to start?

Invoke Workarea wizard

Creates a new workarea, a space in which you can work on repository objects. You'll need to have at least one workarea accessible before you can start creating repository objects.

Invoke Configuration wizard

Takes you step by step through the process of creating a configuration, a grouping of specific repository objects that make up an application (or part of an application).

Open Navigator

Chooses the level in the repository hierarchy at which you want to open the Navigator window:  the entire repository, or a specific workarea, container, configuration or object.

Search Repository

Locates definitions of objects in the repository. You can search for individual objects of a particular type (e.g. tables, modules) either across the entire repository or within a specific part of it, such as a workarea, container or configuration.

Select Navigator Groups

Chooses which categories of object details you want the Repository Object Navigator to display (e.g. enterprise modeling, module design).

Display this screen on startup

Clear this check box if you prefer not to see this Welcome screen each time you start the Repository Object Navigator.


Using shortcut keys to work with the Repository Object Navigator

Shortcuts for menu options

To		Press		As a shortcut for
Open a new Navigator window		CTRL+O		File→Open
Close the active Navigator window		CTRL+W		File→Close
Save (commit) the property values of the selected object to the repository		CTRL+S		File→Save
Print the contents of the active Navigator window		CTRL+P		File→Print
Exit from the Repository Object Navigator		CTRL+Q		File→Exit
Create a new repository object		INSERT		Edit→Create
Undo the last operation performed		CTRL+Z		Edit→Undo
Remove the selected item or items and place the selection on the Clipboard		CTRL+X		Edit→Cut
Copy the selected item or items to the Clipboard		CTRL+C		Edit→Copy
Place the contents of the Clipboard into the active window		CTRL+V		Edit→Paste
Delete the selected elements from the repository		DELETE		Edit→Delete
Locate object definition		F12		Navigator→Goto Object Definition 26 Properties→Locate Object Definition
Return to the object from which you navigated to a referenced object		SHIFT+F12		Navigator→Return to Object Reference
Make the Navigator window the active window if the Property Palette is active		F3		Tools→Navigator
Open a new Property Palette if none is open, or make the Property Palette the active window if the Navigator window is active		F4 OR ALT+ENTER		Tools→Property Palette
Show this shortcut key help topic		CTRL+K		Help→Show Keys
Shortcuts when using the Repository Object Navigator windows

To		Press
Display the next view in the Navigator window		CTRL+PAGE UP
Display the previous view in the Navigator window		CTRL+PAGE DOWN
Make the next window active		CTRL+F6
Edit properties		ALT+ENTER
Shortcuts when using the Repository Object Navigator dialog boxes

To		Press
Go to the next control		TAB
Go to the previous control		SHIFT+TAB
Abandon changes (Cancel)		ESC


Create New Navigator View dialog box

Related Topics

Enables you to specify details of the new view you are creating.

Name

The name of the new view. This name will appear in the Navigator window when the view has been created and activated.

Based On

The element type to which the view is to apply.


Save As View dialog box

Related Topics

Saves a filtered Navigator window as a user-defined view, which you can subsequently implement. How

View Name

The name you want to give this view. This name will appear in the Navigator window.


Select Associations/Select Type dialog box
Select Associations dialog box
Select Type dialog box

Displays a list of element types from which you can choose when you are creating:

•	a repository object

•	an association or reference (a link between two repository objects)


Generic Select Object dialog box

Related Topics

Displays a list of objects from which you can choose. The actual title of this dialog box depends on the context in which it is displayed.

Filter field

Enables you to enter a filter condition for the list.

 button

Entering a name, or part of a name, and clicking this button restricts the list to those objects whose names match the filter condition.

List box

Lists the objects that are available for selection.

Select All button

Selects all the objects listed.

Clear All button

Deselects all the objects listed.


Create Foreign Key Constraint Components dialog box

Enables you to create components for a foreign key definition.

To enforce the foreign key constraint, you can either specify a single column (the join column) in a table (known as the joining table), or an upper and a lower limit column in a table (known as the range table). In this way, you can ensure that values in the column on which the constraint is defined match those in the join column, or fall in the range defined in the upper and lower limit columns.

For Foreign Key Constraint

The name of the foreign key definition for which you are creating components.

Constraint on Table

The name of the table that is to have a foreign key defined.

The list below this table name shows all the columns defined for this table. Select one to use as the foreign key column.

Joining Table/Range Table

The name of the table that is joined to the first table by this foreign key constraint.

The list below this table name shows all the columns defined for this table. Select one to use as the primary key of this referenced table.

 button

Moves the selected details to the text panel at the bottom of the screen.

Join Column

Specifies that the selected column in the Joining Table/Range Table list is a join column (that is, you are using a single column in the referenced table to validate values in the foreign key column).

Lower Limit Column
Upper Limit Column

Specifies that the selected column in the Joining Table/Range Table list is a lower limit or upper limit column respectively (that is, you are using a range table to validate values in the foreign key column). The Upper Limit Column option button is not activated until you have specified a lower limit column.

Details field

Contains the details of the foreign key constraint you are defining.

Reset

Changes the dialog box settings back to the state they were in when the dialog box was invoked.


Export Wizard

The Export Wizard enables you to export repository data to a file in one of the following formats:

•	Oracle database export format

•	text format

In database format, you can choose to export an entire workarea or configuration, or one or more selected containers from a particular workarea.

In text format, you can export anything from an individual PAC or SAC element to the entire contents of a workarea.

A successful export operation generates various output displays but no error messages. To confirm that an export was successful, look at the end of the export log file for the message "Export terminated successfully without warnings".

Export data to Oracle database export file

This option uses the Oracle database server Export utility. You can use this format when transferring data from one Oracle (or compatible) database to another. The data is exported to a file known as a dump file, which has the default extension .DMP.

The wizard checks for external references during the export operation. These occur when an object that is owned by one container has references to objects owned by a different container. If external references are found, the wizard allows you to choose how you want to process them.

Export data to a text file

This option uses the Repository Loader utility. You can use this format only when transferring data from one Oracle Repository installation to another. The data is exported to an ASCII text file in the Repository Loader format, which has the default extension .DAT.

Use this format if you suspect incompatibilities between the source and target repositories, for example because of different database versions.

You can edit the exported data in the file if you are familiar with the Repository Loader format. About


Export Wizard: Options Required

From this screen you choose which objects you want to export. Your choices are:

Option	Sub-Option	Effect
Export an entire workarea	Export only versions visible in a resolved view	Exports all objects or object versions defined by the workarea specification, but not the workarea specification itself.
	Export all versions included in all rules or configurations that make up the workarea	Exports all objects or object versions defined by the workarea specification, together with the specification itself.
	Export only checked-out and non-versioned objects	Exports only objects that are checked out or not under version control, but not the workarea specification. Containers are exported irrespective of state, because they are required to give context to the other checked-out objects.
	Export all versions of all objects in a workarea	Exports the entire version history of every object defined by the workarea specification, together with the specification itself.
Export all objects in a configuration	-	Exports a configuration and all its contents.
Export selected container from a specified workarea	Recurse not selected	Exports all members of a container, including subcontainers but not their contents.
	Recurse selected	Exports all members of a container, including subcontainers and all their contents.


Export an entire workarea

Exports a selected workarea. You can choose how much of the workarea to export: for example, only certain object versions, or all versions of all objects in the workarea. The workarea specification may or may not be exported, depending on the option you choose.

Dialog box options

Specify workarea to export

The name of the workarea to be exported. If you selected a workarea before starting the Export Wizard, the name appears here. Alternatively, you can enter a workarea name, or choose one using the Browse button.

Export only versions visible in a resolved view

Exports only those objects or object versions that are visible in this workarea in the Navigator window. These are defined by the rules and configurations that make up the workarea specification, though the specification itself is not exported. Thus for example, if the workarea specification consists of two rules, LATEST(MAIN) and LATEST(TEST), then objects that appear on both the MAIN and TEST branches have the latest versions from both branches exported.

Export all versions included in all rules or configurations that make up the workarea

Exports only those objects or object versions that are visible in this workarea in the Navigator window. These are defined by the rules and configurations that make up the workarea specification, which is also exported.

Export only checked out and new objects

Exports only checked-out versions of objects in this workarea, together with any objects in the workarea that are not under version control. The workarea specification is not exported.

Export all versions of all objects in a workarea

Exports every version of every object defined by the workarea specification, together with the specification itself. Doing so allows you to export the complete version history of an object. Use this option with caution, however, as it could result in an extremely large export file.


Export all objects in a configuration

Exports a configuration and all its member objects or object versions. You can use the Browse button to locate and select a configuration.


Export selected container from a specified workarea

Exports the contents of a selected container from a specified workarea.

Dialog box options

Specify workarea from which to export container

The name of the workarea from which the container is to be exported. If you selected a workarea before starting the Export Wizard, the name appears here. Alternatively, you can enter a workarea name, or choose one using the Browse button.

Select container to export

The name of the container whose contents you want to export. If you selected a container before starting the Export Wizard, the name appears here. Alternatively, you can enter a container name, or choose one using the Browse button.

Recurse through sub directories

When selected, exports all members of a container, including subcontainers and all their contents. When clear, exports all members of a container, including immediate subcontainers but not their contents.


Export Wizard: Export File and Log File

Specifies where you want to store the export file itself and the log file produced by the export operation.

Dialog box options

Specify export file

The name and location of the file that is to contain the exported data. You can enter a file name and location, or choose one using the Browse button. Make sure the location is a directory to which you have write access.

Specify log file

The name and location of the file that is to contain the log data from the export operation. You can enter a file name and location, or choose one using the Browse button. Make sure the location is a directory to which you have write access.

Dependencies

Export dependency tables

(Database export format only) If you want to export any dependency information for the exported objects that has been created by the Dependency Manager tool, select this check box, otherwise leave it clear. Note that including dependency information could result in exporting a very large amount of repository data.

Display files when finished?

If you want to see the contents of the export file and log file when the operation has finished, leave the default option Yes, otherwise choose No.

Advanced Options

(Database export format only) Displays a further dialog box in which you can specify a rollback segment to use for the export operation. The dialog box also enables you to choose a tablespace for the temporary tables that contain the exported data.

Finish

Begins the export operation.

When you click Finish, you may see a message that the temporary tables are already populated. This means that data from an earlier export or import operation is still in these tables. Click Yes to continue, overwriting the existing data in the temporary tables. Note that there is only one set of temporary tables per repository username. Thus if more than one user runs the Export utility using the same repository username, export data may be unintentionally overwritten.


Advanced Options dialog box

Enables you to specify further import or export options.

Dialog box options

Storage information

Specify rollback segment

Enables you to choose a rollback segment for the operation. An export or import operation may require a large rollback segment if operating on large volumes of data. The dropdown list shows the rollback segments that are available; make sure you choose one that is large enough for the amount of data you are importing or exporting. How

If none of these is large enough contact your database administrator, who can define one that you can select here.

Specify tablespace for table and index storage

Enables you to choose a tablespace to store the temporary tables (also known as the XT tables) used by the operation, together with their indexes.

Export

These check boxes are activated only when you are using the Export Wizard.

Extract registered meta data

When selected, includes data from Oracle schemas that have been registered in the repository. This check box is active only if such data exists in the workarea, container or configuration selected for export.

Import

These check boxes are activated only when you are using the Import Wizard.

Remove dangling references

When selected, removes from the imported data any references to objects that do not exist in the target repository.

Frequent updates

When selected, commits the data to the target repository at frequent intervals during the import operation. We do not recommend performing frequent updates unless you are importing a large amount of data. However, if the operation fails in this case, you may need to roll back manually as the operation would be only partially completed. Because of this, we recommend that the repository owner backs up the repository before anyone uses the frequent updates option.

When cleared, commits only at the end of the operation.


Export Wizard: Objects Selected

This enables you to select one or more individual objects for export. You do this by selecting objects in the left-hand pane and moving them to the right-hand pane by means of the arrow buttons.

Left-hand pane

Shows the objects available for export. This is a list of all objects visible in the current workarea.

Right-hand pane

Shows the objects that are selected for export.

Moves a selected object from the left-hand (available objects) pane to the right-hand (objects selected) pane.

Selects all available objects for export.

Moves a selected object from the right-hand (objects selected) pane to the left-hand (available objects) pane.

Deselects all objects selected for export.


Import Wizard

The Import Wizard enables you to import repository data from a file in one of the following formats:

•	Oracle database export format

•	text format

Import from an Oracle database export file

This option uses the Oracle database server Import utility. You can use this format when transferring data from one Oracle (or compatible) database to another. The data is imported from a file known as a dump file, which has the default extension .DMP.

Import from a text based export file

This option uses the Repository Loader utility. You can use this format only when transferring data from one Oracle Repository installation to another. The data is imported from an ASCII text file in the proprietary Repository Loader format. This file has the default extension .DAT. About


Import Wizard: Import File and Error Log File

Enables you to specify the import file you want to use, and the details of the log files produced by the import operation.

Note:	When you click Next on this screen, you may see a message to the effect that the temporary tables are already populated. This means that data from an earlier export or import operation is still in these intermediate tables, sometimes known as XT tables. Click Yes to continue (doing so will overwrite the existing data in the temporary tables).

Dialog box options

Specify import file

The name and location of the file that contains the data to be imported. You can enter a file name and location, or choose one using the Browse button.

Specify error log file

The name and location of the file that is to contain the error log data from the import operation. You can enter a file name and location, or choose one using the Browse button.

Display logs when finished?

If you want to see the contents of the log files when the operation has finished, leave the default option Yes, otherwise choose No.

Advanced Options

Displays a further dialog box in which you can specify a rollback segment to use for the import operation, and choose a tablespace for the temporary tables.


Import Wizard: Import File

Enables you to specify the import file you want to use.

Dialog box options

Specify import file

The name and location of the file that contains the data to be imported.

Browse

Enables you to locate and choose an import file.

View

Displays the contents of the specified import file.


Import Wizard: Select Container

You see this screen if you are importing data that has no record of an owning container. Because the Import utility needs to know which container to use at the target repository, you must specify a container here.

Dialog box options

Select container

The name and location of the container into which the data to be imported.

Browse

Enables you to locate and choose a container.


Import Wizard: Error Log and Redo Log

Enables you to specify the details of the log files produced by the import operation.

Dialog box options

Specify error log file

The name and location of the file that is to contain the error log data from the import operation. You can enter a file name and location, or choose one using the Browse button.

Specify redo log file

The name and location of the file that is to contain the redo log data from the import operation. You can enter a file name and location, or choose one using the Browse button.

Display logs when finished?

If you want to see the contents of the log files when the operation has finished, leave the default option Yes, otherwise choose No.


Import Wizard: File Contents

This screen lists:

•	the release level of the data you are about to import

•	whether the data was exported from a versioned repository

•	the container level (root or subcontainer) from which the data was exported

•	the temporary repository tables from which you are about to import

The temporary repository tables hold the object and container data that was exported to the dump file.


Import Wizard: Workarea and Container

Enables you to specify the workarea, and the container in that workarea, that is to receive the imported data.

Specify workarea

The name of the workarea to which you want to import the data. You can enter a workarea name, or choose one using the Browse button.

Specify container

The name of the container in the specified workarea to which you want to import the data. The default name is that of the container that was originally exported in the source repository. You can enter a container name, or choose one using the Browse button.


Import Wizard: Create or Update Objects

Enables you to specify whether you want the data to be imported as new objects or object versions, or as updates to existing objects.

The options are:

Create brand new objects

Create new versions where objects exist

Update existing object versions

Some of these options may not be available, depending on how the data was exported. For example, if you exported an entire unresolved workarea with multiple object versions, only the option to create brand new objects is available.

Create brand new objects

Creates new objects in the repository for all the data in the import file, regardless of whether the imported objects already exist in the target repository.

Importing a ...	Effect
Workarea (unresolved)	If you are importing a workarea that has unresolved version conflicts, this option creates a new workarea based on the workarea specification, including all the object versions referred to in the specification. All configurations, rules and container memberships are preserved. Non-versioned objects, and checked-out objects (imported with no version history), are imported as new objects. Checked-in objects are imported unchanged and are placed on the MAIN branch with a single version.
Workarea (resolved)	If you are importing a workarea with no version conflicts, this option loads the objects into the target workarea, creating a single version of each object.  Objects that were checked out or not under version control in the source repository are imported as new objects. Objects that were checked in in the source repository are created as checked-in objects on the MAIN branch. You can use an existing workarea as the target, or you can create a new one with a name you specify in the wizard.  Note that, if you create a new workarea in this way, its specification is empty. Because of this, the new workarea does not include the system folder. Thus all objects that originally referred to objects (such as Languages) in the system folder show null references. You can avoid this situation by creating a new workarea using the Workarea Wizard ) before importing.
Container	Loads the container and its contents into an existing workarea. The container can be imported as a subcontainer, even if it was exported from the source repository as a root container. The container name must be unique within its target context (i.e., workarea root container or subcontainer). Checked-out objects are imported as new objects. Checked-in objects are imported unchanged on the MAIN branch. If you choose the Recurse option, the import includes the container and its contents, together with all its subcontainers and all of their contents.
Configuration	Creates a new configuration containing all objects specified for import. Objects are imported checked in, and are placed on the MAIN branch with a single version. The original version label is maintained.
Create new versions where objects exist

With this option, if an object you are importing already exists in the repository, a new version is created for the imported data. If an object you are importing does not already exist in the repository, a new object is created.

Importing a ...	Effect
Workarea	Loads the objects into the target workarea.  Objects that were checked out or not under version control in the source repository are imported as new objects.  Objects in the source repository that were checked in are created as checked-in objects on the MAIN branch.  You can use an existing workarea as the target, or you can create a new one with a name you specify in the wizard.
Container	Loads the container and its contents into an existing workarea. The container can be imported as a subcontainer, even if it was exported from the source repository as a root container. The container name must be unique within its target context (i.e., workarea root container or subcontainer). If you chose the Recurse option for export, the import includes the container and its contents, together with all its subcontainers and all of their contents. Objects that were checked out or not under version control in the source repository are imported as new objects.  Objects in the source repository that were checked in are created as checked-in objects on the MAIN branch.
Configuration	Creates a new configuration containing all objects specified for import. Objects are imported checked in, and are placed on the MAIN branch with a single version. The original version label is maintained.
Update existing object versions

Caution:	This option is for advanced users wishing to synchronize source and target repositories (i.e., it provides a way of replicating repository data on another database). Because it can overwrite data on the target repository, this option should be used with care.

If an object version you are importing already exists in the repository, this option overwrites the existing version even if that version is checked in. However, if a different version of the object already exists (i.e., it has the same IRID object identifier but a different IVID version identifier), a new version is created. If the object you are importing does not already exist in the repository, a new object is created.

Versioned objects are loaded with the same IRID and IVID values that they had in the source repository. If an object with the same IRID and IVID values already exists in the target repository, it is updated with the properties from the imported data.

Importing a ...	Effect
Workarea (unresolved)	Creates a new workarea based on the workarea specification, including all the object versions referred to in the specification. All configurations, rules and container memberships are preserved.
Workarea (resolved)	Loads the objects into the target workarea, creating a single version of each object. You can use an existing workarea as the target, or you can create a new one with a name you specify in the wizard.
Container	The container retains all the properties that it had in the source repository.  All object versions are imported with the same IRID (object identifier) and IVID (version identifier) values that they had in the source repository. If an object with the same IVID value exists in the target repository, all properties of the object are overwritten by those of the imported object. If there is no object with a matching IVID value, the imported object is inserted into the target repository. If you chose the Recurse option for export, the import includes the container and its contents, together with all its subcontainers and all of their contents, retaining all the properties from the source repository.
Configuration	The configuration retains all the properties that it had in the source repository. All object versions are imported with the same IRID (object identifier) and IVID (version identifier) values that they had in the source repository. If an object with the same IVID value exists in the target repository, all properties of the object are overwritten by those of the imported object. If there is no object with a matching IVID value, the imported object is inserted into the target repository.


Import Wizard: Container Data

This screen indicates that you are importing data that was originally exported from a container.

Specify workarea

The name of a target workarea in which to place this data. If you selected a container when starting the wizard, the workarea in which you selected this container is shown by default. You can choose a workarea by means of the Browse button.


Import Wizard: Container Details

This screen indicates that you are importing data that was originally exported from a container, and you have chosen to create brand new objects.

On this screen you need to specify a few details about the target container. You can either create a new container to hold the objects, or you can add them to an existing container.

Create as a root container at target

This option creates a new root container, with the specified name, in the target workarea.

Add to an existing context folder

This option adds the objects to an existing container, which you specify as follows:

Specify Container Context

Enter the name and location of the target container, or choose one by means of the Browse button.

Specify Name at Target

Specify a new name for the target container if desired, otherwise leave the existing name here.


Import Wizard: Container Exists

This display is for information only. It indicates that you are importing a container that already exists in the target repository and that you have chosen to update existing objects or object versions. This means that you will not be able to move or rename the container in the repository during the import process.


Import Wizard: Resolved Workarea

This display indicates that you are importing data originally exported from a workarea that has no version conflicts.

Specify workarea

Enables you to choose the target workarea. You can:

•	specify the same name as the source workarea (default)

•	specify a target workarea with a different name from the source

You can use the Browse button to locate and select an existing target workarea to use.

If the specified workarea exists in the target repository, the imported data will be merged with its contents. If the specified workarea does not exist, a new workarea is created with that name in the target repository and the data is imported.


Import Wizard: Unresolved Workarea

This display indicates that you are importing data originally exported from a workarea that has objects with multiple versions, and which has not been refreshed to resolve version conflicts. You must create a new workarea to use for the imported data.

Specify workarea

Enables you to specify a new workarea as the target workarea.

Click Finish to complete the operation or Cancel to abandon it, or click Back to change the options you have chosen.


Audit Search Specification dialog box

Enables you to specify object audit properties on which to search.

Date Created

The date when the object was created. You can use query-by-example format, e.g. a value of >1-JAN-99 would search for objects created after this date.

Date Last Modified

The date when the object was last modified. You can use query-by-example format, e.g. a value of >1-JAN-99 would search for objects last modified after this date.

Using Date Format

The date format used by objects that you are searching for. You can choose either DD-MON-YY or DD-MON-YY HH:MI:SS.

Created By

The name of the user who created the object.

Modified By

The name of the user who last modified the object.

No. of Times Modified

The number of times that the object has been modified.

Display Audit Properties

If selected, displays the audit properties in the Search Results dialog box for any objects that match the search conditions.


Version Search Specification dialog box

Enables you to specify object version properties on which to search. You can use these properties to search for objects under version control. You can also search for objects that are not under version control.

Status

The version status to search for. You can search on any combination of these.

Checked In

Searches for checked-in objects under version control.

Checked Out

Searches for checked-out objects under version control.

Not Versioned

Searches for objects that are not under version control.

Version Label

The version label for which to search. You can use the % wildcard.

On Branch

The checkin branch on which to search. You can use the % wildcard.

Display Version Properties

If selected, displays the object version properties in the Search Results dialog box for any objects that match the search conditions.


Repository Search (Advanced) dialog box

This dialog box enables you to perform advanced searches by setting complex search conditions.

Dialog box options

For Type

The type of object for which you are searching.

The dialog box has the following tabs:

Filter Conditions

Sort Sequence

Show Properties


SQL dialog box

Displays the SQL statement that is generated by the parameters that you have set in the Repository Search dialog box.

You can edit the SQL statement in the display window before clicking Execute.


Select Display Group Filter dialog box

Enables you to choose the categories of repository objects that you would like the Navigator window to display. About


Object Hierarchies

Related Topics

For some element types, you can create object instances and display them in a hierarchical fashion. For example, you might want to define a business unit, UNIT1, which has two sub-divisions, UNIT1A and UNIT1B.

The element types for which you can create and display object instances hierarchically are:

Business Functions

Business Units

Critical Success Factors

Domains

Entities

Item Groups

Key Performance Indicators

Locations

Objectives

Modules

Problems


View - List
   List (View Menu)

Displays the names of the repository items in a single-column list.


View - Icons
   Icons (View Menu)

Displays the names and icons of the repository items in a multi-column list.


View - General Details
   General Details (View Menu)

Displays various general details about the objects in the list.

You can choose which details to show. The default set is: name, element type, the date when the object was created, who created it, when it was modified, the user who last modified it and the number of times the item was modified.


View - Version Details
   Version Details (View Menu)

Displays version details, if any, about the objects in the list.

You can choose which details to show. The default set is:  name, element type, branch identifier, version number, version label, status, rule or configuration that caused the object to be included in the workarea, and (if it is currently checked out) the date it was checked out and by whom.


View - Pin Details
   Pin Details (View Menu)

Causes the details displayed in the Details dialog box to remain unchanged (pinned) even if you select another repository object from the Navigator. The Details dialog is in the 'pinned' state when the button is displayed as [image].


View - Show/Hide
Show/Hide (View Menu)

Enables you to choose which object properties to show in the Details window.

Dialog box options

Show in Details View:  General

These check boxes control which properties you see when you select General Details using the [image] toolbar button.

Show in Details View:  Version

These check boxes control which properties you see when you select Version Details using the [image] toolbar button.

The group of properties in the left panel are more general properties, while those in the right panel are specifically related to version control, but you can display any selection of properties in either mode.

IRID

The 38-digit unique identifier of the object.

Type

The element type.

Size

The size of the object in bytes.

Timestamp

The time when the object was last changed.

Date Created

The date when the object was created.

Created By

The user who created the object.

Date Modified

The date when the object was last modified.

Modified By

The user who last modified the object.

No. Modifications

The number of times that the object has been modified since its creation.

IVID

The 38-digit version identifier of the object.

Version

The version number (an integer number) for the object version included in this workarea.

Version Label

The version label for the object version included in this workarea.

Status

The object status:  Checked In, Checked Out or Not Versioned.

Rule

The rule in the workarea specification that causes this object to be included in the workarea, for example LATEST (MAIN).

Date Checked Out

If the object is currently checked out, the date when it was checked out.

Checked Out By

If the object is currently checked out, the user who checked it out.


Copy dialog box

Displays details of objects that you are copying.

Copy

The name and path in the repository of the objects that you have selected to copy.

To

The destination container (the one to which you are copying the objects).

Deep copy

Copies the PAC element and all of its children (for example, for a table definition, copies the columns, unique keys, check constraints etc. as well). When cleared, copies only the PAC element. Note that when copying diagrams, clearing this check box has no effect.

Recurse subcontainers

If you are copying a container, copies the contents of any of its subcontainers as well.

Auto checkout

Causes the destination container to be checked out automatically.

Copy dependencies

Copies any dependency information for the object that has been created by the Dependency Manager tool. When cleared, no dependency information is copied.

Don’t show this dialog again

Select this check box if you do not want to see the Copy dialog box every time you copy an object.


Move dialog box

Displays details of objects that you are moving.

Move

The name and path in the repository of the objects that you have selected to move.

To

The container to which you are moving the objects.

Auto checkout

Causes the destination container to be checked out automatically.

Don’t show this dialog again

Select this check box if you do not want to see the Move dialog box every time you move an object.


File service alert

This indicates that you are attempting to do one of the following:

•	Upload a file that already exists in the repository

•	Download a file that already exists in the file system

You must choose how you want to proceed in order to synchronize the repository and file system copies.

If you are ...	Message displayed
Uploading a file	Upload and overwrite any changes ?  About
Downloading a file	Download and overwrite any changes ?  About


File service alert - uploading a file

If you are uploading a file that already exists in the repository, your choices are as follows. Note that checked-in files cannot be overwritten and are skipped.

Yes

Uploads the file, overwriting the one already in the target container. If other files in this upload operation exist in the target container, you will be prompted again for each file.

Yes to All

Uploads this and any other files you have specified, including any others that already exist in the target container. These files will be overwritten, with no further prompting.

No

Skips this file and continues uploading any other files you have specified. If other files in this upload operation exist in the target container, you will be prompted again for each file.

No to All

Skips this and any other files you have specified that already exist in the target container. Uploading continues with other files that do not already exist in the container.


File service alert - downloading a file

If you are downloading a file that already exists in the file system, your choices are:

Yes

Downloads the file, overwriting the one already in the file system. If other files in this download operation exist in the target file system, you will be prompted again for each file.

Yes to All

Downloads this and any other files you have specified, including any others that already exist in the target file system. These files will be overwritten, with no further prompting.

No

Skips this file and continues downloading any other files you have specified. If other files in this download operation exist in the target file system, you will be prompted again for each file.

No to All

Skips this and any other files you have specified that already exist in the target file system. Downloading continues with other files that do not already exist in the file system.


File synchronization alert

This indicates that you are synchronizing a file or its container where the file has been deleted from the repository but not from the file system.

The message "File name has been removed from the workarea" is displayed. You must choose how you want to proceed. Even if you choose not to delete the file from the file system, it is not automatically uploaded to the repository (to achieve this, repeat the synchronization specifying the option to include files new to the repository).

Your choices are:

Yes

Deletes the file from the file system. If the same situation occurs for other files in this operation, you will be prompted again for each file.

Yes to All

Deletes this and any other files for which the same situation occurs in the current operation. These files are deleted with no further prompting, and synchronization continues for any other files you have specified.

No

Does not delete this file, and continues synchronizing any other files you have specified. If the same situation occurs for other files in this operation, you will be prompted again for each file.

No to All

Does not delete this or any other files in the same situation in this operation. Synchronization continues for any other files you have specified.


Transfer Ownership dialog box

Enables you to transfer ownership of the selected item to another user.

Transfer ownership on

Indicates the workarea, container or configuration for which you are transferring ownership.

To user

The repository user who is to be the new owner.


Synchronization Error dialog box

Lists files that have been changed in the file system while the repository copy is still checked in. These are known as "hijacked files".

File list

Shows a list of the hijacked files.

Upload the file(s) and overwrite repository changes

Uploads the hijacked files from the file system, overwriting the repository copies.

Download the file(s) and overwrite file system changes

Downloads the copies from the repository, overwriting the hijacked files in the file system.

Deal with files individually

Displays a further dialog box enabling you to deal with these files on an individual basis.


Resolve Synchronization Errors dialog box

Enables you to synchronize repository and file system copies of files where synchronization was not possible.

In each case, you can choose whether you want to use the file system copy (upload), the repository copy (download), or merge the two copies. Before doing so, you can check the file in or out, view its version history and compare the two copies.

Repository element

The name of a file that could not be synchronized.

Synchronization state

Indicates why synchronization was not possible. This might be because:

•	the repository and file system copies are different and the system cannot automatically resolve the situation (this is the meaning of the "no valid .RVI entry" message)

•	both the repository and the file system copies have changed

•	the file system copy has been changed while the repository copy was still checked in (this is known as a "hijacked file")

Version state

Indicates whether the repository copy is checked in, checked out or is a new (i.e., non-versioned) file.

File system path

Indicates where the file system copy is located.

Overwrite

Upload

Uploads the selected files from the file system, overwriting the repository copy.

Download

Downloads the selected files to the repository, overwriting the file system copy.

Merge

Enables you to merge the two copies of a selected file. If any conflicts are detected, the Merge window is opened, enabling you to resolve the conflicts.

Version

Check in

Checks in selected files if they are currently checked out.

Check out

Checks out selected files if they are currently checked in.

Utilities

Version history

Runs the Version History Viewer for a selected file, enabling you to view the version history of the file as a graphical tree.

Compare

Highlights the differences between the repository and the file system copies of a selected file.

Select all

Selects all the files in the list for a particular operation.


Source Control Options dialog box

Enables you to view or change various repository connection and container options. This dialog box is available from Oracle Developer Form Builder and Oracle Developer Report Builder.

Repository Connection

Displays the username and database alias for the user currently connected to the repository. The Change button allows you to change the connection.

Workarea

Displays the current workarea. The Change button allows you to change the workarea.

Container

Use this field to select the container that you want to:

•	check the Oracle Developer file out from

•	check the Oracle Developer file in to

We recommend that you store Oracle Developer files in repository folders (i.e. not application systems or other container types).

Container file system mapping

Displays the directory on the file system that is mapped to the container specified in the Container field. If the specified container is not mapped to a file system directory, this field is empty.

Container access rights

Displays the access rights on the container specified in the Container field.


Select Type dialog box

Allows you to select the types of repository objects to be copied or deleted.

Dialog box options

The list box displays all the available element types in the repository. Select the types for which you want to copy or delete objects and click OK. The Select Object dialog box is displayed.


Select Object dialog box

Allows you to select the repository objects to be added to the copy/delete list on the Copy Objects/Force Delete dialog box.

Filter control

Allows you to filter the repository object definitions that are displayed in the list box.

List box

Lists the existing repository objects from which you can choose.

Select one or more entries from this list to identify the repository objects that are to be added to the copy/delete list.

Select All

Selects all entries in the list box. This button is available only if there is more than one entry in the list box.

Clear All

Deselects all entries in the list box.


Compare Workarea dialog box

Allows you to choose whether to compare workareas based on the workarea contents or the workarea specification.

Compare workarea contents

Displays the differences in the set of objects and object versions that are visible in the workarea.

Compare workarea specification

Displays the differences in the set of rules and configurations that determine what is visible in the workarea.


Rules for workarea and configuration specifications

Workareas and configurations are defined by specifications. A specification is a set of rules that define which object versions should be included and which excluded.

When you are creating a workarea or a configuration, one option is to create the workarea or configuration from a set of rules stored in a specification file. Each rule must be on a separate line in a specification file.

A repository rule takes one of the following forms, depending on the rule:

rule_name(object=element_type[, parameters])

rule_name(branch_label[, parameters])

where:

rule_name identifies the rule, for example, INCLUDE_FOLDER or EXCLUDE_OBJECT.

object is a version resolved name (that is, a name that includes a specific version label) which identifies a particular version of a repository object.

element_type is the element type of the object.

parameters are the various rule parameters, explained later in this topic.

branch_label identifies a particular checkin branch, where a rule requires this.

List of available rules

Examples

The following some examples of rules as they appear in a workarea specification:

INCLUDE_FOLDER(NF_HOLLYWOOD{1.2.1.1}=Folder)

EXCLUDE_OBJECT(NF_HOLLYWOOD{1.2.1.1}/REGION{1.1}=Domain)

FOLDER_LATEST_CONTENTS(NF_HOLLYWOOD{1.2.1.1}=Folder,fix06)

LATEST_BETWEEN(fix06,24-FEB-2000,19-APR-2000)

The INCLUDE_FOLDER rule includes in the workarea all the objects from version 1.2.1.1 of the folder named NF_HOLLYWOOD.

The EXCLUDE_OBJECT rule specifically excludes from the workarea version 1.1 of the domain named REGION.

FOLDER_LATEST_CONTENTS specifies that the workarea is to include the latest versions of all objects in version 1.2.1.1 of the NF_HOLLYWOOD folder on the checkin branch named fix06.

The LATEST_BETWEEN rule restricts the workarea to includes the latest versions of all objects on the checkin branch named fix06 that were checked in between 24 February 2000 and 19 April 2000.

Identifying objects in repository rules

Objects are identified in rules using version resolved names, which include a version label that identifies a particular version of a repository object. Generally, the type of object can be specified in addition to the version resolved name by including an equal sign (=) and the element type of the object after the name.

If any special characters are used in an object name, they must be preceded by a caret mark (^).

Dates in repository rules

Some repository rules require dates to be included. Dates can be given in any of the following formats:

DD-MON-YYYY

DD-MON-YYYY HH:MI:SS

Examples:

19-APR-2000

19-APR-2000 12:00:00


Repository rules

The available rules for specifying a workarea or configuration are:

Rule	Effect
EXCLUDE_FOLDER	Excludes all specified containers
EXCLUDE_OBJECT	Excludes all specified objects
FOLDER_LATEST_BEFORE	Includes the latest versions of all objects in the specified container that were checked in before the specified date
FOLDER_LATEST_BETWEEN	Includes the latest versions of all objects in the specified container that were checked in between the specified dates
FOLDER_LATEST_CONTENTS	Includes the latest versions of all objects in the specified container on the specified branch
INCLUDE_CONFIG	Includes all the object versions defined by a configuration
INCLUDE_FOLDER	Includes the latest versions of all objects in the specified container
INCLUDE_OBJECT	Includes the latest version of the specified object
LATEST	Includes the latest versions of all objects on the specified branch
LATEST_BEFORE	Includes the latest versions of all objects on the specified branch that were checked in before the specified date
LATEST_BETWEEN	Includes the latest versions of all objects on the specified branch that were checked in between the specified dates
LATEST_CONFIG_CONTENTS	Includes the latest versions of all the objects in the specified configuration
LATEST_DIAGRAM_CONTENTS	Includes the latest versions of all the objects on the specified branch that make up the specified diagram
EXCLUDE_FOLDER repository rule

Excludes all specified container versions.

EXCLUDE_FOLDER(<folder-path>=<container-element-type>)

Examples

The following excludes version 1.2.1.1 of folder reports:

EXCLUDE_FOLDER(reports{1.2.1.1}=Folder)

The following excludes the version of folder fix(reports) that is on branch fix06 and has sequence number 4 on that branch:

EXCLUDE_FOLDER(fix^(reports^){fix06;4}=Folder)

EXCLUDE_OBJECT repository rule

Excludes all the specified object versions.

EXCLUDE_OBJECT(<object-path>=<element-type>)

Examples

The following excludes version 1.1 of the domain LIST OF THINGS in version 1.2.1.1 of folder reports:

EXCLUDE_OBJECT(reports{1.2.1.1}/LIST OF THINGS{1.1}=Domain)

The following excludes the object MASTER TABLE that has the version sequence 6 on the MAIN branch that is in the latest version of the MAIN branch of folder reports:

EXCLUDE_OBJECT(reports{MAIN;LATEST}/MASTER TABLE{MAIN;6}=Table Definition)

FOLDER_LATEST_BEFORE repository rule

The FOLDER_LATEST_BEFORE repository rule includes the latest versions of all objects in the specified container that were checked in before the specified date.

FOLDER_LATEST_BEFORE(<folder-path>=<container-element-type>,<before-date>)

Examples

FOLDER_LATEST_BEFORE(wa-specs{1.0.1.0}=Folder,19-APR-2000)

FOLDER_LATEST_BEFORE(reports{1.2.1.1}=Folder,19-APR-00 08:00:00)

FOLDER_LATEST_BETWEEN repository rule

The FOLDER_LATEST_BETWEEN repository rule includes the latest versions of all objects in the specified container that were checked in between the specified dates.

FOLDER_LATEST_BETWEEN(<folder-path>=<container-element-type>,<start-date>,<end-date>)

Example

The following includes the only or the latest versions of all objects in folder wa-specs{1.0.1.0} between the given dates:

FOLDER_LATEST_BETWEEN(wa-specs{1.0.1.0}=Folder,19-APR-2000,30-APR-2000)

FOLDER_LATEST_CONTENTS repository rule

The FOLDER_LATEST_CONTENTS repository rule includes the latest versions of all objects in the specified container on the specified branch.

FOLDER_LATEST_CONTENTS(<folder-path>=<container-element-type>,<branch-label>)

Example

The following includes the latest versions of objects in folder reports{1.2.1.1} on branch fix06:

FOLDER_LATEST_CONTENTS(reports{1.2.1.1}=Folder,fix06)

INCLUDE_CONFIG

INCLUDE_CONFIG, while not strictly a repository rule, has a similar format to repository rules. It is used to include a configuration, that is, to include all the object versions defined by a configuration.

INCLUDE_CONFIG(<configuration-path>)

Example

The following includes all the object versions defined by the configuration version services_internal{1.0}.

INCLUDE_CONFIG(services_internal{1.0})

INCLUDE_FOLDER repository rule

The INCLUDE_FOLDER  repository rule includes the latest versions of all objects in the specified container.

INCLUDE_FOLDER(<folder-path>=<container-element-type>)

Example

The following includes the latest versions of all objects in the version of folder reports that has sequence number 5 on the MAIN branch:

INCLUDE_FOLDER(reports{MAIN;5}=Folder)

INCLUDE_OBJECT repository rule

The INCLUDE_OBJECT repository rule includes the latest or the specified version of the specified object.

INCLUDE_OBJECT(<object-path>=<element-type>)

Example

The following includes version 1.0 of the Domain element LIST OF THINGS in the folder reports version 1.2.1.1:

INCLUDE_OBJECT(reports{1.2.1.1}/LIST OF THINGS{1.0}=Domain)

LATEST repository rule

The LATEST repository rule includes the latest versions of all objects on the specified branch.

LATEST(<branch-label>)

Example

The following includes the latest versions of objects on branch fix06:

LATEST(fix06)

LATEST_BEFORE repository rule

The LATEST_BEFORE repository rule includes the latest versions of all objects on the specified branch that were checked in before the specified date.

LATEST_BEFORE(<branch-label>,<before-date>)

Example

LATEST_BEFORE(fix06,19-APR-2000)

LATEST_BETWEEN repository rule

The LATEST_BETWEEN repository rule includes the latest versions of all objects on the specified branch that were checked in between the specified dates.

LATEST_BETWEEN(<branch-label>,<start-date>,<end-date>)

Example

LATEST_BETWEEN(FIX06,19-APR-2000,30-APR-2000)

LATEST_CONFIG_CONTENTS repository rule

The LATEST_CONFIG_CONTENTS repository rule includes the latest versions of all the objects defined by the specified configuration.

LATEST_CONFIG_CONTENTS(<configuration-path>=Configuration,<branch-label>)

Example

The following includes the latest version on branch fix06 of all the objects defined by configuration version fix_config{MAIN;LATEST}:

LATEST_CONFIG_CONTENTS(fix_config{MAIN;LATEST}=Configuration,fix06)

LATEST_DIAGRAM_CONTENTS repository rule

The LATEST_DIAGRAM_CONTENTS repository rule includes the latest versions of all the objects on the specified branch that make up the specified diagram.

LATEST_DIAGRAM_CONTENTS(<diagram-path>=Diagram,<branch-label>)

Example

LATEST_DIAGRAM_CONTENTS(ANALYSIS{1.1}/PURCH{mod1;4}=Diagram,mod1)


Using shortcut keys to work with the Merge Window

Shortcuts for menu options

To		Press		As a shortcut for
Merge the selected data into the target and save the result		ALT + F, S CTRL + S		File→Save
Exit from the Merge Window		ALT + F, X ALT + F4		File→Exit
Show or hide the toolbar		ALT + V,T		View→Toolbar
Navigate to the previous difference in the window		ALT + N, P		Navigate→Previous Difference
Navigate to the next difference in the window		ALT + N, N		Navigate→Next Difference
Navigate to the previous conflict in the window		ALT + N, C		Navigate→Previous Conflict
Navigate to the next conflict in the window		ALT + N, T		Navigate→Next Conflict
Select the source from the difference block currently in focus.		ALT + M, L		Merge→Select Source
Select the target from the difference block currently in focus.		ALT + M, G		Merge→Select Target
Select the common ancestor from the difference block currently in focus.		Alt + M, O		Merge→Select Common Ancestor
Displays the online help documentation		ALT + H, H CTRL + H		Help→Help Topics
Display copyright and version number information about the utility		ALT + H, A		Help→About


Merge Wizard - Target

Related Topics

Enables you to choose the target workarea for the merge, and determine the scope of the merge operation within that workarea.

Target Workarea

The target workarea containing the target objects for the merge operation. A target is any object version that differs from the object version in the source.

Use the Browse button to locate and select another workarea.

Consider all objects in target workarea for merge

Indicates whether or not you want to consider all the objects in the selected workarea as potential targets for a merge operation.

If this option is not selected, you can specify which objects are targets for a merge using the Select objects page of the wizard. The Select objects page is displayed after you have chosen the source objects for the merge in the Source page.


Merge Wizard - Source

Related Topics

Enables you to specify the source for the object versions in the merge operation. Only checked-in object versions can be used as source versions.

Source of Merge

Object versions on a specific branch

Indicates whether you want to use object versions on a specified branch as the source for the merge operation. Enter the name of the branch in the Branch Name field.

Object versions from a specific workarea

Indicates whether you want to use object versions from a specified workarea as the source for the merge operation. Enter the name of the workarea in the Workarea Name field.

Object versions in a specific configuration

Indicates whether you want to use object versions from a specified configuration as the source for the merge operation. Enter the name of the configuration in the Configuration Name field.

Object versions with a particular version label

Indicates whether you want to use only object versions which match a specified version label as the source for the merge operation. Enter the name of the version label in the Version Label Name field.

<Source> Name

Depending on the source option chosen, specifies a branch, a workarea, a configuration or a version label to act as the source context.

For branches, workareas and configurations, use the Browse button to locate and select the source.


Merge Wizard - Select objects

Related Topics

Enables you to specify which objects in the chosen workarea are targets for a merge operation.

Target workarea

The name of the chosen target workarea.

Left list

A list of all the objects in the target workarea.

Right list

Can be populated using the arrow buttons to contain a list of objects that will be considered as target merge candidates. Objects must be located in this list to be included in the merge operation.

Right arrow

Copies the selected object in the left list to the right list, so adding it to the list of merge targets.

Double right arrow

Copies all objects in the left list pane to the right list pane, so adding them to the list of merge targets.

Left arrow

Removes the selected object from the right list, so removing it from the list of merge targets.

Double left arrow

Removes all items from the right list, so removing them from the list of merge targets.


Merge Wizard - Options

Related Topics

Enables you to specify options relating to the merge operation.

General Merge Options

Automatically check out objects?

All the target objects involved in the merge operation will be checked out automatically before the merge operation. Selected by default.

Automatic merge objects if possible?

The Merge window is displayed only if there are conflicts between object versions, so enabling you to resolve the differences; otherwise the Merge window is not displayed.

Check in objects after merging?

Automatically checks in targets after merges, so creating a new version on the same branch as the target.

View list of objects before merging?

Displays the Merge list, enabling you to view a list of all the objects being merged and to instigate the merge operation. Selected by default.

Merge Options for Containers

Merge containers?

Container objects, as well as non-container objects, will be considered as merge candidates. Container objects, such as folders and application systems, are used for organizing other non-container objects, such as tables and files.

Include subcontainers when merging containers?

Subcontainer objects, as well as non-container objects, should be considered as merge candidates. Subcontainer objects are containers nested within other containers.


Merge Wizard - Merge list

Related Topics

Displays a list of all the objects being merged, and enables you to instigate the compare and merge of objects, as well as explicitly checking in and checking out objects.

Workarea

The name of the target workarea.

Default Checkin Branch

The branch to which any selected targets will be checked in. Objects may be checked in automatically if the Check in objects after merging option is selected on the Options page of the wizard. If this option is not selected, objects can be checked in explicitly using the Check In button on this Merge list window.

If no default checkin branch is set, the objects are checked in to the MAIN branch.

List of merge candidates

Name

The name of the object.

Source Version

The source version of the object.

Target Version

The target version of the object.

Merged

Indicates whether the object has been successfully merged in this merge operation.

Status

Indicates whether the object is currently checked in, checked out or not in the workarea. The not in workarea status indicates that this object is a new object that has been added to the source workarea and is not yet in the target workarea. Merging any new objects will add the objects to the target workarea.

Type

The repository object type of the object.

Buttons

Close

Closes the Merge Wizard.

New Query

Restarts the Merge Wizard with all options reset to their defaults.

Merge

Merges the selected candidate object versions. If the Automatic merge objects if possible option on the Options tab is not selected, the Merge window is displayed, once for each selected object in turn.

Compare

Displays a Compare window for each selected object.

Check In

Checks in selected objects in the candidate list that are currently checked out. Note that no new version is created for the result of a merge until the updated target is checked in.

Check Out

Checks out selected objects in the candidate list that are currently checked in.

Select All

Selects all objects in the Merge list, in preparation for a merge, compare, checkin or checkout operation.


Creating repository objects

Related Topics

You can create repository objects from the Repository Object Navigator, or from other tools (for example, the diagramming tools supplied with Oracle Designer).

Note:	In Oracle Designer, you cannot create a diagram from the Repository Object Navigator. You must use an appropriate diagramming tool; installed Oracle Designer diagramming tools are available from the Tools menu.

You must have a workarea available before you can create repository objects. You can either use an existing workarea for which you have the update access right, or you can create a workarea yourself (for which you need the Workareas repository privilege). How

If the workarea you want to use has no containers, you must do one of the following:

•	include an existing container How

•	create a new container How

If you include an existing container, you need the update access right on that container. If you create a container yourself, you need the Containers repository privilege.

About workareas

About containers

About repository objects

About security and access rights

To create a repository object from the Repository Object Navigator:

1.	In the Navigator window of the Repository Object Navigator, do one of the following:

a.	In a workarea, select the name of the container in which you want to create the object.

b.	If the container is not under version control, continue from c.

If the container is under version control (i.e. it has a value for Version Label in the Property Palette) and is not checked out (i.e. it does not display a [image] icon next to the container name), choose Version→Check Out to check out the container.

c.	Click [image].

d.	Select the element type for the object you want to create and click OK.

2.	Type the object name.

3.	(Optional)  Edit the object properties on the Property Palette. How

Some property names or values might be displayed in different colors. About

Note:	Some element types have mandatory properties (shown in red by default). You must either give these properties a value, or abandon creation of the object.

4.	To abandon creation of an object that has not yet been saved, click [image] in the Navigator window.

To abandon definition of a property value that has not yet been saved, click [image] in the Property Palette.

5.	To save the object definition in the repository, either click the [image] toolbar button or select a different node in the Navigator window.


Colors of property names

Property names, and some values, are displayed in different colors in the Property Palette. By default, these are:

Black	Normal
Red	Mandatory parameter, value must be supplied
Blue	Parameter whose value has been edited but not saved
Green	Display-only parameter, cannot be edited; may also indicate that the object is checked in, so value cannot be edited until object is checked out


Creating element hierarchies

You can create some types of repository objects in a parent-child hierarchy if desired. About

For example, you might want to define a business unit, UNIT1, which has two sub-divisions, UNIT1A and UNIT1B.

You can create new objects in a hierarchy, or apply a hierarchy to existing objects.

To create a hierarchy for new objects:

1.	In the Repository Object Navigator, create the parent object. How

2.	Create the objects that are to be the child objects in the hierarchy.

For each child object, set the value of the Parent property to the name of the object you created in step 1 (for domains, use the "Subset of" property, and for entities, use the "Type of" property). To do so:

. 	Click the property value field.

. 	Click the adjacent  icon.

. 	Choose a name from the list and click OK.

. 	Click [image].

3.	If element hierarchy view is not already active for the object you created in step 1 (the [image] icon adjacent to a node indicates that hierarchy view is active for that node):

. 	Select the object.

. 	Choose View→Element Hierarchy View.

4.	Click the  icon next to the parent object to see the hierarchy.

To create a hierarchy for existing objects:

1. 	In the Navigator window of the Repository Object Navigator, select the objects that are to be the child objects in the hierarchy.

2.	Set the Parent property to the name of the parent object (for domains, use the "Subset of" property, and for entities, use the "Type of" property). To do so:

. 	Click the property value field.

. 	Click the adjacent  icon.

. 	Choose a name from the list and click OK.

1. 	In the Navigator tool palette, click [image].

4.	If element hierarchy view is not already active for the object you created in step 1 (the [image] icon adjacent to a node indicates that hierarchy view is active for that node):

. 	Select the object.

. 	Choose View→Element Hierarchy View.

5.	Click the  icon next to the parent object to see the hierarchy.


Creating references

Related Topics

You can create a reference to denote a link between two repository objects. For example, you might want to record the fact that a particular object uses another object.

A reference is an instance of an association type. Association types that have been defined for the element type of a particular object appear in the Navigator window of the Repository Object Navigator.

You can create a reference by using the menus or a toolbar button, or by copying and pasting.

To create a reference using the menus or toolbar:

1.	In the Navigator window of the Repository Object Navigator, locate and select the object from which you want to create the reference. How

2.	If the object is under version control and checked in, choose Version→Check Out and check out the object.

3.	Select the node for the type of reference you want to create. (The node may be displayed immediately under the object name, or under other nodes for that object, such as Usages or Inclusions.)

4.	Click the [image] button.

5.	In the Create Reference dialog box:

a.	Select the objects to be referenced. If selecting more than one object:

•	To select adjacent objects, click the first element, hold down the SHIFT key and click the last object.

•	To select non-adjacent objects, hold down the CTRL key and click the objects you want.

•	To select all objects in the list, click the Select All button.

b.	Click OK.

6.	(Optional) In the Property Palette, edit the reference properties.

7.	Click the [image] toolbar button, or select a different node in the Navigator window.

To create a reference by copying and pasting:

1. 	In the Navigator window of the Repository Object Navigator, select the object to be referenced.

For example, if you are creating a module component table usage, select the table definition of the table that is to be used.

1. 	Choose Edit→Copy to copy the object definition to the Clipboard.

1. 	In the Navigator window, select the object from which the reference is to be made.

For example, if you are creating a module component table usage, select the module component that is to use the table definition.

1. 	Choose Edit→Paste Reference to create the reference.

Note:	Be careful not to choose Edit→Paste or press CTRL+V, as doing so at this point would create a copy of the object you selected in step 1.


Filtering an object list

On some dialog boxes that display lists of repository objects, a filter field at the top of the dialog box enables you enter a filter condition for the list. In this way you can list only those objects whose names match the filter condition.

To filter an object list:

1.	In the filter field at the top of the dialog box, type the filter condition. For example:

abc	Finds an object name starting with abc

abc%	Finds an object name starting with abc

%abc%	Finds an object name containing abc

%abc	Finds an object name ending with abc

2.	Click the [image] button.


Copying, cutting and pasting data

You can copy, cut and paste data from the Navigator window or the Property Palette. The data can be text (for example, a property value from the Property Palette) or object data. You can perform these operations on object data by selecting a primary access controlled (PAC) or secondary access controlled (SAC) element in the Navigator window.

You can use CTRL+C to copy, or CTRL+X to cut, selected data from the Navigator window or the Property Palette to the Clipboard.

You can then use CTRL-V to paste the data wherever you want in the Navigator window or the Property Palette. Note that if you paste copied object data onto another object, it creates a reference between the two objects.

If you want to copy complete object instances, use Utilities→Extended Copy.


Creating shortcuts

While working in a particular container (the context container), you might want to view or edit details of an object owned by another container in your workarea (the owning container). You can do this by creating a shortcut. Objects referenced in this way are denoted by a  icon in the context container.

To create a shortcut (drag-and-drop method)

1. 	In the Navigator window, select the object in the owning container.

1. 	Using the mouse, drag the object to the context container.

1. 	Release the mouse button when the tip of the cursor arrow is over the name of the context container.

To create a shortcut (dialog box method):

1. 	In the Navigator window, select the context container.

1. 	If the context container is under version control, choose Version→Check Out to check it out.

3.	Click [image] in the Navigator tool palette.

1. 	In the Create Reference dialog box, locate the owning container and double-click its name.

5.	Double-click the object to be referenced.


Renaming items in the repository

Related Topics

You can rename:

•	workareas How

•	containers or other objects How

To rename a workarea, you must have the Administrate access right to the workarea.

To rename a container or one of its objects, you must have the Administrate access right to the container.


Renaming workareas

Related Topics

If you change the name of a workarea, no other details of the workarea are affected. About

You must have the Administrate access right to a workarea to rename it. If you are the owner of the workarea, you automatically have this access right.

To rename a workarea:

1.	In the Navigator window of the Repository Object Navigator, select the workarea name.

2.	Choose Edit→Edit Workarea.

3.	In the Name field, edit the workarea name.

1. 	Click Finish.

1. 	To see the effect of the change, keep the workarea name selected and click [image].


Renaming containers and repository objects

Related Topics

You can change the name of a container or of a repository object within it. To do so, you must have the Administrate access right to the container. If you are the owner of the container, you automatically have this access right.

Note that, if you are using version control and more than one version of the container or object exists, all versions will be renamed.

About containers

About repository objects

To rename a container or repository object:

1.	In the Navigator window of the Repository Object Navigator, select the container or repository object.

2.	If the container or object is under version control, choose Version→Check Out to check it out.

3.	Edit the name, either in the Navigator window by clicking the name and typing the new name, or in the Property Palette by typing the new name as the value of the Name property.

4.	Click [image] (or just select another node).


Undoing the last action

Related Topics

In some cases, you can undo the most recent operation that you have performed.

To undo some operations, you can use either the  (Revert) button on the Navigator or Property Palette toolbar, or choose Edit→Undo from the menu (or press CTRL+Z). To undo other operations, you need to perform a specific action as described in the following table.

Operation	How to undo	Effect of Revert button	Effect of Edit→Undo or CTRL+Z
Creating an object or reference	Use Revert button	Creation of the object or reference is abandoned, provided that the definition has not been committed to the repository.	None.
Changing a property	Use Revert or Edit→Undo	The property is set to its previous value, provided that the definition has not been committed to the repository.	The property is set to its previous value, provided that the definition has not been committed to the repository. Choose Edit→Undo again to restore the change.
Checking out an object	Choose Version→Undo Checkout or use alternative method How	None.	None.
Deleting an object	Restore deleted object from the wastebasket. How	None.	None.
Deleting a reference	Cannot be undone.	None.	None.
Saving an object or reference	Cannot be undone.	None.	None.


Exporting repository objects

Related Topics

You can use the Export Wizard to export data to a file from a selected workarea or container in the repository. Using the wizard, you can choose to export the data in either Oracle database (.DMP) format or Repository Loader (.DAT) format.

Note that, if you clear a wastebasket before performing an export, a subsequent import operation will not be able to replicate the wastebasket information at the target repository. You may want to retain this information in the target repository, so you should decide on a wastebasket clearance procedure before exporting.

To export objects from the repository:

1.	In the Repository Object Navigator, in the Navigator window, select a workarea or container from which to export the objects.

2.	Choose Utilities→Export.

1. 	Follow the on-screen instructions in the Export Wizard. Online help is available for each screen of the wizard.

If you see a message indicating that temporary tables are already populated, click Yes to continue.


Importing repository objects

Related Topics

You can import data from a file into a selected container in the repository. The file can be in either Oracle database (.DMP) format or Repository Loader (.DAT) format.

To import objects into the repository:

1.	In the Repository Object Navigator, in the Navigator window, select the container into which you want to import the objects.

2.	Choose Utilities→Import.

1. 	Follow the on-screen instructions in the Import Wizard. Online help is available for each screen of the wizard.

If you see a message indicating that temporary tables are already populated, click Yes to continue.


Using the Designer utilities

The Repository Object Navigator provides access to a number of utilities that are specifically for use with Oracle Designer. These utilities allow you to do the following:

Transform the entity model

Generate a default application system design

Derive entities from tables

Create default function attribute usages

Create default module data usages

Map unbound items

Copy elements with new languages

Update attributes in a domain

Update columns in a domain


Creating default module data usages

This utility creates default module data usages for a selected module. About

To create default module data usages:

1.	In the Repository Object Navigator, in the Navigator window, expand the Modules node.  How

2.	Select the module for which you want to create default data usages.

3.	Choose Utilities→Designer→Create Default Module Data Usages.

4.	When you see the message "Generate data usages has completed successfully", click Close on the dialog box.


Creating default function attribute usages

You can perform a single operation to create default associations for all attributes of all entities used by a particular business function. The associations created are function attribute usages.

To create function attribute usages:

1.	In the Repository Object Navigator, in the Navigator window, expand the Business Functions node.  How

The Business Functions node appears under Enterprise Modeling if the Navigator window is displaying group tabs.

2.	Select the name of the business function for which you want to create the attribute usages.

3.	Check whether the function has entity usages defined, as follows:

a.	Expand the business function.

b.	Expand its Usages node. If a [image] sign appears next to the Using Entities node, the function has entity usages defined.

c.	(Optional) Create further entity usages for the function if desired.  How

4.	Reselect the name of the business function.

5.	Choose Utilities→Designer→Create Function Attribute Matrix.

6.	To view the new function attribute usages:

a.	Requery the business function.  How

b.	Expand the Attributes node (under Using Entities) for an entity used by the business function. You will see usages defined for all the attributes belonging to the relevant entity.

c.	Click an attribute name. In the Property Palette, the Comment property (under Documentation) has the value "Created by system on current_date".


Customizing the Repository Object Navigator

Navigator window

Changing the display order within an element type

Showing or hiding type headings

Showing or hiding the group tabs

Adding your own group tabs

Showing or hiding specific objects

Showing or hiding specific object groups

Creating user-defined object groups

Deleting user-defined object groups

Adding your own views of element types

Displaying properties in the Navigator window

Splitting the Navigator window

Property Palette

Customizing the Property Palette

Specifying text editors for text properties

Setting the date format

General

Showing or hiding the toolbar

Showing or hiding the status bar

Changing text colors and fonts

Showing or hiding the Welcome screen

Setting the options file


Showing or hiding specific object groups

Related Topics

You can display or hide entire groups of repository objects in the Navigator window. About

For example, if you want to see only the objects associated with database design, you can exclude all the other groups from the Navigator window.

You can choose which groups to display in the following ways:

•	from the Welcome screen of the Repository Object Navigator (displayed when you first start the tool)

•	from the Repository Object Navigator menus

To show or hide object groups from the Welcome screen:

1.	On the Welcome screen, choose Select Navigator Groups and click OK.

2.	Select the boxes corresponding to the groups whose members you want to see in the Navigator window. Clear the boxes for the groups whose members are not to be displayed.

To show or hide object groups from the menus:

1.	In the Repository Object Navigator, choose Options→Customize Navigator Groups.

2.	Ensure that the Customize Navigator Groups - Show/Hide tab is selected.

3.	In the Show column, select the boxes corresponding to the groups whose members you want to see in the Navigator window. Clear the boxes for the groups whose members are not to be displayed.


Working with windows

Splitting the Navigator window

Opening a new Property Palette

Organizing windows

Displaying an open window


Splitting the Navigator window

Related Topics

In the Repository Object Navigator, you can split the Navigator window either horizontally or vertically to maintain two independently scrollable views of the window. You do this by moving the split bars (the small rectangular boxes located above the vertical scroll bar and to the left of the horizontal scroll bar):

split bars

To use the Navigator window split bars:

1.	In the Navigator window of the Repository Object Navigator, position the mouse over either split bar.

2.	Drag the split bar while holding down the mouse button.

3.	Release the mouse button when the window is split at the correct position.

To restore a split window to its original state, drag the split bar to its original position.


Displaying an open window

Related Topics

You can display a Navigator window or a Property Palette that is open but not currently visible on the screen, for example, if it is obscured by other windows. When you select such a window for display, it becomes the active window.

To display an open window:

•	Choose Window→<window_name>.


Running reports

You can run a large number of predefined reports about the contents of the repository. You do this through the Repository Reports tool.

To run a repository report:

1.	Choose Tools→Repository Reports.

2.	Choose the report you want to run.

3.	Enter the report parameters. You can choose a destination type of Preview, Printer, File or Screen (Mail is not enabled).

4.	Click the [image] button to run the report.


Printing the contents of the active window

You can print out the contents of the currently-selected Navigator window or Property Palette for reference purposes.

Changing the print setup

Printing the Navigator window or Property Palette


Printing the Navigator window or Property Palette

You can print the current contents of either the Navigator window or the Property Palette.

To preview the print job as it will appear when printed:

1.	In the Repository Object Navigator, select the Navigator window or the Property Palette as desired.

2.	Choose File→Print Preview.

•	To navigate through the pages, choose either the Next Page button or the Prev Page button as appropriate.

•	To specify whether one or two pages are previewed at once, choose the One Page/Two Page button.

•	To increase or decrease the view of the printed pages, choose the Zoom In or Zoom Out button, as appropriate.

•	To print, choose the Print button.

•	To close the Print Preview window and return to the main tool window, choose the Close button.

To specify the range of pages to be printed:

1.	Select the Navigator window or the Property Palette as desired.

2.	Choose File→Print.

3.	Do one of the following:

•	To print all pages, click the All option button.

•	To print out a range of pages, enter the page numbers in the From and To fields associated with the Pages option button.

To specify the print quality used for printing:

1.	Select the Navigator window or the Property Palette as desired.

2.	Choose File→Print.

3.	Choose the required print quality from the Print Quality drop-down list.

To specify the number of copies that you want to print:

1.	Select the Navigator window or the Property Palette as desired.

2.	Choose File→Print.

3.	Specify the number of copies you want to print in the Copies field.

To print a print job to a file:

1.	Select the Navigator window or the Property Palette as desired.

2.	Choose File→Print.

3.	Check the Print to File check box.

4.	Enter the name and location of the file to which you want to print the print job.

Tip:	The full path, including drive and directory name, can be entered in the File Name field, or the drive and directory can be chosen from the Drives drop-down list and the Directories list.


Showing or hiding specific objects (Repository Object Navigator)
Showing or hiding specific objects

You can choose to display in the Navigator window only those repository items with properties that correspond to one or more specified conditions. This is useful, for example, where a repository has a large number of objects of a particular type but you do not want to display all of them in the Navigator window.

The choice of what to display is achieved by specifying filter conditions. You can perform simple filters, for example by object name. Alternatively you can perform complex filters based, for example, on conditions involving logical operators (AND, OR). In all cases, only objects that match the filter conditions are retained in the display.

You can apply a filter to workareas, containers, configurations, element type headings or individual repository objects (either their PAC elements, e.g. tables, or their SAC elements, e.g. columns). You can also apply a filter to lower-level nodes in an object definition, for example references under the Usages node.

To create a filter:

1.	In the Navigator window, select a node on which you want to perform a filter.

2.	Choose Navigator→Filter.

3.	In the Navigator Filter Query dialog box:

a.	Specify the filter conditions. How

b.	Click the Apply button.

c.	(Optional) To save this filter as the default display for objects of this type, click Save as Default. Doing so preserves the filter the next time you start the tool (normally, filters are cleared when you exit from the tool).

d.	(Optional) To save this filter as a user-defined view, click Save as View, type a name for the view and click OK. You can subsequently add this user-defined view to a Navigator window tab.  How

e.	(Optional) From here, you can:

•	Click the Sort Sequence tab if you want to change the display order within an element type.  About

•	Click the Show Properties tab if you want to display object properties in the Navigator window.  About

To clear all filters in the repository:

•	Choose Navigator→Clear All Filters

To clear filters for one or more nodes in a single operation:

1.	In the Navigator window, select one or more nodes for which you want to clear the filter.

2.	Choose Navigator→Clear Selected Filters.

To clear the filter for an individual node:

1.	In the Navigator window, select a node for which filter conditions were specified.

2.	Choose Navigator→Filter.

3.	In the Navigator Filter Query dialog box:

a.	Click anywhere on the line containing the condition you want to clear.

b.	Click [image] in the toolbar.

c.	Click the Apply button.


Changing the display order within an element type

You can change the order in which objects of a particular element type are listed in the Navigator window. You can sort these objects by name, or by any other property, for example, creation date. You can base the sort on as many properties as you like.

To change the display order for an element type:

1.	In the Navigator window of the Repository Object Navigator, select the desired element type.

2.	Choose Navigator→Sort.

3.	In the Navigator Filter Query dialog box:

a.	In the Order By column, select the property or properties by which you want to sort the objects of the selected type. If you choose more than one property, the objects are sorted by the highest property on the list, then by the next highest, and so on.

b.	(Optional) To move a property up or down the list, click the property name so that the line is highlighted, then click the [image] or [image] button as many times as required.

c.	(Optional) To use descending order for the sort, select the appropriate check box or boxes in the Descending column. Ascending order is used by default.

d.	Click the Apply button.

e.	(Optional) To save this display order as the default for objects of this type, click Save as Default. Doing so preserves the display order the next time you start the Repository Object Navigator (otherwise, changes to the display order are reset when you exit from the Repository Object Navigator).

f.	(Optional) To save this display order as a user-defined view, click Save as View, type a name for the view and click OK. You can then add this user-defined view to a Navigator window tab.
How

g.	(Optional) From here, you can:

•	Click the Filter Conditions tab to show or hide specific objects.  About

•	Click the Show Properties tab if you want to display object properties in the Navigator window.  About


Displaying properties in the Navigator window

By default, the Navigator window lists repository objects by name. You can display other properties as well as (or instead of) the name, for example the short name.

You choose properties for display according to the element type. Your choices apply to all objects of the selected type. You can select an element type for a primary access element (for example, tables) or a secondary access element (for example, columns).

Note:	This procedure applies only to the display of properties in the Navigator window. The procedure has no effect on the contents of the Property Palette.

To choose properties for display in the Navigator window:

1.	In the Navigator window of the Repository Object Navigator, select the element type for which you want to choose the properties to display.

2.	Choose Navigator→Display Properties.

3.	In the Navigator Filter Query dialog box:

a.	In the Show column, select the check boxes corresponding to properties that you want to appear in the Navigator window.

b.	Clear the check boxes for properties that are not to appear in the Navigator window.

c.	Click the Apply button. The effects are visible immediately in the Navigator window.

d.	(Optional) To save this property display as the default for objects of this type, click Save as Default. Doing so preserves the property display the next time you start the Repository Object Navigator (otherwise, changes to property displays are reset when you exit from the Repository Object Navigator).

e.	(Optional) To save this property display as a user-defined view, click Save as View, type a name for the view and click OK. You can then add this user-defined view to a Navigator window tab.
How

f.	(Optional) From here, you can:

•	Click the Filter Conditions tab to show or hide specific objects  About

•	Click the Sort Sequence tab if you want to change the display order within an element type  About


Adding your own group tabs

Related Topics

The Repository Object Navigator can display repository objects in groups, controlled by tabs at the top of the Navigator window. The default set of these groups corresponds to different stages in the process of database or application design using Oracle Designer, for example, entity/relationship modeling or module design. About

You can define your own groups of element types (or user-defined views of element types). You can then display the user-defined group in the Navigator window by means of a user-defined group tab, which you can add to the default set of tabs supplied.

To add a new group tab:

1.	If you want the tab to reflect a user-defined view of repository objects (for example, to show only candidate modules), define the view. How

2.	Create the group of element types or views that the tab will display. How

3.	In the Repository Object Navigator, choose Options→Customize Navigator Groups.

4.	On the Show/Hide tab, select the check box corresponding to the group you created in step 2 and click OK.

5.	To see the new tab in the Navigator window, choose View→Show Group Tabs. (If the existing set of group tabs is currently displayed, you will need to choose View→Hide Group Tabs first.)


Creating user-defined object groups

Related Topics

You can create your own group of objects if you want to display only objects of selected element types, or only objects selected by a user-defined view. You can then create a Navigator window tab that will implement this restricted display.

To create a user-defined group:

1.	In the Repository Object Navigator, choose Options→Customize Navigator Groups.

2.	Click the Customize Navigator Groups - Customize tab.

3.	Click the Add Group button.

4.	In the Create New Navigator Group dialog box:

a.	In the Name field, type the name of the new group.

b.	(Optional) If you want to copy an existing group and modify it, choose the existing group from the Copy Group drop-down list.

c.	Click OK.

5.	With the name of the new group selected in the left-hand panel, select the element types or user-defined views (from the right-hand panel) that you want to include in the group. Use the SHIFT key when selecting adjacent items, or the CTRL key when selecting non-adjacent items.

6.	Click the Add button to move the element types or views to the left-hand panel, under the new group name.

You can use the Move Up and Move Down buttons to position a selected element type or view under the new group name in the left-hand panel.

7. 	When you have finished defining the group, click OK on the Customize Navigator Groups dialog box.


Deleting user-defined object groups

Related Topics

If you delete a user-defined object group, only the group definition is deleted, not the repository objects included in the group. The Navigator window tab that implements the group is no longer visible.

To delete a user-defined object group:

1.	In the Repository Object Navigator, choose Options→Customize Navigator Groups.

2.	In the Customize Navigator Groups - Customize tab, select the name of the group you want to delete.

3.	Click the Delete Group button.

4.	Click OK.

5.	To see the effect in the Navigator window, choose View→Show Group Tabs. (If the existing set of group tabs is currently displayed, you will need to choose View→Hide Group Tabs first.)


Adding your own views of element types

For any repository element type, you can define your own view of objects of that type by specifying filter conditions. For example, you might create a view of modules that includes only candidate modules.

When you have created a view, you can implement it by including it in a user-defined group that corresponds to a Navigator window tab.

If you delete a user-defined view, only the view definition is deleted, not the repository objects selected by the view.

To create a user-defined view:

1.	In the Repository Object Navigator, choose Options→Customize Navigator Views.

2.	In the Options - Customize Navigator Views dialog box, click the Add View button.

3.	In the Create New Navigator View dialog box:

a.	Type the name of the new view in the Name field.

b.	From the Based On drop-down list, choose the element type to which the view is to apply.

c.	Click OK.

4.	Specify the filter conditions.  How

5.	Click OK on the Options - Customize Navigator Views dialog box.

To implement a user-defined view:

1. 	In the Repository Object Navigator, choose Options→Customize Navigator Groups.

1. 	Select the Customize tab.

1. 	In the left pane, select the name of the user-defined group to which you want to add the user-defined view.

1. 	In the right pane, select the name of the user-defined view.

1. 	Click Add.

1. 	Select the Show/Hide tab and ensure that the checkbox corresponding to the user-defined group is checked.

1. 	Click OK.

To delete a user-defined view:

1.	In the Repository Object Navigator, choose Options→Customize Navigator Views.

2.	In the Options - Customize Navigator Views dialog box, select the name of the view you want to delete.

3.	Click the Delete View button.


Customizing the Property Palette

You can choose to display or hide certain types of properties in the Property Palette.

To customize the Property Palette:

1.	In the Repository Object Navigator, choose Options→Customize Property Palette.

2.	In the Customize Property Palette dialog box, select or clear the check boxes corresponding to the options you want to customize.

1. 	Click OK.

1. 	To see the effects of your changes on a particular object, click its owning container in the Navigator window, then click the object name.


Showing or hiding the Welcome screen

When you start the Repository Object Navigator for the first time, it displays a screen that offers you a choice of some frequently performed tasks, such as opening a Navigator window or searching the repository. You can choose not to display this screen on subsequent invocations of the Repository Object Navigator.

To hide the Welcome screen, do one of the following:

•	From the Welcome screen itself, clear the check box at the bottom of the screen

•	Choose Options→General Settings and clear the "Show Welcome Screen" check box.

To redisplay the Welcome screen:

1.	Choose Options→General Settings.

2.	Select the "Show Welcome Screen" check box.


Showing or hiding the group tabs

The Navigator window can display a number of tabs at the top, corresponding to groupings of repository element types. About

Selecting a particular tab displays only the objects of the types belonging to that particular group. Hiding the tabs displays objects of all types.

To show the group tabs:

•	In the Repository Object Navigator, choose View→Show Group Tabs.

To hide the group tabs:

•	In the Repository Object Navigator, choose View→Hide Group Tabs.


Choosing element hierarchy view or element list view

Related Topics

When you start the Repository Object Navigator, the Navigator window initially displays its contents in element list view. In this view, all objects in the same container are displayed at the same level.

If you choose element hierarchy view for a selected object and a parent-child hierarchy exists for that object, the hierarchy for that object is displayed graphically.

If you choose element hierarchy view for a selected element type heading, all objects of that type for which a parent-child hierarchy exists have the hierarchy displayed graphically.

Note that not every element type permits objects to be created and displayed hierarchically. About

To choose element hierarchy view:

1.	In the Navigator window of the Repository Object Navigator, select an element type where a parent-child hierarchy exists, or select an individual parent object.

2.	Choose View→Element Hierarchy View.

The [image] symbol indicates that hierarchy view is active below the selected node.

3. 	Click [image] to display the hierarchy at the next level below the selected node.

4. 	Repeat step 3 to see lower levels of the hierarchy.

To choose element list view, choose View→Element List View.


Confirming deletion

Clicking Delete at this point will delete all the items shown in the list.

If you decide not to delete one or more of the items listed, select them and click Remove From List, then click OK to delete the remaining items.

To select adjacent items, hold down the SHIFT key while clicking the items. To select non-adjacent items, hold down the CTRL key while clicking.


Saving a filtered Navigator window as a user-defined view

From the Save as View dialog box, you can save the filtered state of the Navigator window as a user-defined view. Doing so allows you subsequently to access this view of the Navigator window quickly, without respecifying the filter each time.

To save the filter as a user-defined view:

1.	In the Save as View dialog box in the Repository Object Navigator, type a name for the view in the View Name field. This name will appear in the Navigator window.

2.	Click OK.

3.	Click Close in the Navigator Filter Query dialog box.

4.	Add the view to a Navigator window tab. How


Changing the database connection

To change the database connection:

1.	Choose File→Change Connection.

2.	In the Connect dialog box:

a.	Specify a username and password.

b.	Specify a connect string for the Oracle database to which you want to connect (or leave the Connect String field blank if a default connect string has been defined).

c.	Click OK.


Loading and unloading from the command line

Related Topics

From the command line, you can transfer data between repositories using the batch version of the Repository Loader utility. Both repositories must be at the same release level; you cannot use this utility to upgrade repository data from an earlier release.

You supply options to specify what action you want the utility to carry out. The program reads or writes repository data using a text file in a proprietary format. About

Note:	You cannot use this utility to upload or download files between the repository and a file system. If you want to do so from the command line, use the UL (Upload) or DL (Download) commands in the Command Line Tool. How

To run Repository Loader from a command line:

1.	Choose Start→Programs→Command Prompt.

1. 	Enter the following commands:

d:

cd d:\oracle_home\bin

where d: and oracle_home identify the drive and directory to which the Oracle software is installed.

3.	Enter the command as follows:

ckldbt61 username/password@connection [/a:container]
/w:workarea_name  /c:load_file_name  [/l | /u]
[/s:irid] [/n] [/b] [/e:error_file_name]
[/r:redo_file_name]

The options are as follows.

username/password@connection

Mandatory

The username, password and database alias for the repository from which you are unloading or to which you are loading. This must be the first parameter following the utility name.

/a:container

The full pathname of the container in the repository; this pathname is case-sensitive. You must use '\'  as the separator character, for example, “Workarea1\Folder1”.

For unload operations, this is the container from which data is to be unloaded. If you omit this parameter, all root containers and their contents will be unloaded.

For load operations, this is the name of the root container into which data is to be loaded. If you want to load data into a completely new container, specify the name of the container following this /a: option, and include the /n option (see later in this topic) as well. If you omit this parameter, any containers in the load data are created as root containers.

/w:workarea_name

Mandatory

The name of the workarea.

For unload operations, this is the workarea from which data is to be unloaded.

For load operations, this is the workarea into which data is to be loaded. The workarea must already exist.

/c:load_file_name

Mandatory

The full path and name of the load file into which data is to be unloaded or from which data is to be loaded.

/l  /u

To load, use /l (or omit, as this is the default). This reads from the file specified by load_file_name and loads the contents into the specified container.

To unload, use /u. This writes the element or set specified by /s:irid if any, or otherwise the entire contents of the container, to the file specified by load_file_name.

/s:irid

Use this to give the internal repository identifier (IRID) of an element or user-defined set to be unloaded. If you do not specify this option, the contents of the entire container are unloaded.

The IRID is a very large number that unique identifies an element in the repository. You can find out the IRID for an element from the Repository Object Navigator. Select the element in the Navigator window, then select any of its properties in the Property Palette and press F5. The identifier is the long string of numbers shown next to Object ID (not Object IVID, which is the version identifier). You can copy and paste the identifier into the command.

/n

This option is used only for load operations. It specifies that a new destination container is to be created, with the name specified by /a:container. If you do not specify this option for a load operation, the destination container must already exist.

/b

Use this option to disable the progress dialog box for the load or unload operation.

/e:error_file_name

The full path and name for the error log file to be used. By default, the file CKLD65.ERR is used in the working directory (usually oracle_home\BIN). If there are no errors, the file will be created but will be empty. If there are problems with the load or unload, errors explaining the problems are written to the error log file.

/r:redo_file_name

The full path and name for the redo log file to be used. By default, the file CKLD65.RDO is used in the working directory.

The redo file is used to hold any data that could not be unloaded or loaded for some reason. Thus, when you have corrected any errors listed in the error log file, you can reload the data from the redo file.


Opening a Navigator window

Related Topics

You can open a Navigator window:

•	from the Welcome screen of the Repository Object Navigator

•	from the main Navigator toolbar

You can open a Navigator window at any level in the repository hierarchy, including the top (repository) level. All nodes below the selected level are available for display, while those above this level are filtered out of the Navigator window.

To open a Navigator window:

1.	In the Repository Object Navigator, do one of the following:

•	From the Welcome screen, choose Open Navigator and click OK.

•	In the main toolbar, click [image].

2.	In the Open Navigator dialog box:

a.	To navigate up the hierarchy, click [image] repeatedly until the main display area shows the node (for example, a workarea, container or configuration) at whose level you want to open the Navigator.

To navigate down the hierarchy, double-click a node name (for example, Private WorkAreas). Repeat this if necessary, until you see the node at whose level you want to open the Navigator.

b.	Select the node name (do not double-click it, as doing so will drill down on that node).

c.	Click OK to display the Navigator window.

Example - displaying the entire repository

1.	Click [image].

2.	On the Open Navigator dialog box, click [image].

3.	Select the name Repository.

4.	Click OK.

Example - displaying a particular workarea, container or configuration

1.	Click [image].

2.	On the Open Navigator dialog box, double-click Private Workareas, Shared Workareas, Configurations or All Containers as appropriate.

3.	(Optional)  Click  to show the list in alphabetical order.

4.	Select the name and click OK.


Closing a Navigator window

To close a Navigator window:

In the Repository Object Navigator, do one of the following:

•	Double-click the  icon at the top left of the Navigator window.

•	With the Navigator window selected, choose File→Close.

•	Click  at the top right of the Navigator window.


Creating workareas from the Repository Object Navigator

You can create a new workarea from the Repository Object Navigator in one of the following ways:

•	from the Welcome screen

•	from the menus

You can create either a default workarea (the simplest option) or a custom workarea, or you can copy an existing workarea, or create one from a specification stored in a file. About

Note:	You must have the Workareas repository privilege before you can perform this operation. The repository owner can assign this privilege to you.

To create a workarea from the Welcome screen:

1.	Choose the Invoke Workarea Wizard option and click OK.

1. 	Follow the on-screen instructions for creating the workarea. Online help is available for each screen of the wizard.

1. 	When the workarea has been created, choose another option from the Welcome screen.

To create a workarea from the menus:

1.	Choose Tools→Workarea Wizard.

1. 	Follow the on-screen instructions for creating the workarea. Online help is available for each screen of the wizard.

1. 	To see the workarea in the Navigator window, select Private Workareas or Shared Workareas as appropriate and click [image].


Displaying access rights

Related Topics

You can display your access rights, or those of another repository user, for a selected workarea, container or configuration.

Note:	If you do not have the Manage User repository privilege and do not have the Administrate access right to the selected item, access rights for other users will not be shown.

Access rights

About workareas

About configurations

About containers

To display access rights:

1. 	In the Repository Object Navigator, choose File→Access Rights→View Access Rights.

1. 	In the left pane, navigate down the hierarchy until you find the item for which you want to display access rights.

1. 	Select the workarea, container or configuration.

1. 	(Optional) Check the Apply Public and Workarea Rights check box if you want to apply the workarea access rights, together with those defined for the PUBLIC role (for a container) or just those defined for the PUBLIC role (for a shared workarea or a configuration).

1. 	(Optional)  To grant or change access rights for the selected item, click Grant Access. About


Granting or revoking access to workareas, containers and configurations

Related Topics

You can grant or revoke the access rights that you or other repository users have for one or more selected workareas, containers or configurations. You must either own the items yourself or have the Administrate access right to them.

If you grant access to a private workarea, it becomes a shared workarea. If you revoke access by all other users to a shared workarea, it reverts to being a private workarea.

You cannot revoke your Administrate or Select access for an item if you are its owner. You can revoke an access right on an item from another user only if you originally granted the access right, or if you own the item.

Access rights

About workareas

About containers

About configurations

To grant or revoke access rights:

1.	In the Navigator window of the Repository Object Navigator, select the workareas, containers or configurations for which you want to grant or change the access rights.

1. 	Choose File→Access Rights→Grant Access Rights.

1. 	In the Users field, select the user or users to whom you want to grant access. Use the SHIFT key to select adjacent names in the list, or the CTRL key to select non-adjacent names.

1. 	If you are granting access rights, check one or more of the To Grant checkboxes.

If you are revoking access rights, check one or more of the To Revoke checkboxes.

1. 	(Optional)  If you want to grant or revoke access to all subcontainers of a selected container, check the Recurse Sub-Containers checkbox.

1. 	Click Grant if you are granting access rights, or Revoke if you are revoking access rights.


Creating configurations

Configurations define precise sets of repository objects or object versions, and are typically used when an application is ready for building. The configurations used in the build ensure that the application includes exactly the right set of components. About

You can create a new configuration in one of the following ways:

•	from the Welcome screen of the Repository Object Navigator

•	from the menus

Note:	You must have the Configurations repository privilege before you can perform this operation. The repository owner can assign this privilege to you.

To create a configuration from the Welcome screen:

1.	Choose the Invoke Configuration Wizard option and click OK.

2.	Follow the on-screen instructions for creating the configuration. Online help is available for each screen of the wizard.

To create a configuration from the menus:

1.	In the Repository Object Navigator, choose Tools→Configuration Wizard.

2.	Follow the on-screen instructions for creating the configuration. Online help is available for each screen of the wizard.


Emptying wastebaskets

Related Topics

Repository objects that have been deleted are not immediately removed from the repository. Instead, they are placed in a holding area, known as the wastebasket, in the workarea from which they were deleted. You can remove deleted objects from the repository altogether by emptying the wastebasket.

To empty a workarea wastebasket, you must have DELETE access to that workarea.

Caution:	You cannot undo this operation. Repository objects removed in this way cannot be restored.

To empty a wastebasket:

1.	In the Navigator window of the Repository Object Navigator, double-click the wastebasket in the appropriate workarea to see the wastebasket contents.

2.	If you do not see the objects you expect, select the heading Wastebasket and click [image].

3.	Choose Edit→Empty Wastebasket.

4.	Reply Yes to the message to confirm.


Restoring objects from a wastebasket

Related Topics

Repository objects that have been deleted are not immediately removed from the repository. Instead, they are placed in a holding area, known as the wastebasket, in the workarea from which they were deleted. You can restore objects to their former location in the repository, provided that the objects still reside in the wastebasket.

To restore objects from a wastebasket:

1.	In the Navigator window of the Repository Object Navigator, double-click the wastebasket in the appropriate workarea to see the wastebasket contents.

2.	If you do not see the objects you expect, select the heading Wastebasket and click [image].

3.	Choose Edit→Restore from Wastebasket.


Showing or hiding the dialog box for copy or move operations

When copying or moving repository objects, an associated dialog box is displayed by default. This dialog shows a list of the objects you are copying or moving. The dialog also enables you to specify other options, such as whether a versioned object is to be checked out immediately after the operation.

If your requirements for copy or move are the same each time, you can specify that these dialog boxes are not to appear.

To hide the dialog box for copy or move:

1. 	In the Repository Object Navigator, choose Options→General Settings.

1. 	Clear the Confirm Dialog on Copy or Confirm Dialog on Move check boxes as desired.

The option takes effect the next time you start the Repository Object Navigator.

To redisplay the dialog box for copy or move:

1. 	In the Repository Object Navigator, choose Options→General Settings.

1. 	Select the Confirm Dialog on Copy or Confirm Dialog on Move check boxes as desired.

The option takes effect the next time you start the Repository Object Navigator.


Deleting workareas

You cannot delete a workarea if it includes objects that are not under version control, or if it includes versioned objects that are currently checked out.

Note:	Deleting a workarea has no effect on the objects or object versions visible in that workarea, it simply removes the workarea specification.

To delete a workarea:

1.	In the Navigator window of the Repository Object Navigator, select the workarea name.

2.	(Optional)  To process any non-versioned or checked-out objects before deleting the workarea:

a.	Choose Version · List Checkouts.

b.	On the List Checkouts:Criteria dialog box, keep the Sub-Context set to Entire Workarea, select all three check boxes under Show, choose the By Anybody option button and click OK.

c.	For objects listed as Checked Out, either check them in or undo the checkout. For objects listed as Not Versioned, either check them in or delete them when you return to the Navigator window.

d.	Click Close on the List Checkouts dialog box to return to the Navigator window.

3.	With the workarea name selected, choose Edit · Delete.

4.	If you want to delete all the containers in the workarea as well, select the Recursively Delete Subfolders? check box.

5.	Click Delete.


Creating a default workarea

Related Topics

Creating a default workarea is the simplest way to create a new workarea. You are required only to enter the workarea name, though you can optionally enter a description as well.

When you create a workarea, it is initially a private workarea, meaning that only you can access it. Subsequently you can, if you wish, grant one or more other users access to it, thus making it a shared workarea. If you later revoke access to the workarea from all other users, the workarea becomes private again.

A default workarea has the default rule of LATEST(MAIN), meaning that only the latest version of the objects on the MAIN branch will be visible. The default checkin branch of a default workarea is None, meaning that unless a current repository policy specifies a checkin branch, checkins made from this workarea will be to the branch from where the object was checked out.

If you subsequently want to change the specification of a default workarea you use the Edit Workarea Wizard.

To create a default workarea:

1. 	In the Repository Object Navigator, choose Tools · Workarea Wizard.

1. 	Click Create a default workarea.

3.	Enter a name for your new workarea (workarea names must be unique across the repository).

4.	(Optional)  Enter a description for the workarea.

5.	Click Finish to create the workarea.


Copying workareas

Related Topics

You can create a new private workarea by copying the specification of an existing private or shared workarea.

All the attributes of the existing workarea are assigned to your new workarea, including the default checkin branch and the rules and configuration specification.

You can also change the specification of the new workarea, and choose an alternative default checkin branch.

To create a workarea by copying an existing workarea:

1. 	In the Repository Object Navigator, choose Tools · Workarea Wizard.

1. 	Click Copy a workarea.

3.	Enter a name for your new workarea (workarea names must be unique across the repository).

4.	(Optional)  Enter a description for the workarea.

5.	Enter the name of the existing workarea you want to copy.

You can use the Browse button to locate and select a workarea.

6.	(Optional)  To modify the details of the new workarea, choose Next and make the desired changes.

7.	When you are satisfied with the details of the new workarea, choose Finish to create it.


Creating a workarea or configuration from a specification file

Related Topics

You can create a workarea or a configuration from a specification contained in a text file (default extension is .CWS). The specification file contains a list of rules or configurations that define the workarea or configuration. About

You can create this file from a text editor or via the Workarea or Configuration Wizard. How

If you are creating a workarea, unless you choose otherwise the new workarea will have a default checkin branch of None. This means that unless a current repository policy specifies a checkin branch, checkins made from this workarea will be to the branch from where the object was checked out. You can also change the default specification of the new workarea, and choose an alternative default checkin branch.

To create a workarea from a specification file:

1. 	In the Repository Object Navigator, choose Tools · Workarea Wizard.

1. 	Click Create a workarea based on a file stored workarea specification.

3.	Enter a name for your new workarea (workarea names must be unique across the repository).

1. 	(Optional)  Enter a description for the workarea.

5.	Enter the full pathname of the specification file you want to use, or use the Browse button to locate and select a specification file.

6.	(Optional)  To modify the details of the new workarea, click Next and make the desired changes.

7.	When you are satisfied with the details of the new workarea, choose Finish to create it.

To create a configuration from a specification file:

1. 	In the Repository Object Navigator, choose Tools · Configuration Wizard.

1. 	Click Create a new configuration.

1. 	Enter a name for your new configuration and, optionally,  a description.

1. 	Click Next to display the Options page.

1. 	Click Initialize configuration using a file template specification.

6.	Enter the full pathname of the specification file you want to use, or use the Browse button to locate and select a specification file, and click Next.

1. 	In the Edit Specification dialog box, make any changes you want to the specification and click OK. (Click Help on the dialog box for information about how to use it.)

1. 	At the Rules Specification page, click Next.

1. 	At the Members page, add or remove any configuration members, or change their versions, as desired, and click Next.

1. 	At the List External References page, optionally click List External References to view and process any external references for the configuration members, and click Next.

1. 	At the Save page, choose whether you want to check in the configuration as well as saving it. This is the last point at which you can click Back to return to an earlier page of the wizard.

1. 	Click Next to create the configuration.

1. 	At the Summary page, click Finish.


Creating a specification file for a workarea or configuration

Related Topics

You can create a specification file from which a workarea or configuration can subsequently be created.

A specification file has the default file extension .CWS, and can be created from:

•	a text editor

•	the Workarea Wizard

The specification consists of one or more rules, configurations or both. These rules and configurations define the makeup of the workarea or configuration. About

To create a specification file (text editor method):

1. 	Open a new file in the text editor.

1. 	Enter the rules and configurations that will define the workarea.

1. 	Save the file (default extension is .CWS).

To create a specification file (Workarea Wizard method):

1. 	In the Repository Object Navigator, choose Tools · Workarea Wizard.

1. 	Click Create a custom workarea.

1. 	Enter a name for the workarea and click Next twice.

1. 	On the Rules Specification page, click Edit.

1. 	On the Rules tab, define any rules you want to use for the specification:

. 	Choose a rule from the dropdown list, and complete any further fields as required.

. 	Click  to move the rule to the Member rules and configurations pane.

. 	Repeat this step for further rules in the specification.

1. 	On the Configurations tab:

. 	Select the Latest Version box if you want to see only the latest versions of the available configurations, or leave it clear to see all available versions.

. 	Select one or more configurations if you want to include these in the specification.

. 	Click  to move the configurations to the Member rules and configurations pane.

1. 	When you are satisfied with the workarea specification, click OK to return to the Rules Specification page.

1. 	Click Save to file.

1. 	Choose the location for the file and enter its name. The .CWS extension is added by default.

1. 	Click Save to create the specification file and return to the Rules Specification page.

1. 	Click Cancel to exit from the wizard. (If you click Finish, the workarea is actually created with the specification you have just defined.)


Creating a custom workarea

Related Topics

This option offers you the widest range of choices in creating a workarea. You can specify the default checkin branch for repository object versions and set up the workarea specification (the set of rules and configurations that defines the workarea contents).

You can also choose to base your new workarea on the specification of an existing workarea, optionally modifying the specification before creating the new workarea.

If you choose none of the available options, the new workarea will have a default checkin branch of None and a default rule of LATEST(MAIN).

To create a custom workarea:

1. 	In the Repository Object Navigator, choose Tools · Workarea Wizard.

1. 	Click Create a custom workarea.

3.	In the Name field, enter a name for your new workarea (workarea names must be unique across the repository).

1. 	(Optional)  In the Description field, enter a description for the workarea.

5.	(Optional)  If you want to base your new workarea on the specification of an existing workarea, enter the name of the existing workarea in the last field on the page.

You can use the Browse button to select a workarea.

6.	(Optional)  To modify the details of the new workarea, choose Next and make the desired changes.

7.	When you are satisfied with the details of the new workarea, choose Finish to create it.


Editing the file registry

The file registry determines how a particular file type is treated when stored in the repository (for example, whether it is treated as a text or a binary file). A number of file types are predefined, and you can edit this registry to add a new file type or delete an existing one.

You cannot edit a file type once it has been defined; you must delete it and redefine it.

To add a new file type:

1.	Choose Utilities→Edit File Registry.

2.	Scroll to the end of the spreadtable list and select the Pattern field.

3.	Select New Pattern.

4.	In the Pattern field, enter the file name pattern that identifies the file type (for example, "%.exe").

You can use a subpattern for a specific case. A subpattern appears lower down the pattern list than its corresponding general pattern. For example, if line 1 of the list specifies the pattern %.DOC to be treated as text files, a subsequent line can specify a particular file as an exception to this, e.g. MYFILE.DOC can be specified to be treated as a binary file.

5.	In the same row of the spreadtable, select the Rule field.

6.	Choose a rule to decide how files of this type are to be treated.

When the product is installed, only the TXT_FILE rule is defined. To add further rules, choose New Rule and enter a valid rule. About

7.	(Optional)  Enter a description of the file type in the Description field.

8.	(Optional)  Click Apply to add this type and continue editing the file registry.

9.	Click OK to commit your changes to the file registry.

To delete an existing file type:

1.	Choose Utilities→Edit File Registry.

2.	Scroll down the spreadtable list until you see the file type you want to delete.

3.	Click anywhere in that row of the spreadtable.

4.	Click Delete.

If you subsequently change your mind about a deletion before you exit from the dialog box, click anywhere in that row and click Undelete (or just click Cancel).

5.	(Optional)  Click Apply to delete this type and continue editing the file registry.

1. 	Click OK to commit your changes to the file registry.


File registry rules

A number of rules are predefined. The following rules relate to the file type:

Rule	Effect
BIN_FILE	(Default) File is treated as binary
TXT_FILE	File is treated as text

The following rules relate to file compression:

COMPRESSED	File compressed on upload to repository
UNCOMPRESSED	(Default) File not compressed on upload

The default rules for an uploaded file are BIN_FILE and UNCOMPRESSED. Thus if you want a file to be treated as compressed binary, you would only need to specify COMPRESSED for it. Conversely, to treat a file as compressed text, you would need to specify TXT_FILE and COMPRESSED.

Files that are compressed on upload are automatically decompressed on download.


Changing text colors and fonts

To distinguish certain items from others, you can change the color and display font of those items in the Navigator window, the Property Palette or the TextPad.  About

To change text colors:

1.	Choose Options→Color/Font.

2.	In the Color/Font dialog box:

a.	In the Text Color field, select the type of item for which you want to set the text color. About

b.	Click the Color Palette button.

3.	In the Color dialog box:

a.	Select the required color from the palette.

b.	Click OK to display a sample of text in the new color in the sample area in the Color/Font dialog box.

4.	Repeat steps 2 and 3 for any other items for which you want to change the color.

To change text fonts:

1.	Choose Options→Color/Font.

2.	In the Color/Font dialog box:

a.	In the Fonts field, select the type of item for which you want to set the text font.

b.	Click the Font Dialog button.

3.	In the Font dialog box

a.	Select the desired font, style and size.

b.	Click OK to display a sample of text in the new font in the sample area in the Color/Font dialog box.

4.	Repeat steps 2 and 3 for any other items for which you want to change the font.


Uploading files or directories to the repository

You can copy one or more files or directories from a file system to a repository container, in an operation known as uploading.  You can copy from any file system (local or remote) to which your workstation has access.

Once files or directories have been uploaded, you can perform operations on them from within the repository. For example, you can open or edit an uploaded file using a program appropriate to the file type. The right mouse menu on a selected file indicates the operations you can perform. When a file has been uploaded, it can be brought under version control.

If the destination container is under version control, it is checked out automatically if a new file is added. However, the container is not automatically checked in again afterwards.

The effect of an upload operation can differ between Windows and UNIX file systems owing to the case sensitive nature of UNIX file and directory names. About

To upload files or directories to the repository:

1. 	Do one of the following:

•	In the Navigator window of the Repository Object Navigator, select the container that is to hold the files or directories, then choose Utilities→Upload Files and Folders.

•	In Windows Explorer, select the files or directories you want to upload, then use the mouse to drag them to the Navigator window of the Repository Object Navigator, dropping them onto the destination container.

2.	In the Upload from OS Path field, enter the full pathname of the file system directory from which the files are to be uploaded, or use the Browse button to locate and select a directory. (If this field is prefilled, you can edit the field contents.)

3.	To choose individual files by name, use the File(s) / Folder(s) field. Either enter each filename enclosed in double quotes ("") and separated by a space, or use the Browse button to locate and select files.

4.	To upload subdirectories of the selected directory together with their contents, select the Recurse into Subdirectories check box. To upload only files from the selected directory level, leave the check box clear.

5.	(Optional)  If you are using version control and you want to check in the files or directories as soon as they are uploaded, select the Check In Files After Upload box.

6.	Click OK.

7.	If you see an ALERT message indicating that a particular file might be overwritten, choose:

•	Yes to overwrite that file and continue

•	Yes To All to continue, overwriting any files with the same names already in the selected container

•	No to continue, but protecting that file from being overwritten

•	No To All to continue, but protecting any files from being overwritten

•	Cancel to abandon the upload


Performing operations on uploaded files

Related Topics

Once files have been uploaded, you can perform operations on them from within the repository. For example, you can open or edit an uploaded file using a program appropriate to the file type.

To operate on uploaded files:

1.	In the Navigator window, select the file you want to process.

2.	Select the right mouse menu to display a list of the possible operations.

3.	Click the operation you want to perform.

Note:	If you choose Open, the file is opened using whichever program is associated with the Open action for that file type in Windows. If no program is associated, create an association for opening files of that type. You make these associations in Windows Explorer, which you can open by choosing Tools→Explorer. For further instructions on associating files, look in the Help index for Windows Explorer itself.

4.	If the uploaded file is in a container for which no mapping has been specified, you may see an Alert message asking if you want to download the file and overwrite the file system copy (for example, if you try to open the file). Click Yes to continue (doing so enables the repository to locate the file in the file system).

5.	If you choose Delete File, the file is placed in the wastebasket. From there you can either restore the file to its former position in the repository, or remove it from the repository completely.


Downloading files or containers to a file system

Files or containers stored in the repository can be downloaded to any file system (local or remote) to which your workstation has access.

The effect of a download operation can differ between Windows and UNIX file systems owing to the case sensitive nature of UNIX file and directory names. About

To download files or containers to a file system:

1.	In the Navigator window, select the container whose contents you want to download to a file system (or select file names within a container if you want to download individual files).

2.	Choose Utilities→Download Files and Folders.

3.	To choose individual files by name, use the File(s) / Folder(s) field. Either enter each filename enclosed in double quotes ("") and separated by a space, or use the Browse button to locate and select files.

4.	To download subcontainers of a selected container together with their contents, select the Recurse into Subdirectories box. To download only files from the selected container level, leave the check box clear.

5.	In the To OS Path field, type the full pathname of the file system directory to which you are downloading, or use the Browse button to locate and select a directory. (If a file system mapping has been specified, this field is prefilled with the value of the mapping; you can edit this field if you want.)

6.	Click OK.

7.	If you see an ALERT message indicating that a particular file might be overwritten, choose:

•	Yes to overwrite that file and continue

•	Yes To All to continue, overwriting any files with the same names already in the selected file system directory

•	No to continue, but protecting that file from being overwritten

•	No To All to continue, but protecting any files from being overwritten

•	Cancel to abandon the download

8.	(Optional)  When the operation has finished, choose Tools→Explorer to see the downloaded files in the file system.


Synchronizing the repository with a file system

Synchronization enables you to update files in a selected repository container to make them identical to the corresponding files in a mapped file system, or vice versa. About

For example, if the contents of a file are changed in the file system, synchronization ensures that the same changes are made to the corresponding file in the repository. The system works out whether the repository or the file system has the latest files and updates one or the other accordingly. Note, however, that any changes to the file name should be made from the repository and not in the file system.

If you select a container that has not been mapped to a file system, you are required to perform the mapping first. A mapped container is denoted by  in the Navigator window.

If synchronization causes new files to be added to the selected container, the container is checked out automatically. However, it is not checked in again afterwards.

The effect of synchronization can differ between Windows and UNIX file systems owing to the case sensitive nature of UNIX file and directory names. About

To synchronize the repository with a file system:

1.	In the Navigator window, select the container whose contents you want to synchronize.

2.	Choose Utilities→Synchronize Files and Folders.

If the container is not mapped to a file system, a dialog box appears so that you can perform the mapping. How

3.	In the Synchronize dialog box:

a.	(Optional) If you want the contents of any subcontainers of the selected container to be synchronized as well, select the Recurse into Sub-Folders check box, otherwise leave it cleared.

b.	(Optional) If you want to convert synchronized text files from Windows (MS-DOS) format to UNIX format or vice versa, click Options and choose a translation option.

c.	Click Synchronize to begin synchronization.

1. 	If you see an Alert dialog indicating that the repository copy of a file has been removed from the workarea (either by deletion or exclusion), you must choose how you want to handle the file system copy. Choose:

•	Yes to delete this file from the file system

•	Yes to All to delete this and all other files in the same situation from the file system

•	No to avoid deleting this file from the file system

•	No to All to avoid deleting this and any other files in the same situation from the file system

•	Cancel to abandon synchronization


Running Windows Explorer

You can run Windows Explorer from within the current tool. This can be particularly useful when you are uploading or downloading files.

To start Windows Explorer:

•	Choose Tools→Explorer.


Transferring ownership of repository objects

You can transfer ownership to another user of a workarea, container or configuration that you currently own.

If you transfer ownership of a private workarea, it becomes a shared workarea and you retain your existing access rights to it.

If you transfer ownership of a container, all the objects in that container will belong to the new user. To find the owner of a container, look at its Owner property in the Property Palette.

To transfer ownership of an object:

1. 	In the Navigator window of the Repository Object Navigator, select the container, configuration or workarea for which you want to transfer ownership.

1. 	Choose File→Access Rights→Grant Access Rights.

1. 	Click Ownership.

1. 	Select the user to whom you want to transfer ownership.


Comparing workareas

Related Topics

You can compare the contents of two workareas, or you can compare two workarea specifications. The results are displayed in the Compare window. About

To compare two workareas:

1. 	In the Navigator window of the Repository Object Navigator, select the first workarea.

1. 	Choose Utilities→Compare.

1. 	In the dialog box, select the second workarea and click OK.

1. 	In the Compare Workarea dialog box, choose whether you want to compare the contents of the workareas or their specifications.

Comparing workarea contents displays the differences in the set of objects and object versions that are visible in the workarea.

Comparing workarea specifications displays the differences in the set of rules and configurations that determine what is visible in the workarea.


Creating and editing files from the repository

It is possible to create files and edit them from the repository. You must create a file in a particular container.

To create a file from the repository:

1. 	In the Navigator window of the Repository Object Navigator, select the container that is to own the file.

1. 	Click .

1. 	Select Files and click OK.

1. 	Type the name of the file.

1. 	Click  or press RETURN.

To edit a file from the repository:

1. 	Ensure that an application (e.g. a text editor, word processor or compiler) is is associated with the Open action for that file type in Windows. If no program is associated, create an association for opening files of that type. You make these associations in Windows Explorer, which you can open by choosing Tools→Explorer. For further instructions on associating files, look in the Help index for Windows Explorer itself.

1. 	In the Navigator window of the Repository Object Navigator, select the file.

1. 	(Optional) If the file is under version control and checked in, choose Version→Check Out.

1. 	On the right mouse menu, click Open.

1. 	If you see an Alert message asking if you want to download the file and overwrite the file system copy, click Yes to continue (doing so enables the repository to locate the file in the file system).

1. 	Edit the file as desired and save the changes.


Checking rollback segments for import or export

Before you begin an import or export operation, you need to make sure that a large enough rollback segment is available should the operation not succeed.

Note:	The following procedure should be performed by the repository owner, who will also need a username with the DBA system privilege.

To check the rollback segments:

1. 	Open a SQL*Plus window (for example, choose Tools→SQL*Plus from a repository tool).

1. 	To see which rollback segments are online and which tablespaces they belong to, enter:

select segment_name, tablespace_name, status from dba_rollback_segs;

3.	In the Repository Administration Utility, click Check Requirements, then click Tablespaces.

4.	Look under Space Available for the tablespaces containing the rollback segments and determine whether there is one that you listed in step 3 with enough free space for the import or export operation.

5.	If a large enough tablespace is not available, create one or ask the database administrator to do so.