Single

Editable

One

A single document is attached, and the performer can edit it. The dataslot always contains the most recently edited document. For example: An employee writes a proposal and sends it to the Manager. The Manager may edit the proposal and then send it to the Senior Manager. The Senior Manager receives the proposal that is already updated by the Manager, and may edit it further before sending it to the General Manager. At any stage, the document may be returned to any of the earlier performers, who can again edit it. Note that multiple versions of the document are never available, avoiding ambiguity. Note: At each workstep, there is only one performer, and that performer can edit the single document. This type of Document dataslot is used when the workflow is simple, a strict version control is in place, and the decision making performer only needs to focus on the most recent document.

Single

Editable

All

A single document is attached, and all the performers can edit it. The dataslot always contains the most recently edited document - the one last edited by any one of the performers. For example: A Manager initiates a leave plan for his team, with individual team member names. This plan goes to all the members of the team, and each member updates the document with his/her own plan. Any individual’s plan does not depend on or affect another member’s plan, and the sequence of members updating the plan is not important. Since it is a public non-confidential document, a single document can serve the purpose. The Manager can at any time open the document to check whether the plan is complete. This type of Document dataslot is suitable for routine public documents that have specific limited input from all the performers, and the sequence of update is unimportant. Another example is a weekly status report.

Single

Non-editable

One

A single, read-only document, and the performer can only read the document. Any revision must be conveyed to the creator separately. This type of Document dataslot is appropriate when the specific document is solely owned by the creator, or when it is available to the performer only for information. Note: Only one version of the document can exist, and the creator is always responsible for the updates.

Single

Non-editable

All

A single, read-only document, and all performers can only read the document. Any revision must be conveyed to the creator separately. This type of Document dataslot is used when the specific document is solely owned by the creator. In special cases, the creator may get feedback from performers, but can use discretion to apply the feedback. It can also be conveniently used to communicate information to a large group (for example, company-wide information of a new customer) where no feedback is expected. Note: Only one version of the document can exist, and the creator is always responsible for the updates.

Bundle

Editable

One

One or more documents are attached. The performer can edit or remove the documents, as well as attach his/her own documents. The dataslot contains multiple documents that can be attached by different authors, and are of the most recently edited version. For example: An employee writes a proposal and sends it to the Manager. The manager may attach some more documents for reference. The Manager may edit the proposal and reference documents, and may add more supporting documents before sending them all to the Senior Manager. The Senior Manager receives the proposal (already updated by the Manager), and other documents. and may edit one or more documents, attach additional documents, and send them all to the General Manager. At any stage, the documents may be returned to any of the earlier performers, who can again edit them. Note: At each workstep, there is only one performer, and that performer can edit the multiple documents. Note that this situation may result in a loss of prior edits. Note that any of the performers can have the original document, as well as their own edited version of the document attached in this dataslot. Hence multiple versions of the same document may be available at any time. This may be a necessity, when the process requires such tracking.

Bundle

Editable

One - Editable by the author only

One or more documents are attached.The performer can only read the documents authored by others, and can attach his/her own documents. The dataslot contains multiple documents, that can be attached and edited by different authors, and are of the most recently edited version. Note that each document can be edited only by the performer who attached it to this dataslot. For example: An employee writes a feedback form and sends it to the Manager. The Manager may want some changes, but should not be able to do so without the employee’s knowledge. The Manager may give his review separately, and the feedback form is updated only by the employee. This type of Document dataslot is very useful when the specific documents are solely owned by their creators. Note: Only one version of each of the documents can exist, and their creators are always responsible for the updates.

Bundle

Editable

All

One or more documents are attached. All the performers can edit all of these documents. The dataslot contains multiple documents that can be attached and edited by different authors, and are of the most recently edited version. Note that each document can be edited by any of the performers, and that this situation may result in a loss of prior edits.For example: A marketing manager initiates a set of proposals, that require inputs from various departments such as finance, development, HR, and administration. This set goes to the managers of these four groups, and each performer updates the set with own inputs. Individual inputs are only for their own department, and the sequence of updates is not important. The marketing manager can at any time open the set to check the latest update. This type of Document dataslot is suitable for routine public documents that have specific limited input from all the performers, and the sequence of updates is unimportant. Another example is an intranet knowledge base with tracking. Note: Any performer can have the original documents, as well as his own edited version of the documents attached in this dataslot. Hence multiple versions of the documents may be available any time.This may be a necessity, when the process requires such tracking.

Bundle

Editable

All - Editable by the author only

One or more documents are attached. The performers can only read the documents authored by others, and can attach their own documents. The dataslot contains multiple documents that can be attached by different authors. Note that each document can be edited only by the performer who attached it to this dataslot. For example: A procedures dataslot may contain multiple procedures, however, each one is owned by a specific person. If any changes are required, only the creator can carry out the changes. This type of Document dataslot is very useful when different documents are owned by different performers, but are available for public viewing. Note: Only one version of each of the documents can exist, and their creators are always responsible for the updates.

Bundle

Non-editable

One

Read-only documents.The performer can only read the documents. Any review must be conveyed to the creator separately. This type of Document dataslot is appropriate when the specific documents are solely owned by the creators, or when they are available to the performer only for information. Note: Only one version of each of the documents can exist, and their creators are always responsible for the updates.

Bundle

Non-editable

All

Read-only documents. The performers can only read the documents. Any reviews must be conveyed to their creator separately. This type of Document dataslot is used when the specific documents are solely owned by their creators. In special cases, the creators may get feedback from performers, but can use their discretion to apply the feedback. It can also be conveniently used to communicate information to a large group (for example, organization policies) where no feedback is expected. Note: Only one version of each of the documents can exist, and their creators are always responsible for the updates.