Out-of-date objects in a ContentRoutingProject or Project

An object can become out-of-date when in a ContentRoutingProject or standard Project.

If an object is reused into a Project then modified outside the ContentRoutingProject or Project (that is, modified under the configuration), then in the ContentRoutingProject or Project, the object is updated as follows.
  • The object's value in the Out of Date column is set to Yes.
  • The object's value in the Status column is set to read-only.

This indicates that you do not have the latest copy of the object. The object’s status is read-only to protect the integrity of the data.

Example

If an object is reused-copied into two different projects—for example, Proj1 and Proj2, then modified in one of those projects (Proj1 in this example), the object is updated as follows.

  • In Proj1:
    • The object's value in the Out of Date column is set to No.
    • The object's value in the Status column is set to read-write.
  • In Proj2:
    • The object's value in the Out of Date column is set to No.
    • The object's value in the Status column is set to Locked with a Lock Type of Project.

If modified in one project, the object is locked in the second project and cannot be modified. However, the Out of Date column is not set to Yes because the object’s revision number matches the revision number of the original object (the object that was reused and resides under the configuration).

When the project in which the object was modified (in this example, Proj1) is posted, the values in the Out of Date and Status columns in the second project (in this example, Proj2), are updated as follows.
  • The object's value in the Out of Date column is set to Yes.
  • The object's value in the Status column is set to read-only.