Welcome Guest! Register/Login
Web services for automated content conversion and deployment

Hyper.Net SharePoint Edition Getting Started Guide

Show Comments (0)    Public Domain Bookmark this publication
How to modify a SharePoint document library to take advantage of Hyper.Net Working with drafts and versions (lifecycle synchronization) Publishing behavior based on content approval, versioning and check-out settings When SharePoint content approval is disabled
Table of ContentClose
Hyper.Net SharePoint Edition Getting Started Guide
When SharePoint content approval is disabled
     
Versioning
Require check-out
Behavior
None
No
The document version in SharePoint remains 1.0. Every change results in the creation of a Hyper.Net transformation request. Hyper.Net processes each request, replacing the previous 1.0 version of the publication with the new 1.0 version of the publication.
 
     
Major
No
Every change in SharePoint results in a new version, e.g. 2.0, 3.0, 4.0. Every change 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).
Major and minor
No
Every change in SharePoint requires the author to decide if the document should be saved as a major or minor version. The author must explicitly request that a major version be created, otherwise a minor version will result. Hyper.Net transformation requests are created only when new major versions are created. 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
The document version in SharePoint remains 1.0. Hyper.Net transformation requests are created only when the document is checked in. Transformation requests are not created for documents that are modified and saved but left in a checked-out state.
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. Every check-in 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).
Major and minor
Yes
Every change in SharePoint requires the author to decide if the document should be saved as a major or minor version. The author must explicitly request that a major version be created, otherwise a minor version will result. Hyper.Net transformation requests are created only when new major versions are checked in. 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.
Loading, please wait...
About Publications
Contributor
Aruna
Published: 5/11/2011
Tags:
0 5,290 0
Display Options
Embed, Share & Subscribe
Download
Rate & Report
Statistics