Views enable you to customize the manner in which information is presented in the Workbench. When working with views, see the following topics:
Views provide access to specific sets of functions, available through the toolbars and context menus. For example, the Problems view displays errors that exist in the model entities, so you use the Problems view to locate and resolve entity errors. You use the Dictionary view to model and review data in your workspace. The Dictionary view and the Problems view each provide access to a different set of Design Studio functions.
A view can appear by itself or it can be stacked with other views. Additionally, you can undock a view from the workbench. You can change the layout of a perspective by opening and closing views and by docking them in different positions in the workbench. Within a given perspective, views further define your Workbench layout and provide different presentations of resources.
The most common views in the Java perspective are the Problems, Outline, and Package Explorer views. The most common views in the Studio Design perspective are the Solution, Studio Projects, Dictionary, and Data Elements views. The most common views in the Environment perspective are the Cartridge Management view, Console view, and Environment view.
Many views are available that are not native to Design Studio but are required for a variety of tasks, including implementation and builds of cartridges. These include various General views, Team views, Debug views, Java views, and others.
You can right-click on the title bar of a view and select Fast View to create space on your workbench while keeping views minimized but easily accessible. When you select Fast View, the corresponding view temporarily displays on top of the other views. The fast view minimizes again when you click outside of it. Additionally, you can create a fast view by dragging a view onto the Fast View bar in the bottom left corner.
Design Studio perspectives have default combinations of views and editors. You can open a Design Studio view that is not included in the current perspective, minimize views to increase the working space of your monitor, and restore the view to the original size.
To open a view:
From the Window menu, select Show View.
A list of commonly used views appears.
Do one of the following:
If the view you want to open appears in the list, select it.
If the view that you want to open does not appear in the list, select Other In the Show View dialog box, expand the appropriate directory, and select the view.
Design Studio adds the view to the Workbench.
(Optional) Click the Minimize View button for a view to minimize the view and increase the amount of viewable space.
An icon representing the view will appear in the status bar of the view area. Click the Restore button to restore the view to its normal size.
You can minimize and maximize views. When minimized, the view (or view stack) is collapsed to a series of icons on the workbench frame. Minimizing views enables you to retain the collection of views open in a perspective while temporarily creating more space for an editor. You can click the Restore icon to restore the views to the initial size.
To maximize views, double-click the view's title bar. The view fills the entire Workbench. Double-click the title bar a second time to return to the original size.
Use the Data Elements view to view the simple and structured data elements for a selected entity and to perform operations on those data elements.
The Data Elements view is linked to the Solution view, the Studio Projects view, and the Package Explorer view. When you make a selection in any of these views, Design Studio updates the content in the Data Elements view based on the active selection. The Data Elements view enables you to view all data elements associated with the selected entity and to perform operations on the data elements, without needing to open the related editor.
For example, when a Data Schema entity is selected in the Solutions view, you can right-click in the Data Elements view to add data elements to the selected data schema. If a Product specification is selected in the Studio Projects view, you can view the data elements defined on the product in the Data Elements view, and perform refactoring operations. See "Refactoring Entities and Data Elements" for more information about the operations that you can perform on data elements in this view.
Use the Dictionary view to display all data elements for every entity that contributes to the Data Dictionary. The root element is read-only.
You can use this view to create and manage data elements. For example, you can use this view to add elements to data schemas or to refactor data elements.
Additionally, you can use this view to model entities by dragging data from this view into an entity editor. See "Dragging Elements from the Dictionary View" for more information. Also, you can double-click the data element to open the element in the source entity editor.
|Show Only Root Simple Element||Toolbar||Click to display all root level simple elements. Disable to display root level simple and root level structured data elements.|
|Filters elements inherited through entity extension||Toolbar||Click to display only data elements that inherit from a base type. Inherited elements (structured or simple) are defined using a base type as the data type.|
|Filters elements not visible to the active editor based on project dependencies||Toolbar||Click to display only those elements available to the active editor, based on the project dependencies. See "Project Editor Dependency Tab" for information about defining project dependencies.|
|Clear Filter||Toolbar||Click to remove all previously defined filters: all data elements in the workspace appear in the view.|
|Filter Menu||Toolbar||Click to access two sets of view filters: the Tags filter and the Entity Type filter. In the Tags area, select:
In the Entity Type area, select:
|Toolbar||Search for specific data elements, such as a specific address or person, or for specific entities. Enter terms into these fields and click the Filter button to search for the term. Click the Filter button again to clear the search term. When filtering, consider the following:
|Add Simple Schema Element||context menu||Right-click a Schema entity to add a new global simple schema element (an element that has no associated parent structure) to a data schema. A simple schema element cannot contain any child elements.
See "Creating Simple Data Elements" for more information.
|Add Structured Schema Element||context menu||Right-click a Schema entity to add a new global structure (a structure that has no associated parent structure) to a data schema. Structures are complex data types that include embedded data types.
See "Creating Structured Data Elements" for more information.
|Add Structured Child Schema Element||context menu||Right-click a structured data element to add a new child structure (a structure that is included in a parent structure) to a data schema. Structures are complex data types that include embedded data types.
See "Creating Structured Data Elements" for more information.
|Add Simple Child Schema Element||context menu||Right-click a structured data element to add a new child schema element (an element that is included in a parent structure) to a data schema.
See "Creating Simple Data Elements" for more information.
|Delete||context menu||Select to permanently remove the schema element from a data schema.
This action is not available for root level elements (those that represent the entity name).
|Move Up||context menu||Select to move a data element (and the children, if applicable) to a higher position within the set of child data elements.
You can move data elements when:
|Move Down||context menu||Select to move a data element (and the children, if applicable) to a lower position within the set of child data elements.
You can move data elements when:
|Refactoring||context menu||Select to access a menu of options that enable you to propagate data model changes across a solution without sacrificing model integrity. See "Refactoring Entities and Data Elements" for more information.|
You can add elements to data schemas and to modeling entities by dragging elements from the Dictionary view to an entity editor.
You can drag elements from the Dictionary view to an entity when:
The target and source entities are writable. See "Defining Entity Read-Only Properties" for more information.
The target and source entities exist in projects that are unsealed. See "Unsealing Projects" for more information.
The element is not in an unresolved state. See "Refactoring Entities and Data Elements" for more information about resolving elements.
The target entity supports the selected entity type.
Use the Notes view to provide documentation for the entity or data element selected in the Solution view. You can annotate entities and data elements when you want to communicate to other team members information about the solution.
For example, you can contribute content to Design Studio reports by writing your own internal documentation about entities and data elements, and you can format the documentation using plain text or simple HTML. See "Notes Tab" for more information.
The Notes view is linked to the Solution view, the Studio Projects view, and the Package Explorer view. When you make a selection in any of these views, Design Studio updates the content in the Notes view based on the active selection.
Use the Outline view to view relationships, entities, and data elements related to the entity in the active editor. Also, you can perform operations on those relationship folders, entities, and elements.
The Outline view is linked to the editor in focus. When you switch editors, Design Studio updates the content in the Outline view based on the active selection.
The Outline view enables you to navigate through and to perform operations on relationships, entities, and data elements while maintaining focus on the active entity or data element. See "Refactoring Entities and Data Elements" for more information about the operations that you can perform on data elements in this view.
Use the Overview view to review the entire content of any Oracle Communications Order and Service Management (OSM) process, if supported by the active editor. A process may contain hundreds of tasks and subprocesses; the Overview view enables you to navigate throughout a process quickly and to select specific sections of a process for view in the Process editor.
The Overview view always displays the entire diagram. The rectangle represents the position and size of the current view in the Process editor. Move the rectangle to change the section of the diagram displayed in the Process editor. Resize the rectangle to zoom in or zoom out of a specific section of the diagram.
Use the Problems view to review short descriptions of each problem marker in a project. Design Studio creates problem markers on data elements in modeling or in the code during implementation and displays warnings, errors, and informational messages that are generated as you work on projects. For example, if a Java source file contains syntax errors, these errors appear in the Problems view. Similarly, if you make configuration errors while modeling entities, error messages appear in this view.
By default, the problems are logged by severity. You can also group the problems by type. The first column of the view displays an icon that denotes the message type (warning, error, or informational) and the description. The remaining columns display the name of the resource that generated the problem, its path, and its directory location.
Note:Design Studio updates problem markers during project builds. Oracle recommends that you enable the automated build feature to ensure that problem markers are current to the most recent saved content. Problem markers are based on saved content; Design Studio does not update problem markers to reflect unsaved work.
Problem markers indicate that changes are required before the project can deploy successfully. You can double-click any error in the view to open the editor of the affected entity and resolve the problem. In code files, the line containing the problem is highlighted. Design Studio includes multiple layers of validation. Therefore, a single error may generate multiple markers.
Click the View Menu button in the Problems view toolbar and select Configure Contents to define Problem view configuration.
For best results, select Errors/Warnings on Selection to ensure that errors and warnings for the current selection (and children, if applicable) appear.
Additionally, you can filter the Problems view to display only warnings and errors that are associated with a particular resource or group of resources.
See the Eclipse Workbench User Guide for information about using the Problems view.
Use the Relation Graph General view to display graphical representations of entity-to-entity type relationships, such as parent-child relationships. With the Relation Graph view open, you can verify parent-child entity relationships after defining the relation.
|Link||Toolbar||Click to link or unlink the view to the active editor.
When you link views to active editors, Design Studio updates the contents of the view based on the entity displayed in the active editor. For example, when the Relation Graph view is linked, Design Studio updates the contents of the view each time you toggle to a different editor, displaying the relationship graph that is specific to the entity currently displayed in the active editor.
You can unlink the view to prevent Design Studio from updating the contents of the Relation Graph view when the entity is no longer displayed in the active editor.
|Context Menu||Increase and decrease the size of the objects representing the elements in the view.|
|Context Menu||Increase and decrease the area of the relation graph that appears, relative to the active entity.|
Use the Solution view as an entry point to your service fulfillment solutions, to view the relationships among the elements in a solution, and to adjust the level of detail for efficient navigation and design. The Solution view enables you to explore the associations between entities used to model the service domain in the conceptual model and in application projects.
From the Solution view, you can model, run design patterns against, and refactor entities. The Solution view enables you to organize and view your solutions through products, services, resources, orders, and other entities that implement the solution. This view displays relationships among entities in a workspace and includes child folders that represent relationships defined in your solution.
You can filter the Solution view so that child folders appear even if the relationships are not yet established (the folder will be empty; the Solution view will include these folders to indicate that these are important relationships that can be defined).
For example, when you filter the Solution view to show all folders and to display the orders in your workspace, all Order entities include a Creation Tasks folder, a Default Process folder, a Permissions folder, and so forth. Even when no creation task is associated with the order, the Creation Task folder still appears, indicating that a creation task can (and should) be associated with an order.
You can also filter the view to display or hide actions, realizations, and components associated with the entities in the Solution view.
Note:The Solution view is linked to other views and to the active editor. When you select an entity in the Solution view, all linked views are updated to display information about the selected entity.
See Design Studio Concepts for more information about navigating across solutions using the Solution view.
|Category Filters||Click to define options for filtering the Solution view. You can select options to display actions, realizations, and components associated with products, services, and resources. You can also display or hide Functional Area entity realizations and order item parameter bindings.|
|Add Relationship||Click to add relationships to the selected entity.|
|New Category Items||Click to add a new category item to the Solution view. The options that are available depend on the category selected.
For example, if you select an Order entity in the Solution view Category field, you can click the New Category Item arrow to create a new order.
|Show/Hide Folders||Click to display only primary relationships for the entities that appear in the Solution view.|
|Category||Filter for entities that are associated with a specific category. Entities associated with the category display at the root level of the Solution view.|
|Types||Filter for entity types that have been registered for the selected category, which include all types of entities or elements, text documents, Word documents, and any other types contained in your workspace.|
|Filter||Enter an entity name and click the Filter button (represented by a flashlight icon) to search for a specific entity. Click the Filter button again to clear the search term. When searching, consider the following:
Use the Structure view to view relationships for a selected entity or data element and perform operations on the relationship contents. For some relationships, these folders appear even if the relationships are not yet established (the folder will be empty; the Solution view will include these folders to indicate that these are important relationships that can be defined).
For example, if you select an order entity in the Solution view, the Structure view displays a Creation Tasks folder, a Default Process folder, a Permissions folder, and so forth. Even when no creation task is associated with the order, the Creation Task folder still appears in the Structure view, indicating that a creation task can (and should) be associated with an order.
The Structure view is linked to the Solution view, the Studio Projects view, and the Package Explorer view. When you make a selection in any of these views, Design Studio updates the content in the Structure view based on the active selection. The Structure view enables you to navigate through and to perform operations on relationship folder contents while maintaining focus on the active entity. See "Refactoring Entities and Data Elements" for more information about the operations that you can perform on data elements in this view.
Modeling Data Using Context Menus
Use the Studio Projects view to perform modeling activities and other project tasks. This view has various functions available for project tasks, which are accessible from the Studio Projects view toolbar and context menu.
The tree structure displays Design Studio components organized by project. Each project you are working on is represented by one folder as the top level of a tree, with logical groups of entities below it.
The actions available in the Studio Projects view context menu depend on your current selection in the Studio Projects view. For example, Design Studio filters the list of entity creation actions based on the project type associated with the current selection.
In addition to commands for copying, pasting, and deleting entities in the workspace, the Studio Projects view toolbar and context menu also provide the following commands:
|Include Sealed Projects
Exclude Sealed Projects
|Toolbar||Toggle to show and hide sealed projects in the view.|
|Hierarchical view format
Flat view format
|Toolbar and Context Menu||Toggle to Hierarchical view format to display the Studio Projects view contents in a folder structure.
Toggle to the Flat view format to display the Studio Projects view contents with a dot-separated name that includes each folder in the path (if you are using folders to organize your entities).
|Include Empty Folders
Exclude Empty Folders
|Toolbar||Toggle between these filter settings to hide or display empty folders.|
|Link to Editor||Toolbar||Click to link or unlink the view to the active editor.
When you link views to active editors, an entity is highlighted in the view when the corresponding entity editor is active. Also, when you select an entity in the view, the corresponding editor becomes active (assuming that editor is open).
Unlink the view to prevent Design Studio from updating the contents views when an entity is no longer displayed in the active editor.
|Toolbar||Filter entities by location and name combinations based on the pattern and matching position. Enter filter terms into these fields and click the Filter button to search for the term. Click the Filter button again to clear the search term. When filtering, consider the following:
|New||context menu||Select to create new projects and entities.
Design Studio filters the options based on the project type associated with the current selection.
|Copy||context menu||Select to copy a project or entity.|
|Paste||context menu||Select to paste a copy of a project or entity into the workspace. Depending on the location, you may be required to edit the name for uniqueness.|
|Delete||context menu||Select to delete a project or entity from the workspace.
Note: Oracle recommends that you use the Studio Projects view to delete projects.
|Move||context menu||Select to move an entity to a different project.|
|Rename||context menu||Select to rename an entity.|
|context menu||Select Open to display the editor for the project or entity that you have selected in the Studio Projects view.
Select Open Project if there is no active selection in the view.
|context menu||Select to open or close a project in the workspace. See "Closing Projects" and "Opening Projects" for more information.
Note: Though you can open and close projects using other views, Oracle recommends that you perform these operations from the Studio Projects view.
|Expand||context menu||Expands the selected entity to display all child elements of the structure.|
|Collapse||context menu||Collapses a structured data element and hides all child elements of the structure.|
|Import||context menu||Select to import a project into the workspace. Multiple import options may appear, depending on the plug-ins installed. See "Importing Projects" for more information.
Note: Though you can import projects from other views, Oracle recommends that you perform this operation using the Studio Projects view.
|Refresh||context menu||Select to refresh the Studio Projects view.|
|Design Pattern||context menu||Select to apply a design pattern using the Design Pattern wizard. See "Working with Design Patterns" and Design Studio Developer's Guide for more information.|
|Guided Assistance||context menu||Select to open the Design Studio Guided Assistance dialog box, which provides a range of context-sensitive learning aides mapped to the editor or view in focus. See "Using Guided Assistance" for more information.|
|Deploy||context menu||Select to deploy a cartridge using Optimize Deploy. See "Deploying Cartridge Projects with Optimize Deploy" for more information.|
|Properties||context menu||Select to view the properties of the entity and define preferences.|
The Studio Projects view context menu also contains additional actions based on the current selection, as well as actions provided by Eclipse, such as actions that enable you to share projects and apply patches, compare documents, use local history, and so forth. See the Eclipse Workbench User Guide for more information.