8-4 Administrators Guide for Dynamic Converter
If you used an XML-compliant template to create an HTML snippet of code from a content item see
Method 1: Make the Conversion Template XML-Compliant on
page 8-2, then you do not need to specify a layout template that creates the same HTML snippet effect. You can, instead, pass a blank parameter in the Idoc Script
function: incDynamicConversionSales,latest,Business,.
For your convenience, we have included a sample layout template called snippet_ layout.txt see
snippet_layout.txt on page 6-4, which is located in the
ucmDistributionDynamicConverterSamples directory. This sample file includes the basic ingredients for a portal-style web page that draws information HTML snippets
from other content items stored in the Content Server. The results appear very similar to the illustration in
Portal-Style Website Sample .
The file contains the following parts:
■
Header and footer information that displays Content Server borders and navigation
■
HTML tables to control the layout of the portal page two columns in the top table cell and one column in the bottom
■
Three Idoc Script functions to pull three separate pieces of content into the portal page referencing a version, template, and layout file in each
You can start with this portal web page example and then customize it to fit your needs.
8.4 Inline Dynamic Conversion
Dynamic Converter includes an Idoc Script extension that allows you to convert a native document into an HTML snippet without referencing a Classic HTML
Conversion template or layout template. The conversion is the same as using a blank Classic HTML Conversion template with a layout template that specifies body content
only. You cannot, however, modify the conversion template or layout template used in this conversion.
You can convert native documents this way by using the following Idoc Script code: incInlineDynamicConversiondDocName, Revision_Selection_Method
Place the content ID of the native document in the parenthesis along with the revision. For example, if the native document has the content ID SalesDoc, then the complete
Idoc Script syntax would be:
incInlineDynamicConversionSalesDoc, Latest or
incInlineDynamicConversionSalesDoc, LatestReleased This type of conversion is useful for converting native documents into HTML snippets
without having to specify a Classic HTML Conversion template and a layout template in the Content Server.
8.5 Displaying Content Server Metadata on a Web Page
Dynamic Converter includes an Idoc Script extension that allows you to make Content Server metadata for a document available on the converted page. To use this Element,
insert the following code into your conversion template:
HTML Snippets 8-5
dcLoadDocInfo You can add this code to a layout template see
Chapter 6, Classic HTML Conversion Layout Templates
or a Classic HTML Conversion template see Chapter 5, HTML
Conversion Templates , depending on how you are using these templates for your
document conversion. It is important that this code be placed before any part of the web page attempts to use the document metadata.
The simplest solution is to add it to the very top of a layout template. This way, any part of the web page that tries to use the Content Server metadata for the document
will work. You can also add this code to any of the sections of a Classic HTML Conversion template for more information, see Including HTML or scripting code in
a web page in the Template Editor help.
8-6 Administrators Guide for Dynamic Converter
9
Working With Converted Content 9-1
9
Working With Converted Content
This section covers the following topics:
■
Viewing Content Information on page 9-1
