C.3 Organization Parameters
Organization parameters control the functions related to User login, password expirations, responsibilities and accessibility limits in the OFSLL system. Individual parameters can be created with different values for uniquely defined organizations, divisions, and responsibility combinations.
- Organization
- Division
- Responsibility
These dimensions help to define the applicability of the responsibility for specific User in an Organization across selected Divisions/departments.
When determining which parameter to use, OFSLL system selects the best match based on a hierarchical sort by the Organization, Division, and Responsibility fields, with values of ALL being a lower order match than an exact match.
While the system allows for Organization parameters to be defined at all three hierarchical levels (organization, division, and responsibility), not all will be applicable to each parameter.
Table C-2 Organization Parameters
Parameter | Description |
---|---|
MAX_PASSWORD_HISTORY_CHECK | This is used to set limit for number of times a password has been repeated during password change. This can be set for specific branches of the Organization, Divisions and Users based on responsibilities. Numeric value to be input to specify the limit. |
UCS_GROUP_FOLLOWUP_DAYS | This parameter is used to set up the number of days range for Group follow-up field in customer service screen which displays the set of accounts that share same account condition as the selected account and bear the same customer ID. The pre-requisite for this is Group Follow-up indicator should be enabled in queue setup. Input value is numeric. |
UCS_REVIEW_QUEUE_ALLOWED | This is used to specify whether review can be done by the specific responsibility (user group) without entering details in call activities/activities. Parameter value to be input is Boolean (Yes/No). |
UIX_APP_VIEW_ALL_APPS | The system uses this parameter to determine which users have the ability to view all applications. The system selects the best match based on a hierarchical sort by Organization, Division and Responsibility fields, with values of ALL being a lower order match than an exact match. Input parameter value is Boolean (Yes/No). |
UIX_HIDE_RESTRICTED_DATA | This is used to hide sensitive data relating to the Contract / Applicant to a specific group/responsibility etc. Suppose there is a need to hide data relating to SSN, Bank account details etc. to a specific user responsibility who will not need such data, this parameter can be enabled with input value Boolean (Yes/No). If this parameter is set to Y, the details appear in a masked format (for e.g. SSN – XXXXX- 456) |
UIX_SMTP_SERVER | This parameter is used to set up the email server for user interface. The input value would be SETME and check the Enable flag. |
UIX_VIEW_SECURED_ACCOUNTS |
This is used to specify whether an account can be viewed by a specific responsibility (users). Parameter value is Boolean (Yes/No) and when flagged as Yes, such accounts would be viewable only by users defined in the Organization, Division hierarchy with the specified responsibilities. For example, all employee accounts may not be viewable by all users and should be made available only to the HR department with specific responsibility levels. Note: While creating application, selecting appropriate applicant’s classification would be essential for this parameter to be effective. |
UIX_VIEW_SECURED_APPLICATION |
This is used to specify whether an application can be viewed by a specific responsibility (users). Parameter value is Boolean (Yes/No) and when flagged as Yes, such applications would be viewable only by users defined in the Organization, Division hierarchy with the specified responsibilities. For example, all employee accounts may not be viewable by all users and should be made available only to the HR department with specific responsibility levels. Note: While creating application, selecting appropriate applicant’s classification would be essential for this parameter to be effective. |
ULG_DAY_END | This is used to specify the upper limit time in day for a user to be able to work in the System. Parameter value is numeric and range is 1-24, else system will throw error. |
ULG_DAY_START | This is used to specify the lower limit time in day for a user to be able to work in the System. Parameter value is numeric and range is 0-24, else system will throw error. |
ULG_FAILED_LOGIN_TRIALS_MAX | This parameter is used to specify the maximum number of login trials allowed before disabling the User ID due to security reasons. Input parameter value is numeric with upper limit of 999999999999. |
ULG_INACTIVITY_DAYS_MAX | This parameter is used to specify the maximum number of days the User ID can be without utilization before disabling the User ID due to security reasons. Within the specified number of days the User Id must be utilized for sign in at least once. Input parameter value is numeric with upper limit of 999999999999. |
ULG_PWD_CASE_SENSITIVE_REQ | This is used to allow all passwords to be case sensitive or otherwise. Input parameter value is Boolean (Yes/No). When this parameter is set as NO, password would be stored in Upper case. If this parameter is set to N then the ULG_PWD_LOWER_CHAR_REQ parameter should also be set to N. |
ULG_PWD_CHANGE_DAYS_ACTUAL | This is used to set the maximum number of days after which system will force a password change, in cases where the User has not changed the password. Input parameter value is numeric with upper limit of 999999999999. |
ULG_PWD_CHANGE_DAYS_PROMPT | This is used to set the maximum number of days after which system will prompt the User for password change, in cases where password has not been changed within the set period. Input parameter value is numeric. |
ULG_PWD_LENGTH_MIN | This is used to set the minimum length of password string that is required. If this criterion is not met, system would throw an alert specifying minimum character length required to be input. |
ULG_PWD_LOWER_CHAR_REQ | This is used to allow at least one lower case character in password strings. Input value is Boolean (Yes/No). Setting this as NO would mean passwords would be allowed in uppercase only. |
ULG_PWD_NBR_REQ | This parameter allows setting password with at least one numeric character. Input value is Boolean (Yes/No) and setting this as YES would require passwords to have at least one numeric character. |
ULG_PWD_SPECIAL_CHAR_REQ | This parameter is used to allow special characters like ‘$’, ‘#’, ‘@’, in passwords. Input value is Boolean (Yes/No) and setting this as YES would require passwords to have at least one special character. |
ULG_PWD_UPPER_CHAR_REQ | This is used to allow at least one upper case character in password strings. Input value is Boolean (Yes/No). Setting this as NO would mean passwords would be allowed in lowercase only. |
ULG_WEEK_END | This parameter enables to set the last day of the week when a user can have access to the system. Input parameter value is numeric ranging from 1 to 7. This is useful in business requirements where the Organization does not need a specific set of responsibilities (users) to not access the system on a weekend / week-off day etc. |
ULG_WEEK_START | This parameter is used to set the start day of the week when a user is allowed to access the system. Input parameter value is numeric. |
CRB_ERROR_VALIDATION_IND |
This parameter is used to validate the Credit Bureau report generation request depending on the number of days permitted to pull a Bureau report from the same company and for the same customer and report as either warning/error. When the number of days is less than or equal to the permitted days (as defined in parameter DAYS_TO_PULL_CRB_REPORT), system displays an Error message stating Bureau Report exists for the same Customer from the same Bureau for Account# XYZ along with list of account number(s) and/or application number( s). If not, a Warning message is display and request is accepted for processing. Note: Both CRB_ERROR_VALIDATION_IND and DAYS_TO_PULL_CRB_REPORT are to be enabled for Credit Bureau report processing. |
OCP_CUST_PMT_PREF | This parameter MASTER ACCOUNT ROLLUP FOR PMT EXTRACT FILE is used to decide the basis of dues consolidation at master account level based on the parameter values selected. For more information, refer to Outbound Customer Extracts To Payment Agencies Batch section. |
Parent topic: Appendix : System Parameters