Troubleshooting Guide for Forms

This topic explains some problems that might be encountered when created and generating Intelligent Advisor forms using Analytics Publisher and what to do about them.

RTF form templates

Problems and solutions when using RTF form templates are given in the following table.

Table 1. Problems encountered when using RTF form templates
Problem Cause Solution
Publisher ribbon not visible in Microsoft Word after you open it from Policy Modeling

This could be because:

  • you do not have Analytics Publisher Desktop installed
  • the Oracle Analytics Publisher Template Builder for Word Add-in hasn't been activated
  • the version of Microsoft Word is not fully supported by the Oracle Analytics Publisher Template Builder for Word Add-in

Install Analytics Publisher Desktop. For information on how to do this, see Download Analytics Publisher.

Run Word as an administrator to activate the Oracle Analytics Publisher Template Builder for Word Add-in.

If you are still unable to make the ribbon visible, seek further information via the BI Publisher Learning Center or contact Oracle Support.
Publisher ribbon is not displaying correctly in Microsoft Word after you open it from Policy Modeling You have a version of Analytics Publisher installed that is incompatible with the version of Microsoft Office that you have installed.

Install the 32 bit version of Analytics Publisher if you are using Microsoft Office 32 bit, and the 64 bit version of Analytics Publisher if you are using Microsoft Office 64 bit.

To find out which version of Microsoft Office you are using, go to the File menu in Microsoft Word, select Account and then click About Word. The dialog will show which version you are using.
Form will not generate Large file sizes (for example, due to images within the form) require more memory allocation

Check the template size. 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 form.
Normal text does not appear The text follows a conditional or entity-level region Check the previous region has the appropriate end fields.
Font does not display correctly Fonts used when creating the form template may not be available when the form is generated during the interview For more information, see Embed TrueType fonts in generated PDF forms.
Text displays in the wrong direction (for example, left-to-right instead of right-to-left) in an RTF form The form template is not using the template locale Create a copy of the form template in the desired language. Then open the compatibilityOptions.json file in the project directory and change the "FormToRTFUseTemplateLocale" setting to true. Save the file, then close and re-open the Policy Modeling project.
Formatting a number or currency attribute using the Analytics Publisher function <?format-number: <attribute>; '<format>'?> does not use the correct decimal separator The form template is not using the template locale

Open the compatibilityOptions.json file in the project directory and change the following setting depending on your output type:

  • For RTF output, change the "FormToRTFUseTemplateLocale" setting to true.

  • For PDF output, change the "FormToPDFUseTemplateLocale" setting to true.

  • For Excel output (.xls or .xlsx), change the "FormToExcelUseTemplateLocale" setting to true.

Save the file, then close and re-open the Policy Modeling project.
A mapped-in ID field is showing the incorrect number (for example, the number has been rounded) Number values are only supported up to 12 digits of precision When mapping data, some number fields, such as ID fields, have a text field equivalent that you should use instead.
Field values and conditional text do not appear Various causes

Check the syntax matches the recommended syntax (see Analytics Publisher Code for Policy Modeling).

If using conditional text, check that the output value in the generated Extensible Markup Language (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 name is unique (that is, check you do not have an entity and an attribute with the same name).

Check that the font is supported by the output type (for example, Wingdings will not appear in a pdf output). More information on supported fonts is available in the Analytics Publisher documentation and forums.
Heading does not appear The font is unsupported by the output type (for example, Wingdings will not appear in a pdf output).

For more information on supported fonts, see the Analytics Publisher documentation and forums.
Image does not appear

This could be because the object is grouped (grouped objects will not appear in some outputs).

If using an image that is uploaded by the interview user, a blank image is used to prevent Analytics Publisher from crashing when generating the form in the following circumstances:

  • There are no uploaded image files, or
  • The first image file is corrupted, or
  • The first image file has been renamed, or
  • The first file is not an image file, or
  • The first file is not an image file type that is supported by Analytics Publisher, or
  • The form is being generated as an Excel or HTML file (these output types do not support the insertion of uploaded images).

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 form).

If using an image that is uploaded by the interview user, specify the file types that are supported for the upload group, and make sure that the form is generated as a PDF, RTF or XML document. For more information, see Insert an uploaded image into a form.
Image does not display correctly If using an image that is uploaded by the interview user and the file is an animated GIF, only the first frame might be shown. Use a static GIF instead.
Image displays at the wrong size The image is rendering at its original size

Add width and height styling to the field code to control the sizing. For example:

<fo:instream-foreign-object content-type="image/filetype" height="3 in" width="4 in"><?upload_group_control_name_uploaded_image_data?></fo:instream-foreign-object>

Text appears on a new line Text has not been formatted correctly

To format conditional text so that it appears on the same line, see Formatting of conditional text.

Including the text within a table (even a 1x1 table) is another simple way to work around most line break issues.
Error when clicking on form link in an interview The Conditional Region settings in the RTF form template may have not been correctly defined. (For example, if an incorrect data type has been used.) Open the RTF form template and make the appropriate adjustments. For more information, see Insert Conditional Text Into an RTF Form Template.

Further information on developing templates using the Oracle Analytics Publisher Template Builder for Word is available in:

PDF form templates

Problems and solutions when using PDF form templates are given in the following table.

Table 2. Problems encountered when using PDF form templates
Problem Cause Solution
PDF Form Assistant not visible PDF Form Assistant has been closed Close the PDF form and re-open it from within Policy Modeling.
Signatures and barcodes cannot be added to the template The insertion of Intelligent Advisor signatures and barcodes in PDF form templates is not supported by Analytics Publisher which is used to generate the form. None
Form does not generate when you click a form link in an interview

This could be because:

  • the PDF template contains more than one repeating field (entity-level attributes or an explanation) on a single page
  • there is no vertical space between a Start data field and an explanation node
  • there is insufficient vertical space for an explanation to appear

Modify the form template to only have one Start field and one End field per page.

Move the explanation node under the Start data field.

Modify the template to allow sufficient vertical space for the generated explanation to appear between the Start and End data fields.
Font does not display correctly Fonts used when creating the form template may not be available when the form is generated during the interview For more information, see Embed TrueType fonts in generated PDF forms
Field values do not appear Various

If using an entity-level attribute:

  • ensure that there are Start and End data fields in place before and after the entity-level attribute field, and
  • ensure that the entity name is unique (that is, check you do not have an entity and an attribute with the same name).

If the text follows an entity-level group, check the entity group has the appropriate End data field.
Number or currency attribute does not use the correct decimal separator The form template is not using the template locale

Open the compatibilityOptions.json file in the project directory and change the "FormToPDFUseTemplateLocale" setting to true. Save the file, then close and re-open the Policy Modeling project.
A mapped-in ID field is showing the incorrect number (for example, the number has been rounded) Number values are only supported up to 12 digits of precision When mapping data, some number fields, such as ID fields, have a text field equivalent that you should use instead.
Entity-level attributes or explanations are not appearing on a page Repeating fields are used In order for repeating fields (entity-level attributes or explanations) to display on a page, the page should have a tab order of Use Document Structure.
Spacing between the lines in an explanation is incorrect The distance between the Start field and the explanation node is what influences the spacing between each line in the explanation Adjust the spacing accordingly
New page is created for each entity in a repeating field Insufficient vertical space has been allowed in the PDF form template between the Start and End data fields for the generated entity instance data Modify the template to allow sufficient vertical space between the Start and End data fields for the entity group, for example, by including the End field at the bottom of the page

Further information on designing PDF form templates is available in: