This chapter contains the following topics:
Task design provides you with the features that you need to efficiently design and manage tasks. Ensure that the JD Edwards EnterpriseOne tasks that you create comply with task standards so that they are consistent with tasks throughout all JD Edwards EnterpriseOne applications.
Use this task hierarchy when you create task structures:
GXX - system task
GXXYY - module description
GXX10 - Daily Processing
GXX20 - Periodic Processing
GXX31 - Advanced and Technical Operations
GXX41 - System Setup
When you create tasks for an interactive application or batch application, you can designate processing options to be used with them. Processing options for a task determine how the interactive application or batch application is executed, such as whether to prompt the user for a version of an application or to execute an application blindly.
The UDC table 98/CD assists you when defining the task processing options. You access the UDC table 98/CD Task Design on the Task Selection Revisions form (W0082C).
Generally, you should set up UBEs (batch applications) on a task to prompt for a version if there are processing options associated with the UBE. When there are multiple versions of a batch application, the user must select the version before the application executes.
With interactive applications, you should set up blind execution on a task. When an application is set up on a task using the blind execution option, the application executes without any interaction from the user.
This table lists more detailed information about setup options:
| Option Code 98/CD | ZJDE0000 | XJDE0000 | Blank (or not version defined) |
|---|---|---|---|
| Blank = No processing option | Warning: Currently, this setup produces the versions list. Calling the versions list contradicts the definition and purpose of a ZJDE version. Set the Options Code to 1 or 3. | OK: No warning given. The versions list will be presented. | OK: No version exists or more than one UBE version exists. The versions list will display. For an interactive application where there are no versions, use this setup. |
| 1 = Blind execution | OK: A blind submit will occur. Use for interactive applications or batch applications with ZJDE versions. | Warning: An XJDE is not usually a blind execution submit. Set the Option Code to Blank or 2, or determine if the version should be a ZJDE. | Warning: If you are blindly submitting, you should have a ZJDE version defined.
Resolution: Determine which version type you have and set the Option Code accordingly. |
| 2 = Prompt for Versions | Warning: A ZJDE is a blind version submit. It is incorrect to ask for the versions list to be displayed with a ZJDE version. Change the Option Code to 1 or 3, or determine if the version should be a XJDE. | OK: Multiple XJDE versions exist or user-defined versions exist and you want to select from the versions list. Option Code Blank displays the versions list. | OK: Versions list will be displayed. |
| 3 = Prompt for Values | OK: The processing options will display and an automatic launch will occur. | OK: This could happen. Probably more likely to see this at a client site. | Warning: If you have not set up a version, prompting for values is incorrect. If no versions exist, set Option Code to Blank. |