For example, you can use conditional formatting to hide a rich text box unless a specific check box is selected. You can manually specify the size of a control by entering values in the Height and Width boxes. You can also refine the spacing both inside and outside the control by changing the padding, which is the amount of buffer space surrounding the control's contents, or the margins, which is the amount of space between the control's border and any surrounding text or controls on the form template.
To better align the text in a rich text box with its label, click the Align button. When aligning a rich text box, Microsoft Office InfoPath changes the existing value in the Height box to auto. This reduces the height of the rich text box so that the text inside it is better aligned with the surrounding text. InfoPath also changes padding and margin settings as appropriate. To make an explanatory note appear when users move their pointer over the control, enter the text that you want in the ScreenTip box.
Accessibility aids, such as screen review utilities that make on-screen information available as synthesized speech or a refreshable Braille display, often rely on these ScreenTips to interpret information for their users.
You can change the position of a control in the form template's overall tab order. The default tab index setting for all controls in a form template is 0, but the tab order starts with 1. That is, any control with 1 in the Tab index box will be visited first when users press the TAB key. Any control with 2 in the Tab index box will be visited second, and so on.
Any controls with 0 in the Tab index box will come last in the tab order. If you want to skip controls in the tab order, enter -1 in the Tab index box. You can type a letter or number in the Access key box to specify a keyboard shortcut. Keyboard shortcuts enable users to navigate to a control by pressing a combination of keystrokes, rather than by moving the mouse. If you choose to use keyboard shortcuts in your form template, you must communicate to users that the shortcuts exist.
Click Merge Settings to specify how data that users enter into the control should appear when several forms are combined. For example, you can choose to prefix each item from a rich text box with a particular word, or separate each item with a semicolon.
You can use the ViewContext value to identify the control in code. For example, if you know the ViewContext value, you can use that value with the ExecuteAction method of the View object to programmatically perform an editing action on the XML data that is bound to the control. Click Input Scope to specify the type of user input that is intended for the control.
This can help improve the recognition of handwriting and speech input for the control. The Browser forms tab appears only when you are designing a browser-compatible form template. It allows you to control whether data is sent to the server when users change data in the rich text box. InfoPath InfoPath More Notes: If you are designing a browser-compatible form template, certain features in the Rich Text Box Properties dialog box are not available.
Need more help? Expand your skills. Get new features first. Was this information helpful? Learn more. Asked 2 years, 3 months ago. Active 2 years, 3 months ago. Viewed times. I tried : -Uncheck Wrap text. Can anyone help me find what the problem is? Regards , Mint. Improve this question. Mint Luzulite. Mint Luzulite Mint Luzulite 53 6 6 bronze badges.
I remember when I had to output to excel with this requirement, I found the only option to be estimating the maximum required width and setting it in the template. Add a comment. Active Oldest Votes. Enter the following in the Properties dialog:. To avoid this potential security risk, you can use a template parameter value that is generated and passed into the template at runtime. For more information about template parameters, see Defining Parameters in Your Template.
It is a common requirement to print a batch of documents, such as invoices or purchase orders in a single PDF file. Because these documents are intended for different customers, each document will require that the page numbering be reset and that page totals are specific to the document. If the header and footer display fields from the data such as customer name these will have to be reset as well.
BI Publisher supports this requirement through the use of a context command. This command allows you to define elements of your report to a specific section. When the section changes, these elements are reset.
The following example demonstrates how to reset the header and footer and page numbering within an output file:. The following figure shows a sample template. The page numbers will restart, and if header or footer information is derived from the data, it will be reset as well. The columns of a cross-tab report are data dependent. At design-time you do not know how many columns will be reported, or what the appropriate column headings will be. Moreover, if the columns should break onto a second page, you need to be able to define the row label columns to repeat onto subsequent pages.
The following example shows how to design a simple cross-tab report that supports these features. From this XML we will generate a report that shows each industry and totals the sales by year as shown in the following figure:. The template to generate this report is shown in the following figure. The form field entries are shown in the subsequent table.
Note that only the first row uses the column context to determine the number of columns for the table. All remaining rows need to use the cell context to create the table cells for the column. For more information about context commands, see Using the Context Commands. The ability to construct dynamic data columns is a very powerful feature of the RTF template.
Using this feature you can design a template that will correctly render a table when the number of columns required by the data is variable. For example, you are designing a template to display columns of test scores within specific ranges. However, you do not how many ranges will have data to report. You can define a dynamic data column to split into the correct number of columns at runtime. Use the following tags to accommodate the dynamic formatting required to render the data correctly:.
Use one of these tags to define the width of the column when the width is described in the XML data. The width can be described in two ways:. An XML element stores the value of the width. Use this tag to define a multiplier for the column width. If the multiplier is not defined, the widths of the columns are calculated as a percentage of the total width of the table.
This is illustrated in the following table:. If your table columns expand horizontally across more than one page, you can define how many row heading columns you want to repeat on every page. Use the following syntax to specify the number of columns to repeat:. A template is required to display test score ranges for school exams.
Logically, you want the report to be arranged as shown in the following table:. The number of Test Score Range columns is dynamic, depending on the data. The following XML data describes these test scores.
In this case there are five columns: , , , , and Using the dynamic column tags in form fields, set up the table in two columns as shown in the following figure. The first column, "Test Score" is static.
The second column, "Column Header and Splitting" is the dynamic column. At runtime this column will split according to the data, and the header for each column will be appropriately populated. The Default Text entry and Form Field Help entry for each field are listed in the table following the figure. See Form Field Method for more information on using form fields.
The second column is the one to be split dynamically. The width you specify will be divided by the number of columns of data. In this case, there are 5 data columns. The second column will contain the dynamic "range" data. The width of the column will be divided according to the split column width. Wrapping of the data will occur if required. If the total column widths were wider than the allotted space on the page, then the table would break onto another page.
The "horizontal-break-table" tag could then be used to specify how many columns to repeat on the subsequent page. For example, a value of "1" would repeat the column "Test Score" on the subsequent page, with the continuation of the columns that did not fit on the first page.
Note: You can also use the native XSL format-number function to format numbers. Use only one of these methods. If the number format mask is specified using both methods, the data will be formatted twice, causing unexpected behavior.
The group separator and the number separator will be set at runtime based on the template locale. This is applicable for both the Oracle format mask and the MS format mask. To use the Oracle format mask or the Microsoft format mask, the numbers in your data source must be in a raw format, with no formatting applied for example: If the number has been formatted for European countries for example: 1.
This consists of an optional sign "-" followed by a sequence of zero or more decimal digits the integer , optionally followed by a fraction, and optionally followed by an exponent. For example: If you are designing a template to be translatable, using currency in the Microsoft format mask is not recommended unless you want the data reported in the same currency for all translations.
Using the MS format mask sets the currency in the template so that it cannot be updated at runtime. Instead, use the Oracle format mask. For example, LGGD99, where "L" will be replaced by the currency symbol based on the locale at runtime. To format numeric values, use Microsoft Word's field formatting features available from the Text Form Field Options dialog box. The following graphic displays an example:. Note: Subpattern boundary: A pattern contains a positive and negative subpattern, for example, " , 0.
Each subpattern has a prefix, numeric part, and suffix. The negative subpattern is optional. If absent, the positive subpattern prefixed with the localized minus sign "-" in most locales is used as the negative subpattern. That is, "0. If there is an explicit negative subpattern, it serves only to specify the negative prefix and suffix. The number of digits, minimal digits, and other characteristics are all the same as the positive pattern.
That means that " , 0. The following graphic shows an example Form Field Help Text dialog entry for the data element "empno":. Specify an abstract date format mask using Oracle's abstract date format masks. Recommended for multilingual templates. Only one method should be used. If both the Oracle and MS format masks are specified, the data will be formatted twice causing unexpected behavior.
To use the Microsoft format mask or the Oracle format mask, the date from the XML data source must be in canonical format. This format is:. The data after the "T" is optional, therefore the following date: can be formatted using either date formatting option.
Note that if you do not include the time zone offset, the time will be formatted to the UTC time. See Oracle Abstract Format Masks for the description. The detailed usage of format mask, calendar and time zone is described below. If you do not want to specify a format mask with either the MS method or the Oracle method, you can omit the mask definition and use the default format mask. See Oracle Abstract Format Masks for the definition.
To use the default option using the Microsoft method, set the Type to Date, but leave the Date format field blank in the Text Form Field Options dialog.
To use the default option using the Oracle method, do not supply a mask definition to the "format-date" function call, for example:. When you use one of these masks, the output generated will depend on the locale associated with the report. The following table lists the abstract format masks and the sample output that would be generated for US locale:. The term "calendar" refers to the calendar date displayed in the published report.
The following types are supported:. Note: The calendar type specified in the template will override the calendar type set in the profile option. The following example shows the syntax to enter in the help text field of your template:.
BI Publisher enables you to use fonts in your output that are not normally available on the server. To set up a new font for your report output, use the font to design your template on your client machine, then make it available on the server, and configure BI Publisher to access the font at runtime.
You can set the font property for the report in the BI Publisher Font Mappings page, or in the configuration file. Update the BI Publisher configuration file "fonts" section with the font name and its location on the server. For example, the new entry for a TrueType font is structured as follows:.
Now you can run your report and BI Publisher will use the font in the output as designed. For PDF output, the advanced font handling features of BI Publisher embed the external font glyphs directly into the final document. The embedded font only contains the glyphs required for the document and not the complete font definition. Therefore the document is completely self-contained, eliminating the need to have external fonts installed on the printer.
BI Publisher offers the ability to execute preprocessing on your data prior to applying a barcode font to the data in the output document. For example, you may need to calculate checksum values or start and end bits for the data before formatting them.
The solution requires that you register a barcode encoding class with BI Publisher that can then be instantiated at runtime to carry out the formatting in the template. To enable the formatting feature in your template, you must use two commands in your template. The first command registers the barcode encoding class with BI Publisher. This must be declared somewhere in the template prior to the encoding command. The second is the encoding command to identify the data to be formatted.
Use the following syntax in a form field in your template to register the barcode encoding class:. This command requires a Java class name this will carry out the encoding and a barcode vendor ID as defined by the class. This command must be placed in the template before the commands to encode the data in the template. It is the method used to navigate through an XML document. XPath is a set of syntax rules for addressing the individual pieces of an XML document.
This section contains a brief introduction to XPath principles. A node can be one of seven types:. CD is an element, and it has an attribute cattype.
The sample contains the comment My CD Listing. Text is contained within the XML document elements. A node is the most common search element you will encounter. Use a path expression to locate nodes within an XML document.
For example, the following path returns all CD elements:. Further limit your search by using square brackets. The brackets locate elements with certain child nodes or specified values. For example, the following expression locates all CDs recorded by Bob Dylan:. Use the bracket notation to leverage the attribute value in your search. Use the symbol to indicate an attribute. You can also use brackets to specify the item number to retrieve.
XPath also supports wildcards to retrieve every element contained within the specified node. You can combine statements with Boolean operators for more complex searches. The following expression retrieves all Folk and Rock CDs, thus all the elements from the sample:. The pipe is equal to the logical OR operator. For example, we can find all CDs released in or later using the following expression:.
The first character in an XPath expression determines the point at which it should start in the XML tree. No slash indicates a relative reference. An example of a relative reference is:. This statement begins the search at the current reference point.
That means if the example occurred within a group of statements the reference point left by the previous statement would be utilized. To select current and parent elements, XPath recognizes the dot notation commonly used to navigate directories. Use a single period. For example, to retrieve all child nodes of the parent of the current node, use:. XPath is an extremely powerful standard when combined with RTF templates allowing you to use conditional formatting and filtering in your template.
If your XML data contains namespaces, you must declare them in the template prior to referencing the namespace in a placeholder. Declare the namespace in the template using either the basic RTF method or in a form field. Enter the following syntax:.
The placement of these instructions within the converted stylesheet determines the behavior of your template. However, sometimes you need to define the context of the instructions differently to create a specific behavior. To support this requirement, BI Publisher provides a set of context commands that allow you to define the context or placement of the processing instructions.
For example, using context commands, you can:. Specify a for-each loop to repeat either the current data or the complete section to create new headers and footers and restart the page numbering. To specify a context for a processing command using the simplified BI Publisher syntax, simply add context to the syntax instruction. By adding the section context, you can reset the header and footer and page numbering.
The value of the context determines where your code is placed. If you are using form fields, use either option. Use this element to call a named template to be inserted into or applied to the current template. For example, use this feature to render a table multiple times. Assigns the value "red" to the "color" variable. The variable can then be referenced in the template.
Note: An imported style sheet has lower precedence than the importing style sheet. Both are used to define the root element of the style sheet. Note: An included style sheet has the same precedence as the including style sheet. Note: The namespace must be declared in the template. See Namespace Support. The first pattern will be used for positive numbers and the second for negative numbers. All rights reserved.
Contents Previous Top of Page Next. Book List. Contact Us. Establishes the condition for the check box. If the value for the population element is greater than 1,,, the check box will display as checked.
The drop-down form field for the continentIndex element. See the preceding description for its contents. At runtime, the value of the XML element is replaced with the value it is cross-referenced to in the drop-down form field.
Note that this syntax uses an XPath expression to navigate back to the "items" level of the XML to test the attribute.
This field is the placeholder for the debit element from the XML file. Because we want to total this field by page, the page total declaration syntax is added. The field defined to hold the total for the debit element is dt. This field is the placeholder for the credit element from the XML file.
The field defined to hold the total for the credit element is ct. This element has two properties: name - name of the variable you declared for the field. This is an optional property that takes one of the following values: first - the contents appear only on the first page last - the contents appear only on the last page exceptfirst - contents appear on all pages except first exceptlast - contents appear on all pages except last everytime - default contents appear on every page In this example, display-condition is set to "exceptfirst" to prevent the value from appearing on the first page where the value would be zero.
Shows the value on the page. It has the following two properties: name - the name of the field to show. In this case, "InvAmt". This property is mandatory. Retrieves the RTotalVar value for display. Defines the first column as a header that should repeat if the table breaks across pages. Each explicitly set 0 will appear, if no other number occupies the position.
Example: Format mask: When set to , only the incoming data is displayed. Example: Format mask:. Data: 1. Determines the position of the decimal separator. The decimal separator symbol used will be determined at runtime based on template locale.
For example: Format mask: , 0. Determines the placement of the grouping separator. The grouping separator symbol used will be determined at runtime based on template locale. Separates mantissa and exponent in a scientific notation.
Example: 0. E-0 plus sign not shown for positive numbers. Returns value with the specified number of digits with a leading space if positive or a leading minus if negative. Leading zeros are blank, except for a zero value, which returns a zero for the integer part of the fixed-point number. Determines the placement of the decimal separator. For example: Format mask: 9GD99 Data: Determines the placement of the grouping thousands separator.
The year without the century. If the year without the century is less than 10, the year is displayed with a leading zero. The period or era. This pattern is ignored if the date to be formatted does not have an associated period or era string.
Displays the time zone offset for the system's current time zone in whole hours only. This element can be used for formatting only.
Fractional seconds. Use the numbers 1 to 9 after FF to specify the number of digits in the fractional second portion of the datetime value returned. Round year. Accepts either 4-digit or 2-digit input. If 2-digit, provides the same return as RR. If you don't want this functionality, then simply enter the 4-digit year. Daylight savings information. The TZD value is an abbreviated time zone string with daylight savings information. It must correspond to the region specified in TZR. Time zone region information.
The value must be one of the time zone regions supported in the database. Week of year where week 1 starts on the first day of the year and continues to the seventh day of the year. The statement affects the whole section including the header and footer. For example, a for-each section context command creates a new section for each occurrence - with restarted page numbering and header and footer.
See Batch Reports for an example of this usage. The statement will affect the whole column of a table. This context is typically used to show and hide table columns depending on the data.
See Column Formatting for an example. The statement will affect the cell of a table. This is often used together with column in cross-tab tables to create a dynamic number of columns. See Cross-Tab Support for an example. The statement will affect multiple complete fo:blocks RTF paragraphs. This context is typically used for if and for-each statements. It can also be used to apply formatting to a paragraph or a table cell.
See Cell Highlighting for an example. The context will become the single statement inside an fo:inline block.
0コメント