Policy Import trigger

The Policy Import trigger imports Policy and Procedure content from a structured Microsoft Word document into IBM OpenPages® Policy and Procedure fields by parsing the different sections of the document. It is triggered by checking in an attachment to the Policy object.

The trigger supports the Hybrid approach to Policy Management, It also supports updating the version number in the Docucentric approach when a new policy document is checked in. As part of the import process, the trigger also performs extensive validation to ensure that the structure of the Word document adheres to the defined Policy Template.

OpenPages or the customer can configure this component to behave for the customer methodology through registry and application text settings.

The IBM OpenPages Policy Management Policy Import Trigger has the following known limitations:
  • Bulleted lists only support the disc and circle bullet format.
  • Numbered lists only support decimal, upper-alpha, lower-alpha, upper-roman, and lower-roman.
  • Symbol fonts are not supported. You can use the Insert Symbol option and select a symbol using normal font (for example, the copyright symbol).
  • Wingding font is not supported.
  • Cannot set shading from the Shading menu. Workaround: Use text highlighting to achieve a similar effect. (.doc only)
  • Will not display the value of a FORMDROPDOWN. (.doc only)
  • Ordered lists always use a period as the separator. For example, if a list item in the Word doc looks like 1) then it will be 1. after the import.
  • For .doc, the style of the list item marker will be inferred from the text content of the list. The marker's font family and font size will match the first piece of text in the list item. The marker will be bold, italic, and/or colored if all the text in the list item has that same styling.
  • Images, Word Art, and diagrams are not supported.
  • Does not support importing a Table of Contents.
  • All underline styles show as single solid line
  • Superscript/subscripts defined by within a style are not supported (.doc only). Workaround is: Apply sub/superscript from the Font menu instead of using a style.
  • Formatting overrides that conflict with custom styles. For example, if custom style includes a Strong text format and the user manually un-bolds the text within the document, the text will show up bold per the Strong style. (.doc only)
  • Tabs default to 4 spaces, which is not guaranteed to match the spacing in the document since tabs are based on positioning in the document. It is better to use indent when aligning content.
  • Hanging indent (that is, First Line Indents) for lists is not guaranteed to line up perfectly due to the varying width of the list item markers.
  • Within lists, mixing techniques for creating bullets, lists, and indentations will often result in items not being aligned correctly and incorrect numbering of items.
  • Entering several carriage returns to create spacing will not render as extra spacing.
  • Unsupported features:
    • Changes in Text Direction
    • Double Strike Through
    • Emboss, Engrave, Shadow text
    • Text Effects
    • Emphasis Marks
    • Custom Text Spacing
    • Shadowed borders
    • Ascending diagonal cell borders