Design Studio enables you to define preferences that apply to your entire workspace. For example, you can specify whether to package cartridges during incremental builds and define groups of languages with which you intend to work. When defining preferences, see the following topics:
Before you can deploy a cartridge project to a run-time environment, you must determine which entities, libraries, and resources to include (or package) in the project. Typically, Design Studio automatically packages your projects during incremental builds. You can disable this functionality and defer packaging until project deployment.
Note:
Defer packaging only for large projects when packaging is slowing incremental builds. Do not enable this option for systems used for command line builds because it prevents builds from producing complete archives.Design Studio always packages the entities, libraries, and resources for clean builds.
To define packaging preferences:
From the Window menu, select Preferences.
The Preferences dialog box appears.
Select Oracle Design Studio.
Select Defer packaging.
Design Studio will not package the project during incremental builds; packaging is deferred until you deploy the project.
Click OK.
Design Studio supports multiple languages for fields in run-time applications. Use the language preference settings to define the languages that you intend to use in your cartridges and to define the language with which you prefer to work.
To define language preferences:
From the Window menu, select Preferences.
The Preferences dialog box appears.
Select Oracle Design Studio.
Click New.
The Add Language dialog box appears.
Select a language.
Click OK.
Design Studio adds the language to the Languages group.
(Optional) Define the language display priority.
When multiple languages appear in the Languages group, use the Up and Down buttons to reposition the language display priority. The language display priority controls the order in which the languages appear in Design Studio language drop-down lists.
(Optional) Click Remove to delete a language from the Languages group.
In Preferred Language, select the language in which you prefer to work.
Click OK.
Conceptual model preferences enable you to change some validation errors to warnings. For example, you can change the validation severity during conceptual model design if you are working in a single functional area, and when your design work does not require solution validity across all functional areas. By default, Design Studio displays validation errors for all functional areas.
Note:
The Conceptual Model Preferences page displays only the functional areas that are defined in the workspace. If no functional areas are defined in the workspace, the options defined in this procedure are not available.To define conceptual model preferences:
From the Window menu, select Preferences.
The Preferences dialog box appears.
In the left-column menu tree, expand the Oracle Design Studio folder.
Click Conceptual Model Preferences.
Select one of the following:
To relax the validation severity for a functional area, select Model entities relevant to specific Functional Areas.
To retain the default validation severity for all functional areas, select Entire Model (all Functional Areas). This is the default setting.
For each functional area, select one of the following:
To relax the validation severity for a functional area, select Warning. For example, select this option for functional areas that are not directly relevant to the functional area in which you are working.
To retain the default validation severity for a functional area, select Error. Select this option for functional areas in which you intend to work.
Click Apply.
Click OK.
Clean and rebuild the projects in the workspace.
Conceptual Model Preferences Page
About Conceptual Model Preferences
A conceptual model spans multiple functional areas, and includes configuration related to commercial order management, service order management, and technical order management. Your role determines whether you work on the entire model or in a single functional area. For example, an enterprise architect is concerned with the entire model, and needs to ensure that all products, customer facing services, service actions, components, resource facing services, resources, and other conceptual model entities are fully modeled and include valid references and relationships. Enterprise architects need to see validation errors for all missing conceptual model entities and for unresolved references.
A conceptual model may be developed by a team of developers working in different projects. In this organization, some developers work in projects that include only products and references to customer facing services. Other developers may work in projects that include only customer facing services and service actions. While other developers may work with sets of projects that include the resource facing services and resources for a specific technology.
In this organization, there are multiple projects that comprise the entire solution. Developers working in projects related to the service order management and technical order management layers may not be interested in the projects related to commercial order management. These developers will likely want to include in their workspace only those projects in the model that are relevant to their work.
If you load only a subset of the conceptual model projects into your workspace, Design Studio generates validation errors because the system detects missing entities, references, and relationships. You can reduce the number of errors and relax the validation in the areas outside of the scope of your work by defining conceptual model preferences. The Conceptual Model Preferences page in Design Studio enables you to define a validation severity level for each functional area defined in your conceptual model.
Based on the settings that you define for a functional area on the Conceptual Model Preferences page, Design Studio uses the following rules to evaluate the validation severity levels:
For each functional area, Design Studio determines the provider functions that are impacted.
Design Studio generates validation errors for poorly-formed named relationships defined between source and target entities in the impacted provider functions. Validation issues in all other provider functions are identified as warnings.
Design Studio generates action-related validation errors (such as mandatory and multiple action checks) for actions named as a source or target for impacted provider functions and for actions directly associated to the specified functional area.
Design Studio generates realization validation errors for source entities named in the impacted provider functions, including actions. Realization validation issues in all other provider functions are identified as warnings. Design Studio generates fulfillment pattern reference-related errors for source entities in the impacted provider functions. Fulfillment pattern reference-related issues in all other provider functions are identified as warnings.
Use the Conceptual Model Preferences page to select a validation severity level for each functional area.
| Field | Use |
|---|---|
| Enforce referential integrity for | Select one of the following:
|
| Select Functional Areas to Validate | For each functional area, select one of the following:
|
You define Data Dictionary preference settings to specify the tree depth to which the Data Dictionary tree can expand.
To define Data Dictionary preferences:
From the Window menu, select Preferences.
The Preferences dialog box appears.
In the left-column menu tree, expand the Oracle Design Studio folder.
Click Data Dictionary.
See "Data Dictionary Preferences Editor" for more information.
In the Expansion Level field, specify the tree depth to which the Data Dictionary can expand.
Click Apply.
Click OK.
Design Studio restarts.
Use the Data Dictionary preferences page to specify the expansion level of the Data Dictionary.
| Field | Use |
|---|---|
| Expansion Level | Enter the tree depth to which the Data Dictionary tree can expand. The default is 6. If you change the default setting, you must restart Design Studio for the change to take effect.
Note: Expanding the tree depth above 9 may adversely affect system performance. |
The Dictionary View Preferences page enables you to configure the manner in which Design Studio initially filters the entities that appear in the Dictionary view, when viewing entity types in an editor that is linked to the Dictionary view.
Filtering options enable you to determine the types of entities that initially appear for entities in a specific project type or for all projects in the workspace, and for each entity type within a project.
To define Dictionary view preferences:
In Design Studio, from the Window menu select Preferences.
The Preferences dialog box appears.
In the Preferences dialog box menu tree, select Oracle Design Studio and then select Dictionary view.
The Dictionary view preferences page appears.
In the Select Cartridge Project Type field, select an option to define filter options for entities in a specific project type.
In the Entity types column, select an entity type to define the filtering options for that entity type.
In the Default Entity Filter Types column, do any of the following:
Click Select to add additional default entity filter types to the entity type configuration.
Select any of the default entity filter types and click Remove to remove the filter type from the entity type configuration.
Click OK.
Design Studio adds updates the Default Entity Type Filter Types column. The next time you open the entity type in an editor (and if you have linked the editor with the Dictionary view), the Dictionary view initially displays all available entities of the defined types in the project or in any dependent projects.
Use the Dictionary View Preferences page to configure the manner in which Design Studio initially filters the entities that appear in the Dictionary view, when viewing entity types in an editor that is linked to the Dictionary view.
| Field | Use |
|---|---|
| Select All Cartridge Project Type | Select an option to define filter options for entities in a specific project type. |
| Default Entity Filter Types | Displays the entity types that initially appear in the Dictionary view, when viewing entity types in an editor that is linked to the Dictionary view. |
| Remove | Click to remove a filter type from the entity type configuration. |
| Select | Click to add additional default entity filter types to the entity type configuration. |
The Eclipse platform includes a Local History feature which maintains copies of saved files. These copies are maintained only in your workspace. The Local History feature provides a recovery file on your local file system for work not yet committed to source control, and you can use this feature to complement your source control system.
Note:
Oracle does not recommend using the Local History feature for primary backup, as it is subject to media failure and is coupled to a specific workspace.You define preferences for the Local History functionality. For example, Oracle recommends that you change the default settings to define a longer retention period for added security.
To define Local History preferences:
From the Design Studio Window menu, select Preferences.
The Preferences dialog box appears.
Select General, then select Workspace, and then select Local History.
The Local History preferences page appears.
Select Limit history size.
In Days to keep files, enter 28.
Increasing the value in this field to 28 enables recoveries even after extended work stoppages (for example following vacations). Oracle recommends, however, that you check changes into source control regularly.
In Maximum entries per file, enter 50.
In Maximum file size (MB), enter 1.
Click OK.
For more information about the Local History feature, see the Eclipse Help.
The .metadata workspace folder contains information about your workspace. You can back up your workspace preferences and recreate workspaces by exporting and then importing workspace preferences.
For more information about importing and exporting workspace preferences, see the Eclipse Workspace User Guide.