This page (revision-33) 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
33 26-Nov-2021 10:22 11 KB kparrott to previous
32 26-Nov-2021 10:22 11 KB kparrott to previous | to last
31 26-Nov-2021 10:22 11 KB kparrott to previous | to last
30 26-Nov-2021 10:22 11 KB kparrott to previous | to last
29 26-Nov-2021 10:22 11 KB rforbes to previous | to last
28 26-Nov-2021 10:22 11 KB JMyers to previous | to last
27 26-Nov-2021 10:22 11 KB JMyers to previous | to last
26 26-Nov-2021 10:22 11 KB JMyers to previous | to last
25 26-Nov-2021 10:22 11 KB JEscott to previous | to last
24 26-Nov-2021 10:22 11 KB JAiken to previous | to last
23 26-Nov-2021 10:22 11 KB JEscott to previous | to last
22 26-Nov-2021 10:22 10 KB JEscott to previous | to last
21 26-Nov-2021 10:22 10 KB JEscott to previous | to last

Page References

Incoming links Outgoing links
IMFN
IMFN

Version management

Difference between version and

At line 14 changed 3 lines
|Internal Function|The main purpose of an internal function is to allow you to create, view, edit and delete your company’s information within the application. For example, all the individuals who will be using the application are maintained as a list of users through the Maintain Users ([IMUS]) screen.\\In addition, these internal functions allow you to customize some of the structure of the application to suit your company’s needs. You can indicate how information will be presented and who will be able to access or edit this information.
|External Function |External functions are links to either external web pages or to documents stored outside of the application. For example, you may have a company policy that you would like to have accessible on the application. You can create a new function which points the application to that document so that users may view it online.
Through the IMFN screen, you will be able to modify the internal functions and also create and modify external functions.
|Internal Function|The main purpose of an Internal Function is to allow you to create, view, edit and delete your company’s information within the application. For example, all the individuals who will be using the application are maintained as a list of users through the Maintain Users ([IMUS]) screen.\\In addition, these internal functions allow you to customize some of the structure of the application to suit your company’s needs. You can indicate how information will be presented and who will be able to access or edit this information.
|External Function |External Functions are links to either external web pages or to documents stored outside of the application. For example, you may have a company policy that you would like to have accessible on the application. You can create a new function which points the application to that document so that users may view it online.
Through the IMFN screen, you will be able to modify the Internal Functions and also create and modify External Functions.
At line 20 added one line
At line 23 changed one line
There are several function types, however only three apply to Self Service:
There are several function types defined by High Line, however only three apply to Self Service:
At line 28 changed 2 lines
;Screen: This is a supplied function, which looks to a pre-loaded screen. e.g. [WEBEL] (Other Benefit Options in [ESS| MODULE-ESS]). You may only alter Screen functions in Self Service if the original function has been copied. This leaves the original function intact and allows you to make changes to the new version.
%%information Please note that all copied functions will become your responsibility. Any and all changes could be lost during system upgrades as old functions may become obsolete due to technology changes in an upgrade. It is recommended that wherever possible, object security ([IMOS]), translations ([IMLA]) and user defined columns be used to modify the appearance of functions, as these changes will not be affected by upgrades.%%
;Screen: This is a High Line created function, which looks to a pre-loaded screen. e.g. WEBEL (Other Benefit Options in ESS). You may only alter Screen functions in Self Service if the original function has been copied. This leaves the original function intact and allows you to make changes to the new version. See “How Do I Copy/Extend a Function” in this manual for further details. Please note that all copied functions will become your responsibility. Any and all changes could be lost during system upgrades as old functions may become obsolete due to technology changes in an upgrade. It is recommended that wherever possible, object security ([IMOS]), translations ([IMTN], [IMLA]) and user defined columns be used to modify the appearance of functions, as these changes will not be affected by upgrades.
At line 31 changed one line
;Manual:Manual functions are the same as external functions, however, when placed on a menu and accessed by a user, the link will open within the Self Service application.
;Manual:Manual functions are the same as External, however, when placed on a menu and accessed by a user, the link will open within the Self Service application.
\\
At line 35 changed 5 lines
;[Product|PRODUCT_CODE]:This field identifies the product against which the function is applied. Every function must belong to a product of one type or another.
;[Function Name|FUNCTION_NAME]:This field displays the name of the function. This is the shortcut code that you can type in the Command window. For system supplied functions, this should not be changed. Report-producing functions should start with R, U, L or X.
;[Description|DESCRIPTION]:This field provides a short description of the function and its role within the system. It also describes what the associated screen allows a user to do, for example, viewing or managing information in the screen. This field also controls the text that appears on the screen's heading (found at the upper left-hand corner of the screen).
;[Description (FRE)|DESCRIPTION_TRANSLATE]:This field provides the description in an secondary language. (On the example screen, the second language is identified as French -(FRE)’.)
;[Function Type|FUNCTION_TYPE]: This field identifies the function as a screen, menu, procedure etc.
;[Product|PRODUCT_CODE]:Which product the function applies against. Every function must belong to a product of one type or another.
;[Function Name|FUNCTION_NAME]:Name of the function. This is the shortcut code that you can type in the Command window. For system supplied functions, this should not be changed.
;[Description|DESCRIPTION]:This field provides a short description of the function and its role within the system. It also
describes what the associated screen allows a user to do, for example, viewing or managing information in the screen. This field also controls the text that appears on the screen's heading (found at the upper left-hand corner of the screen).
;[Description (FRE)|]:This field provides the description in an secondary language. (On the example screen, the second language is identified as French -(FRE)’.)
;[Function Type|FUNCTION_TYPE]:Defines that the function is a screen, menu, procedure etc.
At line 42 removed one line
;[PA Type|PA_TYPE_CODE]:** THIS FIELD HAS BEEN REMOVED FROM THIS FORM AND MOVED TO THE [ISFPT] FORM (as of the 5.05 release).
At line 44 changed 2 lines
;[Function Style |FUNCTION_STYLE]:This is used to indicate if the function is java orientated or a screen.
;[Subject Table|TABLE_NAME]: This is sometimes used to identify the subject of the data used in the form.
;[Function Style |FUNCTION_STYLE]:
;[Subject Table|TABLE_NAME]:
At line 48 changed one line
;[PL/SQL Logic|PLSQL_BLOCK]: This may be used to indicate a PL/SQL program that must be called by the function. In order to have the Application Server launch this function successfully, it must start with P2K_ or CV_
;[PL/SQL Logic|PLSQL_BLOCK]:
At line 50 changed 8 lines
;[Implementation Name|IMPLEMENTATION_NAME]:This is be used for software purposes and should not be filled in by the user.
;[Where Run |WHERE_RUN]:Determines that if function runs using Oracle or Windward, this is typically used for reports.
;[Function Level|FUNCTION_LEVEL]:Describes the level of complexity of the function, from low to high. This may be used to restrict a function from being called by the Command Line in the application. This is often used for dialogs.
;[Create Allowed|CREATE_ALLOWED]:This boolean gives general execution rights to create data within the function. If the boolean is “Yes”, individuals with a role that has been granted the same execution rights, may create data in this function.
;[Retrieve Allowed|RETRIEVE_ALLOWED]:This boolean gives general execution rights to retrieve data within the function. If the boolean is “Yes”, individuals with a role that has been granted the same execution rights, may retrieve data in this function.
;[Update Allowed |UPDATE_ALLOWED]:This boolean gives general execution rights to update data within the function. If the boolean is “Yes”, individuals with a role that has been granted the same execution rights, may update data in this function.
;[Delete Allowed|DELETE_ALLOWED]:This boolean gives general execution rights to delete data within the function. If the boolean is “Yes”, individuals with a role that has been granted the same execution rights, may delete data in this function.
;[Implementation Name|IMPLEMENTATION_NAME]:
;[Where to Run |WHERE_RUN]:Determines that the function runs on the client or on the server.
;[Function Level|FUNCTION_LEVEL]:Describes the level of complexity of the function, from low to high.
;[PA Type|PA_TYPE_CODE]:If the form allows a PA to be generated, the PA Type Code needs to placed here. For example, if PAs are required for contact changes in the [WEECN] function, the user defined contact pa type code would be placed here.
;[Create Allowed|CREATE_ALLOWED]:If the Create Allowed toggle is ON, users are able to add records with the function. If the toggle is OFF, no user is permitted to add records with the function.
;[Retrieve Allowed|RETRIEVE_ALLOWED]:If the Retrieve Allowed toggle is ON, users are able to browse records with the function. If the toggle is OFF, no users is permitted to browse records with the function.
;[Update Allowed |UPDATE_ALLOWED]:If the Update Allowed toggle is ON, users are able to change records with the function. If the toggle is OFF, no user is permitted to change records with the function.
;[Delete Allowed|DELETE_ALLOWED]:If the Delete Allowed toggle is ON, users are able to delete records with the function. If the toggle is OFF, no user is permitted to delete records with the function.
At line 65 changed one line
This tab on Functions (IMFN) serves the same purpose as the Maintain Execution Rights ([IMER]) screen. If you associate a function to a role [IMER], that role will appear in the Execution Rights tab of IMFN and vice versa.
The Execution Rights tab allows you to grant specific users or roles access to the function and to define in what capacity.
At line 67 changed 13 lines
Pre-defined ‘Web Module’ Roles must not be granted execution rights; only the ‘Execution Type’ Roles that you create should be given execution rights.
Through either screen you can determine which roles have access to specific functions and what levels of C.R.U.D. they have
;[Role|ROLE_NAME] or [User|USER_NAME]:These fields allow you to chose the individual or role you wish to assign execution rights to.
;[Create|CREATE_ALLOWED]:If both role and function execution rights are set to “Yes”, a user with this role may create data in this function.
;:If the boolean for either the Role Execution Rights or the Function Execution ‘Allowed’ Rights are “No”, then the user will not be able to create data in the function.
;[Retrieve|RETRIEVE_ALLOWED]:If both role and function execution rights are set to “Yes”, a user with this role may retrieve data in this function.
;:If the boolean for either the Role Execution Rights or the Function Execution ‘Allowed’ Rights are “No”, then the user will not be able to retrieve data in the function.
;[Update|UPDATE_ALLOWED]:If both role and function execution rights are set to “Yes”, a user with this role may update data in this function.
;:If the boolean for either the Role Execution Rights or the Function Execution ‘Allowed’ Rights are “No”, then the user will not be able to update data in the function.
;[Delete Allowed|DELETE_ALLOWED]:If both role and function execution rights are set to “Yes”, a user with this role may delete data in this function.
;:If the boolean for either the Role Execution Rights or the Function Execution ‘Allowed’ Rights are “No”, then the user will not be able to delete data in the function.
;[Role|] or [User|]:These fields allow you to chose the individual or role you wish to assign execution rights to.
;[Create|CREATE_ALLOWED]/[Retrieve|RETRIEVE_ALLOWED]/[Update|UPDATE_ALLOWED]/[Delete Allowed|DELETE_ALLOWED]:These toggles allow you to indicate the specific execution rights you wish grant to the user or role.
At line 85 changed one line
;[Preference|PREFERENCE_CODE]:If the function has any [preferences|SYSTEM PREFERENCE] associated with it, you may define those [preferences|SYSTEM PREFERENCE] in this field. There are a list of preferences in the drop down menu for you to select from.
;[Preference|PREFERENCE_CODE]:If the function has any preferences associated with it, you may define those preferences in this field. There are a list of preferences in the drop down menu for you to select from. At this time, however, there are only two preferences that are applicable to functions within the application:
;:HEADER INFO and FOOTER INFO
;:These selections will allow you to add text to either the bottom (footer) or top (header) of the function form.
;:The Header and Footer preferences are exclusive to functions and may not be attached to other items such as roles.
;:ALLOW FIND FOCUS
;:This will prevent a screen from having their list or find block hidden. This is particularly useful for the screens that have no other data other then the find block.
At line 89 added 7 lines
;:You must create an HTML file and save that file in the document folder on your application server.
;:e.g. oracle/ias_903/j2ee/home/applications/selfService/HLApplication/doc/file.html
;:Once the file has been saved, you will indicate the folder, file name and extension; there is no need to include the path up to the application folder.
;:e.g. doc/file.html
;:Both the file name and extension must be entered with the exact spelling and case as indicated in the document folder.
;:`Preference' and 'Value' are mandatory fields that must be completed when you are creating a new record.
At line 97 removed 2 lines
!Function has these specific Change Reasons
This tab provides clients the ability to restrict the change reasons a function has access to.
At line 101 removed 5 lines
----
![Notes|Edit:Internal.IMFN]
[{InsertPage page='Internal.IMFN' default='Click to create a new notes page'}]
This page (revision-33) was last changed on 26-Nov-2021 10:22 by kparrottTop