This page (revision-6) 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
6 26-Nov-2021 10:22 1 KB kparrott to previous
5 26-Nov-2021 10:22 1 KB kparrott to previous | to last
4 26-Nov-2021 10:22 1 KB kparrott to previous | to last HOW_DO_I_ADD_A_HEADER_OR_FOOTER_TO_A_SCREEN ==> HOW TO ADD A HEADER OR FOOTER TO A SCREEN
3 26-Nov-2021 10:22 1 KB kparrott 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
HOW TO ADD A HEADER OR FOOTER TO A SCREEN
HOW TO ADD A HEADER OR FOOTER TO A SCREEN

Version management

Difference between version and

At line 2 changed 9 lines
Although headers and footers appear on the form, they are set up at the Function level.
# Access the Maintain Function ([IMFN]) form through the Web Site Administrator main menu. You will be presented with a list of functions.
# Select the function to which you wish to add the Header and/or Footer.
# Click on the Preferences tab.
# Click the Add icon found at the bottom of the list of functions.
# Enter a sequence number. It is recommended using numbers increased by increments of ten. (e.g. 10, 20, 30, etc.)
# Enter in the Preference; HEADER INFO or FOOTER INFO.
# Enter the location of the html or jsp file in the Value field i.e. docs/WEDPN_Header.html
# Save the file.
Headers/Footers in Self Service have been replaced by Messages, which are embedded directly in the forms in the preferred position.\\ \\Steps to add embedded Messages in a form are as follows:
#IMMS - create a new message
** Allows multiple lines and HTML.
** Best practice recommendation: name the Message ‘FORM_HEADER’ (i.e. WEBOEE-HEADER) – allows easy search on client-created messages. Clients may also wish use a naming convention with their customer code embedded – this is not necessary assuming that clients properly label the message as “User Defined”.
#IMWC - create a new Where clause
** Table (Data Source) = P2K_AM_MESSAGES
** Where Clause Condition will be setup as Type = Ad Hoc, Column Name = MESSAGE_CODE, Operator = EQUALS, Value = xxxxx-HEADER (message name from step 1)
#IMFDH – add the Message to the function
** Table Usages tab: add a new table usage for P2K_AM_MESSAGES (Data Source)
*** Table Alias = MMSH (or something unique for this message).
*** Use the where clause created in step 2.
*** Toggle on [x] Retrieve Allowed (save the change).
** Form Layout tab: add a new row (Form Group = something unique, ie: HEADER INFO) to the form layout in the required position/block
*** Parent Group = FORM
*** Layout type = TEXT
*** Decoration = Lined Border, if you want (save)
** In the new Form Group: add a display only field of MMSH.MESSAGE_TEXT (use the alias you created instead of MMSH if different)
*** Display width = SS-Widest
*** Height must be > 1
*** If you don't add a label, the system will display "Text".
*** High Line recommends "Instructions" or "Note".
At line 12 removed one line
Various sample screen headers and footers have been supplied throughout Self Service. These headers and footers are either HTML or JSP files which are saved in the "docs" folder under selfService on your 9ias server.
At line 14 removed one line
The headers and footers provided can be edited to your requirements. It is recommended, however, that you follow the established naming conventions for these files.
At line 16 removed 6 lines
;Header:
Each header is named as follows:
FUNCTION_Header.html or FUNCTION_Header.jsp, where FUNCTION is the name of the function to which you will be applying this header (e.g. WEEPP_Header.html).
;Footer:
Each footer is named as follows:
FUNCTION_Footer.html or FUNCTION_Footer.jsp, where FUNCTION is the name of the function to which you will be applying this footer (e.g. WEEP_Footer.html).
At line 23 removed 4 lines
A header and/or footer will only appear on a screen if the Header Info and/or Footer Info preferences have been properly setup via the Maintain Functions ([IMFN]) screen in Self Service Administration module to call the appropriate HTML or JSP document from the "docs" directory.
Whenever Self Service software updates are provided there is the chance that supplied documents in the "docs" folder will be overwritten. To avoid losing any newly created documents or changes made to the delivered documents, we recommend that you keep a master copy of ALL required headers and footers outside of the server environment.
This page (revision-6) was last changed on 26-Nov-2021 10:22 by kparrottTop