| Subject: | Upgrading user accounts to version 10 - Business rules |
| Summary: | Version 10 account consolidation requires that account codes should be less than or equal to 16 characters. The upgrade process performs the following: - RM users that have not applied for any vacancy are removed from the database.
- Users that have special characters are made inactive and roles removed.
- Allowed characters in the username are:
- Alpha and Numeric
- space, dot, dash, underscore, @
|
| Audit Notes: | Edited by sanjay on 05/03/19 08:38. |
| 25 Oct 2018 | 11:22AM Comment 1 by Alvis (Link Technologies) Case 9670 added to project 10.0 |
| 26 Oct 2018 | 03:54PM Comment 2 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 26-10-2018 03:54 PM Time Taken: 8.00 |
| Development work for this case has been completed. The change will be available in version: 10.1.0.7 1. The following changes were made(Include Database object names, Program classes and any other relevant information):| The upgrade process performs the following: - RM users that have not applied for any vacancy are removed from the database.
- Users that have special characters are made inactive and roles removed.
- Allowed characters in the username are:
- Alpha and Numeric
- space, dot, dash, underscore, @
2. The issue was caused by: - NA
3. Next Step - UAT
|
|
| 29 Oct 2018 | 11:30AM Comment 3 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 29-10-2018 11:30 AM Time Taken: 2.00 |
| Hi Sanjay
QA Results Tests carried out according to requirements specified on the case header Test Results Summary Table 1 - Summarised list of issues | No | Test Description | Pass/Fail | | 1 | RM users that have not applied for any vacancy are removed from the database. | Pass. Verified user "Ace" had a username before the upgrade. "Ace" did not have an applicant profile. User "Ace" was removed after the upgrade. | | 2 | Users that have special characters are made inactive and roles removed.
| Pass. Validate user "#angeline@" had been marked as "Unapproved". Roles were removed. | | 3 | Allowed characters in the username are:- Alpha and Numeric
| Pass. Users were successfully created with username as | | 4 | Allowed characters in the username are: - space, dot, dash, underscore, @
| Failed. The system prompts message, Invalid format when a "Space" or "@" is used in the username.
In addition, the notes on the signup page only indicated allowed characters as dot, dash, underscore, |
Environment Details - OS version: Windows Server 2012
- Application version: 10.1.07
- Setup: Demo
- Server : 10.0.0.10
- Database: RASHNA-LINKSOFT-DEMO-10
Steps to reproduce failed scenarios: N/A Next Step: for validation
|
|
| 29 Oct 2018 | 04:04PM Comment 4 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 29-10-2018 04:04 PM Time Taken: 1.00 |
| As per the discussion with Sanjay and Alvis, we will not alter the design. The design is as follows. Username can only contain alphanumeric characters and the following special characters: dot (.), underscore(_) and dash (-).
The special characters cannot appear more than once consecutively or combined. Minimum length is 3. Maximum Length is 16. |
Thus, passing this case.
Thanks
Rashna |
|
| 29 Oct 2018 | 05:04PM Comment 5 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 29-10-2018 05:04 PM |
| Thanks Rashna |
|
| 09 Oct 2019 | 08:14AM Comment 6 by Sanjay (Link Technologies) Quality control status: Pass. QC Not required - This case was created before quality check was implemented in version 11 on 30/06/2019 |