Axway Composer > Working with objects > Basic operations > Checking objects

Checking objects

Recursive Check: checking an object and the objects it uses

Purpose

The principal purpose of the check function in Composer is to verify that all mandatory object definitions are correct. Where object definitions are incorrect, the software identifies the errors and lists them in the Log.

When you check an object, Composer checks that:

All mandatory object properties are correctly defined
The syntax of any DML expressions is correct

In addition, you must check an object before you can:

Before checking an object

Before you begin: For each life cycle status, the following table indicates the action you must take to check an object.

Status icon	Status	Action
	ToBeChecked	Complete the procedure described below.
	Checked	None. The object is already checked.
	ReadyToSend	None. The object is already checked.
	Archived	None. The object is already checked.
	ToBeCommitted	None. The object is already checked. CFT only
	Committed	None. The object is already checked.

Checking an object

Composer performs different types of check, depending on where (in the interface) you select to perform the check.

Checking a single object

To check only the properties of the object on display:

Select the open object properties window in the right pane.
Select File > Check from the menu bar. Alternatively, click on the toolbar.
Composer verifies that the property definitions and syntax of the selected object are correct.
Select:

File > Save to save the object in the repository.

File > Close to close the object properties window.

Checking an object and all the objects it uses: Recursive Check

To check both an object and all the objects that it uses:

Select the object in the navigator pane.
On the navigator toolbar, click . Alternatively, right-click the object and select Recursive Check from the contextual menu.

Composer verifies the property definitions of the selected object and of all the objects used by that object.

In addition, you can perform a Recursive Check on objects that you select in the:

Entity Browser
Dependencies Browser

Select the object or objects that you want to check and click on the Browser toolbar.

What happens when you check an object

For both a single Check and a Recursive Check, Composer displays the results of the operation in the Log pane displayed at the bottom of the main screen display.

Successful check

If the object definitions are valid, Composer:

Sets the status of the object(s) to Checked
Displays next to the name of the checked object(s), both in the navigator pane and in the Browsers

Failed check

If the property definitions or DML syntax are not correct, Composer displays a list of the errors in the Log. The object status remains ToBeChecked.

Errors are typically caused by problems in specific fields of specific metadata objects. For direct access to those fields and those objects, double-click the error in the Log. Composer automatically opens the properties window for the appropriate object, and displays the tab and field that caused the error.