This chapter contains the following topics:
Section 3.2, "Understanding Form Control Design-Time Considerations"
Section 3.5, "Associating a Data Item Description with a Field"
Section 3.7, "Setting the Tab Sequence of Controls on a Form"
Use form controls to provide specific functions within an application such as these:
Insert field controls on forms to display data, enter data, calculate data, store data permanently or temporarily, or pass data between fields and forms.
Place check boxes on forms to provide for multiple selections, or radio buttons to indicate mutually exclusive selections.
Each form includes specific default controls, depending on the type of form that you are creating. However, you might need to add additional controls when you design the form. Choose from standard Windows graphical controls as well as JD Edwards EnterpriseOne custom controls.
All form controls are locked by default, this is seen by a "NO" cursor when mouse is hovered over the controls. The controls can be unlocked by clicking on the Form menu and selecting Lock Form Controls. This option will unlock the selected form for modifying controls. An information message box will display when you launch an application to indicate if the form is in lock mode. (Release 9.1 Update 2)
When controls are hidden they are by default not viewable in FDA. To view the hidden controls click the Show Hidden Controls in the Form menu. Hidden controls will be displayed in blue italic text. (Release 9.1 Update 2)
This table lists the controls, the forms on which they can be used, and their purpose:
Control | Valid Form Types | Description |
---|---|---|
Calendar | All Form Types | Use a calendar control to provide standard calendar capabilities to users which can be tied to some system events. |
Check Box | All Form Types | Use one or more check boxes to provide the user with options that are not mutually exclusive. |
Combo Box | All Form Types | Use combo box to provide user a drop down list of items. |
Edit | All Form Types | Use edit fields to display data and to enable users to enter information for a specific instance of a data item. |
Grid control | Browse Portlet
Edit Portlet Find/Browse (default control) Header Detail (default control) Headerless Detail (default control) Power Browse (default control) Power Edit Reusable Browse Subform Reusable Edit Subform Search & Select (default control) Wizard (page only) |
Use grids to display data and to enable users to enter information. Unlike an edit control, grid controls can show multiple data items and multiple table rows at once. |
Group | All Form Types | Use this control to group other controls together visually. |
Image | All Form Types | Use image controls to place a static or animated graphic on a form. |
Media Object | All Form Types | Use media object controls to enable users to enter rich text and attach files to a form. |
Parent Child | Browse Portlet
Edit Portlet Reusable Browse Subform Reusable Edit Subform Parent/Child Browse (default control) Power Edit Wizard (page only) |
Use parent child controls to present a hierarchical grid view or a tree view. |
Push Button | All Form Types | Use a push button to initiate an action or a set of actions. |
Radio Button | All Form Types | Use radio buttons to provide the user with sets of options. The radio buttons in each set are mutually exclusive. |
Saved Query Control | Browse Portlet
Edit Portlet Find/Browse Header Detail Headerless Detail Parent/Child Browse Power Edit Power Browse Reusable Browse Subform Reusable Edit Subform Search & Select Wizard (page only) |
Use a saved query control to enable users to create and save data queries and to provide them with a set of queries from which to choose. |
Static Text | All Form Types | Use static text as labels on the form. |
Subform | Browse Portlet
Edit Portlet Reusable Browse Subform Reusable Edit Subform Power Edit Power Browse Wizard (Wizard control only) |
Use subforms to provide one BV and a group of controls associated with it. Place multiple subforms on a power form to provide multiple, collective data views on one form. The subform created this way will not be reusable by other forms or applications. |
Subform Alias | Browse Portlet
Edit Portlet Reusable Browse Subform Reusable Edit Subform Power Browse Power Edit Wizard |
Use a subform alias to place a reusable subform on the form. A reusable subform is a subform with a data view and a set of controls associated with it. |
Tab Control | All Form Types | Use tab controls to present a large number of controls on one or more tab pages. Power forms can have any number of tab controls, but all other forms are restricted to one. You cannot use tab control on a subform that is a tab page. |
Tab Page | Only apply to tab controls | Use a tab page control to define one page in a tab control. |
Text Block Control | All Form Types | Use text block controls to display free-form HTML text and plain text elements. |
Text Search Control | Browse Portlet
Edit Portlet Find/Browse Header Detail Headerless Detail Parent/Child Browse Power Edit Power Browse Reusable Browse Subform Reusable Edit Subform Search & Select Wizard (page only) |
Use text search controls to enable full text searches against a generated index (as opposed to searching against the underlying BV). |
Tree Control | All Form Types | Use tree controls to display a tree structure. |
Wizard | Wizard (default control) | Use wizard controls to create self-directed applications. This specialized control is available only on wizard forms. |
Some control property values are common to all controls, although many are shared by just a few. This table lists the property values for all control types. The descriptions given in some cases are for general use only. If a particular property significantly impacts a given form type, then those impacts are discussed in detail in the chapter devoted to that control. In addition to the standard controls you can add to a form using the Insert menu in FDA, this table includes grid columns which have their own property values separate from the grid itself and the standard menu properties such as OK, Save, Cancel, and so forth because they can act as push button controls. They are referred to as buttons in this table; for example, Select button.
This section provides an overview of the Chart Control.
Use the Chart Control to set properties on a visible chart. These charts help plant managers quickly quantify the state of operations at a plant. FDA provides a set of system functions specific for the Chart Control. The chart Control uses the following files:
Data XML
The data XML file determines the information that a graph displays. The Chart Control uses a data XML file that you create to call system functions. You can create the data XML file using any editor, such as business functions or event rules. Data XML is required for the Chart Control. See Appendix: A for examples of data XML.
Graph XML
The graph XML file determines how the information that a graph displays is formatted, i.e. in a bar or pie format. JD Edwards provides default templates of graph xml files for you to use to design your charts. You can change or modify the information in the graph XML to change the appearance of the chart. The graph XML file is optional for the Chart Control. If the graph XML file is not specified for the Chart Control, then the graph will be displayed in the format specified by the graph name attribute in the data XML file. See Appendix: B for examples of graph XML.
FDA enables you to create the following chart types:
bar_basic
combo_basic
combo_markers
ine_basic
pie_basic
pie_onetime
stacked_bar_basic
stacked_bar_ontime
To quickly view how your chart will look, you can use the Direct XML Graph Access application located at the following
URL: http://<web server host>:<web server port>/jde/GraphPrototype.maf
The Direct XML Graph Access contains a sample of every chart JD Edwards EnterpriseOne provides. It contains an example DTD and data XML for each chart that you can edit to see immediately how your changes will impact the chart. You can also enter your own DTD and data XML to review a chart you have created.
You must use your EnterpriseOne login credentials to access the Direct XML Graph Access application.
The following table contains the system functions EnterpriseOne created for the charting control.
System Function | Description |
---|---|
Draw Chart(Chart Control) | Call this system function to render a chart. Assume its DataXML is correctly populated. After calling other system functions to set chart properties, be sure to call this system function to show the new result. Otherwise, the new properties will not be shown on the form. |
Set Data XML(Chart Control, data) | Call this system function to set DataXML for the chart. Runtime will automatically read graphName from DataXML and set it to GraphName on this chart. The data XML is required to be set for a chart control. Otherwise an error is displayed. |
Set Graph XML(Chart Control, graphXML) | Call this system function to set customized graphXML for the chart. If this function is called, its graphXML will be used instead of graphName from the DataXML. |
Set Graph Template(Chart Control, graphTemplate) | Call this system function to set graphName for the chart. Runtime will read the checked in graph.xml based on the graphName. |
Set Title(Chart Control, title) | Call this system function to set the title for this chart. |
Set Title Visible(Chart Control, true/false) | Call this system function to make the title visible or invisible for this chart. |
Set Footnote(Chart Control, footnote) | Call this system function to set a footnote for the chart. |
Set Footnote Visible(Chart Control, true/false) | Call this system function to make a footnote visible or invisible for the chart. |
Set Legend Orientation(Chart Control, Orientation) | Call this system function to set the orientation for this chart. Valid values for Orientation are <Vertical> or <Horizontal>. |
Set Legend Position(Chart Control, position) | Call this system function to set the position for the chart. Valid values for Position are <Top>,<Left>,<Right>, or <Bottom>. |
Set Legend Visible(Chart Control, true/false) | Call this system function to make the legend visible or invisible for the chart. |
Reset(Chart Control) | Call this system function to reset all properties, but leave DataXML,graphXML and graphName unchanged. |
Get Last Chart Click Event(rowIndex, columnIndex) | Call this system function at the beginning of the "Chart is Clicked" FDA event. Tools will return the actual row and column index of the element clicked in the output ER variables. Application development can then use these ER variable values to execute any subsequent logic in the "Chart is Clicked" FDA event. |
Turn Off Chart Clicked Event(Chart Control) | Call this system function to disable clickable events on this chart. The default is to have clickable events be disabled. |
Turn On Chart Clicked Event(Chart Control) | Call this system function to enable clickable events on this chart. The default is to have clickable events be disabled. |
The following table contains the C code system functions that applications call within C business functions to set chart properties in the web client.
System Functions | Description |
---|---|
JDE_SetDataXML(lpBhvrCom, int chartId, JCHAR * dataXml) | Call this system function to set DataXML for this chart. |
JDE_SetGraphXML(lpBhvrCom, int chartId, JCHAR * graphXml) | Call this system function to set customized graphXML for this chart. |
JDE_DrawChart(lpBhvrCom, int chartId) | Call this system function to render a chart. Assume its DataXML is correctly populated. to show the new result. Otherwise, the new properties won't be shown on the form. |
C side system functions do not exist for the title, footnote, legend, and chart click properties.
This section contains example data XML for each of the chart type provided in EnterpriseOne. You can modify the code in these data XMLs to alter what information is displayed on the chart.
The graph name attribute in the data XMLs below relates directly to the graph XML types in section Example Graph XMLs. All of the graph types share a common DTD, which is described in section Example Graph DTD.
bar_basic.xml
<Graph graphName="bar_basic"> <O1Title text="Week Ending" visible="true" /> <Y1Title text="Cost Variance (USD)" visible="true" /> <LocalRelationalData> <Row columnKey="9/1/05" rowKey="Actual Variance" dataValue="1504" /> <Row columnKey="9/8/05" rowKey="Actual Variance" dataValue="980" /> <Row columnKey="9/15/05" rowKey="Actual Variance" dataValue="-675" /> <Row columnKey="9/22/05" rowKey="Actual Variance" dataValue="784" /> <Row columnKey="9/29/05" rowKey="Actual Variance" dataValue="0" /> <Row columnKey="9/1/06" rowKey="Actual Variance" dataValue="1504" /> <Row columnKey="9/8/06" rowKey="Actual Variance" dataValue="980" /> <Row columnKey="9/15/06" rowKey="Actual Variance" dataValue="-675" /> <Row columnKey="9/22/06" rowKey="Actual Variance" dataValue="784" /> <Row columnKey="9/29/06" rowKey="Actual Variance" dataValue="0" /> </LocalRelationalData> </Graph>
combo_basic
<Graph graphName="combo_basic"> <O1Title text="Week Ending" visible="true" /> <Y1Title text="Days" visible="true" /> <LocalRelationalData> <Row columnKey="1-Sept 05" rowKey="Actual DSI" dataValue="38" /> <Row columnKey="8-Sept 05" rowKey="Actual DSI" dataValue="25" /> <Row columnKey="15-Sept 05" rowKey="Actual DSI" dataValue="24" /> <Row columnKey="22-Sept 05" rowKey="Actual DSI" dataValue="27" /> <Row columnKey="1-Sept 05" rowKey="Target DSI" dataValue="10" /> <Row columnKey="8-Sept 05" rowKey="Target DSI" dataValue="10" /> <Row columnKey="15-Sept 05" rowKey="Target DSI" dataValue="10" /> <Row columnKey="22-Sept 05" rowKey="Target DSI" dataValue="10" /> </Local⇒ RelationalData> </Graph>
combo_markers.xml
<Graph graphName="combo_markers"> <O1Title text="Week Ending" visible="true" /> <Y1Title text="Days" visible="true" /> <LocalRelationalData> <Row columnKey="1-Sept 05" rowKey="Actual DSI" dataValue="38" /> <Row columnKey="8-Sept 05" rowKey="Actual DSI" dataValue="25" /> <Row columnKey="15-Sept 05" rowKey="Actual DSI" dataValue="24" /> <Row columnKey="22-Sept 05" rowKey="Actual DSI" dataValue="27" /> LocalRelationalData> </Graph>
line_basic.xml
<Graph graphName="line_basic"> <O1Title text="Week Ending" visible="true" /> <Y1Title text="Cost Variance (USD)" visible="true" /> <LocalRelationalData> <Row columnKey="9/1/05" rowKey="Actual Variance" dataValue="1504" /> <Row columnKey="9/8/05" rowKey="Actual Variance" dataValue="980" /> <Row columnKey="9/15/05" rowKey="Actual Variance" dataValue="-675" /> <Row columnKey="9/22/05" rowKey="Actual Variance" dataValue="784" /> <Row columnKey="9/29/05" rowKey="Actual Variance" dataValue="0" /> <Row columnKey="9/1/06" rowKey="Actual Variance" dataValue="1504" /> <Row columnKey="9/8/06" rowKey="Actual Variance" dataValue="980" /> <Row columnKey="9/15/06" rowKey="Actual Variance" dataValue="-675" /> <Row columnKey="9/22/06" rowKey="Actual Variance" dataValue="784" /> <Row columnKey="9/29/06" rowKey="Actual Variance" dataValue="0" /> </LocalRelationalData> </Graph>
pie_basic.xml
<Graph graphName="pie_basic"> <LocalRelationalData> <Row columnKey="January 2005" rowKey="On Time" dataValue=".11" /> <Row columnKey="January 2005" rowKey="Early" dataValue=".21" /> <Row columnKey="January 2005" rowKey="Late" dataValue=".05" /> <Row columnKey="January 2005" rowKey="Past" dataValue=".12" /> <Row columnKey="January 2005" rowKey="History" dataValue=".25" /> <Row columnKey="January 2005" rowKey="Now" dataValue=".03" /> <Row columnKey="January 2005" rowKey="Then" dataValue=".14" /> <Row columnKey="January 2005" rowKey="When" dataValue=".09" /> </LocalRelationalData> </Graph>
pie_ontime.xml
<Graph graphName="pie_ontime"> <LocalRelationalData> <Row columnKey="January 2005" rowKey="On Time" dataValue=".11" /> <Row columnKey="January 2005" rowKey="Early" dataValue=".21" /> <Row columnKey="January 2005" rowKey="Late" dataValue=".05" /> </LocalRelationalData> </Graph>
stacked_bar_basic.xml
<Graph graphName="stacked_bar_basic"> <O1Title text="Week Ending" visible="true" /> <Y1Title text="On Time Production" visible="true" /> <LocalRelationalData> <Row columnKey="9/1/05" rowKey="On Time" dataValue="95" /> <Row columnKey="9/8/05" rowKey="On Time" dataValue="8" /> <Row columnKey="9/15/05" rowKey="On Time" dataValue="9.2" /> <Row columnKey="9/22/05" rowKey="On Time" dataValue="70" /> <Row columnKey="9/1/05" rowKey="Early" dataValue="1" /> <Row columnKey="9/8/05" rowKey="Early" dataValue="10" /> <Row columnKey="9/15/05" rowKey="Early" dataValue="40" /> <Row columnKey="9/22/05" rowKey="Early" dataValue="18" /> <Row columnKey="9/1/05" rowKey="Late" dataValue="0" /> <Row columnKey="9/8/05" rowKey="Late" dataValue="15" /> <Row columnKey="9/15/05" rowKey="Late" dataValue="4" /> <Row columnKey="9/22/05" rowKey="Late" dataValue="50" /> </LocalRelationalData> </Graph>
stacked_bar_ontime.xml
<Graph graphName="stacked_bar_ontime"> <O1Title text="Week Ending" visible="true" /> <Y1ReferenceLine> <ReferenceLine index="0" visible="true" text="Goal" value="95.0" /> </Y1ReferenceLine> <Y1Title text="On Time Production" visible="true" /> <LocalRelationalData> <Row columnKey="9/1/05" rowKey="On Time" dataValue=".90" /> <Row columnKey="9/8/05" rowKey="On Time" dataValue=".85" /> <Row columnKey="9/15/05" rowKey="On Time" dataValue=".92" /> <Row columnKey="9/22/05" rowKey="On Time" dataValue=".72" /> <Row columnKey="9/1/05" rowKey="Early" dataValue=".10" /> <Row columnKey="9/8/05" rowKey="Early" dataValue=".10" /> <Row columnKey="9/15/05" rowKey="Early" dataValue=".04" /> <Row columnKey="9/22/05" rowKey="Early" dataValue=".18" /> <Row columnKey="9/1/05" rowKey="Late" dataValue="0" /> <Row columnKey="9/8/05" rowKey="Late" dataValue=".05" /> <Row columnKey="9/15/05" rowKey="Late" dataValue=".04" /> <Row columnKey="9/22/05" rowKey="Late" dataValue=".10" /> </LocalRelationalData> </Graph>
This section contains example graph XML for each of the chart type provided in EnterpriseOne. You can modify the code in these graph XMLs to alter how the chart displays information.
bar_basic.xml
<?xml version="1.0" ?> <Graph version="3.2.0.22" autoLayout="AL_ALWAYS" markerTooltipType="MTT_VALUES"⇒ graphicAntialiasing="true" textAntialiasing="true" seriesEffect="SE_AUTO_⇒ GRADIENT" frameSizeAutomatic="false"> <Background fillColor="#f1f6f0" /> <Footnote horizontalAlignment="RIGHT"> <GraphFont name="SansSerif" size="9" bold="false" italic="false" underline="false"⇒ /> </Footnote> <LegendArea visible="true" automaticPlacement="AP_NEVER" position="LAP_TOP" fill⇒ Color="#ffffff" /> <LegendText horizontalAlignment="LEFT"> <GraphFont name="SansSerif" size="9" bold="false" italic="false" underline="false"⇒ /> </LegendText> <O1TickLabel textRotation="TR_HORIZ" horizontalAlignment="RIGHT" tickLabel⇒ Staggered="false" tickLabelSkipMode="TLS_AUTOMATIC" tickLabelSkipCount="0" tick⇒ LabelSkipFirst="0" automaticRotation="AR_HORIZ_ROTATE_270"> <GraphFont name="SansSerif" size="9" bold="false" italic="false" underline="false"⇒ /> </O1TickLabel> <O1Title> <GraphFont name="SansSerif" size="11" bold="true" italic="false" underline="false"⇒ /> </O1Title> <SeriesItems defaultColor="" /> <X1Title wordWrapEnabled="false" /> <Y1MajorTick visible="true" /> <Y1TickLabel horizontalAlignment="RIGHT"> <GraphFont name="SansSerif" size="9" bold="false" italic="false" underline="false"⇒ /> </Y1TickLabel> <Y1Title> <GraphFont name="SansSerif" size="11" bold="true" italic="false" underline="false"⇒ /> </Y1Title> <Y2TickLabel horizontalAlignment="RIGHT" /> <Y2Title wordWrapEnabled="false" /> <Y1ReferenceLine> <ReferenceLine index="0" lineWidth="2" displayedInLegend="true" lineColor=⇒ "#ff0000" /> </Y1ReferenceLine> </Graph>
combo_basic.xml
<?xml version="1.0" ?> <Graph version="3.2.0.22" seriesTooltipLabelType="TLT_NONE" groupTooltipLabelType=⇒ "TLT_NONE" markerTooltipType="MTT_VALUES" markerDisplayed="true" markerShape⇒ InLegend="true" graphicAntialiasing="true" textAntialiasing="true" seriesEffect=⇒ "SE_AUTO_GRADIENT" frameSizeAutomatic="false"> <Background fillColor="#f1f6f0" /> <Footnote horizontalAlignment="RIGHT"> <GraphFont name="SansSerif" size="9" bold="false" italic="false" underline="false"⇒ /> </Footnote> <LegendArea visible="true" automaticPlacement="AP_NEVER" position="LAP_TOP" fill⇒ Color="#ffffff" /> <LegendText horizontalAlignment="LEFT"> <GraphFont name="SansSerif" size="9" bold="false" italic="false" underline="false"⇒ /> </LegendText> <O1TickLabel textRotation="TR_HORIZ" tickLabelSkipMode="TLS_AUTOMATIC" tickLabel⇒ SkipCount="0" tickLabelSkipFirst="0" automaticRotation="AR_HORIZ_ROTATE_270"> <GraphFont name="SansSerif" size="9" bold="false" italic="false" underline="false"⇒ /> </O1TickLabel> <O1Title> <GraphFont name="SansSerif" size="11" bold="true" italic="false" underline="false"⇒ /> </O1Title> <SeriesItems defaultMarkerShape="MS_NONE" defaultFitlineType="FT_NONE"> <Series id="0" markerType="MT_BAR" /> <Series id="1" markerType="MT_MARKER" markerShape="MS_DIAMOND" lineWidth="2" color=⇒ ⇒ ⇒ ⇒ ⇒ ⇒ ⇒ ⇒ ⇒ ⇒ ⇒ "#ff0000" /> <Series id="2" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="3" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="4" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="5" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="6" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="7" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="8" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="9" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="10" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="11" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="12" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="13" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="14" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="15" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="16" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="17" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="18" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="19" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="20" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="21" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="22" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="23" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="24" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="25" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="26" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="27" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="28" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="29" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> </SeriesItems> <Y1MajorTick visible="true" /> <Y1TickLabel> <GraphFont name="SansSerif" size="9" bold="false" italic="false" underline="false"⇒ /> </Y1TickLabel> <Y1Title> <GraphFont name="SansSerif" size="11" bold="true" italic="false" underline="false"⇒ /> </Y1Title> <Y2MajorTick visible="true" /> <Y1ReferenceLine> <ReferenceLine index="0" lineWidth="2" lineColor="#ff0000" displayedInLegend=⇒ "false" /> </Y1ReferenceLine> </Graph>
combo_markers.xml
<?xml version="1.0" ?> <Graph version="3.2.0.22" seriesTooltipLabelType="TLT_NONE" groupTooltipLabelType=⇒ "TLT_NONE" markerTooltipType="MTT_VALUES" markerDisplayed="true" markerShape⇒ InLegend="true" graphicAntialiasing="true" textAntialiasing="true" seriesEffect=⇒ "SE_AUTO_GRADIENT" frameSizeAutomatic="false"> <Background fillColor="#f1f6f0" /> <Footnote horizontalAlignment="RIGHT"> <GraphFont name="SansSerif" size="9" bold="false" italic="false" underline="false"⇒ /> </Footnote> <LegendArea visible="true" automaticPlacement="AP_NEVER" position="LAP_TOP" fill⇒ Color="#ffffff"/> <LegendText horizontalAlignment="LEFT"> <GraphFont name="SansSerif" size="9" bold="false" italic="false" underline="false"⇒ /> </LegendText> <O1TickLabel textRotation="TR_HORIZ" tickLabelSkipMode="TLS_AUTOMATIC" tickLabel⇒ SkipCount="0" tickLabelSkipFirst="0" automaticRotation="AR_HORIZ_ROTATE_270"> <GraphFont name="SansSerif" size="9" bold="false" italic="false" underline="false"⇒ /> </O1TickLabel> <O1Title> <GraphFont name="SansSerif" size="11" bold="true" italic="false" underline="false"⇒ /> </O1Title> <SeriesItems defaultMarkerShape="MS_NONE" defaultFitlineType="FT_NONE"> <Series id="0" markerType="MT_BAR" /> <Series id="1" markerType="MT_MARKER" markerShape="MS_DIAMOND" lineWidth="2" color=⇒ ⇒ ⇒ ⇒ ⇒ ⇒ ⇒ ⇒ ⇒ ⇒ ⇒ "#ff0000" /> <Series id="2" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="3" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="4" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="5" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="6" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="7" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="8" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="9" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="10" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="11" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="12" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="13" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="14" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="15" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="16" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="17" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="18" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="19" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="20" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="21" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="22" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="23" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="24" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="25" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="26" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="27" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="28" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> <Series id="29" markerType="MT_MARKER" markerShape="MS_DIAMOND" /> </SeriesItems> <Y1MajorTick visible="true" /> <Y1TickLabel> <GraphFont name="SansSerif" size="9" bold="false" italic="false" underline="false"⇒ / </Y1TickLabel> <Y1Title> <GraphFont name="SansSerif" size="11" bold="true" italic="false" underline="false"⇒ /> </Y1Title> <Y2MajorTick visible="true" /> <Y1ReferenceLine> <ReferenceLine index="0" lineWidth="2" lineColor="#ff0000" displayedInLegend=⇒ "false" /> </Y1ReferenceLine> </Graph>
line_basic.xml
<?xml version="1.0" ?> <Graph version="3.2.0.22" graphType="LINE_VERT_ABS" depthAngle="0" legendScrollbar⇒ Presence="SP_NEVER" legendSeriesCount="0" graphicAntialiasing="true" text⇒ Antialiasing="true" markerShapeInLegend="true" frameSizeAutomatic="false"> <Background fillColor="#f1f6f0" /> <Footnote horizontalAlignment="RIGHT"> <GraphFont name="SansSerif" size="9" bold="false" italic="false" underline="false"⇒ /> </Footnote> <LegendArea visible="true" automaticPlacement="AP_NEVER" position="LAP_TOP" fill⇒ Color="#ffffff"/> <LegendText horizontalAlignment="LEFT"> <GraphFont name="SansSerif" size="9" bold="false" italic="false" underline="false"⇒ /> </LegendText> <O1TickLabel textRotation="TR_HORIZ" tickLabelSkipMode="TLS_AUTOMATIC" tickLabel⇒ SkipCount="0" tickLabelSkipFirst="0" automaticRotation="AR_HORIZ_ROTATE_270"> <GraphFont name="SansSerif" size="9" bold="false" italic="false" underline="false"⇒ /> </O1TickLabel> <O1Title> <GraphFont name="SansSerif" size="11" bold="true" italic="false" underline="false"⇒ /> </O1Title> <Y1MajorTick visible="true" /> <Y1TickLabel> <GraphFont name="SansSerif" size="9" bold="false" italic="false" underline="false"⇒ /> </Y1TickLabel> <Y1Title> <GraphFont name="SansSerif" size="11" bold="true" italic="false" underline="false"⇒ /> </Y1Title> <Y2MajorTick visible="true" /> </Graph>
pie_basic.xml
<?xml version="1.0" ?> <Graph version="3.2.0.22" autoLayout="AL_ALWAYS" depthAngle="50" depthRadius="0"⇒ pieDepth="0" groupTooltipLabelType="TLT_NONE" graphicAntialiasing="true" text⇒ Antialiasing="true" pieTilt="0" seriesEffect="SE_AUTO_GRADIENT" graphType="PIE"> <Background fillColor="#f1f6f0" /> <Footnote horizontalAlignment="RIGHT"> <GraphFont name="SansSerif" size="9" bold="false" italic="false" underline="false"⇒ /> </Footnote> <LegendArea visible="false" /> <LegendText horizontalAlignment="CENTER" /> <O1TickLabel textRotation="TR_HORIZ" tickLabelSkipMode="TLS_NOSKIP" automatic⇒ Rotation="AR_NO_ROTATE" /> <O1Title wordWrapEnabled="false" /> <PlotArea fillColor="#f1f6f0" /> <PieLabel> <GraphFont name="SansSerif" size="11" bold="true" italic="false" underline="false"⇒ /> </PieLabel> <Slice labelPosition="LP_OUTSIDE_WITH_FEELER" /> <SliceLabel textType="LD_TEXT_PERCENT"> <GraphFont name="SansSerif" size="9" bold="false" italic="false" underline="false"⇒ /> </SliceLabel> <X1Title wordWrapEnabled="false" /> <Y1TickLabel horizontalAlignment="RIGHT" /> <Y1Title wordWrapEnabled="false" /> <Y2TickLabel horizontalAlignment="RIGHT" /> <Y2Title wordWrapEnabled="false" /> </Graph>
pie_onetime.xml
<?xml version="1.0" ?> <Graph version="3.2.0.22" autoLayout="AL_ALWAYS" depthAngle="50" depthRadius="0"⇒ pieDepth="0" groupTooltipLabelType="TLT_NONE" graphicAntialiasing="true" text⇒ Antialiasing="true" pieTilt="0" seriesEffect="SE_AUTO_GRADIENT" graphType="PIE"> <Background fillColor="#f1f6f0" /> <Footnote horizontalAlignment="RIGHT"> <GraphFont name="SansSerif" size="9" bold="false" italic="false" underline="false"⇒ /> </Footnote> <LegendArea visible="false" /> <LegendText horizontalAlignment="CENTER" /> <O1TickLabel textRotation="TR_HORIZ" tickLabelSkipMode="TLS_NOSKIP" automatic⇒ Rotation="AR_NO_ROTATE" /> <O1Title wordWrapEnabled="false" /> <PlotArea fillColor="#f1f6f0" /> <PieLabel> <GraphFont name="SansSerif" size="11" bold="true" italic="false" underline="false"⇒ /> </PieLabel> <SeriesItems> <Series id="0" color="#336699" /> <Series id="1" color="#ffff00" /> <Series id="2" color="#ff0000" /> </SeriesItems> <Slice labelPosition="LP_OUTSIDE_WITH_FEELER" /> <SliceLabel textType="LD_TEXT_PERCENT"> <GraphFont name="SansSerif" size="9" bold="false" italic="false" underline="false"⇒ /> </SliceLabel> <X1Title wordWrapEnabled="false" /> <Y1TickLabel horizontalAlignment="RIGHT" /> <Y1Title wordWrapEnabled="false" /> <Y2TickLabel horizontalAlignment="RIGHT" /> <Y2Title wordWrapEnabled="false" /> </Graph>
stacked_bar_basic.xml
<?xml version="1.0" ?> <Graph version="3.2.0.22" seriesTooltipLabelType="TLT_NONE" groupTooltipLabelType=⇒ "TLT_NONE" markerTooltipType="MTT_VALUES" graphicAntialiasing="true" text⇒ Antialiasing="true" seriesEffect="SE_AUTO_GRADIENT" graphType="BAR_VERT_STACK"> <Background fillColor="#f1f6f0" /> <Footnote horizontalAlignment="RIGHT"> <GraphFont name="SansSerif" size="9" bold="false" italic="false" underline="false"⇒ /> </Footnote> <LegendArea automaticPlacement="AP_NEVER" position="LAP_TOP" fillColor="#ffffff" ⇒ /> <LegendText horizontalAlignment="LEFT"> <GraphFont name="SansSerif" size="9" bold="false" italic="false" underline="false"⇒ /> </LegendText> <O1TickLabel textRotation="TR_HORIZ" tickLabelSkipMode="TLS_AUTOMATIC" tickLabel⇒ SkipCount="0" tickLabelSkipFirst="0" automaticRotation="AR_HORIZ_ROTATE_270"> <GraphFont name="SansSerif" size="9" bold="false" italic="false" underline="false"⇒ /> </O1TickLabel> <O1Title> <GraphFont name="SansSerif" size="11" bold="true" italic="false" underline="false"⇒ /> </O1Title> <Y1ReferenceLine> <ReferenceLine index="0" lineWidth="2" lineColor="#ff0000" displayedInLegend=⇒ "true" /> </Y1ReferenceLine> <Y1TickLabel> <GraphFont name="SansSerif" size="9" bold="false" italic="false" underline="false"⇒ /> </Y1TickLabel> <Y1Title> <GraphFont name="SansSerif" size="11" bold="true" italic="false" underline="false"⇒ /> </Y1Title> </Graph>
stacked_bar_ontime.xml
<?xml version="1.0" ?> <Graph version="3.2.0.22" seriesTooltipLabelType="TLT_NONE" groupTooltipLabelType=⇒ "TLT_NONE" markerTooltipType="MTT_PERCENT_VAL" graphicAntialiasing="true"⇒ textAntialiasing="true" seriesEffect="SE_AUTO_GRADIENT" graphType="BAR_VERT_⇒ PERCENT"> <Background fillColor="#f1f6f0" /> <Footnote horizontalAlignment="RIGHT"> <GraphFont name="SansSerif" size="9" bold="false" italic="false" underline="false"⇒ /> </Footnote> <LegendArea automaticPlacement="AP_NEVER" position="LAP_TOP" fillColor="#ffffff" ⇒ /> <LegendText horizontalAlignment="LEFT"> <GraphFont name="SansSerif" size="9" bold="false" italic="false" underline="false"⇒ /> </LegendText> <O1TickLabel textRotation="TR_HORIZ" tickLabelSkipMode="TLS_AUTOMATIC" tickLabel⇒ SkipCount="0" tickLabelSkipFirst="0" automaticRotation="AR_HORIZ_ROTATE_270"> <GraphFont name="SansSerif" size="9" bold="false" italic="false" underline="false"⇒ /> </O1TickLabel> <O1Title> <GraphFont name="SansSerif" size="11" bold="true" italic="false" underline="false"⇒ /> </O1Title> <SeriesItems> <Series id="0" color="#336699" /> <Series id="1" color="#ffff00" /> <Series id="2" color="#ff0000" /> </SeriesItems> <Y1ReferenceLine> <ReferenceLine index="0" lineWidth="2" lineColor="#ff0000" displayedInLegend=⇒ "true" /> </Y1ReferenceLine> <Y1TickLabel> <GraphFont name="SansSerif" size="9" bold="false" italic="false" underline="false"⇒ /> </Y1TickLabel> <Y1Title> <GraphFont name="SansSerif" size="11" bold="true" italic="false" underline="false"⇒ /> </Y1Title> </Graph>
This section contains example graph DTD for each of the chart type provided in EnterpriseOne. You can modify the code in these graph DTDs to alter how the chart displays information.
<?xml version='1.0' encoding="UTF-8"?> <!ELEMENT Graph (Footnote?,MarkerText?,O1Title?,Title?,Subtitle?,X1Axis?,Y1Axis?,Y1Reference⇒ Line?,Y1Title?,Y2Axis?,Y2Title?,LocalRelationalData) <!--the graphName is the name of a pre-defined tempate to use--> <!ATTLIST Graph graphName CDATA #REQUIRED <!-- Graph definition of the footnote --> <!ELEMENT Footnote EMPTY> <!ATTLIST Footnote text CDATA #IMPLIED visible (true | false) #IMPLIED <!ELEMENT MarkerText (GraphFont?, X1ViewFormat?, Y1ViewFormat?, Y2ViewFormat?, ⇒ ZViewFormat?) > <!-- MarkerText attributes: markerTextPlace: where, in relation to the marker, the marker text appears; outside max is above bar on max edge is sitting on the bar inside max is on the bar, near the top inside min is on the bar, near the bottom center is centered on the bar custom lets you set the angle and radius **next to attributes in effect only when markerTextPlace is MTP_CUSTOM** markerTextAngleDefault: angle of the text, in degrees, measured from the center of the marker markerTextRadiusDefault: distance from the center of the marker, 0 - 100 --> <!ATTLIST MarkerText visible (true | false) #IMPLIED fontSizeAbsolute (true | false) #IMPLIED markerTextPlace (MTP_OUTSIDE_MAX | MTP_ON_MAXEDGE | MTP_INSIDE_MAX | MTP_INSIDE_MIN | MTP_CENTER | MTP_CUSTOM) #IMPLIED markerTextAngleDefault CDATA #IMPLIED markerTextRadiusDefault CDATA #IMPLIED > <!-- Title for the ordinal axis (O1Axis)--> <!ELEMENT O1Title EMPTY> <!ATTLIST O1Title text CDATA #IMPLIED visible (true | false) #IMPLIED > <!-- Graph definition of the title; appears in graph image --> <!ELEMENT Title EMPTY> <!ATTLIST Title text CDATA #IMPLIED visible (true | false) #IMPLIED > <!-- Graph definition of the subtitle; appears in graph image --> <!ELEMENT Subtitle EMPTY> <!ATTLIST Subtitle text CDATA #IMPLIED visible (true | false) #IMPLIED > <!-- Reference line for Y1-axis: includes up to 3 actual lines --> <!ELEMENT Y1ReferenceLine (ReferenceLine*) > <!-- Represents the actual line in ReferenceLine element --> <!ELEMENT ReferenceLine EMPTY > <!-- ReferenceLine attributes: index: which line in this axis; 0, 1, or 2 text: description of reference line value: where along the axis the line should appear displayedInLegend: whether a key to the line appears in the legend --> <!ATTLIST ReferenceLine index CDATA #REQUIRED visible (true | false) #IMPLIED lineWidth CDATA #IMPLIED text CDATA #IMPLIED value CDATA #IMPLIED displayedInLegend (true | false) #IMPLIED lineColor CDATA #IMPLIED lineStyle (LS_SOLID | LS_DASH | LS_DOTTED | LS_DASH_DOT) #IMPLIED > <!-- Title for the Y1-axis (left side); reads up --> <!ELEMENT Y1Title EMPTY> <!ATTLIST Y1Title text CDATA #IMPLIED visible (true | false) #IMPLIED > <!-- Title for the Y2-axis (right side); reads down --> <!ELEMENT Y2Title EMPTY> <!ATTLIST Y2Title text CDATA #IMPLIED visible (true | false) #IMPLIED > <!-- Relational data for local data source: Graph builds a grid of data from this element and children --> <!ELEMENT LocalRelationalData (Row+) > <!ELEMENT Row EMPTY> <!ATTLIST Row columnKey CDATA #IMPLIED dataValue CDATA #IMPLIED rowKey CDATA #IMPLIED > <!-- ViewFormat specifies number formatting--> <!ELEMENT ViewFormat EMPTY > <!-- ViewFormat attributes numberType: format numbers as currency or percent? thousandSeparator: character for separating thousands decimalSeparator: character for separating whole number from decimal currencySymbol: currency symbol; numberType must be NUMTYPE_CURRENCY leadingZero: display leading zeros? decimalDigit: number of decimal digits to display posNumFmt: format for positive numbers negNumFmt: format for negative numbers posCurFmt: format for positive currency negCurFmt: format for negative currency scaleFactor: how much to scale (abbreviate) numbers scaleDownThousands: character(s) to use when numbers represent thousands scaleDownMillions: character(s) to use when numbers represent millions scaleDownBillions: character(s) to use when numbers represent billions scaleDownTrillions: character(s) to use when numbers represent trillions scaleDownQuadrillions: character(s) to use when numbers represent quadrillions javaDateFormat: Java date format oracleDateFormat: Oracle date format "used" attributes specify whether one of the above properties has been explicitly set; used for merging when using rules --> <!ATTLIST ViewFormat numberType (NUMTYPE_GENERAL | NUMTYPE_CURRENCY | NUMTYPE_PERCENT) #IMPLIED thousandSeparator CDATA #IMPLIED decimalSeparator CDATA #IMPLIED currencySymbol CDATA #IMPLIED leadingZero (true | false) #IMPLIED decimalDigit CDATA #IMPLIED posNumFmt (POS_NUMFMT_NUM | POS_NUMFMT_POS_NUM | POS_NUMFMT_NUM_POS ) #IMPLIED negNumFmt (NEG_NUMFMT_OP_NUM_CP | NEG_NUMFMT_NEG_NUM | NEG_NUMFMT_NUM_NEG)⇒ #IMPLIED posCurFmt (POS_CURFMT_CUR_NUM | POS_CURFMT_NUM_CUR | POS_CURFMT_CUR_SPAC_NUM |POS_CURFMT_NUM_SPAC_CUR | POS_CURFMT_POS_CUR_NUM | POS_CURFMT_CUR_NUM_POS | POS_CURFMT_POS_NUM_CUR | POS_CURFMT_NUM_POS_CUR | POS_CURFMT_NUM_CUR_POS | POS_CURFMT_POS_NUM_SPAC_CUR | POS_CURFMT_POS_CUR_SPAC_NUM | POS_CURFMT_NUM_SPAC_CUR_POS ) #IMPLIED negCurFmt (NEG_CURFMT_OP_CUR_NUM_CP | NEG_CURFMT_NEG_CUR_NUM | NEG_CURFMT_CUR_NEG_NUM | NEG_CURFMT_CUR_NUM_NEG | NEG_CURFMT_OP_NUM_CUR_CP | NEG_CURFMT_NEG_NUM_CUR | NEG_CURFMT_NUM_NEG_CUR | NEG_CURFMT_NUM_CUR_NEG | NEG_CURFMT_NEG_NUM_SPAC_CUR | NEG_CURFMT_NEG_CUR_SPAC_NUM | NEG_CURFMT_NUM_SPAC_CUR_NEG ) #IMPLIED scaleFactor (SCALEFACTOR_NONE | SCALEFACTOR_THOUSANDS | SCALEFACTOR_MILLIONS | SCALEFACTOR_BILLIONS | SCALEFACTOR_TRILLIONS | SCALEFACTOR_QUADRILLIONS ) #IMPLIED scaleDownThousands CDATA #IMPLIED scaleDownMillions CDATA #IMPLIED scaleDownBillions CDATA #IMPLIED scaleDownTrillions CDATA #IMPLIED scaleDownQuadrillions CDATA #IMPLIED javaDateFormat CDATA #IMPLIED oracleDateFormat CDATA #IMPLIED numberTypeUsed (true | false) #IMPLIED thousandSeparatorUsed (true | false) #IMPLIED decimalSeparatorUsed (true | false) #IMPLIED currencySymbolUsed (true | false) #IMPLIED leadingZeroUsed (true | false) #IMPLIED decimalDigitUsed (true | false) #IMPLIED posNumFmtUsed (true | false) #IMPLIED negNumFmtUsed (true | false) #IMPLIED posCurFmtUsed (true | false) #IMPLIED negCurFmtUsed (true | false) #IMPLIED scaleFactorUsed (true | false) #IMPLIED scaleDownThousandsUsed (true | false) #IMPLIED scaleDownMillionsUsed (true | false) #IMPLIED scaleDownBillionsUsed (true | false) #IMPLIED scaleDownTrillionsUsed (true | false) #IMPLIED scaleDownQuadrillionsUsed (true | false) #IMPLIED javaDateFormatUsed (true | false) #IMPLIED oracleDateFormatUsed (true | false) #IMPLIED > <!-- ViewFormats for different number values that can appear in marker text and tooltip text --> <!ELEMENT X1Axis (ViewFormat?) > <!ELEMENT X1ViewFormat (ViewFormat) > <!ELEMENT Y1Axis (ViewFormat?) > <!ELEMENT Y1ViewFormat (ViewFormat) > <!ELEMENT Y2Axis (ViewFormat?) > <!ELEMENT Y2ViewFormat (ViewFormat) > <!ELEMENT ZViewFormat (ViewFormat) >
This section provides an overview of the relationship between data items and controls and discusses how to:
Attach a data item to a control.
Override a default DD trigger.
On a form, you can use any data item that is in the BV and any data item from the DD. BV items are associated with the database; they are retrieved from and updated to the database tables. DD items are not connected to the database; their values are not retrieved from nor updated to the database tables by the system. On a form, BV items appear with a blue box in the left corner, and DD items appear with a yellow box in the left corner. Use DD items as work fields for ER or fields that are not directly connected to the database table.
You can associate data item values with these control types:
Check boxes.
Edit controls.
Grid controls (columns).
Parent child controls (columns).
Radio buttons.
Radio buttons must be associated with DD items. All radio buttons with the same DD item are considered to be a group. Selecting one radio button within the group automatically clears all other radio buttons in the same group.
Combo boxes
The rest of the controls types either cannot be associated with a data item, such as push buttons, or essentially act as containers for controls, such as subforms and tab pages, which may in turn be associated with a data item, according to their type.
If you want the user-entered value for a control to update a database record, then the control must be associated with a BV item. For example, a check box can be associated with the database field called Taxable. In the check box properties, the Checked value should be Y and the Unchecked value should be N. You can use these values in ER as well.
Each DD item has a set of properties (such as Default Value) and behaviors (such as Format Rules and Edit Rules). When you create a DD item, you define its default properties and behaviors at that time. You can override previously-defined DD items at the application level, which enables you to further customize how data items behave at runtime. You can disable default properties and behaviors for a specific item, as well as override to use different values and triggers.
To attach a data item to a control:
Select the control, and then click Data Item Information in the Property Browser and click the ellipses button that appears in the Data Item Information field.
On Control Properties, perform one of these tasks:
To attach a data item from the BV attached to the form, click the Business View Items tab and double-click a data item.
To attach a data item from the DD, click the Data Items tab, search for the data item you want, and then double-click it.
To override the data item name as it appears on the form, click the General tab, click Override Text, and then enter the name you want to use in the Event Rules Title field.
The Text is Overridden property in the Property Browser changes to Yes. To return the display name to the DD name, change Text is Overridden to No.
To override default DD properties and triggers.
On the form, double-click a control with an attached DD item.
On Edit Properties, click the Overrides tab, and then click Data Dictionary Overrides.
On Data Dictionary Overrides, to disable one or more triggers, select the ones you want to disable in the Disable box.
To override a trigger, click the applicable trigger type and complete the form that appears.
For example, if you click Default Value, the Override Default Value form appears and you would make your changes there.
This section provides an overview of the relationship between data item descriptions and fields and discusses how to display the title of a data item associated with a field.
When you insert an edit control on the form and associate a data item with it, FDA does not automatically associate a description with the field. If you want to display the row description for the data item automatically on the form, you must associate the data item description with the field.
When you associate a description with an edit control, a description of the value in the control automatically appears next to it. Associating a description is optional but is useful as a visual aid on the form.
For example, suppose that the address book number, for example, 1001 appears in an edit control or in an edit control. When the user presses Tab to move out of the control, the address book name, XYZ Company, appears next to the control as the associated description.
To display the title of a data item associated with a field:
Click the control, and then select Edit, Associate Description.
FDA creates a static text block and attaches it to the cursor so that you can place it where you want.
Click the approximate location on the form where you want the description to appear.
Sometimes, you want a set of controls to be taken as a whole by the user. The classic example is when you want the user to select one item from a list of items, and this situation is typically resolved by creating a radio button for each option and then grouping them so that the user can select only one at a time.
To provide the user with a visual cue that the controls are grouped, you can place a group box around the controls. Use the Title property for the group box to label the group on the form.
If you want to create more space on a form or only display controls when needed, you can apply the Collapsable property. When the Collapsable property has been applied to the group box a title bar will appear. Clicking on the title bar will expand / collapse the group box. Once the Collapsable property is applied you can also use the Expand Group Box and Collapse Group Box Control System Functions within Event Rules. You can place a collapsable group box next to another (parallel) as long as the group box property Position -Top is the same value for both. (Release 9.1 Update 3)
This section provides an overview of tab sequences and discusses how to change the tab sequence on a form.
The tab sequence of the controls determines the order in which the cursor travels through the controls on the form. Each control that is designated as a tab stop is numbered to reflect how the cursor will travel. For example, when the user opens the form, the cursor appears on the control labeled number one. When the user presses Tab, the cursor moves sequentially to the control (tab stop) labeled number two on the form.
Only those controls that are designated as tab stops in the control properties are affected by the tab sequence. The default tab sequence is the order in which you place the controls on the form.
These properties can override the first tab stop:
Default cursor on add mode
Default cursor on update mode
To change the tab sequence:
On the form with which you are working, select Layout, and then Tab Sequence.
FDA displays each control so you see its number in the tab sequence instead of its name.
Click the controls in the order in which you want the cursor to travel.
The first control that you click becomes number one, the second becomes number two, and so on. To reset the numbers to their original values, right-click anywhere in the window.
Note:
Subforms contain their own sequence orders for objects on the subform. Therefore, you set the tab sequence on each subform within the subform itself. The subform, then, becomes a single object in the tab sequence for the power form.Click Layout , and then Tab Sequence again to stop selecting the sequence.
OR
Click Layout, and then click Update Tab Sequence.
Right-click on a control on which you want to change the tab sequence.
The Tab Sequence field displays.
Change the number in the field to reflect where you want that field in sequence to the other fields.
Press Enter.
FDA automatically adjusts the remaining fields in the sequence. For example, if you change a field sequence from 2 to 4 the remaining fields adjust as follows:
Original Field Sequence | Adjusted Field Sequence |
---|---|
Field 1 | Field 1 |
Field 2 | Field 4 |
Field 3 | Field 2 |
Field 4 | Field 3 |
The FDA Compare tool in Form Design Aid (FDA) enables you to compare one version of an application to another. You can compare them on the application level to determine whether forms have been added, deleted, or rearranged and whether the properties have changed. You also can compare the forms in the applications to each other to see whether controls have been added, deleted, or rearranged and whether the properties have changed.
Additionally, you can compare two different applications as well. This feature is useful when you have made a new application by copying an existing one and then modifying it. Then, when you upgrade, you can not only compare the base application to its new counterpart, but also you can compare a custom application.
See "Understanding FDA Compare" in the JD Edwards EnterpriseOne Tools Software Updates Guide.