Bundles in Collaborative Lifecycle Management

The revise operation follows different rules depending on the object:

• Revising a bundle reference is not recommended since it creates a new reference of the bundle without its instance.
• Revising the father of a bundle triggers a completion mechanism which consists in revising the bundle accordingly. It therefore remains once-instantiated.

The new revision from operation allows you to specify a specific property for the bundle reference. Here are the different rules that depend on the object:

• To be revised: the bundle is revised during the operation.
• To be inserted as new: the bundle is inserted as new during the operation.
• To be reused: not possible.

The branch operation follows different rules depending on the object:

• New branch of a bundle reference is not recommended since it creates a new reference of the bundle without its instance.
• New branch of bundle’s father triggers a completion mechanism which consists in creating a new branch of the bundle accordingly. It therefore remains once-instantiated.

The duplicate operation follows different rules depending on the object:

• Duplicating a bundle reference on its own is not recommended since it will create a new reference of bundle without is instance.
• Duplicating the father of bundle triggers a completion mechanism which consists in duplicating bundles accordingly so that they remain once-instantiated.

The advanced duplicate operation allows you to specify a specific property on the bundle reference:

• Exclude: the bundle is excluded during the operation.
• Duplicate: the bundle is duplicated during the operation.
• Reuse: not possible.

The delete operation follows different rules depending on the object:

• Deleting a bundle reference is authorized.
• Deleting the father of bundle runs the completion mechanism and deletes the bundle instance with its reference.

The transfer ownership operation follows different rules depending on the object:

• Transferring ownership of a bundle reference alone in a private collab space is not recommended. The bundle reference and all aggregated objects are transferred and are not searchable.
• Transferring ownership of the father of bundle runs the completion mechanism which consists in transferring the bundle reference with its father.

The reserve/unreserved operations follow the standard behavior.

The access rights operation follows the standard behavior.

The subscribe/unsubscribe operations follow the standard behavior.

The change maturity operation follows the standard behavior. There is no completion mechanism.

The “Replace by New Duplicate” operation is the addition of a replace operation plus a duplicate operation. The duplicated part triggers the completion mechanism will also revises the bundle.

The “Replace by New Revision” operation is the addition of replace operation plus a revision operation. The revision part triggers the completion mechanism which will revises the bundle.