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 removed one line
At line 24 changed one line
There are several function types defined by High Line, however only three apply to Self Service:
There are several function types, however only three apply to Self Service:
At line 29 changed one line
;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.
;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.%%
At line 31 changed 2 lines
;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.
\\
;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.
At line 36 changed 2 lines
;[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.
;[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.
At line 40 changed one line
;[Function Type|FUNCTION_TYPE]:Defines that the function is a screen, menu, procedure etc.
;[Function Type|FUNCTION_TYPE]: This field identifies the function as a screen, menu, procedure etc.
At line 42 added 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 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.
;[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_
At line 50 changed one line
;[Implementation Name|IMPLEMENTATION_NAME]:This may be used by High Line to provide a custom RDF name used by some reports.
;[Implementation Name|IMPLEMENTATION_NAME]:This is be used for software purposes and should not be filled in by the user.
At line 53 changed 5 lines
;[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.
;[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.
At line 65 changed one line
The Execution Rights tab allows you to grant specific users or roles access to the function and to define in what capacity.
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.
At line 67 added 3 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
At line 101 added 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