This page (revision-15) was last changed on 26-Nov-2021 10:22 by Kevin Higgs

This page was created on 26-Nov-2021 10:22 by JMyers

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
15 26-Nov-2021 10:22 3 KB Kevin Higgs to previous
14 26-Nov-2021 10:22 3 KB jmyers to previous | to last
13 26-Nov-2021 10:22 3 KB JAiken to previous | to last
12 26-Nov-2021 10:22 3 KB RForbes to previous | to last
11 26-Nov-2021 10:22 3 KB JEscott to previous | to last FORMATTED EQUALS WHERE CLAUSE OPERATOR ==> FORMATTED EQUALS WC OPERATOR
10 26-Nov-2021 10:22 3 KB JEscott to previous | to last
9 26-Nov-2021 10:22 3 KB JEscott to previous | to last
8 26-Nov-2021 10:22 2 KB JMyers to previous | to last
7 26-Nov-2021 10:22 2 KB JAiken to previous | to last
6 26-Nov-2021 10:22 2 KB JMyers to previous | to last
5 26-Nov-2021 10:22 2 KB JMyers to previous | to last
4 26-Nov-2021 10:22 2 KB JEscott to previous | to last
3 26-Nov-2021 10:22 2 KB JMyers to previous | to last
2 26-Nov-2021 10:22 2 KB JMyers to previous | to last
1 26-Nov-2021 10:22 2 KB JMyers to last

Page References

Incoming links Outgoing links
IMWC
IMWC

Version management

Difference between version and

At line 1 removed 2 lines
[{TableOfContents }]
At line 5 changed 20 lines
The Maintain Where Clauses (IMWC) form allows you to create and edit Where Clauses within the system. Where clauses are used to conditionally select data from a table. They may be used to filter data on forms, approval processes, LOV’s and people lists.
%%information In order to use Where Clauses, you should be familiar with SQL.%%
The definition data for the Maintain Where Clauses screen is stored in the [P2K_AM_WHERE_CLAUSES] and [P2K_AM_CONDITIONS] tables.
;[Data Source|DATA_SOURCE_NAME]:The data source is the table location in which the information being filtered into the where statement is derived from.
;[Where Clause|WHERE_CLAUSE_CODE]:This field identifies the Where Clause.
;[Usage|WHERE_CLAUSE_USAGE]:This field will indicate if the Where Clause is Pre-loaded (system provided), User Defined or Obsolete. All Where Clauses created by clients should have a usage of ‘User Defined’.
;[Description|DESCRIPTION]:This field provides a brief description outlining the intention of the ‘Where Clause’. Although it is not a mandatory field, it is recommended to always provide a brief description for the purpose of clarity
;[Type|CONDITION_TYPE]:This field indicates whether the criteria have been written in the Java or if the criteria are defined on an ‘as required’ basis. There are two options available, Java Defined and Ad Hoc. Users should use the type Ad Hoc.
;[Java Code|PREDEFINED_CONDITION_CODE]:Some 'pre-loaded' where clauses contain java logic, this predefined logic is specified in this field. This field is not used with user-defined where clauses or conditions.
;[Column Name|COLUMN_NAME]:This field allows you to define the filters to be used with the Where Clause. You may use more than one filter on a where clause. If you do use multiple filter statements, they are joined by ‘and’ in the statement.
;:e.g. You can use multiple columns to return a Positions LOV that will be filtered first by department, next by active status, and finally by date.
;[Operator|COMPARISON_OPERATOR]:This field allows you to provide an SQL statement to further filter the information.
;:e.g. Equals, Formatted Equals, Greater Than, In, Is Not Null, Is Null, Less Than,…\\By selecting [Formatted Equals|FORMATTED EQUALS WC OPERATOR] in the Operator, the user is able to specify a date format in the Format Symbols field.
;[Grouping|GROUPING]: This field is not used at this time.
;[Value|VALUE]:This field indicates what data the column name is to be compared with. For example this could be the as of date, lexicon values, numbers or specific data within the database such as a department code.
;[Usage|CONDITION_USAGE]:This field is used to determine whether a condition on a where clause was supplied or has been added by a user to customize the where clause.
The Maintain Where Clauses (IMWC) form is used to filter data on forms, approval processes, LOV’s and people lists.
This section explains the purpose of Where Clauses within the application and the Maintaining Where Clause screen.
In order to use Where Clauses, you should be familiar with SQL.
The Maintain Where Clauses screen allows you to create and edit Where Clauses within the
system.
Data Source This field indicates the data source that the Where Clause will be attached. (Mandatory)
e.g. The Positions table used for an LOV that the Where Clause will then filter.
Where Clause
This field identifies the Where Clause.
Usage
This field will indicate if the Where Clause is Pre-loaded (McKessonHigh Line provided),
User Defined or Obsolete.
Description
This field provides a short description of the Where Clause.
Type
This field categorizes the Where Clause into a specific type.
For example: Ad Hoc, Predefined
Predefined
If the Where Clause is pre-loaded, its predefined name will appear in this field.
This field is not normally used.
Column
This field allows you to define the filters to be used with the Where Clause.
You may use more than one filter on a Where Clause. If you do use multiple filter
statements, they are joined by ‘and’ in the statement.
e.g. You can use multiple columns to return a Positions LOV that will be filtered first by department, next by active status, and finally by date.
Operator
This field allows you to provide an SQL statement to further filter the information.
e.g. equal to, not equal to, less than, greater than.
Value
This field completes the SQL statement of the previous field.
e.g. active status, Finance department.
At line 26 changed 14 lines
For example, if you wished to only see the LOV positions that are in the Finance department, you would insert the following information in those fields:
* Column = ID.DPS_ID
* Operator = equal to
* Value = Finance
;[Description|DESCRIPTION]:This field will provide a full description of how the Where Clause operates.
;[Physical Column|COLUMN_NAME]:This field indicates the name of the column in the table as defined in the database.
;[Physical Condition|PREDEFINED_CONDITION_CODE]:This field indicates the predefined condition implemented within the Java code itself.
;[Test Where Clause|ACT_WHERE_CLAUSE_CHECK_RESULTS]: This button allows you to test the Where Clause to see if it returns the correct information in a timely manner.
----
![Notes|Edit:Internal.IMWC]
[{InsertPage page='Internal.IMWC' default='Click to create a new notes page'}]
For example, if you wished to only see in the LOV positions that are in the Finance department, you would insert the following information in those fields:
Column = ID.DPS_ID
Operator = equal to
Value = Finance
Description
This field will provide a full description of how the Where Clause operates.
Test Where Clause This button allows you to test the Where Clause to see if it returns the correct information in a timely manner.
This page (revision-15) was last changed on 26-Nov-2021 10:22 by Kevin HiggsTop