As authors contribute content, they might find items that are locked by other
users, because either they are being edited by another user or a draft item has been created.
When a user is editing an item, the item is locked to other users. This means other users
are unable to edit the item until the current user closes the item that they are editing. A
lock symbol is displayed against items that are currently locked.
Administrators can lock and unlock items by selecting them and clicking either the Lock
or Unlock button.
The locking of sites, site areas, taxonomies, and categories is configurable and
is not enabled by default. When locking is enabled, authors cannot create any children
under the locked site or site area. This only applies to items that are located one level
below a locked parent.
When a new draft of a published item is created, a check mark is displayed next to the
published item indicating that no other user can create a draft until the current draft
progresses through a workflow and its state changes to published.
Infospace JSR 168, JSR 286 portlets and IBM Lotus Web Content Management for WebSphere portals, liferay, weblogic using RAD, Inter-portlet communication, Ajax, SQL. Java, Interview Questions and much more...
Tuesday, March 16, 2010
Library Versioning in IBM Lotus Web Content Management!!!!
With library versioning, administrators can group the items within a library by label or
date and time.
If something goes wrong, the administrators can go back to a previous version,
selected by date or label.
A library cannot be restored while any items are currently locked or checked out
by users. Before restoring a library, you must view all published items in a library and
unlock any items marked as checked out or locked.
date and time.
If something goes wrong, the administrators can go back to a previous version,
selected by date or label.
A library cannot be restored while any items are currently locked or checked out
by users. Before restoring a library, you must view all published items in a library and
unlock any items marked as checked out or locked.
Item Versioning in IBM Lotus Web Content Management !!!!
Lotus Web Content Management a versioning systems with which authors, designers,
and administrators can track the changes that have been made to specific items or to an
entire library, identify versions of libraries by date or tag, and restore them in the future.
Following options are available to define when an item should be versioned.
are available:
versioningStrategy.Default = always | never | manual
versioningStrategy.AuthoringTemplate = always | never | manual
versioningStrategy.Component = always | never | manual
versioningStrategy.Content = always | never | manual
versioningStrategy.PresentationTemplate = always | never |
manual
versioningStrategy.Site = always | never | manual
versioningStrategy.Taxonomy = always | never | manual
versioningStrategy.Workflow = always | never | manual
You can restore a version by viewing an item's version history and selecting a version to
restore.
and administrators can track the changes that have been made to specific items or to an
entire library, identify versions of libraries by date or tag, and restore them in the future.
Following options are available to define when an item should be versioned.
- Manual : A version action can be added to a workflow stage to create a new version
when entering or exiting the workflow stage.
A version action in a draft stage will not trigger versioning, since a draft
cannot have versions.
It is possible to create only one version of the item in a stage. - Always : A version of an item is created each time you save an item, or, if the item is
participating in a workflow, each time the item's state changes to published. - Never: Versioning is never used.
are available:
versioningStrategy.Default = always | never | manual
versioningStrategy.AuthoringTemplate = always | never | manual
versioningStrategy.Component = always | never | manual
versioningStrategy.Content = always | never | manual
versioningStrategy.PresentationTemplate = always | never |
manual
versioningStrategy.Site = always | never | manual
versioningStrategy.Taxonomy = always | never | manual
versioningStrategy.Workflow = always | never | manual
You can restore a version by viewing an item's version history and selecting a version to
restore.
Subscribe to:
Posts (Atom)