Scribd
Upload
5 views

04 - FormTypes &event Rules

JDE Development Training Doc

Uploaded by

zqtbok
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
5 views

04 - FormTypes &event Rules

JDE Development Training Doc

Uploaded by

zqtbok
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 17

J.D.

J.D. Edwards
Edwards Forms
Forms
Find / Browse Form

 Search, View or Select Multiple Rows


 Entry point to an application
 Non-input capable grid
 FIND Button
 ADD Button
(Takes you to another form to add
information)
 SELECT Button
 Only one Business View
(Displays data from only one table)
Fix / Inspect Form

 View, Add, Update a single record


 Never has a grid
(Can only update one record at a time)
 OK Button
(Updates the table or saves the information to
the Database)
 CANCEL Button
(No Database changes)
 Only One Business View
(Contains only one record)
Headerless Detail

 View, Add or Delete multiple records


 Input capable grid
 No FIND Button
 Only One Business View
(Updates only one table)
Header Detail Form

 Add, View or Change multiple detail records


 Add, Update a single header record
 No FIND Button
 Input Capable Grid
(add or update detail records)
 2 Business Views
(Update or add records from 2
different tables, one for the grid, one
for the form)
Search & Select Form

 Search and return a value


(Usually called using a visual assist)
 Non-input capable grid
 View multiple records
 FIND Button
 Only One Business View
(Review records from one table)
Message Form

 Display messages or request action


 Static text
 Modal, not sizable
 Allows Push Buttons
 No Business View
 Form Interconnect not allowed
Parent Child Form

 Shows Parent / Child relationships


 Tree format – left side
 Grid in browse mode – right side
(detail records of the child node of the
tree)
 Only One Business View
Event Rules
Event c t s
Event Rules bj ects
EventRules Obje ts
E R Objects
vent Rules Objec s
Event ules O ject
Rules Ob
e n t s
Ev venetns ts
E Ev vents ts
E Even
FoFromrms
F
F orm s
o
Fo rms s
Versatility Through Design rms
Event Rules Overview
APPLICATION

FORMS

CONTROLS

EVENTS

EVENT RULES
What Questions need to be answered when
setting up Event Rule Logic?

?
 What LOGIC (Event Rule)
should I use?
 What CONTROL should I use?
 What EVENT should I use?
 What RUNTIME Data
STRUCTURE should I use?
What
What Kind
Kind of
of LOGIC
LOGIC (Event
(Event Rule)
Rule) is
is available?
available?

 Form Interconnections
 System Functions
 Business Functions
 Assignments/Calculations
 IF / WHILE statements

The Key Question is:


What am I trying to
accomplish?
What CONTROL should I use?
 Should the logic happen at the form
level? Such as…
* Initializing a field
* Hiding a control until a
specific condition occurs
 Should the logic happen when a
button is clicked? As when...
* Calling another form
 Should the logic happen when
exiting a field? For example...
* Calculating a new field value
Simple CONTROLS
 Buttons
Event = Button clicked
 Fields
Events = Tab into control
Tab out of control

Complex CONTROLS
 Forms
Events = Several (Event flow)
 Grids
Events = Several (Event flow)
What
What EVENT
EVENT do
do II use?
use?

 Depends on the CONTROL chosen


 Each CONTROL has its own set of
events.
 If the CONTROL is a form, each form
type has its own Event Rule Processing
flow

 For CONTROLS that have multiple events,


the order of processing the events is very
important (Event Rule Flow)
What
What Runtime
Runtime Structure
Structure Do
Do II Use?
Use?

BC = A column in the
 During processing, data is business view
GC = A column in the
stored in memory in internal grid
data structures FC = A control on the
 As a general rule, BC and FC form
share the same internal FI = A value passed
through Form
structure if FC is associated
Interconnection
with a database item PO = A value passed
from a processing
option
More
More Runtime
Runtime Data
Data Structures
Structures

GB = Grid Buffer column


QC = QBE Column
HC = A Hypercontrol
VA = Event Rules Variable
SV = A System Variable
SL = System Literal

You might also like