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

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
22 26-Nov-2021 10:22 26 KB kparrott to previous
21 26-Nov-2021 10:22 26 KB kparrott to previous | to last

Page References

Incoming links Outgoing links
Training.Create_Winward_Report...nobody
Training.Create_Winward_Report

Version management

Difference between version and

At line 14 changed one line
;Step 1:Create a new function for this report.\\ \\Any report run from within ePersonality must be defined as a function in the [IMFN] screen. The first two reports will be retrieving data from the HR tables only and is similar to the [RENA] report.\\ \\
;Step 1:Create a new function for this report.\\ \\Any report run from within [{$applicationname}] must be defined as a function in the [IMFN] screen. The first two reports will be retrieving data from the HR tables only and is similar to the [RENA] report.\\ \\
At line 57 changed one line
If the data source provided to the template only contains one piece of information, it can simply be added to the report using an OUT tag. However, most reports will need to display several rows of information, sorted by one or more items. In this situation, a FOREACH tag will be needed to look through the data to display all the rows that pass the selection criteria defined within ePersonality.
If the data source provided to the template only contains one piece of information, it can simply be added to the report using an OUT tag. However, most reports will need to display several rows of information, sorted by one or more items. In this situation, a FOREACH tag will be needed to look through the data to display all the rows that pass the selection criteria defined within [{$applicationname}].
At line 87 changed one line
;Step 2:In ePersonality, run the [REBR] report by typing the command into the command window.
;Step 2:In [{$applicationname}], run the [REBR] report by typing the command into the command window.
At line 94 changed one line
Currently, the report will retrieve every employee from the database and report them under the department they are currently working in. While this is useful, it would be more helpful to prompt the user for a specific month or months to report. Since we are restricting the amount of data that Windward needs to process, this must be done within ePersonality.
Currently, the report will retrieve every employee from the database and report them under the department they are currently working in. While this is useful, it would be more helpful to prompt the user for a specific month or months to report. Since we are restricting the amount of data that Windward needs to process, this must be done within [{$applicationname}].
At line 105 changed one line
*Parameter length of ‘2’\\ \\Turning on the Filter checkmark indicates to ePersonality that this parameter will modify the SELECT statement in [IMLQ]. With this checkmark turned on, a Validation Clause is required in the CLAUSE tab of the [IMPM] record.\\ \\TO_CHAR(BIRTH_DATE, 'MM') IN (<LIST>)\\ \\Adding the code segment shown above will allow the user to enter one of more, 2 character months as a qualifier for the report list. \\ \\The final step is to add this parameter to the report parameter definition within the IMFDH screen.\\ \\
*Parameter length of ‘2’\\ \\Turning on the Filter checkmark indicates to [{$applicationname}] that this parameter will modify the SELECT statement in [IMLQ]. With this checkmark turned on, a Validation Clause is required in the CLAUSE tab of the [IMPM] record.\\ \\TO_CHAR(BIRTH_DATE, 'MM') IN (<LIST>)\\ \\Adding the code segment shown above will allow the user to enter one of more, 2 character months as a qualifier for the report list. \\ \\The final step is to add this parameter to the report parameter definition within the IMFDH screen.\\ \\
At line 123 changed one line
;Step 3:Open MS Word and created a new RTF file that matches our new function name, REHC.rtf. Again, ensure that the file name is in uppercase while the extension is lowercase. Both ePersonality and the Windward report engine are case sensitive when it's looking for the report template file.
;Step 3:Open MS Word and created a new RTF file that matches our new function name, REHC.rtf. Again, ensure that the file name is in uppercase while the extension is lowercase. Both [{$applicationname}] and the Windward report engine are case sensitive when it's looking for the report template file.
At line 146 changed one line
The following two images show sample output from this report when run from ePersonality.\\ \\
The following two images show sample output from this report when run from [{$applicationname}].\\ \\
At line 160 changed one line
All High Line supplied Windward report templates are shipped in a single ZIP file. Most of the templates are stored in Rich Text Format [RTF], but there can be XLSX and DOCX as well. During the installation and configuration of the Oracle Application Server, a copy of these files would have been placed in the REPORTS folder under the HLAppResources directory used by each ePersonality instance.\\ \\
All High Line supplied Windward report templates are shipped in a single ZIP file. Most of the templates are stored in Rich Text Format [RTF], but there can be XLSX and DOCX as well. During the installation and configuration of the Oracle Application Server, a copy of these files would have been placed in the REPORTS folder under the HLAppResources directory used by each [{$applicationname}] instance.\\ \\
At line 169 changed one line
*Ensure the vendor field is XML (file or url) and edit the File/URL field to point to the following URL:[http://argo.highlinecorp.com/selfService_AS01/reportdatastructure?NAME=RENAC]\\%%information Please note the URL shown above is an example only. You will need to alter this URL to point to your application server and Self Service instance.%%\\This URL is another entry point into the Self Service component of High Line's ePersonality application. This URL simply provides the XML format of the data that will be provided to the Windward report engine when the specified function is run. Auto Tag requires a data structure to provide a list of item that can be added to the report from its Data Bin.
*Ensure the vendor field is XML (file or url) and edit the File/URL field to point to the following URL:[http://argo.highlinecorp.com/selfService_AS01/reportdatastructure?NAME=RENAC]\\%%information Please note the URL shown above is an example only. You will need to alter this URL to point to your application server and Self Service instance.%%\\This URL is another entry point into the Self Service component of High Line's [{$applicationname}] application. This URL simply provides the XML format of the data that will be provided to the Windward report engine when the specified function is run. Auto Tag requires a data structure to provide a list of item that can be added to the report from its Data Bin.
At line 181 changed one line
;Step 8:Save the report and connect to ePersonality as a user authorized to run RENA.
;Step 8:Save the report and connect to [{$applicationname}] as a user authorized to run RENA.
At line 189 changed one line
The next step is to alter the data that is presented to the new template for reporting. This is not controlled by either the template or Windward. Instead, altering this will need to be done within your ePersonality environment. Each report that has a subject table defined within its [IMFN] screen must have an entry in the [IMLQ] to build a report list. Since [RENAC] has the P2K_HR_ASSIGNMENT_DETAILS table defined for its subject table, there must be an entry within [IMLQ] with an LOV name of [IMPV_RENAC]. EP will look for an entry that starts with IMPV_ followed by the function name of the report. The Query Text defined in the [IMLQ] entry is a simple SQL select statement that will build a list of assignment detail ID's that are passed to our report. By altering this SQL statement we can change the quantity of data that will be processed by the report.\\ \\
The next step is to alter the data that is presented to the new template for reporting. This is not controlled by either the template or Windward. Instead, altering this will need to be done within your [{$applicationname}] environment. Each report that has a subject table defined within its [IMFN] screen must have an entry in the [IMLQ] to build a report list. Since [RENAC] has the P2K_HR_ASSIGNMENT_DETAILS table defined for its subject table, there must be an entry within [IMLQ] with an LOV name of [IMPV_RENAC]. EP will look for an entry that starts with IMPV_ followed by the function name of the report. The Query Text defined in the [IMLQ] entry is a simple SQL select statement that will build a list of assignment detail ID's that are passed to our report. By altering this SQL statement we can change the quantity of data that will be processed by the report.\\ \\
This page (revision-22) was last changed on 26-Nov-2021 10:22 by kparrottTop