When transformation requests are created
During the lifecycle synchronization process, Hyper.Net transformation requests may be created when the following events occur in SharePoint:
| |
· |
Upload
|
| |
· |
Edit properties
|
| |
· |
Edit in Word and Save
|
| |
· |
Check-in
|
When Hyper.Net processes a transformation request, the entire document is published, including all of its renditions. Even if the only change to a document was a metadata value in SharePoint, for example, Hyper.Net will still transform the document into all required renditions and republish the resulting content. While this may seem wasteful, it is not without purpose.
Hyper.Net's lifecycle synchronization process is conservative. This allows you to meet even the most stringent compliance requirements. A conservative process requires that any rendition of a document released to a target audience be a complete and accurate reflection of what exists in the document management system. If Hyper.Net were to update a metadata value and a version number without updating the published renditions as well, this would be in violation of strict document control principles, because—technically seen—the document content was produced from the version 3.0 document in SharePoint, for example, instead of from the latest document version 4.0. This would not survive a compliance audit.
Fortunately, the publishing process is so fast that the extra processing required to maintain strict compliance with document control best practices can be easily borne by most systems and is worth it. In many ways, focusing on this issue is similar to trying to reduce file sizes by 10 kilobytes in an age when drive space is no longer a serious application bottleneck.