| |
|
|
Parameter
|
Description
|
|
Doc.Type
|
The name of the document type profile. In our example, you would use the name Procedure.
|
|
Transformer
|
The name of a transformer that implements the transformations necessary to create and publish the various renditions of a document. This feature is useful in advanced situations where source document content must be manipulated in a specific way before transformation, for example, or when you wish to post-process the transformed result before it is published to satisfy an unusual business requirement, or when you need to transform a document authored in an unusual application.
In most cases, the value default should be used here. Refer to the Hyper.Net Support Database at www.coextant.com for information on creating a custom transformer.
|
|
Category
|
The name of the category associated with all publications transformed by this document type. In our example, this would be a specific procedure category.
|
|
Language
|
The language of the document. You can use any value here. This value allows you to categorize and select content by language in the WCMS application. If selection of content by language is not required in your solution, you may leave this value blank.
|
|
Target
|
The target database where Hyper.Net's output should be populated. In SharePoint, the target database is implemented as a list. This value should remain HNHDS but may be changed in advanced scenarios. Refer to the Hyper.Net Support Database at www.coextant.com for details.
|
|
Url
|
The URL linking to the application that renders the content from the target database. This setting is ignored when using Hyper.Net's MOSS or WSS publisher because content is rendered by SharePoint itself.
|
|
Override Calculated Values
|
Normally, the values on the document type profile will be overridden by a corresponding value found on the content type profile. The content type in SharePoint can thus be used to provide users with restricted control over the publishing process—for example the ability to select or enter a category or language, or the ability to enable an optional audio file rendition. Values on the content type may also be computed.
In most situations, this option should be disabled (not checked).
If you enable this option, the values specified on the document type profile will always be used. Any corresponding values found on the content type profile will be ignored. This allows you to impose a configuration across document sets in cases where you do not have full control over the content type profiles being used throughout the organization.
|
|
Transformed Format
|
Enable: A Rich Hypertext rendition will be created for the document. If the document being transformed is not a Word or Word-compatible document, this setting is ignored.
Disable: The rendition will not be created.
|
|
Revision
|
Defines how revision marks should be handled before creation of the Rich Hypertext rendition.
Accept: All revision marks are accepted before transformation.
Reject: All revision marks are rejected before transformation.
Show: All revision marks are preserved and formatted using the revision mark settings configured for the copy of Word installed on the transformation server (for example strike-through red and underline blue).
|
|
XSLT
|
The name of the XSLT file used to parse HNXML into the final HTML that is published into the target database. Hyper.Net comes with an XSLT designed to transform HNXML into HTML 4.0 that is strictly compliant with W3C standards: hnxml.xslt. You can copy and modify this XSLT to accommodate business requirements for the required output formats. In this case you would provide the name of your customized XSLT file here. In most situations the default value hnxml.xslt should be left unchanged. Refer to the Hyper.Net Support Database at www.coextant.com for additional details.
|
|
HTML Format
|
Enable: A Flat HTML rendition of the document will be created using the original authoring application. The resulting output components will be collected, normalized and populated into the target database.
Disable: The rendition will not be created.
|
|
PDF Format
|
Enable: A PDF rendition of the document will be created.
Disable: The rendition will not be created.
|
|
PDF/A Format
|
Enable: A PDF/A rendition of the document will be created.
Disable: The rendition will not be created.
| |
|
|
Note
|
If your solution requires PDF to PDF/A transformation or requires watermarking, compounding or metadata stamping in your published PDF/A files, you may need to install Hyper.Net's optional PDF/A Transformation Engine on the Hyper.Net Transformation Server. Be sure to discuss your requirements with your Hyper.Net consultant.
|
|
|
Flash Format
|
Enable: A Flash rendition of the document will be created.
Disable: The rendition will not be created.
| |
|
|
Note
|
This feature requires the installation of Hyper.Net's optional Flash Converter on the Hyper.Net Transformation Server.
|
|
|
Audio Format
|
Enable: An MP3 rendition of the document will be created.
Disable: The rendition will not be created.
|
|
Source Format
|
Enable: A copy of the original document will be created and stored as a publication rendition.
Disable: The rendition will not be created.
|
|
Schema
|
The name of the transformation schema to be used for the content type. You can create a transformation schema for each document type or share them between document types.
|
|
Appr. Notification Email
|
A notification is sent to the indicated email address after the publication has been created in the publication approval area of the publication library.
| |
|
|
Note
|
The publication approval feature is intended for use with document storage systems that do not provide their own approval function. Because content approval occurs within SharePoint, this feature is not supported by Hyper.Net SPE's MOSS or WSS Publisher. Configuration of this parameter will therefore have no effect.
To enable approval on the publication side, Hyper.Net's SQL Publisher must be used. Be sure to discuss your requirements with your Hyper.Net consultant.
|
|
|
Prod. Notification Email
|
A notification is sent to the indicated email address after the publication has been created in the production area of the publication library and is viewable to the intended user audience.
| |
|
|
Note
|
The publication approval feature is intended for use with document storage systems that do not provide their own approval function. Because content approval occurs within SharePoint, this feature is not supported by Hyper.Net SPE's MOSS or WSS Publisher. Configuration of this parameter will therefore have no effect.
To enable approval on the publication side, Hyper.Net's SQL Publisher must be used. Be sure to discuss your requirements with your Hyper.Net consultant.
|
|
|
Effective Version Management
|
Enabled: Effective Version Management is enabled for the publication.
Disabled: This feature is disabled.
| |
|
|
Note
|
Effective Version Management is a function that allows multiple versions of the same publication to exist in the target database at the same time. Each version is marked with an effective date in the past, present or future. The end-user is presented with the currently effective version of the publication by default, but may look into the past or into the future as needed. This function is useful for meeting advanced quality management requirements.
Due to limitations in the SharePoint data model, the effective version management feature is not supported by Hyper.Net SPE's MOSS or WSS Publisher. This setting should therefore be set to Disabled when publishing into MOSS or WSS.
To enable effective version management for use with SharePoint, Hyper.Net's SQL Publisher must be used. Be sure to discuss your requirements with your Hyper.Net consultant.
|
|
|
Version Retention
|
The number of publications to retain in the publishing site when Effective Version Management has been enabled.
|
|
Disabled Effective Version Management
|
When Effective Version Management is disabled—which is the case when using Hyper.Net's MOSS or WSS Publisher—you must decide how the source files contained in the transformation requests sent to the Hyper.Net Transformation Server should be handled. If your organization requires a tight audit trail, you should select the first option below. This requires more space in Hyper.Net's bookkeeping system, however. The other two options allow you to save space by deleting source files you will never need again (subsequent requests from SharePoint will contain the source files they need to create a publication).
Keep Source Files for All Versions: All source files remain "attached" to their corresponding transformation requests.
Discard Source Files When Versions Are Replaced in Production: When a publication is replaced, the source file stored in the previous version's transformation request is deleted. The source file associated with the current version's request is retained. This is the default setting because it allows the request associated with the current version to be re-queued by the administrator.
Discard Source Files When Versions Are Published in Production: Removes the source file stored in a transformation request as soon as the request has been successfully processed. This setting ensures that no source files remain in Hyper.Net's bookkeeping system. It is therefore no longer possible for the administrator to re-queue requests. If a publication must be re-published, it must be once again saved in SharePoint.
| |
|
|
Tip
|
Before selecting one of these options, be sure to find out how your corporate policies impact this issue.
|
|
|
Appr. Publication Readers
|
A list of users who are authorized to review and approve publications created by the system for approval. All users on this list must approve the publication. When all have approved, the publication moves automatically into production (it is marked for release to the general audience).
| |
|
|
Note
|
The publication approval feature is intended for use with document storage systems that do not provide their own approval function. Because content approval occurs within SharePoint, this feature is not supported by Hyper.Net SPE's MOSS or WSS Publisher. Configuration of this parameter will therefore have no effect.
To enable approval on the publication side, Hyper.Net's SQL Publisher must be used. Be sure to discuss your requirements with your Hyper.Net consultant.
|
|