(Yield) Maps - StellarSupport - John Deere

JDOffice 1.2
The system will remember your changes as you move from one tab to another, however
they are not saved. To save your Setup information, click Apply; the tabs will remain open
so you can continue working, but all the work done on each tab since you opened Setup
will be saved. Clicking OK will also save all the work, but will close the Setup tabs. Click
Cancel to discard all of the changes to all of the tabs since the last time you clicked Apply
(saved).
At any time you can edit the data on these tabs. Simply highlight what you want to edit, and
type in the new information over it. However, do NOT rename any of the sample data.
Leave these as examples and create new entries for your information.
After saving your Setup data to the PC Card, insert the card into the Mobile Processor.
When the machine is started, the Setup information will be available on the GreenStar
Display.
Note: Text fields marked with an asterisk (*) are required.
Tag Numbers
A Tag number not only represents the Setup item in the directory structure of the
computer, but it follows the Setup item through the years and does not change. The tag
number is randomly assigned and cannot be edited or deleted. To view a tag number,
position the mouse pointer over the item’s display name field title; the number will appear
in a popup window. When you move the mouse away from the field title, the popup will
close.
Long Names vs. Display Names
JDOffice requires a long and a short name (Display name) for all Setup items except flags.
The long name can be up to 64 characters; the short name can be up to 20 characters.
After you type in a long name and move to another text box, JDOffice will automatically
copy the first 20 characters into the short display name text box. The short display names
will be used throughout the program (except on reports) so you are free to rename any of
them.
Making Setup Items Inactive/Active
Setup items cannot be deleted; however, they can be made inactive.
If an item has been used in the Task Builder or the Task Wizard (refer to page 70 and 72,
respectively) as part of an operation, or if it had been previously used in unloaded data,
46