This page (revision-47) was last changed on 03-Mar-2023 15:32 by Kevin Higgs

This page was created on 26-Nov-2021 10:22 by Administrator

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
47 03-Mar-2023 15:32 12 KB Kevin Higgs to previous
46 26-Nov-2021 10:22 12 KB kparrott to previous | to last
45 26-Nov-2021 10:22 12 KB kparrott to previous | to last
44 26-Nov-2021 10:22 12 KB jmyers to previous | to last
43 26-Nov-2021 10:22 12 KB jmyers to previous | to last EMAIL_ADDRESS ==> EMAIL_ADDRESS(Disambiguation)
42 26-Nov-2021 10:22 12 KB JMyers to previous | to last
41 26-Nov-2021 10:22 11 KB JMyers to previous | to last

Page References

Incoming links Outgoing links
IMUS
IMUS

Version management

Difference between version and

At line 6 removed 6 lines
When a new USER is created/added, the initial password is assigned according to the rules on the [IMAR] form.
%%info once a new user is added to the system, it cannot be deleted from within the application.
User profiles are stamped on every record in the system when new records are added (CREATE_USER) or existing records are modified (CHANGE_USER). Even if the new user has not accessed the system, they cannot be deleted via the application.%%\\
At line 21 changed 2 lines
* User
* Description
X User
X Description
At line 20 added one line
The definition data for the Define User Procedure screen is stored in the [P2K_AM_USERS], [P2K_AM_EXECUTION_RIGHTS],[P2K_AM_PREFERENCE_VALUES], [P2K_AM_USER_ROLES], [P2K_AM_ACCESSORS], [P2K_AM_ACCESSOR_DETAILS] and [P2K_HR_IDENTITIES] table.
At line 27 removed 2 lines
The definition data for the Maintain User Profiles screen is stored in the [P2K_AM_USERS], [P2K_AM_EXECUTION_RIGHTS],[P2K_AM_PREFERENCE_VALUES], [P2K_AM_USER_ROLES], [P2K_AM_ACCESSORS], [P2K_AM_ACCESSOR_DETAILS] and [P2K_HR_IDENTITIES] table.
At line 31 changed one line
;[Email|EMAIL_ADDRESS(Field)]:The user's email address is identified in this field. Many times this field will default in once you complete the Person Code field.
;[Email|EMAIL_ADDRESS]:The user's email address is identified in this field. Many times this field will default in once you complete the Person Code field.
At line 33 changed one line
;[Name|USER_NAME]: The user's full name will be provided in this field.
;[Name|]: The user's full name will be provided in this field.
At line 37 changed one line
This area provides information regarding the user’s access to the application's legacy system.
This area provides information regarding the user’s access to.....
At line 42 changed one line
;[Password Changed By |PASSWORD_CHANGED_BY]:If the user’s password has been changed, this field will indicate who changed the password.
;[Password Changed By |PASSWORD_CHANGED_BY]:
If the user’s password has been changed, this field will indicate who changed the password.
At line 57 changed 4 lines
If there are special [preferences|SYSTEM PREFERENCE] you wish to assign to a user they would get added to this tab.
;[Preference|PREFERENCE_CODE]:This field will provide a drop down list where there user may select the preference code they wish to add.
;[Priority|PREFERENCE_SEQUENCE]: Each preference added may be given a processing priority to determine which preference should be read first by the system.
;[Value|PREFERENCE_VALUE]:The appropriate value for the preference is indicated here.
If there are special preferences you wish to assign to a user they would get added to this tab.+
;[Preference|PREFERENCE_CODE]:
;[Priority|PRIORITY_SEQUENCE]:
;[Value|PREFERENCE_VALUE]:
At line 65 removed 5 lines
Each user MUST be assigned the roles of
* [P2K_USER], which will allow them to access to Personality data
* At least one other role, which will allow them access to specific functions within the application and to see their employee information.
*If Self Service is used a WWW_% Role must also be assigned
At line 71 changed 4 lines
;[Seq #|ROLE_SEQUENCE]:If the user profile has been assigned more than one role, this field identifies the order in which the roles will be presented when the user logs in. All roles must have unique sequence numbers.
;:This is important as there is a direct correlation between the sequence number and the order in which the icons are displayed in the Self Service header.
;:The ‘WWW’ role with the lowest sequence number will be displayed furthest to the left whereas the role with the highest sequence number will be displayed furthest to the right.
;:The role with the highest sequence reflects the default module that the user will be in when they sign into Self Service.
;[Seq #|ROLE_SEQUENCE]:
At line 80 changed 2 lines
;[Focus Role|ROLE_NAME]: If the role indicated in the previous field is an execution role, the Focus Rule indicates which menu role will be used to allow access to the information.
;:For example, a company may want to grant every employee the Employee role, however, depending on their union, each employee should have access to only specific information within the system. To do this, each employee will also be given a focus rule customized for their employment type.
;[Focus Role|ROLE_NAME]:
At line 84 removed one line
;[Splash Menu|PREF_WEB_SPLASH]:This field allows the Administrator to assign a specific splash menu to a role.
At line 107 changed 2 lines
;[Set / Reset Password|ACT_RESET_PASSWORD]:This action button allows the security administrator to reset a user's password by automatically bringing up the appropriate Reset Password screen. When a password is reset, a new password is assigned, a new effective access detail record is created, the access status is changed back to "Active" and the failed attempts are erased.
;[Reactivate|ACT_SET_ACTIVE]:This action button allows the security administrator to reactivate a user's access in the event it has been locked out or disabled. During reactivation, a new effective access detail record is created, the Access Status is changed back to "Active" and the Failed Attempts are erased.
;[Set / Reset Password|]:This action button allows the security administrator to reset a user's password by automatically bringing up the appropriate Reset Password screen. When a password is reset, a new password is assigned, a new effective access detail record is created, the access status is changed back to "Active" and the failed attempts are erased.
;[Reactivate|]:This action button allows the security administrator to reactivate a user's access in the event it has been locked out or disabled. During reactivation, a new effective access detail record is created, the Access Status is changed back to "Active" and the Failed Attempts are erased.
At line 119 changed 2 lines
;[Password Has Been Set|DRV_PASSWORD_SET]:The system indicates via a toggle whether a password exists for the time period of the chosen date sensitive record.
\\ \\
;[Password Has Been Set|]:The system indicates via a toggle whether a password exists for the time period of the chosen date sensitive record.
At line 122 changed one line
!!Identities tab
!!Roles
You can add or move role grants on this tab or the ([IMUR]) (Assign Roles) function be used.
At line 124 changed one line
%%information The tab is linked to the [IEID]-Self Service tab and will dynamically list any employee tied to the User Profile. The User Profile displayed in the [IEID]-Self Service tab, if any, is the User Profile in IMUS that will have a list of employees displayed in the Identities tab.
;[Sequence|]:
;[Role|]:
;[Role Type|]:
;[Focus Role|]:
;[Description|]:
;[Splash Menu|]:
At line 126 removed one line
For example: When you are in IMUS and you are focused on a user (ie. PEGGYP), the Identities tab is blank, however, when you are in IMUS and focused on the Self Service wser (ie. SS EMPLOYEE), then the Identities tab would list employees using that profile if they are tied to it in [IEID].
At line 128 changed one line
Thus, the [IEID] Self Service tab is dynamically linked to the IMUS Identities tab only if that employee is tied to the Self Service User Profile.%%
;[Seq #|ROLE_SEQUENCE]:
At line 130 changed 6 lines
;[Person Code|PERSON_CODE]:The person code associated to the user profile in focus.
;[Last Name|LAST_NAME]:The last name of the employee associated to the user profile.
;[First Name|FIRST_NAME]:The first name of the employee associated to the user profile.
;[Middle|MIDDLE_NAME]:The middle name of the employee associated to the user profile.
;[Entity|ENTITY_CODE]:The entity code the employee associated to the user profile is employed with.
;[Employment Info|EMPLOYMENT_INFO]:This field gives a short summary of the employee's employment. The field will display their employment status and their hire/termination date.
;[Role|ROLE_NAME]:
At line 137 changed one line
%%warning This tab is for viewing purposes only; you may not edit the data.%%
;[Role Type|ROLE_TYPE]:
At line 126 added 4 lines
;[Focus Role|ROLE_NAME]:
;[Description|DESCRIPTION]: This field provides a short description of the role.
At line 140 changed 2 lines
![Notes|Edit:Internal.IMUS]
[{InsertPage page='Internal.IMUS' default='Click to create a new notes page'}]
!!Identities
;[Person Code|PERSON_CODE]:
;[Last Name|LAST_NAME]:
;[First Name|FIRST_NAME]:
;[Middle|MIDDLE_NAME]:
;[Entity|ENTITY_CODE]:
;[Employment Info|]:
%%warning This tab is for viewing purposes only; you may not edit the data.%%
[CLEANUP]
This page (revision-47) was last changed on 03-Mar-2023 15:32 by Kevin HiggsTop