Validate scripts and other external components

Some objects depend on external components to run, such as script function libraries and references to other objects’ attributes. The status of these external components can change, perhaps disabling some capability of the object.

For example, an object refers to a value of an attribute of another object, which is subsequently deleted. This will result in the remaining object going to a Warning status.

Normally, the system will update the validation status of an object when the missing script function or object/attribute is later added to the system. But there are a few cases where the status of an object needs to be manually validated by the user.

For example:

• When importing scripts and script libraries, there are cases when the script will import before the associated library and validate incorrectly, and

• When graphics associated with an object are imported along with a graphic they embed, the containing graphic may be imported first and validated incorrectly.

In each of these situations, the object may incorrectly have a status of either Bad or Warning. In this case, you may want to manually validate the object to update its status, especially if the status is preventing the object from being deployed. For more information, see Validate an object manually.

Two kinds of indicators are shown in the object icons:

• Deployment status for instances only.

• Configuration status for templates and instances.