Writing Scripts

This chapter provides an overview of creating a script and discusses how to:

Click to jump to parent topicUnderstanding How to Create a Script

You can create scripts with Oracle's JD Edwards EnterpriseOne Autopilot by using either manual or automatic script generation. When you generate a script manually, you create the script by selecting commands from the Command menu. The commands you create will execute sequentially when the script runs. To create a script automatically, you use event capture to generate a script that is based on the actions you perform as you use the JD Edwards EnterpriseOne software.

Click to jump to parent topicCreating a Script from Event Capture

This section provides an overview of creating scripts from event capture and discusses how to use the Create a Script from Capture option.

Note. Event Capture works only with JD Edwards EnterpriseOne Windows-based applications. Starting with the 8.11 release, JD Edwards EnterpriseOne applications are exclusively web-based. Consequently, you can use Event Capture with 8.10 and prior releases, but not with 8.11 and subsequent releases.

Click to jump to top of pageClick to jump to parent topicUnderstanding How to Create a Script from Event Capture

You can use JD Edwards Autopilot to translate events in the software into a JD Edwards Autopilot script. Using the Create a Script from Capture option in JD Edwards Autopilot enables you to automatically create a script from actions that you perform in the software without having to understand the internal data relationship or the intricacies of creating a JD Edwards Autopilot script manually. Generating a script from the event stream can also increase the productivity of scripting and shorten the learning curve for an inexperienced user.

When you create a script from event capture, you create a script framework, not a finished script. JD Edwards Autopilot captures all the events in the stream. You might not need all those events. You will have to decide how to modify the scripts generated from the tool.

Although the script might not be fine tuned to suit your needs, these unmodified scripts have many uses. For example, you can capture a process that is causing an error in a JD Edwards Autopilot script and then email the script to your support organization.

Note. When you use the Create a Script from Capture option to create a script, it is recommended that you use the fast paths instead of the menus when calling an application.

Click to jump to top of pageClick to jump to parent topicCreating a Script from Event Capture

To create a script from event capture:

  1. From your desktop or the appropriate directory, launch JD Edwards EnterpriseOne and sign on.

  2. In JD Edwards Autopilot, from the File menu, select New.

  3. From the Tools menu, select Create a Script from Capture.

  4. On Create a Script with Event Capture, complete the field Script Name.

  5. Click Start Capture.

  6. On JD Edwards EnterpriseOne Solution Explorer, complete the Fast Path field and press Enter:

    Enter a command in the Fast Path, such as 3/G11. You cannot enter an abbreviation of a program, such as OMW, UDC, OL and so on. If the fast path command does not contain a menu selection, the JD Edwards Autopilot script will fail.

    You can capture multiple applications in a sequence as long as you always start an application by entering a command in the fast path.

  7. Perform your task.

    JD Edwards Autopilot captures and records every event. Ensure that you are performing actions deliberately in order to create the most accurate script. For example, if you click the OK button twice, JD Edwards Autopilot records two events.

  8. Click Stop Capture when you have finished your task, and then click Generate Script.

    Your new script loads in the JD Edwards Autopilot script view pane.

  9. From the File menu, select Save to save your script.

  10. Modify the script as needed.

Click to jump to parent topicWriting a Script Using Context Commands

This section provides an overview of writing a script using context commands and discusses how to:

Click to jump to top of pageClick to jump to parent topicUnderstanding How to Write Scripts Using Context Commands

You can begin scripting context commands in one of three ways: by selecting a command from the Command menu, by clicking a hot key on the keyboard, or by clicking a toolbar button. When you do so, lists appear in the command pane. You make selections from populated lists and enter information in unpopulated lists. When you click the Insert button, JD Edwards Autopilot inserts one or more command lines into the Script pane. The context command is identified in the Script pane with words and symbols.

In general, the sequence that you follow to write primary context commands is as follows:

Some context commands depend on other context commands. For example, Header is a context command, but you set the header as the context only after you have set an application and a form as the context for the script.

The general sequence that you follow to write secondary commands is as follows:

Click to jump to top of pageClick to jump to parent topicSetting the Context as a UBE

There are several ways that you can set the context as a UBE. You can begin the script by launching the UBE from the Batch Versions program (P98305), or you can launch an interactive application and then perform a report exit to the Batch Versions program. You can launch an interactive application, then perform a row exit that launches a blind execution. You can launch a UBE from a menu that is hard-coded to submit the version automatically. Finally, you can launch a UBE that launches another UBE. In this case, JD Edwards EnterpriseOne software launches any subsequent UBEs and then blindly submits them without any further intervention by JD Edwards Autopilot.

When you click UBE in the Command menu, options for executing a Fast Path and for creating a Work With Batch Versions command appear. You can use these options to establish the way that JD Edwards Autopilot submits the UBE, except when a menu is hard-coded to automatically submit it.

If you select a UBE that is not automatically submitted, you must write a command to click the Submit button on the Version Prompting form. Before you write that command, however, you can click the option that enables you to select data for your report. In some cases, after you submit the UBE and select data, you can set processing options. Doing so requires you to write a UBE Processing Options command to the script and set the options by making choices from the lists in the command pane.

Finally, you can select the way to print the UBEs that you submit. You can instruct JD Edwards Autopilot to wait for the UBE to print before resuming running the script, or you can send the UBE to print, but tell JD Edwards Autopilot to continue running the script. If it is appropriate to the function you are testing, you can also write a command to close the Batch Versions program and return to Explorer.

Click to jump to top of pageClick to jump to parent topicLaunching a UBE

You can use JD Edwards Autopilot to launch a UBE from a variety of contexts. You might begin the script by launching a UBE from a menu. On the other hand, you might launch a UBE after you launch an interactive application. In this case, you might launch the UBE from a report menu, or you might launch it after you perform a row exit. You might also select to launch a UBE that is automatically submitted. Finally, you can launch a UBE that in turn launches one or more additional UBEs.

Click to jump to top of pageClick to jump to parent topicSetting the Context as an Application

You often begin a script by launching an application. This process establishes both the application and the form that you work with in the script.

Note. Concerning the Menu List and Setting Context, the Menu list includes the text of the menu item in Explorer, the Fast Path, and the application version. You can launch different versions of the same application from different Explorer menus. Be sure to select the menu item that is associated with the version and processing options that you want to test.

Access JD Edwards Autopilot.

  1. Select Application from the Command menu.

  2. From the Application list in the command pane, click an application.

  3. From the Menu list in the command pane, click the name of a menu item.

  4. Click the Insert button.

    JD Edwards Autopilot inserts the Application, Fast Path, and Form command lines into the Script pane. In the play back while scripting mode, JD Edwards Autopilot launches the specified version of an interactive application. The form appears on the screen with the JD Edwards Autopilot window, and you can navigate between the two.

Click to jump to top of pageClick to jump to parent topicLaunching a UBE from a Menu

If you want to launch a UBE from a menu, you must make choices from each of the three lists that appear in the command pane when you click UBE in the Command menu: Application, Menu Item, and Version. You also select both of the options in the command pane: Execute FASTPATH and Create Work With Batch Versions commands. The first option establishes the Fast Path JD Edwards Autopilot uses to access the UBE; the second option commands JD Edwards Autopilot to automatically perform a QBE search in the Work With Batch Versions - Available Versions form for the UBE version that you chose. When you clear this option, you must manually create the command to submit the UBE from the Version Prompting form.

To launch a UBE from a menu:

  1. From the Command menu, select UBE.

  2. In the command pane, make a selection from each of the available lists:

  3. Select both the Execute FASTPATH and Create Work With Batch Versions commands options, if available.

  4. Click the Insert button.

    When you click the Insert button, JD Edwards Autopilot automatically inserts a series of command lines in the script. The command sequence ends at the Form {Version Prompting} command line.

Click to jump to top of pageClick to jump to parent topicLaunching a UBE from a Report Menu

You might want to launch a UBE from the Reports menu in an interactive application. In this case, you begin the script by launching an interactive application. You use the Press Custom Button option to select a report. You select the UBE without the Execute FASTPATH option, and the Menu Item list containing Fast Paths to the UBEs disappears. You select the Create Work With Batch Versions commands option, which means that you write the command to submit the UBE from the Version Prompting form.

To launch a UBE from a report menu:

  1. From the Command menu, select Application.

  2. In the command pane, select options from these lists:

  3. Click the Insert button.

  4. From the Command menu, select Press Toolbar Button.

    Note. Ensure that the INSERT line in the script is always at the child level.

  5. In the Button list, expand Custom Button, and then expand Report.

  6. Select a report.

  7. Click the Insert button.

  8. From the Command menu, select UBE.

  9. In the command pane, select a UBE.

    Do not select the Execute FASTPATH option. Clear it, if it is selected.

    Note. When you clear the Execute FASTPATH option, the Menu Item list disappears. Do not clear this option until you have chosen the UBE. If you clear the option before you select the UBE, JD Edwards Autopilot turns the option on again after you have chosen the UBE, and you must clear it again.

  10. Select a version from the Version list.

  11. Select the Create Work With Batch Versions commands option.

  12. Click the Insert button.

    Because you turned on the Create Work With Batch Versions commands option, JD Edwards Autopilot automatically writes a series of script commands that ends at the Form {Version Prompting} command line.

Click to jump to top of pageClick to jump to parent topicLaunching a UBE from a Row Menu

You can launch a UBE from a Row menu in an interactive application. To do so, you begin by launching an interactive application. After you have written a row exit command using the Press Custom Button option, you select the UBE command. You click neither of the command pane options. The Menu Item list disappears, and you select a version. If you clear the Batch Versions option, JD Edwards Autopilot blindly submits the UBE.

To launch a UBE from a Row menu:

  1. From the Command menu, select Application.

  2. In the command pane, select options from these lists:

  3. Click the Insert button.

  4. From the Command menu, select Set QBE Cell Value.

  5. In the command pane, select options from these lists:

  6. Click the Insert button.

  7. From the Command menu, select Press Toolbar Button.

  8. In the Button list in the command pane, under the Standard Button heading, select Find.

    Important! Do not select options from the Next Form list. If you select these options and insert the command, JD Edwards Autopilot launches the new interactive application that you chose.

  9. Click the Insert button.

  10. From the Command menu, click Select Grid Row.

  11. In the command pane, click these options:

  12. In the Source of Row Number list, select a value source.

  13. In the value selection list, enter a row number or select a variable or valid values list.

  14. Click the Insert button.

  15. From the Command menu, click Press Toolbar Button.

  16. Click Custom Button.

  17. Click Row.

  18. Select a Row selection.

    Important! Ensure that you do not make choices from the Application or Next Form lists because they launch applications. You need to launch a UBE.

  19. Click the Insert button.

  20. From the Command menu, click UBE.

  21. In the command pane, select a UBE from the UBE list.

    Important! Deselect both the Execute FASTPATH and Create Work With Batch Versions commands options.

  22. Select a version from the Version list.

  23. Click the Insert button.

    JD Edwards Autopilot automatically submits the UBE.

Click to jump to top of pageClick to jump to parent topicLaunching a UBE That Is Automatically Submitted

If you launch a UBE that is hard-coded to submit the version automatically, you cannot click the options in the command pane. When you select the UBE, JD Edwards Autopilot disables both of the options and the Version list disappears. You select from the Menu Item list and click the Insert button, and then JD Edwards Autopilot launches the UBE and blindly submits it.

To launch a UBE that is automatically blindly submitted:

  1. From the Command menu, click UBE.

  2. In the command pane, select a UBE that will be blindly submitted from the UBE list.

    When you select the UBE in this scenario, JD Edwards Autopilot disables both options and the Versions list disappears.

  3. Select a menu item from the Menu Item list.

  4. Click the Insert button.

Click to jump to top of pageClick to jump to parent topicLaunching a UBE from Another UBE

You might launch a UBE from a menu or from an application that in turn launches one or more subsequent UBEs. In this case, JD Edwards EnterpriseOne software automatically launches any UBEs that are called by the first one and blindly submits them. You do not select versions or printing options, or set processing options. Without further direction from the JD Edwards Autopilot script, JD Edwards EnterpriseOne software completes all of the processes that are associated with the UBEs that the first UBE launches.

To launch a UBE from another UBE:

  1. In the Command menu, follow the steps for creating a script that launches a UBE from a menu, a Report menu from an interactive application, or a Row menu from an interactive application.

  2. In the command pane, select a UBE from the UBE list.

    If the UBE is coded to launch another UBE, JD Edwards Autopilot disables the Execute FASTPATH option and removes the Menu Item list from the command pane.

  3. Select a version from the Version list.

  4. Deselect the Create Work With Batch Versions command option.

  5. Click the Insert button.

Click to jump to top of pageClick to jump to parent topicSubmitting a UBE

You write a command to submit the UBE only when you have turned on the Create Work With Batch Versions commands option in the command pane. When you select this option, JD Edwards Autopilot automatically writes commands that culminate with the Form {Version Prompting} command line. You then use the Press Standard Button option to write a command to click the Submit button on this form.

To submit a UBE:

  1. Write commands through the command line Form {Version Prompting}.

  2. From the Command menu, select Press Toolbar Button.

  3. In the Button list in the command pane, click Standard Button.

  4. Select Submit.

  5. Click the Insert button.

Click to jump to top of pageClick to jump to parent topicSelecting Data for a UBE

After you launch a UBE, you might want to refine the data that appears in your report. If so, you can use the Criteria Design Aid feature in JD Edwards Autopilot, which you access either by clicking UBE Selection in the command menu or by clicking the CDA button on the toolbar. This feature enables you to script entries to the Data Selection form.

You can use the Criteria Design Aid feature when you launch a UBE with the Create Work With Batch Versions commands option turned on. If you launch the UBE from a menu, JD Edwards Autopilot automatically inserts a series of commands that ends at the Form {Version Prompting} command line. If you launch the UBE from a Report menu, you write a series of commands that culminates at the same point. In either case, however, when the script reaches the Form {Version Prompting} command line, you can write a command to click the Data Selection option and a command to submit the report for data selection.

At this point, you can click the UBE Selection command and use the JD Edwards Autopilot command pane to script entries to the Data Selection form. When you are finished, you can click the OK option in the command pane. If you stored values in a variable earlier in the script, you can use these values in the right operand of the Data Selection form. You must, however, type the name of the variable in the Right Operand list of the command pane. In addition, the variable name must be enclosed in angle brackets (<>).

After you enter a variable for the right operand, JD Edwards Autopilot displays options that you use to designate the value of the variable as a single value, a range of values, or a list of values.

You use Criteria Design Aid in conjunction with writing a UBE command, not as a stand-alone command. In addition, some UBEs enable you to set processing options. You use JD Edwards Autopilot to set the processing options for the UBE after you have selected the data that you want to appear in the report. You complete the UBE submission process by sending the report to the printer.

Important! Concerning object names, enter the object name in the left operand list exactly as it appears in the drop-down menu of the list on the Data Selection form. Likewise, enter an object name in the right operand list exactly as it appears in the drop-down menu of the list in the Data Selection form, unless you enter a literal value. If you enter a literal value, you can enter a single value, multiple values, or a range of values. You separate multiple values with commas; you separate a range of values with a hyphen.

To select data for a UBE:

  1. From the Command menu, select UBE.

  2. In the command pane, select options from these lists:

  3. Select both the Execute FASTPATH and Create Work With Batch Versions commands options.

  4. Click the Insert button.

  5. From the Command menu, select Check box/Radio Button.

  6. In the command pane, click DataSelectionYN in the Radio Button or Check Box list.

  7. In the Source of Input list, click Check.

  8. Click the Insert button.

  9. From the Command menu, select Press Toolbar Button.

  10. From the Button list, select Standard Button, and then Submit.

  11. Click the Insert button.

  12. From the Command menu, select UBE Selection.

  13. In the command pane, complete these fields:

  14. If you enter a variable in the Right Operand list, click one of these options that appear in the command pane in order to specify the type of value:

  15. Click the Insert button.

  16. After you write as many UBE Selection commands as you need, click the Press OK option and then click the Insert button.

Click to jump to top of pageClick to jump to parent topicSetting UBE Processing Options

After you submit a UBE version, you might see the Processing Options form appear. In this case, you must set processing options for the UBE before you can run the report. To set the processing options for the UBE, you select UBE Processing Options in the command menu, and then select options from the command pane.

To set UBE processing options:

  1. Submit a UBE.

  2. From the Command menu, select UBE Processing Options.

  3. In the Processing Options list of the command pane, click the node of a processing options tab.

  4. Select a processing option.

  5. Select a source of value from the Source list (if applicable).

  6. If the value is literal, enter it in the unpopulated Literal Value field. If you select Variable as the value source, JD Edwards Autopilot populates the Variables list, which contains the UBE version with which you are working, as well as the names of any variables for which you have set values.

  7. Click the Insert button.

  8. In the command pane, click the Press Toolbar Buttons node in the Processing Options list.

  9. If you are satisfied with the processing options that you set up, click OK. If you are not, click Cancel.

  10. Click the Insert button.

Click to jump to top of pageClick to jump to parent topicPrinting a UBE

Clicking UBE Print in the Command menu produces three options in the command pane. If you select the option Wait for UBE to complete before continuing, JD Edwards Autopilot submits the UBE to the printer and waits for it to complete before it resumes the script playback. If you do not select this option, JD Edwards Autopilot continues playing back the script without waiting for the UBE to run.

If the UBE you run does not print, click the Expect No Printer Selection Window option. This option ensures that JD Edwards Autopilot does not wait for a printer window to appear before it resumes the script.

Turning on the option Create exit Work With Batch Versions commands, enables you to automatically write a Form command line for Work With Batch Versions - Available Versions and a Press Toolbar Button {Close} command to return to the form that was active before launching the UBE. You select this option only if you launched the UBE with the Create exit Work With Batch Versions commands option turned on.

To print a UBE:

  1. Submit the UBE and set any necessary processing options, or after JD Edwards Autopilot blindly submits the UBE, from the Command menu, select UBE Print.

  2. In the command pane, click one or more of these options:

  3. Click the Insert button.

Click to jump to top of pageClick to jump to parent topicSetting the Context as an Interconnected Application

In scripting a command to click a standard button, such as Add, you might exit from one JD Edwards EnterpriseOne application to another. When this occurs, you must script an application interconnection by clicking Application Interconnect in the Command menu.

For example, you might want to write a script using the Customer Ledger Inquiry application (P03B2002). If you launch the application, select the menu item Work With Customer Ledger Inquiry, then script clicking the Add button and Unknown/None from the Next Form list, JD Edwards EnterpriseOne software exits to a new application, Standard Invoice Entry (P03B11).

If you click Form in the Command menu, the Standard Invoice Entry form does not appear in the Form list in the command pane. This tells you that by clicking the Add button, you exited to another application. You cannot continue scripting until the Application and Form command lines in JD Edwards Autopilot mirror the application and form that are active.

Using the Application Interconnect command, you can ensure that the script includes the new application and form in the Script pane so that you can continue scripting. Remember that you use the Application Interconnect command after you exit to a new application.

To set the context as an interconnected application:

  1. From the menu bar in the form to which you have exited, click Help.

  2. Select About JD Edwards.

  3. Note the application ID and form name and click OK.

  4. In JD Edwards Autopilot, in the Command menu, Click Form.

    Note that Standard Invoice Entry does not appear in the Form list.

  5. In the Command menu, click Application Interconnect.

  6. In the command pane, select from the lists that appear:

  7. Click the Insert button.

    JD Edwards Autopilot interconnects to the new program or form, and the Application and Form command lines in the Script pane now mirror the program and form that are active. You can now script additional commands.

Click to jump to top of pageClick to jump to parent topicSetting the Context as a Processing Option

You might want to set processing options for a particular application before you begin writing secondary commands for the application. To do so, you select an application and menu item from the command pane as if you are launching an application. However, before clicking the Insert button, you click the Processing options only option in the command pane. This option enables you to select processing options from lists in the command pane.

To set the context as a processing option:

  1. From the Command menu, select Application.

  2. From the Application list in the command pane, click an application.

  3. From the Menu list in the command pane, click the name of a menu item.

  4. In the command pane, select the Processing options only option.

  5. Click the Insert button.

    The command pane now displays a list of the processing options tabs for the application version you have chosen. In the Script pane, the command line shows the Launch Processing Options symbol, the template for the application, and the version of the application that you chose.

  6. Expand the node of one of the tabs.

  7. Select a processing option.

    JD Edwards Autopilot populates the Source list in the command pane with two sources of input: literal and variable.

  8. Select a source of value.

    When you do so, a value selection list appears in the command pane.

  9. If the value is literal, enter it in the unpopulated Literal Value field. If the value is a variable, JD Edwards Autopilot populates the Variables list with the names of any variables whose values you have set.

  10. Click the Insert button.

    JD Edwards Autopilot enters to the Script pane a command line that summarizes the processing options you have chosen.

    Note. With the play back while scripting feature turned on, when you insert a processing option value in JD Edwards Autopilot, the tool inserts the value to the corresponding control in the Processing Options form.

  11. In the command pane, click the Press Buttons node in the Processing Options list.

  12. If you are satisfied with the processing options you have set up, click OK. If you are not, click Cancel.

  13. Click the Insert button.

    Note. You can insert as many processing options to the script as you wish. You can then launch the application, if you desire. When you do so, be sure not to select the Processing options only option in the command pane.

See Also

Using a Variable as a Source of Input

Click to jump to top of pageClick to jump to parent topicDefining Unwanted Windows

When you create scripts, windows and message boxes such as Communication Fail, Confirm Delete, or Scheduled Packages might appear. These windows and message boxes are not routinely recognized by JD Edwards Autopilot scripts and their unexpected appearance might cause your scripts to fail. To prevent script failure, you can specify what you want JD Edwards Autopilot to do when certain windows and message boxes appear.

You can enter, edit, and delete any windows or message boxes from a list that you create. You can also designate a subscript for JD Edwards Autopilot to play when a particular window or message box appears.

To define unwanted windows:

  1. From the Tools menu, select Unwanted Windows.

  2. On Close Unwanted Windows, click New to define a new unwanted window.

    Alternatively, click a row in the Window To Search For And Close pane, and then click Edit.

    Note. To delete an entry, click a row in the Window To Search For And Close pane, and then click Delete. The system does not prompt you with a confirm delete message. Once you delete the selection, you cannot recover it. You will have to enter a new unwanted window entry if you need to replace the deleted one.

  3. On New Unwanted Window Entry, complete the If This Window Is Found field:

    Enter the exact name of the form. Ensure that you enter the exact form name the way it appears in language (for example, English, French, German, and so on).

  4. Select one of these options:

  5. Click OK.

  6. On Close Unwanted Windows, click Apply, and then click OK.

Click to jump to top of pageClick to jump to parent topicSetting the Context as a Form

When you insert an Application command in the script, JD Edwards Autopilot inserts in the Script pane the name of the form that you selected from the menu list. When you move to a new form, you must script the Form command to establish the context in JD Edwards Autopilot. You can script the Form command either from the Next Form list or from the Command menu.

To script the Form command using the Next Form list:

  1. Insert an application into a script.

  2. From the Command menu, select a command that enables you to switch forms, for example, Press Toolbar Button.

  3. In the Button list, click a button-clicking option, such as Add, that takes you to another form.

  4. In the Next Form list, click the name of the form that appears next.

    The Next Form list contains the names of the forms that are included in the current application.

  5. Click the Insert button.

Click to jump to top of pageClick to jump to parent topicScripting the Form Command Using the Command Menu

Access JD Edwards Autopilot.

To script the Form command using the command menu:

  1. Insert an application into a script.

  2. From the Command menu, select Form.

    The Form list appears in the command pane. It displays the names of all forms that are included in the current application.

    Note. You can also display the Form list in the command pane by clicking the Form button in the toolbar.

  3. Select a new form to be confirmed that matches the active form in the software.

  4. Click the Insert button.

    In the Script pane, the new Form command line contains the name of the active form in the software.

Click to jump to top of pageClick to jump to parent topicSetting the Context as a Grid Column

After you launch an application and select a form, you can establish a grid column in the form as a context for further scripting. When you click Set Grid Cell Value in the Command menu, a Grid Column list appears in the command pane if the active form has a grid detail area. From this list, you can select a specific column to further refine the context.

To set the context as a grid column:

  1. From the Command menu, select Set Grid Cell Value.

  2. In the Form/Subform Hierarchy list, select the appropriate form or subform.

  3. In the Grid Column list, select a grid column in which you want to enter data.

  4. Select a source of input from the Source of Input list.

  5. In the value selection list, select or enter a value and click the Insert button.

    When you click the Insert button, JD Edwards Autopilot writes both a Grid (or Detail Information) context command line and a Type To action command line in the Script pane.

Click to jump to top of pageClick to jump to parent topicSetting the Context as a Header

After you launch an application and select a form, you can establish the header portion of the form as the context for further scripting. When you click Set Header Control Value in the Command menu, a Header Control list appears in the command pane from which you can select a specific control to further refine the context.

To set the context as a header:

  1. In the Command menu of the JD Edwards Autopilot window, click Set Header Control Value.

  2. In the Form/Subform Hierarchy list, select the appropriate form or subform.

  3. In the Header list, select a control to which you want to input data.

  4. Select a source of input from the Source of Input list.

  5. In the value selection list, select or enter a value and then click the Insert button.

    When you click the Insert button, JD Edwards Autopilot writes both a Header context command line and a Type To action command line in the Script pane.

Click to jump to top of pageClick to jump to parent topicSetting the Context as a QBE Line

The QBE line provides another context in which you can script commands after you launch an application and select a form.

When you click Set QBE Cell Value on the command menu, a Grid Column list appears in the command pane, if the active form has a grid detail area. You can select a specific column to further refine the context.

To set the context as a QBE line:

  1. Insert an application into a script.

  2. From the Command menu, select Set QBE Cell Value.

  3. In the Form/Subform Hierarchy list, select the appropriate form or subform.

  4. In the Grid Column list, select a grid column in which you want to enter data.

  5. Select a source of input from the Source of Input list.

  6. In the value selection list, select or enter a value and click the Insert button.

    When you click the Insert button, JD Edwards Autopilot writes both a Grid (or Detail Information) context command line and a Type To action command line in the Script pane.