Troubleshooting guide for using BI Publisher with Oracle Policy Modeling

This topic explains some problems that might be encountered when using BI Publisher with Oracle Policy Modeling and what to do about them.

BI Publisher ribbon not visible in Microsoft Word

If you cannot see the BI Publisher Ribbon in your Microsoft Word document after you open it from Policy Modeling, it means you do not yet have the BI Publisher Add-in for Microsoft Word installed. For information on how to do this, see Download BI Publisher.

Document will not generate

Check the template size. Large file sizes (eg due to images within the document) require more memory allocation. If in doubt, remove images and re-try.

Check all fields have the correct syntax. If in doubt, delete any area that you are concerned about then re-generate the document.

If deploying to an external version of Web Determinations (ie using Build and Run), check that the document generation server is correctly configured/started (refer to installation instructions for more information). If in doubt, try to Build and Debug within OPM to determine whether it is an issue with the document template or the external configuration.

Normal text does not appear

If the text follows a conditional or entity-level region, check the previous region has the appropriate end fields.

Font does not display correctly

Check the font is a predefined font for BI Publisher. If not, you will need to define a font mapping from a base font in the RTF or PDF template to a target font to be used in the published document. More information is available in the BI Publisher documentation/forums.

Field values and/or conditional text do not appear

Check the syntax matches the recommended syntax (see BI Publisher code for Oracle Policy Modeling).

If using conditional text, check that the output value in the generated XML matches the value in the condition, including any formatting if using the formatted value.

If the text follows a conditional or entity-level region, check the previous region has the appropriate end fields.

If using an entity-level attribute:

ensure that the appropriate entity tags are in place before and after the field, and
ensure that the entity public name is unique (ie check you do not have an entity and an attribute with the same public name).

Check the font is a standard font. Some fonts are only supported by some outputs (eg Wingdings will not appear in a pdf output). More information on supported fonts is available in the BI Publisher documentation/forums.

Headings/images do not appear

If using an image, shape, text box or similar:

check whether the object is grouped (grouped objects will not appear in some outputs), and
try changing the Text Wrapping setting (depending on the context of how the image is used, some text layout options may impede the display of the image in the generated document).

See also, "Field values and/or conditional text does not appear" troubleshooting section above.

Text appears on a new line

See the BI Publisher documentation for how to include fields and conditional formatting in-line. Including the text within a table (even a 1x1 table) is a simple way to work around most line break issues (see sample OPM projects for examples).

Error when clicking on document link

If you encounter an error when clicking on the document link on the summary screen, the BI Publisher template's Conditional Region settings may have not been correctly defined (for example, if an incorrect data type has been used). If this occurs, you should open the BI Publisher template and make the appropriate adjustments (see insert conditional text for more information).