Generating InfoPath forms (pre version 5.2)
To generate XML documents
3 To generate repeating entries (an array) based on the values in a Notes multi-valued item, add the multi=‘repeat’ attribute to your <ppm:replace> tag. This will cause the surrounding XML tag to be repeated once for each input value encountered. You can also specify multi='repeatparent' to repeat the surrounding XML tag and its parent once for every value encountered in the multi-valued item. This option is useful for encoding multiple attachments (see below) or other repeating group elements in InfoPath.To avoid generating tags when the Notes values are null, missing or empty strings, use the ifempty='remove' or ifempty='removeparent' attribute. This will cause the surrounding XML tag (or its parent) to only be generated if there is actual data in the source Notes item.
4 To generate rich text entries, add the encode=’xhtml’ attribute to your <ppm:replace> tag. This will cause the HTML markup extracted from your Notes documents to be saved into your generated document as XML tags rather than as plain text.When using encode='xhtml' any Notes DocLink icons that are encountered are converted to encoded icons in your XML document. To disable this behavior, add the attribute linkicons=’false’ to your <ppm:replace> tag. This will cause Notes DocLink icons to be replaced with a simple text link instead.
Other possibilities for the encode attribute are 'commonname' and 'abbreviatedname' for formatting Notes names and 'datetime', 'dateonly' and 'timeonly' for formatting XML Date/Time values.
If you wish the source data column to copied “as is” into the XML document, you can use encode=’xml’ rather than encode=’xhtml’. This might be useful if, for example, you have a Notes item that contains pure XML or you have created a formula column in your source data definition that emits an XML fragment. If you omit the encode attribute completely, the source data will be encoded as a Text element by default and any special characters (such as XML angle brackets) will be escaped.
To encode your attachment as an InfoPath attachment (using InfoPath’s proprietary format), add the encode=‘attachment’ attribute to your <ppm:replace> tag. To encode your attachment using standard base64 encoding, add the encode=‘base64’ attribute to your <ppm:replace> tag. This later choice is useful in some XML applications, but not for InfoPath.
To substitute target information in your XML, use the tag, <ppm:replace target=’site’>. Currently, the only supported value is “site” which yields the complete site URL.
Generating InfoPath forms (post version 5.2)
To generate InfoPath form documents from Lotus Notes documents that were created using Notes forms
With some form templates, the XSN importer cannot determine what the HREF (location of template) should be for a generated document. For instance, if a template was imported into Central Admin, approved by an administrator, then assigned to a site, where SharePoint automatically created a content type for it. In this case, the published XSN location is not in the XSN. For these unusual cases, you need to specify the template location in the Published XSN location field. This field will be automatically loaded with the location if the XSN importer can determine the HREF.
Generating raw HTML and XML
Generating read-only HTML
•
•
© ALL RIGHTS RESERVED. Feedback Termini di utilizzo Privacy Cookie Preference Center