This page (revision-25) was last changed on 26-Nov-2021 10:22 by JAiken

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
25 26-Nov-2021 10:22 5 KB JAiken to previous
24 26-Nov-2021 10:22 4 KB JEscott to previous | to last
23 26-Nov-2021 10:22 4 KB JEscott to previous | to last
22 26-Nov-2021 10:22 4 KB JEscott to previous | to last
21 26-Nov-2021 10:22 4 KB JEscott to previous | to last

Page References

Incoming links Outgoing links
IMDAO
IMDAO

Version management

Difference between version and

At line 15 changed 3 lines
;[Type |DATA_SOURCE_TYPE]:This field categorizes the Where Clause into a specific type.
;:For example: Ad Hoc, Predefined
;[Predefined|PREDEFINED_CONDITION_CODE]:If the Where Clause is pre-loaded, its predefined name will appear in this field. This field is not normally used.
;[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.
At line 19 changed 3 lines
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.
%%information 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.%%
At line 23 changed 3 lines
;:e.g. equal to, not equal to, less than, greater than.
;[Value|VALUE]:This field completes the SQL statement of the previous field.
;:e.g. active status, Finance department.
;[Value|VALUE]:This field completes the SQL statement of the previous field.\\ \\This field holds information used to filter the where clause against. For example, it may be "Active" if the where clause is to filter a list of employees based on their employment status.
;[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.
At line 32 changed 2 lines
;[Physical Column Name|]:
;[Test Where Clause |]:This button allows you to test the Where Clause to see if it returns the correct information in a timely manner.
;[Physical Column Name|COLUMN_NAME]:This field will display name of the column that is used to filter the where clause.
;[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.
At line 38 changed 6 lines
;[Cache Status |]:
;[Cached Columns |]:
;[Clear Table Data |]:
;[Clear All Cached Tables |]:
;:%%warning Only use in the most extreme cases%%
\\ \\
;[Cache Status |DRV_CACHE_STATUS]:This field indicates if the data source selected in the find block has been added to the application's cache or not. If the data source has been added, the field also indicates how many rows have been cached.
;[Cached Columns |DRV_CACHED_COLUMNS]:This box indicates which columns associated to the data source are cached.
;[Clear Table Data |ACT_CLEAR_TABLE_CACHE]:If necessary the user may clear the table's data from the cache. This may be necessary if changes to the data within the table are not refreshing for the users.
\\
!Only to be used in extreme cases
;[Clear All Cached Tables |ACT_CLEAR_ALL_TABLE_CACHES]: This action button will clear data from ALL of the cached tables, not just the one selected in the find block.
At line 46 changed 5 lines
;[Function|FUNCTION_NAME]:
;[MFN Usage|FUNCTION_USAGE]:
;[Join Clause|JOIN_CLAUSE]:
;[Where Clause|WHERE_CLAUSE]:
;[MFT Usage|]:
;[Function|FUNCTION_NAME]:This field displays a function which makes use of the data source selected in the find block.
;[MFN Usage|FUNCTION_USAGE]:This field displays the function's usage, meaning if the function is pre-loaded or user-defined.
;[Join Clause|JOIN_CLAUSE]:This field displays the join clause to the data source selected in the find block.
;[Where Clause|WHERE_CLAUSE_CODE]:If the function has a where clause defined for the data source selected, the [where clause code|WHERE_CLAUSE_CODE] will display here.
;[MFT Usage|FORM_TABLE_USAGE]: This field indicates if the form's table usages are pre-loaded with the application or if they were user-defined.
At line 52 changed one line
;[Create|CREATE_ALLOWED]/[Retrieve|RETRIEVE_ALLOWED]/[Update|UPDATE_ALLOWED]/[Delete Allowed|DELETE_ALLOWED]:
;[Create|CREATE_ALLOWED]/[Retrieve|RETRIEVE_ALLOWED]/[Update|UPDATE_ALLOWED]/[Delete Allowed|DELETE_ALLOWED]: The security access available for the function is displayed using these toggles.
At line 56 changed 4 lines
;[LOV Code|LOV_CODE]:
;[LOV Usage|LOV_USAGE]:
;[Where Clause|WHERE_CLAUSE]:
;[Exclude From Cache|]:
;[LOV Code|LOV_CODE]:This field displays an LOV code that has been defined for the data source selected in the find block.
;[LOV Usage|LOV_USAGE]:This field displays whether the LOV was pre-loaded with the application or if it was defined by a user.
;[Where Clause|WHERE_CLAUSE_CODE]:If a where clause is tied to the LOV, the where clause code is displayed here.
;[Exclude From Cache|EXCLUDE_FROM_CACHE]:If the LOV is to be excluded from the application's cache, it is indicated here.
----
![Notes|Edit:Internal.IMDAO]
[{InsertPage page='Internal.IMDAO' default='Click to create a new notes page'}]
This page (revision-25) was last changed on 26-Nov-2021 10:22 by JAikenTop