When you revive a terminated object, the object, along with its properties and relationships,
is restored to an active status in the configuration that it was terminated.
Which objects can be revived?
Only the interface definitions, properties, and relationship definitions with the
same termination date as the object can be revived.
Only the object and any validated relationships can be revived. The revive functionality
does not cascade to other items, unless the delete flags on the relationship definition
specify the object and relationship. In that case, the related object can be brought
back to active.
You cannot use the Revive command for the following:
-
A document object.
-
An object that has a mandatory relationship to another object that is also terminated.
The object cannot be revived because the relationship cannot be reinstated.
-
An object whose class definition was subsequently deleted from the schema.
-
An object where reviving the relationships breaks the cardinality for the related
object. For example, TAG_001 was related to an equipment item and then terminated;
Tag_002 was then related to the same equipment item. TAG_001 cannot be revived because
cardinality states you can only have one tag related to an equipment class.
-
An object that was terminated by a merge action.
-
An object that was terminated by an unclaim action.
-
Click Query > Query With History, and select a type.
-
In the Live and terminated [objects] dialog box, select a terminated object, and select Revive.
The current values of properties are shown with a green icon. Historical values for
properties that have been terminated are displayed with a blue icon.
-
You must revive terminated objects one at a time.
-
When an object is revived, the end objects of each relationship are validated to see
if they are still active in the database. If an end object is no longer active in
the database, the object and its relationship cannot be revived.