Types of Checkpoints
The table below lists the types of checkpoints that may appear in an object’s history, and the action that created the checkpoint.
| Type | Description |
|---|---|
| Add GNote | Attach a global note to the selected object. This appears in the history of the object to which the note is attached. |
| Add LNote | Attach a local note to an object within the selected container object. This does not appear in the history of the object to which the note was attached, it appears in the history of the container object only. |
| Add Lock | Indicates that an object within the ContentRoutingProject, standard Project or configuration is being modified. |
| Cfg Chkpt | Checkpoint the parent configuration, ContentRoutingProject and standard Project. |
| Created | Create the object. |
| Deleted | Remove Object from all views—object does not appear in any current view. |
| Del Item | Remove an object from the selected container object |
| Del LNote | Remove a local note attached to an object in the selected container object. This does not appear in the history of the object to which the note was attached, it appears in the history of the container object only. |
| Del Lock | Indicates that a lock on an object within the ContentRoutingProject, standard Project or configuration was deleted. |
| Del Note | Remove a global note attached to the selected object. This appears in the history of the object to which the note was attached. |
| Del ObDef | Delete an object definition |
| Del User | Remove a desktop |
| Del WkFl | Remove a workflow template |
| Ed Lnote | Select and open a local note attached to an object. This does not appear in the history of the object to which the note was attached, it appears in the history of the container object only. |
| Edited | Modify the contents of the object |
| Edit Note | Select and open a note attached to a specific object. This appears in the history of the object to which the note is attached. |
| Edit WkFl | Edit the workflow of the selected ContentRoutingProject or Project object |
| Forward | Forward the selected Project object, or one or more objects in the ContentRoutingProject. This is not in the history of the ContentRoutingProject or standard Project in the configuration (the original project). It is only in the history of the standard Project or objects in the ContentRoutingProject in the workflow. |
| ImportDoc | Create objects with the Dynamic Import application interface. |
| New Item | Create an object within the selected container object |
| New ObDef | Add an object definition |
| New User | New User Add a desktop |
| New WkFl | Create a workflow template |
| No Change | Error during a copy or move |
| Open | User is in the process of editing the contents of the object |
| Posted | Successful posting of a ContentRoutingProject, standard Project, or object in a project |
| Post Fail | Post attempt of ContentRoutingProject, standard Project or object in a project failed |
| Pre-Post | Checkpoint generated just before Contenta attempts to post. A Posted checkpoint usually follows this checkpoint. |
| Read Note | Read a note |
| Same | Edit a module with no changes |
| Set Post | Mark or unmark an object for posting in the selected ContentRoutingProject or standard Project |
| Set Prop | Modify the property sheet entries of the selected object |
| System | Default checkpoint type |
| Transfer | Copy an object from another location, or receive a ContentRoutingProject or standard Project that was forwarded to you in the workflow. |
| Undo | Restore a previous revision—this replaces the current version. This appears in the history of the container object. |
| User | User creates a checkpoint by selecting the Checkpoint option on the Edit menu. |
User and System Generated Checkpoints in History
Entries for automatic (system generated) checkpoints include:
- Checkpoint ID; Internal revision number.
- Desktop name of the user who was responsible for the checkpoint.
- •Date and time of the revision.
Entries for user generated checkpoints include:
- Checkpoint ID; Internal revision number.
- Desktop name of the user who was responsible for the checkpoint.
- Date and time of the revision.
- Name given to the checkpoint by the user.
- User comment given to the checkpoint.