This page (revision-17) was last changed on 26-Nov-2021 10:22 by Karen Parrott

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
17 26-Nov-2021 10:22 7 KB Karen Parrott to previous
16 26-Nov-2021 10:22 7 KB Karen Parrott to previous | to last
15 26-Nov-2021 10:22 7 KB kparrott to previous | to last
14 26-Nov-2021 10:22 7 KB RForbes to previous | to last
13 26-Nov-2021 10:22 7 KB JMyers to previous | to last
12 26-Nov-2021 10:22 7 KB JMyers to previous | to last
11 26-Nov-2021 10:22 7 KB JMyers to previous | to last
10 26-Nov-2021 10:22 7 KB JMyers to previous | to last
9 26-Nov-2021 10:22 6 KB JMyers to previous | to last
8 26-Nov-2021 10:22 7 KB JMyers to previous | to last
7 26-Nov-2021 10:22 7 KB JMyers to previous | to last
6 26-Nov-2021 10:22 7 KB JMyers to previous | to last
5 26-Nov-2021 10:22 7 KB JMyers to previous | to last
4 26-Nov-2021 10:22 6 KB JMyers to previous | to last
3 26-Nov-2021 10:22 6 KB JMyers to previous | to last
2 26-Nov-2021 10:22 6 KB JMyers to previous | to last
1 26-Nov-2021 10:22 6 KB JMyers to last

Page References

Incoming links Outgoing links
FINDING_RECORDS
FINDING_RECORDS

Version management

Difference between version and

At line 5 changed one line
Each form in Personality provides records to users based on certain criteria. The purpose of this paper is to outline methods of refining the records available from the Find Block/List and to provide instruction on the methods of using the query tool from the form toolbar.
Each form in [{$applicationname}] provides records to users based on certain criteria. The purpose of this paper is to outline methods of refining the records available from the Find Block/List and to provide instruction on the methods of using the query tool from the form toolbar.
At line 11 changed one line
The Query action is seen in the screen shot as the flashlight icon which allows you to search for information using any fields on your current form with simple comparison operators.
The Query action as seen in the screen shot as the flashlight icon, allows you to search for information using any fields on your current form with simple comparison operators.
At line 15 changed 2 lines
In the example below a query can be performed on the [IEAS] to provide a list of employees that work in the same location.\\
[{Image src='FindingRecords_01.jpg'}]
In the example below a query can be performed on the IEAS to provide a list of employees that work in the same location.\\
[FindingRecords_01.jpg]
At line 22 changed one line
#Click on the flashlight icon in the toolbar. A separate window will open with four areas that will need to be populated.
#Click on the flashlight icon in the toolbar. A separate window will open. This window contains four areas that will need to be populated
At line 24 changed 2 lines
#*Comparison Operator: The search is performed by comparing the Field prompt to the value indicated in the value field. The comparison operator determines the action of the comparison (equal to, like, contains).
#*Value: This is the value of the Field prompt which the query will look for.
#*Comparison Operator: The search is performed by comparing the Field prompt to the value indicated in the value field. The comparison operator determines the action of the comparison.
#*Value: This is the value of the Field prompt in which the query is being performed.
At line 27 changed one line
#Once the Query Criteria has been entered select “OK”. This opens another window displaying the query results. Notice that as you scroll with your cursor through each of these records, the [IEAS] screen will change to reflect the highlighted employee.
#Once the Query Criteria has been entered select “OK”. This opens another window displaying the query results. Scrolling with your cursor through each of these records the IEAS will change to reflect the highlighted employee
At line 31 changed one line
%%information Note that while the Position field on [IEAS] is found on the P2K_HR_ASSIGNMENT_DETAILS it is the FIND_EEM that determines what record is displayed.%%
%%information Note that while the Position field on IEAS is found on the P2K_HR_ASSIGNMENT_DETAILS it is the FIND_EEM that determines what record is displayed.%%
At line 33 changed one line
Screens that contain individual tables in the form like [IPTR], [IALS], [IBSC], [IPTL] etc. can also be queried without using the find. In the example below two separate results occur when the same query is performed with the cursor in different locations on [IPTR].
Screens that contain individual tables in the form like IPTR, IALS, IBSC, IPTL etc. can also be queried without using the find. In the example below two separate results occur when the same query is performed with the cursor in different locations on IPTR.
At line 35 changed 3 lines
With the cursor in the [IPTR] Find Block/List: The query found all batches that contained employees that met the wage rate criteria.\\ \\
[{Image src='FindingRecords_02.jpg'}]\\ \\
[{Image src='FindingRecords_03.jpg'}]\\ \\
With the cursor in the IPTR Find Block/List: The query found all batches that contained employees that met the wage rate criteria.\\ \\
[FindingRecords_02.jpg]\\ \\
[FindingRecords_03.jpg]\\ \\
At line 40 changed 2 lines
[{Image src='FindingRecords_04.jpg'}]\\ \\
[{Image src='FindingRecords_05.jpg'}]\\ \\
[FindingRecords_04.jpg]\\ \\
[FindingRecords_05.jpg]\\ \\
At line 43 changed 13 lines
Each form in Personality has the ability to perform queries based on the “find” associated to the form. The find can be found as a header on each function in [{$applicationname}]. The find determines the criteria when filtering records on the form.\\ \\
Many forms throughout Personality utilize the same find block. Looking at all the employee screens you can see that they utilize a common find.\\ \\
[{Image src='FindingRecords_06.jpg'}]\\ \\
The find on each form can be customized at the form level (individual screen) or at system level (all screens that use a common find block) to meet search criteria requirements.\\ \\
[{Image src='FindingRecords_07.jpg'}]\\ \\
This find is called “FIND_EEM”. In most cases the find being used by a form can be found by looking up function definition on [IMFN]. If the form is using a Find Block it will be listed in the “FIND LOV” field.\\ \\
Once the name of the “Find LOV” has been identified it can be maintained on the [IMLOVL] form.\\ \\
[{Image src='FindingRecords_08.jpg'}]\\ \\
If additional criteria are required to filter records on a form they can be added to the find block.\\
%%warning Find Block/List’s should not be directly edited. See set up examples in the next section for proper methods in altering the find.%%\\
In some cases there may be forms that do not utilize a find block. These forms have pre-loaded finds loaded directly on the form itself and typically are not employee related. Forms that have the find located directly on the form can be changed using object security to remove fields not required and [IMFD] to add additional fields.\\ \\
[{Image src='FindingRecords_09.jpg'}]\\ \\
----
Each form in ePersonality has the ability to perform queries based on the “Find” associated to the form. The find can be found as a header on each function in ePersonality. The find determines the criteria when filtering records on the form.\\
Many forms throughout ePersonality utilize the same find block. Looking at all the employee screens you can see that they utilize a common find.\\ \\
[FindingRecords_06.jpg]\\ \\
The find on each form can be customized at the form level (Individual screen) or at system level (all screens that use a common find block) to meet search criteria requirements.\\ \\
[FindingRecords_07.jpg]\\ \\
This find is called “FIND_EEM”. In most cases the find being used by a form can be found by looking up function definition on IMFN. If the form is using a Find Block it will be listed in the “FIND LOV” field.
Once the name of the “Find LOV” has been identified it can be maintained on the IMLOVL form.
If additional criteria are required to filter records on a form they can be added to the find block.
Find Block/List’s should not be directly edited. See set up examples in the next section for proper methods in altering the find.
In some cases there may be forms that do not utilize a find block. These forms have pre-loaded finds loaded directly on the form itself and typically are not employee related. Forms that have the find located directly on the form can be changed using object security (To remove fields not required) and IMFD to add additional fields.
At line 59 added one line
At line 58 changed 8 lines
#Determine the name of the find that is to be edited on the desired functions ([IMFN]). For example, use the FIND_EEM and add the government code as part of the search criteria.
#Open the [IMLOVL] once the name of the find has been determined.
#Deep copy the original find.
#*Rename the find in a manner suitable to your needs.(In this case we will rename the find to FIND_EEM_EXT)
#*Change the LOV Usage from “Pre-Loaded to “User Defined”
#*Populate the Replacing LOV field with the name of the original find. (In this case FIND_EEM)
#*Add the search criteria field. The sequence is important as it determines where the new search criteria will be displayed. (In this case it is the EID_ID.GOVERNMENT_CODE field)
[{Image src='FindingRecords_11.jpg'}]\\ \\
a) Determine the name of the find that is to be edited on the desired functions (IMFN). In the example we will use the FIND_EEM and will be adding the government code as part of the search criteria
b) Open the IMLOVL once the name of the find has been determined.
c) Deep copy the original find.
 Rename the find in a manner suitable to your needs. (In this case we will rename the find FIND_EEM_EXT)
 Change the LOV Usage from “Pre-Loaded to “User Defined”
 Populate the Replacing LOV field with the name of the original find (in this case FIND_EEM)
 Add the search criteria field. The sequence is important as it determines where the new search criteria will be displayed. (In this case it is the EID_ID.GOVERNMENT_CODE field)
At line 67 changed 2 lines
[{Image src='FindingRecords_12.jpg'}]\\ \\
----
At line 70 changed 2 lines
In some cases there may be a requirement to change the Find Block/List for an individual form only. In this situation both the Find Block/List and the form must be duplicated and marked as “User Created” (otherwise they will be over written on a future release). \\ \\
Using the same example as above the government code field will be added as a search criteria on the [IEAS] only.\\ \\
In some cases there may be a requirement to change the Find Block/List for an individual form only. In this situation both the Find Block/List and the form must be duplicated and marked as “User Created” (otherwise they will be over written on a future release).
Using the same example as above the government code field will be added as a search criteria on the IEAS only.
At line 73 removed 8 lines
#Go to the form in which the find is to be updated on [IMFN] and find out the name of the Find Block/List from the Find LOV field
#Go to [IMLOVL] and deep copy the Find Block/List found on [IMFN].
#Make any alterations to the find (in this case we will add the government code). Make sure the Replacing LOV field is left blank.
#Click the Clear LOV and Load LOV buttons.
#In [IMFN] copy the form and function in which the new find will be added using the button “Copy Function and Form”.
#Rename the function in a manner suitable to your needs. Make sure the new form is marked as “User Defined” in the usage field
#Replace the Find LOV on [IMFN] with the name of your custom created Find Block/List.
#Add execution rights and privileges to this new form while restricting the rights and privileges from the original form using the [IMER]/[IMFN]/[IMUS] screens.
At line 82 changed one line
When you next log in the new [IEAS] screen will be using the new find.
a. Go to the form in which the find is to be updated on IMFN and find out the name of the Find Block/List from the Find LOV field
b. Go to IMLOVL and deep copy the Find Block/List found on IMFN
c. Make any alterations to the find (In this case we will add the government code). Make sure the Replacing LOV field is left blank.
d. Click the Clear LOV and Load LOV buttons.
At line 84 changed 3 lines
----
![Notes|Edit:Internal.FINDING_RECORDS]
[{InsertPage page='Internal.FINDING_RECORDS' default='Click to create a new notes page'}]
e. In IMFN copy the form and function in which the new find will be added using the button “Copy Function and Form”.
f. Rename the function in a manner suitable to your needs. Make sure the new form is marked as “User Defined” in the usage field
g. Replace the Find LOV on IMFN with the name of your custom created Find Block/List.
h. Add execution rights and privileges to this new form while restricting the rights and privileges from the original form using the IMER/IMFN/IMUS screens.
When you next log in the new IEAS screen will be using the new find.
This page (revision-17) was last changed on 26-Nov-2021 10:22 by Karen ParrottTop