AppsRules Training Guide V 4.0.0.1

_________________________________________
Logical Apps AppsRules

Training Guide
Software Version:
4.0.0.0
________________________________________________________________________
About Logical Apps

______________________________________________________________________________________
Logical Apps Solutions provides the internal controls to deploy business rules for Oracle
Applications. Logical Apps mission is to improve the flexibility of Oracle Applications,
enabling users to support their business processes through the deployment of business
rules.
Your Opinion Matters to Us
Thank you for using Logical Apps AppsRules and this training guide. You may help us
to communicate more effectively with our customers. If you have any comments about
this training guide, please send them to the following address or call us directly at (949)
453-9101.
Logical Apps, Inc.
15420 Laguna Canyon Road
Suite 260
Irvine, CA 92618
Attn: Documentation Manager
Or you may contact our documentation group by e-mail:
support@logicalapps.com
________________________________________________________________________
Table of Contents
______________________________________________________________________________________
INTRODUCTIONS .......................................................................................................... 4
WHAT IS APPSRULES?................................................................................................. 4
PURPOSE OF THIS CLASS........................................................................................... 4
PREREQUISITES ............................................................................................................ 4
APPSRULES TRAINING AGENDA ............................................................................. 5
ARCHITECTURE............................................................................................................ 6
STRUCTURE.................................................................................................................... 7
APPSRULES PROCESS FLOW.................................................................................. 7
PART 1 RULE DEFINITION .................................................................................... 11
PART 2 SECURITY RULES...................................................................................... 19
LAB#1 BUILDING SECURITY RULES ............................................................................ 23
PART 3 NAVIGATION RULES................................................................................ 24
LAB#2 NAVIGATION RULES........................................................................................ 27
PART 4 MESSAGE RULES....................................................................................... 28
LAB#3 MESSAGING RULES ......................................................................................... 30
PART 5 DEFAULT VALUE RULES ........................................................................ 30
LAB#4 DEFAULT VALUE RULES ................................................................................. 31
PART 6 LIST OF VALUE RULES............................................................................ 32
LAB#5 LIST OF VALUES RULES .................................................................................. 36
PART 7 FIELD ATTRIBUTE RULES...................................................................... 37
LAB#6 FIELD ATTRIBUTE RULES ................................................................................ 38
PART 8 SQL RULES .................................................................................................. 39
LAB#7 SQL RULES..................................................................................................... 41
PART 9 AUDIT RULES ............................................................................................. 42
LAB#8 AUDIT RULES .................................................................................................. 52
PART 10 APPSEXTEND ............................................................................................ 53
LAB#9 EXTENSION RULES .......................................................................................... 59
PART 11 APPSFLOW INTEGRATION................................................................... 60
PART 12 - APPSRULES MIGRATING RULES ..................................................... 62
PART 13 SUPPORT .................................................................................................... 68
APPENDIX A SUBSCRIBERS .................................................................................. 70
APPENDIX B SUBSCRIBER LISTS ........................................................................ 73
______________________________________________________________________________________
Welcome & Overview
________________________________________________________________________
Welcome & Overview

Introductions
During this part of the session participants will introduce themselves.
Name
Job Title
Role/Job Description
Course Expectations
What is AppsRules?
AppsRules allows users to define business rules to support your business processes.
Business Rules allow your organization to control how data can be interacted with
through the Oracle Forms GUI. With AppsRules you can:
Add security down to the field level

Increase data integrity
Generate Audit Data
Increase User Productivity
Purpose of This Class

This session prepares participants to use AppsRules. This training guide includes
practical examples and detailed instructions on how to use each of the business rule
features within AppsRules to provide your organization with solid solutions.
Prerequisites
This Training Guide assumes that you have a basic understanding of the Oracle
Applications modules for which your organization is deploying AppsRules. Many
business rules that you wish to deploy do not require any knowledge of any coding
languages, however, AppsRules is powerful enough to allow for coding directly in the
tool if advanced business rules require such flexibility. If you do not have a basic
understanding of Oracle Applications, we suggest that you begin to use AppsRules in
conjunction with a person in your organization who is knowledgeable in Oracle
Applications.
Copyright 2003 by Logical Apps, Inc.
AppsRules Training Material

AppsRules Training Agenda
Time
Topic
Duration
Training Session I
1 Hour
- Welcome & Overview - Business Rule Overview - Building Security Rules Overview - Business Rules - Security Rules ** Break **
20 Min.
20 Min.
20 Min.
40 Min.
20 Min.
20 Min.
15 Min.
Training Session II
1 Hour
- Navigation/Productivity Rules - Building Message Rules - Building Default Value Rules - Building List Of Value Rules - Navigation/Productivity Rules - Message Rules - LOV Rules - Default Value Rules ** Lunch **
20 Min.
10 Min.
10 Min.
20 Min.
45 Min.
10 Min.
10 Min.
15 Min.
10 Min.
1 Hour
Training Session III
30 Min.
- Building Field Attribute Rules - Building SQL Rules - Field Attributes - SQL Rules ** Break **
15 Min.
15 Min.
30 Min.
5 Min.
25 Min.
10 Min.
Training Session IV
1 Hour
- Building Audit Rules - Building Extensions -
30 Min.
30 Min.
1 Hour
5 Min.
25 Min.
30 Min.
15 Min.
30 Min.
Lab I
Lab II
Lab III
Lab IV
- Field Attributes - Audits - Extensions ** Break **
Training Session V
- Using Rule Migration - Troubleshoot/Support - Review Best Practices -
10 Min.
10 Min.
10 Min.
______________________________________________________________________________________

Architecture
AppsRules is completely integrated with Oracle Applications by storing rule definitions
in the Oracle database, and executing those rules using Oracles Custom Library. Because
the AppsRules Engine is called from the Custom Library rules setup in AppsRules are not
affected by upgrades or patches to Oracle.
The integration between Oracle Application, Oracle Forms, Oracle Customer Library,
AppsRules, and the Oracle Database is illustrated below.
______________________________________________________________________________________

Structure
AppsRules Process Flow
The highest structure of AppsRules can be described in three general components:
Oracles Custom Library
AppsRules Rule Engine
Rules stored in the database
Oracle calls the custom library for every form you use. AppsRules uses the custom
library to call the rule engine. AppsRules has modified the Custom Library to call a
database package and its own attached library our AppsRules engine. This package
then reads the business rules/zooms defined in the AppsRules data entry form and passes
the instructions back to the Custom Library. The Custom Library accepts the instructions
and dynamically enables the desired behavior..
Process Flow
______________________________________________________________________________________

Step 1.0
Step 2.0
Step 3.0
Step 4.0
Step 5.0
Enter Rule Name

Enter Rule name. AppsRules allows you to group your individual Rules
under one blanket rule name. Typically, organizations prefer to organize their
rules by module.
Enter Rule Elements
Identify Form Name to be included in the rule
Identify Event, which determines when the new business rule will execute.
AppsRules supports both documented Custom library calls and
undocumented calls (see the Undocumented Events for more details on
this.)
Event Tracker
When New Form
When New Block
When New Item
When New Record
When Validate Record
Audit
Undocumented Events
List Subscriber
Define target to which the rule applies.
Rules and Rule Elements can target:
Responsibilities
Profiles
Operating Units
Inventory Organizations
Users
Data
Capture Metadata Elements on Target Form
Touch each field and tab that you would like to secure; this will add that field,
block, and tab to the metadata repository.
Enter Rule Details

Define Rules at the field, record and form level
______________________________________________________________________________________

Step 5.1
Step 5.2
Step 5.3
Security Rule
This rule controls who can see, create transactions and update key data
elements
Navigation Rule
This tool allows you to create new navigation rule from Tools Menu
and Zoom button to link forms together and streamline process.
Message Rule
This rule allows you to create messages to alert users.
It allows users to get notified if certain data conditions exist, work
instructions, or other critical information
Step 5.4
Default Value Rule
This rule allows you to populate fields with default values on any
Oracle Applications form.
Fields can be populated using either a static list or a SQL statement.
Step 5.5
Step 5.6
Step 5.7
Step 5.8
List of Values Rule

This rule allows you to both alter List of Values for fields that
currently use an LOV and assign a new LOV to fields that are freeform text.
Field Attributes Rule
This rule allows you to alter the Prompt Text associated to a specific
field and/or alter the Next Navigation Field.
SQL Rule
This rule allows your organization with the flexibility to write any
types of rules required to solve a specific business problem.
It allows you to create rules as if you were actually creating a new
program unit inside a form or library
Audit Rule
This field allows you to create audit rules to monitor changes to key
field in the Oracle Application forms.
All Logical Apps Audits are stored within a single table enabling easy
reporting. Reporting is handled in two different ways:
Using a seeded Logical Apps Audit Detail Report
______________________________________________________________________________________
Step 5.9
Step 6.0
AppsExtend
AppsExtend allows for the rapid development of simple custom forms.
These forms allow for the extension of currently defined Oracle Forms.
Test Rule
Step 7.0
Use online auditing queries available through a new form
AppsRule provides debug option
Migrate Rule
Logical Apps provides a solution to migrate these rules from one

instance to the other from the AppsRules tools menu.
Entire rules can be migrated or individual elements of the rule.
These rules are sent using XML files and not by creating database
links.
______________________________________________________________________________________
10

Part 1 Rule Definition
AppsRules Rules, Elements, Subscribers, Build Metadata
Create Apps Rule - (Level 1 Process Flow)
5.0
Rule Details
5.1
Security Rule
5.2
Navigation
Rule
5.3
Message
Rules
Apps Rule
5.4
Default Value
Rule
1.0
Rule Name
2.0
Rule
Elements
3.0
Subscriber
4.0
Capture
Metadata
Element on
Target Form
5.5
List of Values
Rule
6.0
Test Rule
7.0
Migrate Rule
5.6
Field Attribute
Rule
5.7
SQL Rule
5.8
Audit Rule
5.9
AppsExtend
This section describes the initial structure for AppsRules. Users will learn how to group
rules together and target the business rules at specific groups.
Before defining the rule, youll need to know the form name you want to apply the rule
to. The most accurate way to do this is:
Navigate to the form you want to create a rule for

Select Help>About Oracle Applications scroll down until you see Form Name
Write down, or copy the Form Name. In this example, you would write down
APXDMVD
______________________________________________________________________________________
11
Creating a New Rule

Rules are comprised of Rule Elements, Subscribers, and Details. To create a new Rule,
follow these steps:
Select and Open AppsRules from the Oracle Applications Navigation Window:
Step 1 Define Rule

______________________________________________________________________________________
12
Enter a Rule Name

o Typically, organizations prefer to organize their rules by module with
names like AR Rules or OM Rules
Enter a Description for the rule
Verify the Active flag is selected
Verify the Debug flag is not selected. For use of the debug flag, see Part 11,
Support)
The Subscribers Exist check box will only be selected when subscribers have
been assigned to this rule
Step 2 Define a Rule Subscriber

Click Rule Subscribers
Select value from the When column
o The When column determines when a rule will be used. For instance,
when you want the rule to apply to a specific responsibility, you would
select Responsibility. The choices are:
1. Responsibility
2. Operating Unit
3. Profile
4. Inventory Org
5. User
6. Data
7. Subscriber List
8. AppsFlow
When building a new rule you should assign yourself as the User Subscriber. This
way the rule will only apply to you while building and testing and not affect others. See
figure 1.3.1.
Figure 1.3.1.
______________________________________________________________________________________
13

Step 3 Define Rule Element
Enter the Form Name
o The User Form Name will be populated automatically
o If you do not know the Form Name, you may select a User Form Name
instead
Select the Event **Event Tracker.
o The Event field determines when the business rule will execute. The
following are events used in the standard Oracle forms:
1. When New Form fires when the form first opens
2. When New Block fires when navigate to a new block
3. When New Record fires when navigate to a new record
4. When New Item fires when navigate to a new field
o The following are Events created by AppsRules:

1. **Event Tracker Tracks and builds metadata from each field that
is touched
2. The Audit Event Tracks and logs all changes to fields
3. Zoom Special Special Zoom Validation
Verify that the Active check box is selected for the Rule Element and the Rule.
See figure 1.2.1.
Figure 1.2.1
______________________________________________________________________________________
14

Step 4 Build Metadata
While the Event Tracker is on, you need to navigate to the form and click in the fields
you plan to create rules for.
For example:
Navigate to the Suppliers form

Click on each field and tab that you would like to secure; this will add that field,
block, and tab to the AppsRules metadata repository for this target form
o 11i Users can start building rules immediately. Place the cursor on a field
that you wish to secure and select the appropriate rule directly from the
AppsRules Actions menu. Currently the Action rules are only security
rules. See Figure 1.4.1.
Figure 1.4.1
Step 5 View new Events
Back in AppsRules we now have additional metadata about the target form.
______________________________________________________________________________________
15
Locate your Rule

Select the Events LOV, note the Events available to you
o In the next section, we will change the Event from **Event Tracker to the
most applicable event for your new rule to execute.
o If you created rules using the AppsRules Actions menu when the **Event
Tracker was on, you will see these rules in the Details.
______________________________________________________________________________________
16

Event Definitions
You can change your event at any time. We will use the Requisition form as an example
to help distinguish when certain events are best suited.
PO_REQ_HDR block
Item
Record
LINES block
Below are general guidelines to follow when selecting the Event:
When New Form this fires once when the form is first opened. If you select this
event there is no need to enter any additional data in the Block Name and Field
fields.
o Example: As soon as the Requisitions form is opened, the rule elements
will execute. So if you have a rule that hides the Rev field in the LINES
block, it will not be visible to the user when the form opens.
When New Block this fires each time your cursor lands on a new block. If you
enter a block name for this event, it will only execute the rule if the cursor is in
the specified block.
o Example: If the rule hides the Rev field in the LINES block, the Rev field
will be visible when the form opens, but if the user clicks anywhere in the
LINES block, it will hide.
When New Item this fires each time your cursor lands on a new field. You may
choose to specify both a block name and field for this event to restrict the rule
execution to only when this event fires on a specific field.
o Example: We want to require the Rev field if the item entered is a certain
product line. We could not use a When New Form or When New Block
event because we do not know the item until they have entered it. Using
When New Item, when the user clicks in the Rev field it will execute the
rule.
______________________________________________________________________________________
17
When New Record this fires each time your cursor navigates to a new record.
This event will for fire for both new records and existing records. The block
name can be entered if you wish to restrict the rule execution to only a specific
block.
o Example: We want to default the requestor for each new record.
When Validate Record this fires for each record that is being saved. This event
will also usually fire each time you leave a record. The block name can be
entered if you wish to restrict the rule execution to only a specific block.
o Example: If the requisition exceeds a certain amount, pop up a message
that tells the user it will first
Audit Audit is a special Logical Apps event that will track all changes made to a
specified form.
o Its highly advised that users specify a block name for Audit type rules.
Without specifying the block all changes to the form will be tracked.
o The Audit event is designed to fire using the events When New Record
and When Validate Record. These are standard event calls that are
supported by Oracle and must exist in a form for the audit feature to work
properly.
o Note that many of the FND type forms (Define Application User,
Define Responsibility, etc) currently do not make this event call.
Other Events you may see Undocumented event calls in the Event LOV. This
is by design; when your *Event Tracker event is turned on it captures all the event
calls that are being deployed to the custom.pll.
o You may use these special events, however, Oracle does not support these
events and you may discover that after a patch that these special events
suddenly disappear.
o Logical Apps does not discourage the use of these event calls, but
encourages users to work with the standard event calls when possible.
______________________________________________________________________________________
18

Part 2 Security Rules
AppsRules Developing Security Rules
5.0
Rule Details
5.1
Security Rule
5.2
Navigation
Rule
Apps Rule
5.3
Message
Rules
5.4
Default Value
Rule
1.0
Rule Name
2.0
Rule
Elements
3.0
Subscriber
4.0
Capture
Metadata
Element on
Target Form
5.5
List of Values
Rule
6.0
Test Rule
7.0
Migrate Rule
5.6
Field Attribute
Rule
5.7
SQL Rule
5.8
Audit Rule
5.9
AppsExtend
This section describes how to develop security rules at the field, record, and form levels.
Users will learn how to deploy advanced security rules to control who can view, create,
transact, and update key data elements.
When to Use this Rule?
Typically, security rules are set when the form first opens or when a specific block is
navigated to. Use the events When New Form or When New Block.
Create and Deploy Security Rules
Using the rule created in Part 1, we will continue defining the rule element.
Select the event When New Block for the rule element created in Part 1
o After using the **Event Tracker, you always return to the rule element and
change it to the most appropriate Event
Click Details
______________________________________________________________________________________
19
From the Type pop list, select Field

From the Block/Tab, select a block from the available list of values
o All blocks you clicked in while **Event Tracker was on will be listed
o Note that this list of values is not enforced, you may type the block name
From the Field Name, select the field you would like to apply a security rule to
Select any of the security rules. See figure 2.1.1.
o Required
o No Update
o No Insert
o No Delete
o Hide
Verify Active is selected
Figure 2.1.1
In the above example, we created a security rule based on a Field type. The different
rule types and associated security rules that can be created are as follows:
Field
Hide a Field
Prevent Update to a Field
Prevent Insert to a Field
Make a Field Required
Enforce Upper/Lower Case
Tab
Hide a Tab (11i)
Form
Prevent Update to a Form
______________________________________________________________________________________
20
Prevent Insert to a Form

Block
Prevent Insert to Block
Prevent Update to Block
Prevent Delete to Block
Filter data using a default where clause
Alter the Order by (11i)
Defining Block Security Rule

When defining a Block rule type, two new fields appear at the bottom of the canvas,
Default Where and Order By, see figure 2.6.3
o Default Where the Default Where field will filter the data that is returned to
that block. Change the Default Where when you need to filter the data that
someone can see
The statement should start with Where and specify a base table
field in the where condition. A base table field is a field that exists in
the table the block is based on. (This is usually slightly different than
the related field name on the form.)
o Order By the Order By field will order the data that is returned to that block.
The statement should start with Order by and specify the base table
fields to order by separated by commas
*Note: Some forms that use Folders frequently reset the default where rules. Logical
Apps is currently working with Oracle Development to add the event PRE-QUERY to
overcome this limitation (11.5.10 Oracle Release).
______________________________________________________________________________________
21
Figure 2.6.3
Creating Multiple Security Rules
Its very possible that many rules are deployed on the same form and event. AppsRules
provides a quick way of creating multiple security rules at once.
Select Security tab

From the menu, select Tools>Elements
All fields you clicked on while the **Event Tracker was enabled are displayed,
see figure 2.6.2
Include all desired fields
- To include all fields, click Select All, then click Accept
- To include specific fields, select the Include Flag, then click Accept
All the selected fields will drop into the Security canvas where the rule configuration
can be completed.
______________________________________________________________________________________
22
Figure 2.6.2
Lab#1 Building Security Rules
______________________________________________________________________________________
23

Part 3 Navigation Rules
AppsRules Developing Navigation Rules
5.0
Rule Details
5.1
Security Rule
5.2
Navigation
Rule
Apps Rule
5.3
Message
Rules
5.4
Default Value
Rule
1.0
Rule Name
2.0
Rule
Elements
3.0
Subscriber
4.0
Capture
Metadata
Element on
Target Form
5.5
List of Values
Rule
6.0
Test Rule
7.0
Migrate Rule
5.6
Field Attribute
Rule
5.7
SQL Rule
5.8
Audit Rule
5.9
AppsExtend
This section describes how to develop navigation rules. Users will learn how to link
forms together and streamline the navigational experience.
AppsRules allows you to create new navigation rules from your Tools menu and Zoom
button. There are a few noted differences between 11.0.3 and 11i:
Release 11.0.3
Tools menu is referred to as the Special menu
Oracle allows the addition of up to 15 Special Menu entries
Release 11i
Oracle allows the addition of up to 45 Tool Menu entries.
Tools 1-15 are enabled within the Forms Tools menu
Tools 16-30 is enabled within the Forms Reports menu
______________________________________________________________________________________
24

Tools 31-45 is enabled within the Forms Actions menu
New entries can append or overwrite the seeded menu entries from Oracle. It may be
desirable to overwrite an existing Tools menu entry if you wish the end user to not have
that ability.
Typically, navigation rules are set when the form is first opened. Use the event When
New Form.
The target form you plan to navigate to must be available in the responsibility you
access it from. In other words, if you do not have access to a specific form then the Tools
menu will not allow you to navigate there.
(You can add a function to a menu without displaying the actual function on the menu
screen by omitting the prompt for that particular sequence.)
Create and Deploy Navigation Rules
Adding to the Menu
Select Navigation tab

In Sequence, select the tools menu sequence
o If you do not want to overwrite an existing Oracle menu entry, start
with a high menu entry, such as Tools 45, and work towards the lower
menu entries
Enter a Label
o This is what shows up in the Tools menu
Select function name for the function you intend on navigating to
o List of values will show user form name and short form name
o Figure 3.1.1. shows example of Purchase Order Summary Screen
Leave Parameters blank
o Parameters can alter the functionality for a specific form, use to pass in
values to the target form
o QUERY_ONLY=YES. Passing this parameter will cause the target
form to appear in query only mode.
Use default Icon Name
o Optionally provide a new icon name (11i) that will be added to your
toolbar while in the target form. It should be noted that enabling a
new icon does add extra overhead to the rule. See figure 3.1.1.
Leave default for BizRules Action
o Will be selected when defining concurrent programs (instead of forms)
______________________________________________________________________________________
25
Figure 3.1.1
Defining a Zoom
The Zooms region allows users to define a Zoom from a block to another form. If a
zoom is enabled, the
key will be enabled and provide for a quick link between the
block and a new form.
Enter From Block

o Enter block where zoom is active
Select function name for the function you intend on navigating to
o List of values will show user form name and short form name
Leave Parameters blank
o Parameters can alter the functionality for a specific form, use to pass in
values to the target form
o QUERY_ONLY=YES. Passing this parameter will cause the target
form to appear in query only mode.
You may only have a single zoom per block making the menu rules much more
powerful.
______________________________________________________________________________________
26
Lab#2 Navigation Rules
______________________________________________________________________________________
27

Part 4 Message Rules
AppsRules Developing Message Rules
5.0
Rule Details
5.1
Security Rule
5.2
Navigation
Rule
Apps Rule
5.3
Message
Rules
5.4
Default Value
Rule
1.0
Rule Name
2.0
Rule
Elements
3.0
Subscriber
4.0
Capture
Metadata
Element on
Target Form
5.5
List of Values
Rule
6.0
Test Rule
7.0
Migrate Rule
5.6
Field Attribute
Rule
5.7
SQL Rule
5.8
Audit Rule
5.9
AppsExtend
This section describes how to develop informative message rules. With messages, we
can notify users if certain data conditions exist, give work instructions, or other critical
information.
Typically, messages are set when the form is first opened or when a specific field is
navigated to. Use the events When New Form and When New Item (for When New Item
specify the block name and field).
Create and Deploy Message Rules
Click Messages tab

Enter Sequence
o Messages will display in the order of the sequence
Enter Description of Message
In the Message box, type the message you would like to show users, see figure 5.1.1
______________________________________________________________________________________
28

o Messages can be based on any of the Events in the Rule Elements form
o Since our Rule Element has an Event of When New Form, this message will
pop up as soon as the user opens the form
Messages can also be based on data conditions. For example, you may want a
promotional message to pop up when a user enters a certain item on an order. To do this,
define a Data Element Subscriber and setup the conditions you want to check.
Tip: To alert everyone when the system is about to go down, select the form name
All Application Forms and the event When New Form. When any form is opened, the
message will appear.
Figure 5.1.1
All messages display as a Note type of message. Users must acknowledge the message
prior to continuing, see figure 5.1.2
Figure 5.1.2
______________________________________________________________________________________
29
Lab#3 Messaging Rules
Part 5 Default Value Rules

AppsRules Developing Default Value Rules
5.0
Rule Details
5.1
Security Rule
5.2
Navigation
Rule
Apps Rule
5.3
Message
Rules
5.4
Default Value
Rule
1.0
Rule Name
2.0
Rule
Elements
3.0
Subscriber
4.0
Capture
Metadata
Element on
Target Form
5.5
List of Values
Rule
6.0
Test Rule
7.0
Migrate Rule
5.6
Field Attribute
Rule
5.7
SQL Rule
5.8
Audit Rule
5.9
AppsExtend
This section describes how to develop default value rules. With default value rules, we
can default information into fields on a form with static, SQL or form default types.
______________________________________________________________________________________
30

Typically default values are set are set when the form is first opened or when a specific
field is navigated to. Use the events When New Form and When New Item (for When
New Item specify the block name and field)
Scenario
We want the Alternate Name in the Supplier field to default from the Supplier name,
once we navigate out of the Supplier Name field.
Steps - Create and Deploy Default Value Rules
Click Default Values tab

Enter Block Name VNDR
o Block where field you plan to default value exists
Enter Field Name VENDOR_NAME_ALT_MIR
o Form field name you want to default value into
Enter Default Type FORM
o Static The value you type in Default Value field will be defaulted
o SQL Select a SQL rule that will return a value to be defaulted
o Form Enter the block and field to default the value from
Enter Default Value VNDR.VENDOR_NAME_MIR
o Block and field name to default value from
5.1.1
Lab#4 Default Value Rules
______________________________________________________________________________________
31

Part 6 List of Value Rules
AppsRules Developing LOV Rules
5.0
Rule Details
5.1
Security Rule
5.2
Navigation
Rule
Apps Rule
5.3
Message
Rules
5.4
Default Value
Rule
1.0
Rule Name
2.0
Rule
Elements
3.0
Subscriber
4.0
Capture
Metadata
Element on
Target Form
5.5
List of Values
Rule
6.0
Test Rule
7.0
Migrate Rule
5.6
Field Attribute
Rule
5.7
SQL Rule
5.8
Audit Rule
5.9
AppsExtend
This section describes how to develop rules that will both alter and create new List of
Values. Users will learn how to filter the data in current List of Values and assign new
List of Values to fields that are currently free-form text.
Typically LOVs are set when the form is first opened or when a block is navigated to.
Use the events When New Form and When New Block.
Create and Deploy LOV Rules
AppsRules allows you alter List of Values for fields that currently use an LOV and assign
a new LOV to fields that are free-form text. Below are instructions for altering an LOV
and for adding a new LOV.
______________________________________________________________________________________
32

Prerequisite
Before altering or creating a new LOV, it is critical that you first run the **Event Tracker
and click on any fields that you wish to apply an LOV rule to in your target form.
Alter LOV
Navigate to Form and click in field that has LOV you want to change
Turn Trace on by selecting Help>Diagnostics>Trace>Regular Trace from the
menu
o This will run a trace on the everything you do in the form, it will get us the
Select statement used to create the LOV
Select any value from the available LOV of the field you want to change
Turn trace off by selecting Help>Diagnostics>Trace>Regular Trace from the
menu
Navigate back to AppsRules, find your rule and select the List of Values tab
Enter Block Name where LOV exists
Enter Field Name that has the existing LOV you want to change
Record Group and LOV Name will default
Select Create TKPROF Trace File from the LogicalApps Utilities menu
o This will launch a concurrent program to translate the trace file you
created.
View your concurrent requests and upon completion, view the contents of the log
file. Search for the SQL that was executed to run your LOV
Copy the SQL statement directly into the SQL Text field within the LOV
configuration.
o If bind variables exist in this statement (you can identify a bind variable as
it will say something like :1 or :5) then it may be required to open the form
to identify the actual SQL that is being executed
o Modify the Where and/or Order by clause of the SQL statement
Verify Active flag is selected
When altering an existing LOV, the columns returned cannot be changed, only the
Where and Order by
______________________________________________________________________________________
33
Figure 6.1.1
The record group in figure 6.1.1 is actually VENDOR_TYPES, AppsRules

automatically appends LA_ to the front.
Create New LOV

Run the **Event Tracker for the fields you plan to create new LOVs for
o Be sure to change the Event back to appropriate event
Navigate back to AppsRules, find your rule and select the List of Values tab
Enter Block Name where LOV exists
Enter Field Name that has the existing LOV you want to change
Record Group will default with the field name prefixed by LA_
LOV Name will default to APPCORE_ZOOM
A template of the SQL text will appear, alter the SQL text as necessary. You may
create a static list, or select from a table or view.
o Columns must have an alias of Name and Value
Examples of each follow:
o Figure 6.1.2 shows example of template for selecting static values
o Figure 6.1.3 shows example of selecting from a table
______________________________________________________________________________________
34
Figure 6.1.2
To create multiple values in your static LOV, use the UNION statement. Example:
SELECT High NAME, High VALUE FROM DUAL
UNION
SELECT Medium NAME, Medium VALUE FROM DUAL
UNION
SELECT Low NAME, Low VALUE FROM DUAL
______________________________________________________________________________________
35
Figure 6.1.3
Lab#5 List of Values Rules
______________________________________________________________________________________
36

Part 7 Field Attribute Rules
AppsRules Developing Field Attribute Rules
5.0
Rule Details
5.1
Security Rule
5.2
Navigation
Rule
Apps Rule
5.3
Message
Rules
5.4
Default Value
Rule
1.0
Rule Name
2.0
Rule
Elements
3.0
Subscriber
4.0
Capture
Metadata
Element on
Target Form
5.5
List of Values
Rule
6.0
Test Rule
7.0
Migrate Rule
5.6
Field Attribute
Rule
5.7
SQL Rule
5.8
Audit Rule
5.9
AppsExtend
In this section well see how AppsRules can easily change the order in which fields are
navigated to when using the Tab key on the keyboard. Well also change a field prompt
to something more descriptive to you.
Typically Field Attribute rules are set when the form is first opened. Use the event When
New Form.
Scenario:
In this example, we want to change the prompt of the END_DATE_ACTIVE_MIR field
on the VNDR block of the Supplier form from Inactive On to Last Order Date. Also,
when the user tabs out of the Last Order Date field, we want to go directly to the Invoice
Amount Limit field, see figure 7.1.1
Steps Change tab order and field prompt
Select Field Attributes tab
______________________________________________________________________________________
37
Enter Block Name VNDR

o Block where field you plan to change exists
Enter Field Name END_DATE_ACTIVE_MIR
o Form field name you want to change prompt for
For the Prompt Text, enter Last Order Date
o This will change the prompt from Inactive On to Last Order Date
Enter Next Navigation Field INVOICE_AMOUNT_LIMIT
o This is the field that will get focus after Last Order Date when user hits Tab
key on keyboard
Figure 7.1.1
Lab#6 Field Attribute Rules
______________________________________________________________________________________
38

Part 8 SQL Rules
AppsRules Developing SQL Rules
5.0
Rule Details
5.1
Security Rule
5.2
Navigation
Rule
5.3
Message
Rules
Apps Rule
5.4
Default Value
Rule
1.0
Rule Name
2.0
Rule
Elements
3.0
Subscriber
4.0
Capture
Metadata
Element on
Target Form
5.5
List of Values
Rule
6.0
Test Rule
7.0
Migrate Rule
5.6
Field Attribute
Rule
5.7
SQL Rule
5.8
Audit Rule
5.9
AppsExtend
This section describes how to develop your own company specific rules using the SQL
function. SQL rules provide your organization with the flexibility to write any types of
rules required to solve a specific business problem.
Create and Deploy SQL Rules
AppsRules allows you to create rules as if you were actually creating a new program unit
inside of a form or library.
Navigate to SQL tab

Enter Sequence Number
o This is the order in which the procedures will execute
Enter a Procedure Name
Modify the PL/SQL template in the SQL Text box
o You may not reference form bind variables directly in this window
o To reference a field you must use the name_in function, see figure 8.1.1
o Declare variables before the BEGIN statement
Click Compile
______________________________________________________________________________________
39
o Launches a concurrent program to compile the code

o Validates the SQL is syntactically correct
Review concurrent Program log for errors
If success, Exit Oracle Applications and log back in
o SQL rules are implemented via the custom library, which may be cached
when you log in. To test recently compiled rules log out and log in to the
application.
All active SQL rules will be compiled, not just yours. Be sure to check the log to
ensure everything compiled successfully
Figure 7.1.1
In release 11.03 may not create cursor loops
A link to the Logical Apps Business Rule forum is available directly from the
tools menu. Here you will find some practical examples of code you could use. Logical
Apps asks that you contribute code to make this a real collaboration area to help
everyone.
______________________________________________________________________________________
40
Lab#7 SQL Rules
______________________________________________________________________________________
41

Part 9 Audit Rules
AppsRules Developing Audit Rules
5.0
Rule Details
5.1
Security Rule
5.2
Navigation
Rule
Apps Rule
5.3
Message
Rules
5.4
Default Value
Rule
1.0
Rule Name
2.0
Rule
Elements
3.0
Subscriber
4.0
Capture
Metadata
Element on
Target Form
5.5
List of Values
Rule
6.0
Test Rule
7.0
Migrate Rule
5.6
Field Attribute
Rule
5.7
SQL Rule
5.8
Audit Rule
5.9
AppsExtend
This section describes how to develop form level audits. All Logical Apps Audits are
stored within a single table enabling easy reporting. Reporting is handled two different
ways:
1. A seeded Logical Apps Audit Detail Report is available
2. Online Audit Query is available through a form
Audit data is stored in LA_BR_AUDIT_HISTORY
Create and Deploy Audit Rules
AppsRules allows you to create audit rules to monitor changes to key fields in Oracle
Application forms.
Step 1 Create Audit Rule
Navigate to AppsRules and create a new Rule
Create a new Rule Element with form to audit
Select Event Audit
Enter Block Name to audit
______________________________________________________________________________________
42
o Although the block is not required, Logical Apps highly advises selecting
the block name, see figure 9.1.1
Verify Rule and Rule Element are Active
Figure 9.1.1
Step 2 Create Audit Rule Details
Click Details
Enter Block Name to audit
Enter Field Name to audit
Enter Record Keys to uniquely identify the audit record
o For example, if I am auditing Suppliers I would want to identify a Supplier
by their name and number.
o Prefix Record Key with the block name (for example, BLOCK.FIELD),
see figure 9.1.2
Verify Active Flag is selected
Defining more than two record keys
If more than two record keys are required to uniquely identify a transaction follow these
instructions:
Click inside of either Record Key1 or Record Key2

Select Tools>Special>Define Multiple Record Keys
You may enter up to four record keys in this region
o The record keys will become concatenated with ~
______________________________________________________________________________________
43
Figure 9.1.2
Step 3 Compile Audit Data
Make change to field you are auditing

Navigate to AppsRules
Select Tools>Compile Audit History, see figure 9.1.3
You can also schedule Audit history compilation.
______________________________________________________________________________________
44
Figure 9.1.3
Step 3 Linking History to the Entity
AppsRules allows you to link the audit history to the form being audited, using a
Navigation rule.
Create a new Rule

Create a Rule Element with Event When New Form, see figure 9.1.4
______________________________________________________________________________________
45
Figure 9.1.4
Click Details
Select a Tools Sequence
o This will be the link that opens the audit form
Enter Label users will see
Select the Logical Apps AppsRules Audit in the To Function, see 9.1.5
______________________________________________________________________________________
46
9.1.5
Enter parameters so the form will automatically query up our audit history for the
specific entity.
o The parameters we pass are the form_name, record_key1, and
record_key2. See figure 9.1.6
9.1.6
Form Name must be surrounded with quotes. Example: APXDMVD

Variables must be surrounded by pound signs. Example: #VNDR.VENDOR_ID#
The Logical Apps AppsRules Audit function must be in the responsibility that will
access this form. For the above example - I would add this function to the purchasing
menus.
______________________________________________________________________________________
47

Step 4 Viewing History from the form
Navigate to target form

Select the menu you created your link in, see figure 9.1.7
Figure 9.1.7
______________________________________________________________________________________
48

AppsRules Viewing Audit History
This section describes how to view your audit history both online and through a
concurrent report.
Viewing Online
Open Form where Audit Rule is enabled

Select Tools>Special>Audit History
o Must be enabled to view from Tools menu
All audit history will be shown in the from, see figure 9.1.8
Figure 9.1.8
Click the flashlight icon to open a find window, see figure 9.1.9
o The find window will restrict your selection criteria to the parameters
passed. Most fields have a LOV to select from.
o Fields that do not have an LOV may be searched using the wild card. For
example, to find all audit history for record_key1 that starts with A, type
A% in the Record Key1 field and click Find.
______________________________________________________________________________________
49
Figure 9.1.9
Click Find
To export data, select File>Export
The Logical Apps AppsRules Audit form function may be added to any menu
structure to perform audit queries across all audit records.
Standard Report Submission
Audit History may also be accessed through standard report submission. The report
Logical Apps AppsRules Audit Detail Report is available with parameters as shows in
figure 9.2.0.
______________________________________________________________________________________
50
Figure 9.2.0.
None of the above parameters are required, however, it is recommended that you at least
specify the Audit Rule.
The Audit Rule contains an LOV and should descriptively name the audit rule.
Once the Audit Rule is specified, the Rule Element Description will enable and
contain descriptions for each of the element for the Audit Rule specified.
Field Name will be enabled if the Rule Element Description is populated. This
parameter will contain all the enabled audit fields for the rule and rule element
specified above.
The Responsibility parameter is always enabled. If you would like to filter the
reporting to see the changes that a specific responsibility made then populate this
parameter.
Record Key1 and Record Key2 uniquely identify an audit history transaction with
a specific record. These parameters contain a list of values from your actual audit
history. If you are attempting to run an audit history report for a specific record,
such as a distinct account combination, and the account combination is one of the
record keys, then it can be entered right here. If the parameter does not validate it
means that you have no data for that specific record key.
The User parameter is always enabled and allows you to search for audit history
made by a specific user.
The Creation Start and End Dates will filter the report to only audit records that
have been transacted between these dates.
The report output will look similar to figure 9.2.1.
______________________________________________________________________________________
51
Figure 9.2.1
Lab#8 Audit Rules
______________________________________________________________________________________
52

Part 10 AppsExtend
AppsRules Developing New Forms
5.0
Rule Details
5.1
Security Rule
5.2
Navigation
Rule
Apps Rule
5.3
Message
Rules
5.4
Default Value
Rule
1.0
Rule Name
2.0
Rule
Elements
3.0
Subscriber
4.0
Capture
Metadata
Element on
Target Form
5.5
List of Values
Rule
6.0
Test Rule
7.0
Migrate Rule
5.6
Field Attribute
Rule
5.7
SQL Rule
5.8
Audit Rule
5.9
AppsExtend
This section describes how you can configure new forms using the AppsExtend feature in
AppsRules. AppsExtend allows for the configuration of a new form using Business
Rules.
______________________________________________________________________________________
53

Create and Deploy Extensions using AppsExtend
AppsRules allows you to configure new forms using AppsExtend. AppsExtend relies
heavily on AppsRules for the successful configuration of new forms.
AppsExtend
1.0
Create
Extension
Form
Create LOV for

AppsExtend
Field?
NO
4.0
Create Navigation
to link to
Extension Form
Yes
2.0
Create LOV
3.0
Link LOV to
Extension
Form
Step1 Create AppsExtend Form

Navigate to AppsRules and select the AppsExtend tab
Enter an Extension Name (**Remember Extension Name!)
Enter a Description for your Extension
Select Attributes to store your new form data in
o Attributes1 15 are available (Attributes in Apps Extend are not the same
as attributes used by Oracle Flexfields)
Subscribers are the key differentiator between Flexfields and Extension Elements.
For instance, if you want to require additional information, but only for certain items, you
could setup a subscriber for the Extension form with those requirements.
Enter Label that will be shown on the new form

Select Enabled
Select Required if needed
If you would like an LOV to be attached to this field, verify Enable LOV is
selected and see Step 2
______________________________________________________________________________________
54
Figure 10.1.1
Step2 (Optional) Create LOV for AppsExtend Field
You can configure the LOVs used by AppsExtend by simply creating a LOV rule for this
form.
Create New LOV
Create a new Rule
o Rule will be specifically setup to create a List of Values that can be used
on your Extension Form, see figure 10.1.2
______________________________________________________________________________________
55
Figure 10.1.2
Click Rule Subscribers - **Very Important! If you do not create a Data Rule
Subscriber, the LOV will be attached to all AppsExtend forms, see figure 10.1.3.
Figure 10.1.3
Enter the following data:

o When = Data
o Profile/Data = PARAMETER.EXTENSION_TYPE
o Condition = Equal
o Value is blank
o Data Dependent Values = <Type your AppsExtend form name>
o Keep defaults for the rest of the fields
______________________________________________________________________________________
56
Create Rule Element

o Form Name = LAAEELM
o User Form Name will auto populate
o Event = When New Item
o Block Name = LA_EXTENSION_VALUES
o Filed Name = <AttributeN> (Enter Attribute you created in Extension
Form)
Be sure Rule Name and Rule Element are Active
Click Details
Click List of Values tab
o Block Name = LA_EXTENSION_VALUES
o Filed Name = <AttributeN> (Enter Attribute you created in Extension
Form)
o Record Group and LOV Name should auto populate
o Enter SQL text to form your LOV, see Part 6 for Developing LOV Rules.
Example in figure 10.1.4
Save Rule
Figure 10.1.4
Step3 Link Extension Form
Next, this new Extension needs to be linked to the entity. Well create a new rule in
AppsRules to link the Supplier form to this newly configured AppsExtend form.
Create a new Rule, with the Event When New Form

______________________________________________________________________________________
57
Select the tools menu sequence

Enter a Label
o Example: Supplier Quality Rating, see 10.1.5
Select AppsExtend Value Form as the function name
Enter Parameters
o Pass Extension Type parameter, this will be the Extension Name you
created in Step1
o Pass primary keys that link the extension data to form. You can have up
to two keys:
Disposition_ID
Distposition_ID2
o Example: EXTENSION_TYPE = Supplier Quality Rating
DISPOSITION_ID = #VNDR.VENDOR_ID#
Use default Icon Name
Leave default for BizRules Action
Click Done
Figure 10.1.5
Step3 View AppsExtend Form
Navigate to form you setup in Step3.

o In this example, the Supplier form
Select the new AppsExtend form from menu
______________________________________________________________________________________
58

o In this example, Supplier Quality Rating, see figure 10.1.6
Figure 10.1.6
Extension definitions are stored in LA_EXTENSION_ELEMENTS and Extension

values are stored in LA_EXTENSION_VALUES
Lab#9 Extension Rules
______________________________________________________________________________________
59

Part 11 AppsFlow Integration
AppsRules Executing Workflows using AppsFlow from
AppsRules
This section will describe how AppsFlow workflows can be launched directly from
AppsRules. If you have not purchased or installed AppsFlow then disregard this section.
Create and Deploy Navigation Rules
AppsRules allows you to use the same form events to also launch AppsFlow processes.
AppsFlow processes are configured workflows, such as a New Supplier Process, that
can enforce setup configurations, enforce approval processes, or just FYI notifications.
To link a form event to an AppsFlow process:
Create a Rule and Rule Element with the desired Event
Select Details
Select AppsFlow tab
o Note if no AppsFlow processes are defined then this tab will not be
displayed.
Enter Sequence to run process flows
Select Process from Process LOV
Figure 11.1.1 shows the AppsFlow we are linking to in this example
o Note the Table Name and Primary Keys
Figure 11.1.1
______________________________________________________________________________________
60
Type = Form
Enter Disposition values
o In this example, we only have one primary key, so we only need to fill
in Disposition_ID1. Enter the TABLE_NAME.PRIMARY_KEY
from the flow you are linking, see figure 11.1.2
o You may also pass static values
Figure 11.1.2
______________________________________________________________________________________
61

Part 12 - AppsRules Migrating Rules
5.0
Rule Details
5.1
Security Rule
5.2
Navigation
Rule
5.3
Message
Rules
Apps Rule
5.4
Default Value
Rule
1.0
Rule Name
2.0
Rule
Elements
3.0
Subscriber
4.0
Capture
Metadata
Element on
Target Form
5.5
List of Values
Rule
6.0
Test Rule
7.0
Migrate Rule
5.6
Field Attribute
Rule
5.7
SQL Rule
5.8
Audit Rule
5.9
AppsExtend
This section describes how you can migrate your rules from one instance to another. The
migration feature is a push from the source instance to a target instance.
Configure the migration machines and instances
AppsRules allows you to configure the instances and machines where the target instances
reside. The configurations are probably best configured by the DBA. To configure:
Open AppsRules
Select LogicalApps Utilities>Migration Path Setup, see figure 12.1.1
______________________________________________________________________________________
62
Figure 12.1.1.
Click Machines, see figure 12.1.2
______________________________________________________________________________________
63
Figure 12.1.2
Enter Machine Name (Not the IP Address)

Enter User Name
Enter Password
Login criteria is specific for the user which has Execute, Read and Write
privileges on APPL_TOP (usually applmgr)
After configuring the machines, close the window and press the Instances button
see, figure 12.1.3.
______________________________________________________________________________________
64
Figure 12.1.3
Enter Instance Name

Select Host
o LOV of machines defined in previous
Enter Connect String
o Connection string to the target instance
o Example: jdbc:oracle:thin:@pismo.whq.logicalapps.com:1527:visdemo
All connect strings will always start with jdbc:oracle:thin:@

Then rest of the connect string is unique to your environment. The connect string will
include the host name, the port, and the instance name. The easiest place to locate the
correct information is within the tnsnames file (DBA should have, or any developer). In
viewing our internal connect string above pismo.whq.logicalapps.com is the host name;
1527 is the port, and visdemo is the instance name. Remember to put in the colons as
shown in the example.
Save - Youve now completed the configuration for a migrating instance.
Migrating Rules from one instance to another

AppsRules allows you to easily migrate rules from one instance to another. You may
choose to migrate an entire rule, or just a rule element. To start the migration:
Open AppsRules
______________________________________________________________________________________
65
Select Rule you wish to migrate

Select LogicalApps Utilities >Migrate Rules
o A new window will appear containing the rule name where your cursor
was placed
o You may choose to migrate this entire rule or narrow your criteria to just a
specific rule element by populating the Rule Element field
Select Target Instance from LOV, see figure 12.1.4.
Figure 12.1.4
Click Migrate
o Concurrent program will launch to complete the migration process
Review your request and make sure the program completes successfully
To require login to the destination database before migration will occur, set Profile
Option: XXLAAPPS:Enable Migration Security = Yes
Reasons Why the Program Might Fail:
If you are migrating just a rule element then the rule must already exist in the
target instance.
______________________________________________________________________________________
66
If subscribers are identified in the source instance that do not exist in the target
instance the migration will fail (example: Ive specified a user or responsibility
that does not exist in my target instance.)
If failure occurs information will be contained in the log file. If you are unable to
identify why the migration failed then re-run the migration and change the
Debug Level from Low to High and re-evaluate.
Typical failures are due to an incorrectly configured connection string within the
Migration Setup.
______________________________________________________________________________________
67

Part 13 Support
AppsRules Troubleshooting Rules and Using Logical Apps
Support
This section describes how you can troubleshoot rules that are not working and how to
use Logical Apps Support Services.
Troubleshooting Rules
Occasionally rules that you configure will either appear not to work or will not work as
desired. Each Oracle Form is unique, coded by one too many developers, and may
perform code that conflicts with your rules. If you encounter a situation where a rule
does not appear to work then the below are some guidelines to help you troubleshoot the
rule:
1. Review the rule and verify that the rule is active and that the subscribers are
correct.
2. Turn on the Debug flag and return to the target form to see if the rule message
appears. If it does not appear, then you have a problem either with the form not
calling the custom.pll (log a tar with Oracle for the event that you have specified),
the subscriber condition is not being met (remove all subscribers and re-test),
AppsRules is not installed properly (review your other rules that are working and
make sure they still work), or the rule is not active. At this time the Debug Flag
may cause a form to close but at least you will know if the rule fired to begin
with.
3. If you see the debug messages appear but the rule still is not behaving correctly,
then alter the triggering event. For example, perhaps you are making certain
fields non-updatable but they allow update. Some forms dynamically alter the
field properties after the form opens. In this case, if your event was tied to When
New Form event you should change this to When New Block; this will allow
Oracle to execute their code then you can execute your own.
4. SQL Rules do not compile correctly. You must review the SQL code and make
sure its valid. The Log file that is generated from SQL rule compilation
usually will point you to the right direction. Please note that Logical Apps does
not support the code you are configuring within the SQL window.
Help Configuring Rules
There are times when a rule is complicated in nature. Logical Apps offers a Frequently
Asked Questions link from our Web-Site that will help with guide you to a solution. If a
client would like help configuring a solution Logical Apps does offer remote consulting
services to build and configure complex rules. For more information on remote rule
building or on-site consulting services email info@logicalapps.com.
______________________________________________________________________________________
68

Logical Apps Support Web-Site
Logical Apps support site can be reached directly through the Logical Apps homepage,
www.logicalapps.com, or directly at http://support.logicalapps.com.
From this site you can view Frequently Ask Questions, Gain Access to Training Material,
and if needed, log a support ticket.
When should I log a support ticket?
You should log a support ticket if youve made reasonable attempts to troubleshoot the
rule and the rule still does not execute or behave as desired.
Support requests can be made via the Logical Apps support web-site,
http://support.logicalapps.com, or, by calling Logical Apps at 949.453.9101 x260. WebSupport is available 24 hours a day, phone support is available 8:00 AM to 7:00 PM
(Pacific Time) Monday Friday.
______________________________________________________________________________________
69

Appendix A Subscribers
AppsRules The Power of Subscribers
Subscribers define when a rule should be enforced. Having the ability to target forms
only when certain conditions exist make applying business rules powerful and flexible.
Subscribers can be attached to Rules and/or Rule Elements using the following When
types:
Responsibilities
Profiles
Operating Units
Inventory Organizations
Users
Data
Subscriber Lists
Defining a Subscriber When

When:
Responsibility is selected, set the appropriate condition and select the

responsibility from the Value column
o For instance, you only want this rule to be applied when the user is logged
in with the responsibility equal to Purchasing Super User
Profile is selected, select the profile you want to check in the Profile/Data column
and set the appropriate condition. Select or enter the profile value to check for in
the Value column
o For instance, you only want this rule to be applied when the PO: Change
Supplier Site profile is equal to Y
______________________________________________________________________________________
70
Operating Unit is selected, set the appropriate condition and select the Operating
Unit from the Value LOV
o For instance, you only want this rule to be applied when the Operating
Unit is Vision Operations
Inventory Organization is selected, set the appropriate condition and select the
Inventory Organization from the Value LOV
o For instance, you only want this rule to be applied when the Inventory
Organization is V1
User is selected, set the appropriate condition and select the Oracle user from the
Value LOV
o For instance, you only want this rule to be applied when the User is not
equal to DABBOTT and CSMITH
Data is selected, enter or select the block and field to check in the Profile/Data
column. Set the appropriate condition and enter the value to check for in the Data
Dependent Value column
o For instance, you only want this rule to be applied when the Suppliers
Inactive On (VNDR.END_DATE_ACTIVE_MIR) is greater than
sysdate (today)
Subscriber List is selected, set the appropriate condition and select a pre-defined
Subscriber List from the Value LOV. See Appendix B, for more on setting up
Subscriber Lists
o You only want this rule to be applied when the conditions set in the
subscriber list are true. For instance, only when the User is equal to
CSMITH and the Operating Unit is Vision Operations or the User is equal
to DABBOTT and the Operating Unit is Vision Operations
More Subscriber Fields

Data Type - Change the Data Type as needed to correspond with the Data Dependent
Value you are checking for
And/Or Multiple subscribers can be defined. Use the And/Or column to group
the subscribers as desired
Grouping Enter numbered groups when you define multiple subscribers with
combinations of And/Or selections
Allow Reversals If this is not selected, once a rule has been enforced, it will stay
enforced, even if the next record did not meet the subscriber criteria
o For instance, while browsing the suppliers, you come to a record that
enforces a rule to make a field required. If allow reversals is not checked,
when you browse to the next record the field will continue to be required,
even if the subscriber data is not true for that record
View Statement This will display the SQL statement created with the subscriber
criteria.
______________________________________________________________________________________
71
______________________________________________________________________________________
72

Appendix B Subscriber Lists
AppsRules Defining Subscriber Lists
Subscriber Lists are an extension of Subscribers. They are used to define lists of
Subscribers that you find you need to use on multiple business rules. If you define the
subscribers as a list, you may apply that Subscriber List to your Rule Subscriber or
Element Subscriber.
Subscriber Lists are created through the Tools>AppsRules Subscriber Lists menu
Subscriber Lists have most of the same functionality as the regular subscriber setup. The
following When types are available when defining Subscriber Lists:
______________________________________________________________________________________
73
______________________________________________________________________________________
74

AppsRules Training Guide V 4.0.0.1

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

AppsRules Training Guide V 4.0.0.1

Diunggah oleh

Hak Cipta:

Format Tersedia

_________________________________________

Logical Apps AppsRules

About Logical Apps

Welcome & Overview

Welcome & Overview

Add security down to the field level

Purpose of This Class

Copyright 2003 by Logical Apps, Inc.

AppsRules Training Material

Training Session III

- Building Audit Rules - Building Extensions -

AppsRules Training Material

AppsRules Training Material

AppsRules Training Material

Enter Rule Name

Enter Rule Details

AppsRules Training Material

List of Values Rule

AppsRules Training Material

Use online auditing queries available through a new form

AppsRule provides debug option

Logical Apps provides a solution to migrate these rules from one

AppsRules Training Material

Navigate to the form you want to create a rule for

AppsRules Training Material

Creating a New Rule

Step 1 Define Rule

AppsRules Training Material

Enter a Rule Name

Step 2 Define a Rule Subscriber

AppsRules Training Material

o The following are Events created by AppsRules:

AppsRules Training Material

Navigate to the Suppliers form

AppsRules Training Material

Locate your Rule

AppsRules Training Material

Below are general guidelines to follow when selecting the Event:

AppsRules Training Material

AppsRules Training Material

AppsRules Training Material

From the Type pop list, select Field

AppsRules Training Material

Prevent Insert to a Form

Defining Block Security Rule

AppsRules Training Material

Select Security tab

AppsRules Training Material

Lab#1 Building Security Rules

AppsRules Training Material

AppsRules Training Material

Select Navigation tab

AppsRules Training Material

Enter From Block

AppsRules Training Material

Lab#2 Navigation Rules

AppsRules Training Material

Click Messages tab

AppsRules Training Material

AppsRules Training Material

Lab#3 Messaging Rules

Part 5 Default Value Rules

AppsRules Training Material