Business Application Diagram error messages

A property value was incorrect and was updated during the load.

Error message and resolution should be self-explanatory.

The .4ba file is invalid and contains incorrect node definitions. Contact your local support center.

There are conflicts between items (they share same ID or file path).

Resolve the conflict. (Right-click and select Resolve Conflict menu option.)

Implement the item. (Right-click on item and select Implement.)

Error message and resolution should be self-explanatory.

Some implemented item file is missing on the disk. Restore the file or recreate the item and implement it.

Open the template file settings.agconf and fix the errors.

Open the template file settings.agconf and add the property definition.

Multiple items share the same name property and it should be unique. Modify name property value so that it is unique within the file items.

Multiple relations share the same name property, name should be unique. Modify name property value so that it is unique within the file relations.

<Constraint> (<description>) constraint failed.

Invalid source <Item>. When a constraint is defined with minSource and maxSource values as 0, it implies that the source item should not have any outgoing relations of type given in reference. This error occurs as the item has non-supported outgoing relations.

Remove all the unsupported outgoing relations from the item.

<Constraint> (<description>) constraint failed.

Invalid destination <Item>. When a constraint is defined with minDestination and maxDestination values as 0, it implies that the destination item should not have any incoming relations of type given in reference. This error occur as the item has non-supported incoming relations.

Remove all the unsupported incoming relations from the item.

<Constraint> (<description>) constraint failed.

Number of outgoing Relations, <Count>, are less than <Expected Count>.

The numbers of outgoing relations from the item are less than the expected minimum outgoing relations count. Add at least <Expected Relation Count> number of outgoing relations to fix this problem.

Number of outgoing Relations, <Count>, are greater than <Expected Count>.

The numbers of outgoing relations from the item are greater than the expected maximum outgoing relation count. User has to remove the extra added relations, so that the relation count will not across <Expected Relation Count> which is the maximum number of outgoing relations allowed.

Number of incoming Relations, <Count>, are less than <Expected Count>.

The numbers of incoming relations to the item are less than the expected minimum incoming relations count. User has to add at least <Expected Relation Count> number of incoming relations to fix this problem.

Number of incoming Relations, <Count>, are greater than <Expected Count>.

The numbers of incoming relations to the item are greater than the expected maximum incoming relation count. User has to remove the extra added relations, so that the relation count will not across <Expected Relation Count> which is the maximum number of incoming relations allowed.

An ID is blank, the file is invalid. Contact your local support center or remove the item containing the ID an create a new one.

Multiple items share the same id, creating a conflict. (Right-click and select Resolve Conflict menu option.)

A build rule execution is trying to access data not described in the template settings.agconf (through the Business Application diagram). Update the template settings.agconf file, adding the unsupported item or change the file build rule to not use the file.

Some defined property does not belong to the current settings (orphan) and are ignored by the compilation process. For solutions, see Orphan properties.

Some defined property group does not belong to the current settings (orphan). For solutions, see Orphan properties.

Some node contains metadata definitions which do not belong to the current settings (orphan). They are ignored by the compilation process. For solutions, see Orphan properties.

The Item definition does not exist in the current template settings. It is ignore by the compilation process. Add the Item definition to the template settings.agconf, convert the item to a corresponding supported Item type (Right-click and select Convert menu option.), or remove the item.

The relation definition does not exist in the current template settings and is ignored by the compilation process. To resolve this error:

1. Add the Relation definition to the template settings.agconf.
2. Convert the item to a corresponding supported Item type (context menu convert action).
3. Remove the item.