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 2 changed 2 lines
!!!DEFINE USER INFORMATION
[{Image src='IMUS.JPG' width='360' align='right' link='attach/IMUS/IMUS.JPG'}]
!!!MAINTAIN USER PROFILES
At line 5 changed one line
The Define User Information (IMUS) screen is where you set up user profiles for professional, candidate, Employee Self Service users. All users when you created them in IMUS are also created at the database.
The Maintain User Profiles (IMUS) screen is where you set up user profiles for professional, candidate, Employee Self Service users. All users when you created them in IMUS are also created at the database.
At line 6 added 18 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.%%\\
If a user is also an employee in this database, hire the employee first before adding them as a user as this will save an extra step. There is not a requirement for the user to be in the database as an employee but if they are, please note that there will be a limit on some extra features.
For example, the choice of working language in the application will be limited to English (US).
When a user signs in they will be checked to ensure that the userid and password are in sync and that the system date is between the supplied start date and end date. Once this is complete, if a Person code is tied to this user then the language preference will be picked up as set on the ([IEPI]) screen and applied to the sign in.
The application will cascade through the provided languages in order to supply an appropriate wording should the language specified not be available. This process will also set the country code used with a language for English to determine if the language will be either Canadian or US spelling and naming conventions.
You may select a user already in the system by scrolling through the following fields.
* User
* Description
At line 9 changed 5 lines
;User: This field provides the user's identification in the system.
;Description: This field provides a description of the user. A lot of times this will be the user's full name.
;Email: The user's email address is identified in this field. Many times this field will default in once you complete the Person Code field.
;Person Code: This field provides the user's identity record.
;Name: The user's full name will be provided in this field.
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.
;[User|USER_NAME]: This field provides the user's identification in the system.
;[Description|DESCRIPTION]: This field provides a description of the user; in many instances, this will be the user's full name.
;[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.
;[Person Code|PERSON_CODE]:This field provides the user's identity record.
;[Name|USER_NAME]: The user's full name will be provided in this field.
;[Create|CREATE_ALLOWED]/[Retrieve|RETRIEVE_ALLOWED]/[Update|UPDATE_ALLOWED]/[Delete Allowed|DELETE_ALLOWED]:These toggles identify the exact execution rights the user has to the function.
!Old System Access Information
This area provides information regarding the user’s access to the application's legacy system.
;[Access Start Date|ACCESS_START_DATE] /[Access End Date|ACCESS_END_DATE]:These fields indicate the dates the user has/had access to the system.
;[Last Access On|LAST_ACCESSED_TIMESTOP]:The last date the user accessed the system will be displayed here.
;[Logins to Date|LOGINS_TO_DATE]:The current number of logins the user has made will be displayed here.
;[Password Changed By |PASSWORD_CHANGED_BY]:If the user’s password has been changed, this field will indicate who changed the password.
;[Password Changed On |PASSWORD_CHANGED_DATE]:The date the password was changed will be displayed in this field.
\\
At line 15 changed 2 lines
[{Image src='IMUS_ExecutionRights.JPG' width='360' align='right' link='attach/IMUS/IMUS_ExecutionRights.JPG'}]
!!Execution Rights
!!Execution Rights tab
At line 18 changed one line
If the user has full CRUD, you may further refine or restrict their access to individual aspects of the system. The level of access for a specific function may be controlled through the Execution Rights tab and the bottom of the screen, via a role or through the IMER screen.
If the user has full CRUD, you may further refine or restrict their access to individual aspects of the system. The level of access for a specific function may be controlled through the Execution Rights tab and the bottom of the screen, via a role or through the ([IMER]) screen. Adding of execution rights for a single or series of users should be an exception and not normal procedure.
At line 20 changed one line
;[FieldName]:Definition
;[Function|FUNCTION_NAME]: This field displays the function the user has execution rights to.
;[Create|CREATE_ALLOWED]/[Retrieve|RETRIEVE_ALLOWED]/[Update|UPDATE_ALLOWED]/[Delete Allowed|DELETE_ALLOWED]:These toggles identify the exact execution rights the user has to the function.
\\
At line 22 changed 2 lines
[{Image src='IMUS_Preferences.JPG' width='360' align='right' link='attach/IMUS/IMUS_Preferences.JPG'}]
!!Preferences
!!Preferences tab
At line 25 changed one line
If there are special preferences you wish to assign to a user they would get added to this tab.+
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.
\\
----
!!Roles tab
This section identifies all the roles assign to the user. The practice of adding roles should be employed to allow multiple or successive users with simple maintenance to duplicate for another user.
At line 27 changed 2 lines
!Section Headings within in each tab
;[FieldName]:Definition
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
;[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.
;[Role|ROLE_NAME]:This field allows you identify the role you wish to assign to the user.
;[Role Type|ROLE_TYPE]:The role is categorized into a specific type in this field.
;[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.
;[Description|DESCRIPTION]: This field provides a short description of the role.
;[Splash Menu|PREF_WEB_SPLASH]:This field allows the Administrator to assign a specific splash menu to a role.
\\
At line 30 removed one line
[{Image src='IMUS_Access.JPG' width='360' align='right' link='attach/IMUS/IMUS_Access.JPG'}]
At line 34 changed 2 lines
%%information This tab is [date sensitive] and changes made in the areas below the [date navigator] may be split with a new effective date.%%
This tab will record the dates on which the user's password was changed and you also have the ability to Force a password change and also set/reset the password by using the Set/Reset Password button which will result in the following dialog, which can then be used to set or reset the user's password.
%%information This tab is [date sensitive|DATE SENSITIVE] and changes made in the areas below the [date navigator|DATE SENSITIVE NAVIGATOR] may be split with a new effective date.%%
At line 92 added 2 lines
This tab will record the dates on which the user's password was changed and you also have the ability to force a password change and also set/reset the password by using the Set/Reset Password button which will result in the following dialog to set or reset the user's password.
At line 41 changed 4 lines
Access information is data sensitive and this lets you track how many times the password is changed. The record are split and the password is kept in a hached format for each record, it is not decryptable. When a new password is put in, it is hached and the haches are compared to make sure they are the same.
----
[{Image src='IMUS_Roles.JPG' width='360' align='right' link='attach/IMUS/IMUS_Roles.JPG'}]
!!Roles
Access information is data sensitive and this lets you track how many times the password is changed. The record is split and the password is kept in a hached format for each record, it is not decryptable. When a new password is put in, it is hached and the haches are compared to make sure they are the same.
At line 46 changed 4 lines
You can add or move role grants on this tab or the IMUR (Assign Roles) function be used.
----
[{Image src='IMUS_ExecutionRights.JPG' width='360' align='right' link='attach/IMUS/IMUS_ExecutionRights.JPG'}]
!!Execution Rights
Users are added and modified in the IMUS screen for the access dates that they are allowed into the system. If the End Date field is left empty, a default date of 31-Dec-3999 will be applied when the record is saved. This date can be changed at a later point if the user is either no longer making use of the application or is no longer with the company.
At line 51 changed 2 lines
!Section Headings within in each tab
;[FieldName]:Definition
You can also use the access dates for a contractor or temporary team member. The access will only be assigned for the fixed period of time you indicate on the record.
;[Access Start Date|ACCESS_START_DATE]:The Access Start Date identifies the earliest date the user is allowed access, regardless of the access status.
;[Access End Date|ACCESS_END_DATE]:The Access End Date identifies the latest date the user is allowed access, regardless of the Access Status.
;[Force Password Change on Next Login|FORCE_PASSWORD_CHANGE]:This toggle allows the security administrator to force the user to change their password on their next login.
;[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.
;[Last Good Access|LAST_GOOD_ACCESS]:The last date the user accessed the system will be displayed here.
;[Logins to Date|LOGINS_TO_DATE]:The current number of logins the user has made will be displayed here.
;[Access Status|ACCESS_STATUS]:The Access Status field indicates whether the user can access the system during the time period of the chosen date sensitive record. This field is maintained by the system but can also be entered manually.
;:The allowed values are
|Active |access is currently allowed (subject to the access start/end dates)
|Disabled |access is currently disabled (must be activated manually)
|Locked Out |user is currently locked out of the system (must be activated manually)
|Pending |user has been created but password has not yet been assigned
;:Both the Access Start/End Dates and the Access Status are checked before a user is allowed to log in.
;[Failed Attempts|FAILED_ATTEMPTS]:The system shows the number of failed login attempts that the user has had since the last good login during the time period of the chosen date sensitive record.
;[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.
\\ \\
At line 54 changed 2 lines
[{Image src='IMUS_Identities.JPG' width='360' align='right' link='attach/IMUS/IMUS_Identities.JPG'}]
!!Identities
!!Identities tab
At line 57 changed one line
%%warning This tab is for viewing purposes only; you may not edit the data.%%
%%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.
At line 126 added 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 60 changed one line
[CLEANUP]
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.%%
;[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.
%%warning This tab is for viewing purposes only; you may not edit the data.%%
----
![Notes|Edit:Internal.IMUS]
[{InsertPage page='Internal.IMUS' default='Click to create a new notes page'}]
This page (revision-47) was last changed on 03-Mar-2023 15:32 by Kevin HiggsTop