|
|
Loading...
|
|
|
Hyper.Net SharePoint Edition Getting Started Guide
|
(0)
|
When SharePoint content approval is enabled
| |
|
|
|
Versioning
|
Require check-out
|
Behavior
|
|
None
|
No
|
This combination of settings violates accepted document control practices. Implicit in any content approval process is versioning, otherwise the approval is worthless because it leaves no audit trail. This combination of settings is therefore not supported by Hyper.Net. Hyper.Net transformation requests will not be created.
| |
|
|
Tip
|
If you are using these settings in your organization, it is advisable to re-evaluate your implementation against your business requirements. Such an implementation may lead to future compliance violations.
|
|
|
Major
|
No
|
Every change in SharePoint automatically sets the content approval status to Pending. The content approval process must be manually initiated. A Hyper.Net transformation request is created only when a new major version changes its state to Approved. Hyper.Net processes each request, replacing the previous version of the publication (for example 2.0) with the new version of the publication (for example 3.0).
|
|
Major and minor
|
No
|
Every change results in a new minor version in SharePoint. The creation of a major version initiates the approval process. Hyper.Net transformation requests are created only when new major versions are approved. Hyper.Net processes each request, replacing the previous version of the publication (for example 2.0) with the new version of the publication (for example 3.0). Minor versions stored in SharePoint are not published via Hyper.Net.
|
| |
|
|
|
None
|
Yes
|
This combination of settings violates accepted document control practices. Implicit in any content approval process is versioning, otherwise the approval is worthless because it leaves no audit trail. This combination of settings is therefore not supported by Hyper.Net. Hyper.Net transformation requests will not be created.
| |
|
|
Tip
|
If you are using these settings in your organization, it is advisable to reevaluate your implementation against your business requirements. Such an implementation may lead to future compliance violations.
|
|
|
Major
|
Yes
|
Every change in SharePoint results in a new version, e.g. 2.0, 3.0, 4.0, but only when the document is checked in. When a document is checked in, its initial approval state is Pending. The content approval process must be manually initiated. A Hyper.Net transformation request is created only when a new major version changes its state to Approved. Hyper.Net processes each request, replacing the previous version of the publication (for example 2.0) with the new version of the publication (for example 3.0).
|
|
Major and minor
|
Yes
|
This is the typical document control implementation with fine-grained versioning, check-in and approval. Check-out and check-in result in minor versions in SharePoint. The team collaborates until it is determined that the document is ready for approval. It is then checked in as a new major version and the approval process is initiated. Every approval results in the creation of a Hyper.Net transformation request for the new major version. Hyper.Net processes each request, replacing the previous version of the publication (for example 2.0) with the new version of the publication (for example 3.0).
|
Loading, please wait...
|
|
|
|
|
|
|