Show TOC

Background documentationLifecycle Management Locate this document in the navigation structure

 

Feature

Type of Change

Description

Customizing Manage Task Panel Tree

New

You can choose to hide models from view in the Manage task panel. This makes it easier when working with a source control system that contains a large number of models that are not relevant to you.

To do this, from the context menu of one or more development components or models in the source control repository choose Remove From Workspace. (Selecting a development component hides all the models within that development component.) The selected models are removed from the repository tree, but still remain in the source control system. To view the hidden models, in the context menu of the relevant development components choose Sync. The models are synced to the local workspace and are visible in the tree again.

Note Note

You cannot remove models from the workspace if they are checked out by you or added by you to source control (but not yet checked in).

End of the note.

Deleting Unused Components

New

When adding a development component to source control, and when checking it in, a check is performed to find coded services in the development component that are not reused by any other component. A dialog box is then displayed asking whether you want to delete them. If they are not required, deleting them may help to improve response times when working with source control.

Pausing Multiple-Selection Source Control Operations

New

When you check out, synchronize, or revert multiple models or development components in the source control system, you can specify whether you want Visual Composer to pause the operation if an error occurs with one of the models or development components. You can then decide whether to cancel the entire operation or continue with the remaining models or development components.

To pause one of the previously mentioned operations if there is an error, select the Prompt on error checkbox in the dialog box that is displayed after you start the operation. If you do not select this checkbox, Visual Composer collects the error information and displays it only at the end of the entire operation.

Saving Referenced Models

New

When adding a model to source control, or checking a model in to source control, if the model references other models that have unsaved changes, you must save the referenced models before checking in the model. A prompt is displayed during the check-in process enabling you to save the relevant models.

Checking In Dependent Components

New

When checking in a model to source control, you can now choose whether to also check in any referenced (dependent) components at the same time. To do this, select the Check in with dependencies checkbox in the prompt displayed during the check-in operation.

Ability to Force Synchronization

New

If a development component or model has the status synced, but for some reason you think that it is not synchronized with the version that is checked in to the source control repository, you can force synchronization to occur. In the Manage task panel, in the context menu of the item you want to synchronize choose Force Sync.

Virus Scan Support

New

If you have configured the virus scan interface to include external virus scanners on the AS Java, you can activate the visualcomposer virus scan profile in NetWeaver Administrator to automatically scan models for viruses during Visual Composer import and migration operations.

For more information, see Data Storage Security.

New Behavior When Adding Items to Source Control

Enhanced

Previously, when you added a model or development component to source control, it also automatically checked in the model(s). Now, when you add a model or development component to source control, it is added to the source control repository with the status Added to source control, but is not checked in. Any models in the local development component that are referenced by a model being added to source control are also added to the source control system together with the selected model.

A model or development component with status Added to source control cannot be seen by other users until it is checked in. When you add a development component to source control, it reserves a name for it in the source control repository. You can reuse models that have been added to source control according to the same reuse rules that apply to models that have been checked in to source control.

After you have added a development component or model to the source control system, but have not yet checked it in, you can choose to move it back to the local repository by right-clicking it in the source control repository tree in the Manage task panel and choosing Move to Local Repository from the context menu. Note that if you move a development component back to the local repository, the source control name reservation is canceled and references between models in the local repository and models in this development component may be broken.

Ability to Select Models in Migration Wizard

Enhanced

Previously, before migrating models from Visual Composer 7.0 to Visual Composer 7.2, you had to first export the models using the Visual Composer 7.0 system. Now, you can run the Migration wizard in Visual Composer 7.2 and select the models you want to migrate directly from the Visual Composer 7.0 repository (without needing to first export them).

Configuring Devserver and SDIC Properties

New

When setting up a connection for Visual Composer to SAP NetWeaver Developer Studio, you can now configure properties both the devserver and SDIC properties using the Connect Visual Composer Designtime with NW Development Infrastructure configuration wizard.

For more information, see Configuring Devserver and SDIC Properties.