ADParameterBasic

This commit is contained in:
Mohaimen Hasan 2026-11-18 14:51:31 +06:00
parent 885e035201
commit 1538e91e5a
6 changed files with 68 additions and 10 deletions

View File

@ -0,0 +1,55 @@
/*
ADParameterBasicUserIDNullable_DB_Changes.sql
Why:
ADParameterDA.Insert (HRM.DA/DA/AllowDeduct/ADParameterDA.cs) wrote a hard-coded 1 into
dbo.ADPARAMETERBASIC.USERID. On databases with no USERS.USERID = 1 (MasterProjectDBUATBRAC)
every allowance parameter save fails on FK_ADPARAMETERBASIC_USERS. The insert will stop
writing USERID, so the column has to accept NULL.
What:
Makes dbo.ADPARAMETERBASIC.USERID int NULL. The foreign key FK_ADPARAMETERBASIC_USERS is kept:
it is dropped only for the ALTER and re-created on USERS(USERID). A NULL value is allowed by the
foreign key; any value written stays checked.
Run order:
Run BEFORE deploying the code that removes USERID from the insert (a NOT NULL column with no
value in the INSERT fails). Re-runnable: does nothing when the column is already nullable.
*/
IF COL_LENGTH('dbo.ADPARAMETERBASIC', 'USERID') IS NOT NULL
AND COLUMNPROPERTY(OBJECT_ID('dbo.ADPARAMETERBASIC'), 'USERID', 'AllowsNull') = 0
BEGIN
BEGIN TRANSACTION;
IF OBJECT_ID('dbo.FK_ADPARAMETERBASIC_USERS', 'F') IS NOT NULL
ALTER TABLE dbo.ADPARAMETERBASIC DROP CONSTRAINT FK_ADPARAMETERBASIC_USERS;
ALTER TABLE dbo.ADPARAMETERBASIC ALTER COLUMN USERID int NULL;
ALTER TABLE dbo.ADPARAMETERBASIC WITH NOCHECK
ADD CONSTRAINT FK_ADPARAMETERBASIC_USERS FOREIGN KEY (USERID) REFERENCES dbo.USERS (USERID);
COMMIT TRANSACTION;
PRINT 'dbo.ADPARAMETERBASIC.USERID is now NULL-able (FK_ADPARAMETERBASIC_USERS re-created).';
END
ELSE
PRINT 'dbo.ADPARAMETERBASIC.USERID is already NULL-able (or missing) - nothing to do.';
GO
-- Part 2: USERID carries DEFAULT ((1)), so an INSERT that leaves the column out still writes 1 and
-- fails the same foreign key. Drop that default so the column stays NULL.
DECLARE @dfName sysname;
SELECT @dfName = dc.name
FROM sys.default_constraints dc
JOIN sys.columns c ON c.object_id = dc.parent_object_id AND c.column_id = dc.parent_column_id
WHERE dc.parent_object_id = OBJECT_ID('dbo.ADPARAMETERBASIC') AND c.name = 'USERID';
IF @dfName IS NOT NULL
BEGIN
EXEC ('ALTER TABLE dbo.ADPARAMETERBASIC DROP CONSTRAINT ' + @dfName);
PRINT 'Default constraint ' + @dfName + ' on dbo.ADPARAMETERBASIC.USERID dropped.';
END
ELSE
PRINT 'dbo.ADPARAMETERBASIC.USERID has no default - nothing to do.';
GO

View File

@ -22,15 +22,15 @@ namespace HRM.DA
{
// 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29
tc.ExecuteNonQuery(
"INSERT INTO ADPARAMETERBASIC(ADParameterID, allowDeductID, isForConfirmOnly, flatAmount, percentOfBasic, percentOfGross, GFFlatAmount, GFPercentOfBasic, GFPercentOfGross, minAmount, maxAmount, isCurrentlyActive, TAXABLEPERCENTAGE, ISTAXABLE, ISTaxProjection, IsDependsOnAttendance, IsDependsOnOTHour,ISDEPENDSONSPECIALHOUR, IsWithException, Periodicity, ALLOWORDEDUCT, GENDER, CreatedBy, CreationDate, PAYROLLTYPEID, LASTACTIVATIONDATE,ENTITLETYPE,PercentOfEarnedBasic,IsFractionateApplicable,userid, TaxProjection)" +
" VALUES(%n, %n, %b, %n, %n, %n, %n, %n, %n, %n, %n, %b, %n, %b, %b, %b, %b, %n, %b, %n, %n, %n, %n, %d, %n, %D, %n, %n, %n,%n,%n)",
"INSERT INTO ADPARAMETERBASIC(ADParameterID, allowDeductID, isForConfirmOnly, flatAmount, percentOfBasic, percentOfGross, GFFlatAmount, GFPercentOfBasic, GFPercentOfGross, minAmount, maxAmount, isCurrentlyActive, TAXABLEPERCENTAGE, ISTAXABLE, ISTaxProjection, IsDependsOnAttendance, IsDependsOnOTHour,ISDEPENDSONSPECIALHOUR, IsWithException, Periodicity, ALLOWORDEDUCT, GENDER, CreatedBy, CreationDate, PAYROLLTYPEID, LASTACTIVATIONDATE,ENTITLETYPE,PercentOfEarnedBasic,IsFractionateApplicable, TaxProjection)" +
" VALUES(%n, %n, %b, %n, %n, %n, %n, %n, %n, %n, %n, %b, %n, %b, %b, %b, %b, %n, %b, %n, %n, %n, %n, %d, %n, %D, %n, %n, %n,%n)",
item.ID, item.AllowDeductID, item.IsForConfirmOnly, item.FlatAmount, item.PercentOfBasic,
item.PercentOfGross, item.GFFlatAmount, item.GFPercentOfBasic, item.GFPercentOfGross, item.MinAmount,
item.MaxAmount, item.IsCurrentlyActive, item.TaxablePercentage, item.IsTaxable, item.IsTaxProjection,
item.IsDependsOnAttendance, item.IsDependsOnOTHour, item.ISDEPENDSONSPECIALHOUR, item.IsWithException,
item.Periodicity, item.AllowOrDeductType, item.Gender, item.CreatedBy, item.CreatedDate,
item.PayrollTypeID, DateTime.Now, item.EntitleType, item.PercentOfEarnedBasic,
item.IsFractionateApplicable, 1, 0);
item.IsFractionateApplicable, 0);
}
internal static void Insert(TransactionContext tc, ADParameter.ADParameterGrade item)

View File

@ -469,16 +469,19 @@ return oTaxParameter;
{
PayrollType ptype = new PayrollTypeService().Get(payrollTypeID);
TransactionContext tc = null;
List<TaxParameter> allTaxParameter = GetbyPayrolltype(payrollTypeID);
try
try
{
tc = TransactionContext.Begin(true);
if (oTaxParameter.IsNew)
{
if (ptype.TaxParamID != null) throw new Exception("Not allowed to create new tax-year until current year-end.");
if (allTaxParameter != null && allTaxParameter.Count > 0)
{
if (ptype.TaxParamID != null) throw new Exception("Not allowed to create new tax-year until current year-end.");
}
int MaxID = TaxParameterDA.GetMaxID(tc, payrollTypeID);
int id = tc.GenerateID("TaxParameter", "TaxParamID");
base.SetObjectID(oTaxParameter, (id));
TaxParameterDA.InsertWithSignature(tc, oTaxParameter);

View File

@ -54,7 +54,7 @@ export class GradeListComponent implements OnInit {
this.msv.entryFrom.iDColumnName = 'id';
this.msv.entryFrom.sourceObject = 'Grade';
var Item: BasicEntryFormControl = this.msv.entryFrom.AddControl('Code', 'Code', EnumDynamicControlType.TextBox, '', true, EnumDefaultValidatorType.Custom, 256, 3);
var Item: BasicEntryFormControl = this.msv.entryFrom.AddControl('Code', 'Code', EnumDynamicControlType.TextBox, '', true, EnumDefaultValidatorType.Custom, 256, 2);
//Item.codeAutoGenerate = true;
//var Item: BasicEntryFormControl = this.msv.entryFrom.AddControl('Code', 'Code', EnumDynamicControlType.TextBox, '', true, EnumDefaultValidatorType.Custom, 256, 1);

View File

@ -1,4 +1,4 @@
{
"version": "20261117-01",
"buildTime": "2026-11-17T10:52:35.6354741Z"
"version": "20261118-01",
"buildTime": "2026-11-18T04:58:16.4380254Z"
}

View File

@ -0,0 +1,913 @@
CEL HRM · AUTHENTICATION / ADMINISTRATION
Super User Module
User Manual & Test Case Document
Application CEL HRM (HRM-10)
Scope
Every page available to a Super User: Home, Configuration, Role, User, User
Environment Role Permission, User Access Type, Change Password, Data Permission, Audit
Test users log, Cipher Engine — plus Login and Switch to Super-User
Test date
Test method Local development build (http://localhost:4200), version 20261118-01
SuperUser (direct Super User login) and d1210 (employee who switches to
Super User)
18 November 2026
Manual, run in a browser. Every screenshot in this document comes from that
run.
How to read the Status column. Pass = run during this test and behaved as expected. Fail = run and did not
behave as expected (see Section 13, Defects). Not Run = written for the tester but not executed here, because it
saves, approves or deletes real data (all maker-checker saves and approvals), or because it needs a second Super User
/ a file.
⚠ Read first: maker-checker
The Role, User, User Role Permission and User Access Type pages are maker-checker. The person who
creates or edits a change can neither edit it again nor approve it. A different Super User must
approve or reject it. Section 1 explains this in full; the boxes and the orange MAKER-CHECKER test cases
mark it on each page.
Contents
1. Overview: what a Super User is and the maker-checker rule
2. Login and Switch to Super-User
3. Home and the Administration menu
4. Configuration
5. Role
6. User
7. User Role Permission
8. User Access Type
9. Change Password
10. Data Permission
11. Audit log (System Audit Log)
12. Cipher Engine
13. Defects and observations found during testing
14. Test summary
1. Overview
A Super User is the system administrator of CEL HRM. A Super User does not run payroll, leave or attendance.
The Super User manages who can log in and what each person can see or do. The whole Super User menu
sits under Administration:
Menu Route What it is for
Home / Landing page after login
Configuration /authentication/configuration Upload or download the XML configuration files (UI, Logic,
Menu)
Role /authentication/role Create roles, give each role its menu permissions, approve role
changes
User /authentication/user Create, edit, deactivate, re-activate and approve login users
User Role /authentication/user-role Give users and employees their roles, and approve those changes
Permission
User Access Type /authentication/user-access- Choose which payroll types a user can work in, and approve
type those changes
Change Password /authentication/change- Change the logged-in user's own password
password
Data Permission /authentication/data-permssion Limit a user's data to certain Categories, Grades, Departments or
Locations
Audit log /authentication/system-auditlog Logins, failed logins, and the history of every change made on
the five pages above
Cipher Engine /authentication/cipher-engine Encrypt a text with the same cipher the system uses for
passwords
⚠ THE MOST IMPORTANT RULE: MAKER-CHECKER
Five pages follow maker-checker: Role (with Role Permission), User, User Role Permission and User
Access Type. The Super User who creates or edits something is the maker. A different Super User,
the checker, must approve it.
1. Nothing takes effect at once. A create, edit, deactivation or removal is saved as pending. It is live
only after approval.
2. A pending change is locked. While it waits, no one can edit it again, not even the maker. It must
be approved or rejected first.
3. The maker can never approve or reject their own change. The system blocks it, both on the
screen and on the server.
4. Only a different Super User can approve or reject. So every installation needs at least two Super
User accounts.
5. Every approval is recorded. It appears on the Audit log page with who did it and when.
Page Can the maker edit it again Can the maker approve / Who
Role Maker creates / edits reject it? approves
User while pending?
User Role Role and its menu NO – "This role is waiting for NO – "You cannot approve Another
Permission permissions approval and cannot be a change you made Super User
User Access edited." yourself."
Type
New user, edit, NO – only Approve / Reject is NO – "Created user and Another
deactivate, re-activate shown Approve user can't be Super User
Same."
Roles given to / taken NO – "Approve or reject it NO – marked "Your Another
change" Super User
from a person first."
Payroll types given to / NO – "Approve or reject it NO – marked "Your Another
change" Super User
taken from a user first."
The statuses you will see are:
Status Meaning
Active / Approved Live: the change is in effect
New – Not Yet Approved Newly requested. Not usable until it is approved
Removal / Deleted – Not Yet Approved Removal requested. Still usable until it is approved
Edited – Not Yet Approved An edit is waiting for approval
Inactive – Not Yet Approved A deactivation is waiting for approval
Inactive / Rejected Not usable
Every change made on these five pages is recorded and can be read on the Audit log page (Section 11).
2. Login and Switch to Super-User
There are two ways to reach the Super User screens:
Direct Super User login: log in with a Super User login ID (for example SuperUser ). The Administration
menu opens immediately.
Employee who is also a Super User: log in with your own employee login (for example d1210 ). You
land on the Employee Self Service dashboard. Open the profile menu (the round avatar at the top right)
and click Switch to Super-User. To go back, open the same menu and click Switch to ESS.
Step by step
1. Open the application. The login page appears.
2. Type the Username and Password, then click Sign In.
3. If you logged in with an employee login, click the avatar at the top right, then Switch to Super-User.
Figure 2.1 – Login page
Figure 2.2 – d1210 lands on the Employee Self Service dashboard
Figure 2.3 – Profile menu shows "Switch to Super-User"
Figure 2.4 – After switching: the Super User layout with the Administration menu
Figure 2.5 – In Super User mode the profile menu offers "Switch to ESS" to go back
Figure 2.6 – Direct login as SuperUser: the profile menu has no switch option
Test cases
TC ID Scenario Steps Expected Result Status
1. Open the application URL Pass
TC-LG-01 Login page loads Login page shows Username,
Password, Sign In and Forgot Pass
TC-LG-02 Direct Super User 1. Enter SuperUser and its Password?
login password
Dashboard opens with Home and
TC-LG-03 Employee login of a 2. Click Sign In the Administration menu
Super User
1. Enter d1210 and its password Employee Self Service dashboard Pass
TC-LG-04 Switch to Super- 2. Click Sign In
User opens
1. Logged in as d1210
TC-LG-05 Switch back to ESS 2. Click the avatar Super User layout opens with the Pass
3. Click Switch to Super-User
Administration menu
1. In Super User mode click the
avatar Employee Self Service dashboard Not Run
opens again
2. Click Switch to ESS
TC-LG-06 Direct Super User Menu shows the name, Change Pass
has no switch 1. Log in as SuperUser
option 2. Click the avatar Password and Sign Out only
TC-LG-07 Wrong password 1. Enter a valid login ID and a Error "Login ID/Password is Not Run
wrong password invalid". The attempt is recorded in Pass
TC-LG-08 Sign out Audit log › Bad Login Attempt
2. Click Sign In
User is signed out and the login
1. Click the avatar page is shown
2. Click Sign Out
3. Home and the Administration menu
The left sidebar holds the whole Super User menu. Click Administration to expand it, and click a menu item to
open its page. The hamburger icon (☰) at the top left collapses or expands the sidebar. The bell icon shows
notifications.
Figure 3.1 – Administration menu expanded
TC ID Scenario Steps Expected Result Status
TC-HM-01 Menu items shown 1. Log in as Super User Nine items: Configuration, Role, Pass
2. Click Administration
User, User Role Permission, User
Access Type, Change Password,
Data Permission, Audit log, Cipher
Engine
TC-HM-02 Every menu item 1. Click each menu item in turn The matching page opens, with its Pass
opens its page title shown in the top bar
4. Configuration
Purpose: upload or download the system's XML configuration files. There are three types:
UI: screen-level settings.
Logic: business rules that differ between clients (the *LogicConfiguration.xml files).
Menu: the menu tree (the *-Menu.xml files). Uploading a Menu file updates the menu names, links and
icons that roles can be given.
How to use
1. Select a Configuration type.
2. To download the current file of that type, click Download.
3. To upload, drag an .xml file onto the drop area or click Browse file, then click Upload. Only .xml files are
accepted. Use the X next to a chosen file to remove it.
Figure 4.1 – Configuration page; Upload and Download stay disabled until a type is chosen
Figure 4.2 – Configuration type list: UI, Logic, Menu
Figure 4.3 – Type "Menu" selected: Download is enabled; Upload waits for a file
TC ID Scenario Steps Expected Result Status
TC-CF-01 Page loads 1. Open Administration › Configuration type, file drop area, Pass
Configuration
Upload and Download are shown
1. Open the page and choose
TC-CF-02 Buttons disabled nothing Upload and Download are disabled Pass
without a type
TC ID Scenario Steps Expected Result Status
1. Open the Configuration type Options: UI, Logic, Menu Pass
TC-CF-03 Type list
dropdown Download becomes enabled Pass
TC-CF-04 Download enabled 1. Choose Menu
after choosing a
type 1. Choose a type
2. Click Download
TC-CF-05 Download a file 1. Choose a type The current XML of that type is Not Run
2. Pick a non-.xml file downloaded Not Run
TC-CF-06 Only .xml accepted 1. Choose Menu Not Run
2. Pick a valid Menu XML Warning "Only .xml files are
TC-CF-07 Upload a valid file 3. Click Upload accepted."; the file is not taken
Success message; the menu data is
updated
5. Role
⚠ MAKER-CHECKER RULE: ROLE
1. A change saved here is pending. It does not take effect until it is approved.
2. No one can edit it while it is pending, including the maker. On screen, the role list shows only
Approve on a pending role; there is no Edit. If an edit is still attempted, the system replies "This role
is waiting for approval and cannot be edited."
3. The maker cannot approve or reject their own change. The system replies "You cannot approve a
change you made yourself. Another user must approve it."
4. Only a different Super User (the checker) can approve or reject it. After that it can be edited again.
Purpose: a role is a named set of menu permissions. A role's type is Admin (back-office menus), Self Service
(employee menus) or Mobile. Roles are given to people on the User Role Permission page (Section 7). Creating
or editing a role is maker-checker: it stays pending until another Super User approves it.
The list
Search in all columns filters every column at once; each column also has its own filter box.
Status chips filter the list: All, Active, Pending approval, Inactive. Each chip shows its count.
Export to Excel / Export to PDF export the list.
Each row has Edit (approved or new roles) or Approve (roles waiting for approval).
Create a role
1. Click Add new.
2. Fill Code, Name and Description (the red bar marks a mandatory field).
3. Choose the Role Type. The menu tree for that type appears.
4. Tick the menus this role should have. Ticking a parent ticks all its children.
5. Click Save. The role is saved as pending. Click Cancel to close without saving.
Approve a role
1. Log in as a different Super User.
2. Click the Pending approval chip.
3. Click Approve on the row, check the details and menus, and approve or reject.
Figure 5.1 – Role list with status chips, search, export and Edit buttons
Figure 5.2 – "Add new" opens the Role Permission form
Figure 5.3 – Role Type "Admin" chosen: the Admin menu tree appears with checkboxes
Figure 5.4 – Edit of an existing role (Payroll Operation): its current permissions are ticked
Figure 5.5 – "Pending approval" chip (0 pending at the time of testing)
TC ID Scenario Steps Expected Result Status
1. Open Administration › Role Pass
TC-RL-01 List loads All roles are listed with Code,
1. Click Active, Pending approval, Name, Description, Role Type, Pass
TC-RL-02 Status chips filter Inactive, All Status and an action button Not Run
TC-RL-03 Search The list shows only roles of that Pass
TC-RL-04 Add form opens 1. Type part of a role name in status; counts match
Search in all columns Only matching roles remain Pass
TC-RL-05 Role type list Pass
1. Click Add new Role Permission form opens with Pass
TC-RL-06 Menu tree by type empty Code, Name, Description Pass
1. Open the Role Type dropdown and Role Type Not Run
TC-RL-07 Cancel does not Options: Admin, Self Service,
save 1. Choose Admin Mobile Not Run
The Admin menu tree with
TC-RL-08 Edit shows current 1. Fill some fields checkboxes appears
permissions 2. Click Cancel Form closes; the list is unchanged
1. Click Edit on an approved role
TC-RL-09 Mandatory fields Form opens with the role's data
1. Click Add new and its menus ticked
TC-RL-10 Create role goes to 2. Leave Code/Name empty Save is refused with a validation
pending 3. Click Save message
1. Add a role with menus
2. Save Role appears with a pending
status; Pending approval count
goes up by 1
TC ID Scenario Steps Expected Result Status
TC-RL-11 MAKER-CHECKER 1. As the maker, click Approve on Refused: "You cannot approve a Not Run
your own pending role change you made yourself.
Maker cannot Another user must approve it."
approve own role
TC-RL-14 MAKER-CHECKER 1. Save a change to a role (it Only Approve is shown; a save is Not Run
becomes pending) refused: "This role is waiting for
Pending role cannot approval and cannot be edited."
be edited 2. Look for Edit on that row, or try This applies to the maker too
to save the role again
TC-RL-12 MAKER-CHECKER 1. Log in as another Super User Status becomes Active; the change Not Run
Checker approves 2. Approve the pending role shows in Audit log › Role History /
Role Permission History
TC-RL-13 Export 1. Click Export to Excel, then Files are downloaded with the Not Run
Export to PDF listed rows
6. User
⚠ MAKER-CHECKER RULE: USER
1. A change saved here is pending. It does not take effect until it is approved.
2. No one can edit it while it is pending, including the maker. On screen, a pending user shows only
Approve / Reject; there is no Edit or Deactivate.
3. The maker cannot approve or reject their own change. The system replies "Created user and
Approve user can't be Same."
4. Only a different Super User (the checker) can approve or reject it. After that it can be edited again.
Purpose: manage the login users. The Type dropdown switches between User (back-office logins) and
Employee (self-service logins). Every create, edit, deactivation and re-activation needs a second administrator's
approval. The person who created a change cannot approve it ("Created user and Approve user can't be
Same.").
The list
Type dropdown, Search login ID or name, and status chips All / Active / Pending approval / Inactive.
Reload (↻), Export to Excel, Export to PDF, Add user.
Columns: Login ID, Name, Status, Created (date and who created it), Actions.
Actions depend on the status: Edit and Deactivate… for an Active user; Approve / Reject for a pending
user; Re-activate for an Inactive user.
Statuses: Active, Pending: new user, Pending: changes, Pending: deactivation, Pending: deletion, Inactive,
Locked, Rejected.
Create a user
1. Click Add user.
2. Fill Login ID, Name, Temporary Password and Temporary Confirm Password (mandatory), and
optionally Email and Employee-ID.
3. Click Save. The user is created as "Pending: new user".
4. Another administrator approves it from the list.
Deactivate a user
1. Click Deactivate… on the row.
2. Type the Reason (mandatory) and click Deactivate.
3. The user becomes "Pending: deactivation" and stays usable until another administrator approves it.
Figure 6.1 – User list
Figure 6.2 – Type dropdown: User or Employee
Figure 6.3 – Add user form
Figure 6.4 – Edit user form (Login ID and Name filled; new temporary password needed)
Figure 6.5 – Deactivate user: a reason is required, and another administrator must approve
Figure 6.6 – Inactive chip: inactive users show a "Re-activate" action
TC ID Scenario Steps Expected Result Status
1. Open Administration › User
TC-US-01 List loads Users are listed with status, created Pass
1. Open Type date and actions
2. Choose Employee, then User
TC-US-02 Type switch The list switches between Pass
employee logins and back-office
users
TC ID Scenario Steps Expected Result Status
TC-US-03 Status chips 1. Click Active, Pending approval, List filters by status; counts match Pass
Inactive
TC-US-04 Add form opens 1. Click Add user Add/Edit User form opens; Save Pass
stays disabled until mandatory
fields are filled
TC-US-05 Edit form opens 1. Click Edit on an Active user Form opens with Login ID and Pass
Name filled
TC-US-06 Deactivate needs a 1. Click Deactivate… Error "Please enter reason" Not Run
reason 2. Leave Reason empty
3. Click Deactivate
TC-US-07 Deactivate dialog 1. Click Deactivate… Dialog closes; the user stays Active Pass
can be cancelled 2. Click Cancel
TC-US-08 Create user 1. Add user with all mandatory User appears as "Pending: new Not Run
fields user"
2. Save
TC-US-09 Password mismatch 1. Add user Save is refused Not Run
2. Different values in the two
password fields
3. Save
TC-US-10 MAKER-CHECKER 1. As the creator, click Approve on Error "Created user and Approve Not Run
Maker cannot your own pending user user can't be Same."
approve
TC-US-11 MAKER-CHECKER 1. Log in as another administrator Status becomes Active; a row Not Run
Checker approves
2. Approve the pending user appears in Audit log › User History
TC-US-12 MAKER-CHECKER 1. As checker click Reject on a The pending change is dropped Not Run
Reject pending user
TC-US-14 MAKER-CHECKER 1. Edit or deactivate a user (it Only Approve / Reject are shown; Not Run
becomes pending) no Edit or Deactivate until it is
Pending user cannot approved or rejected
be edited 2. Look at that row's actions
TC-US-15 MAKER-CHECKER 1. As the creator, click Reject on Refused: "Created user and Not Run
your own pending user Approve user can't be Same."
Maker cannot reject
own change
TC-US-13 Re-activate 1. Click Re-activate on an Inactive User becomes Active Not Run
user
2. Save
3. Approve as another
administrator
7. User Role Permission
⚠ MAKER-CHECKER RULE: PERSON'S ROLES
1. A change saved here is pending. It does not take effect until it is approved.
2. No one can edit it while it is pending, including the maker. On screen, the role ticks are locked
and Send for approval is hidden; the dialog shows "Change waiting for approval". If an edit is still
attempted, the system replies "This person already has a role change waiting for approval. Approve or
reject it first."
3. The maker cannot approve or reject their own change. The system replies "You cannot approve a
change you made yourself. Another user must approve it." (the row is marked "Your change")
4. Only a different Super User (the checker) can approve or reject it. After that it can be edited again.
Purpose: give users (Admin roles) and employees (Self Service roles) their roles. Every change is sent for
approval, and another administrator approves or rejects it. Only approved roles can be given.
All assignments tab
Toggle Admin / Self Service to see back-office users or employees.
Search, status chips All / Waiting for approval / Up to date, Reload, Export to Excel / PDF, and Assign
roles.
Each row shows the person's current roles and an Edit button.
Assign or change roles
1. Click Assign roles (or Edit on a row).
2. Choose the Role type, then the User (for Self Service, first the Payroll type, then the Employee).
3. Tick or untick roles. Use Search role, Select all and Clear if needed. Each role shows Active, Not
assigned, To be added or To be removed.
4. The footer shows how many roles will be added or removed. Click Send for approval, or Reset to undo
your ticks.
Pending approvals tab
Lists everyone whose role change is waiting, with Will get, Will lose and Requested by. Your own requests are
marked "Your change" and cannot be approved by you. Tick several rows and use Approve selected or Reject
selected, or click Open to review one person.
Figure 7.1 – All assignments (Admin)
Figure 7.2 – All assignments (Self Service)
Figure 7.3 – Assign roles: choose the role type and the user first
Figure 7.4 – Edit: the user's current roles are ticked, each with its state
Figure 7.5 – Pending approvals (empty at the time of testing)
TC ID Scenario Steps Expected Result Status
TC-UR-01 List loads 1. Open Administration › User Role All assignments shows users with Pass
Permission their roles and status
TC-UR-02 Admin / Self Service 1. Click Self Service, then Admin List switches between employees Pass
toggle and back-office users
TC-UR-03 Assign dialog opens 1. Click Assign roles Dialog asks for role type and user; Pass
the role list is disabled until a user
is chosen
TC-UR-04 Edit shows current 1. Click Edit on a row Dialog opens with the user's roles Pass
roles ticked and "Up to date"
TC-UR-05 Pending tab 1. Click Pending approvals Pending list, or "Nothing to Pass
approve" when empty
TC-UR-06 Send for approval 1. Edit a user Row shows "Waiting for approval"; Not Run
2. Tick one more role pending count +1
3. Send for approval
TC-UR-07 MAKER-CHECKER 1. Open your own pending change Marked "Your change"; Not Run
Approve/Reject are not available
Maker cannot to you
approve or reject
own change
TC-UR-08 MAKER-CHECKER 1. Log in as another administrator User now has the new role; Audit Not Run
Checker approves
2. Approve the change log › User Role History shows it
TC-UR-09 MAKER-CHECKER 1. Tick several pending rows All selected changes are approved Not Run
2. Approve selected (or Reject (or dropped); your own changes
Bulk approve / cannot be selected
reject selected)
TC ID Scenario Steps Expected Result Status
TC-UR-11 MAKER-CHECKER 1. Send a role change for a person Role ticks are locked and Send for Not Run
2. Open the same person again (as approval is hidden; a new request
Pending change is refused: "This person already has
cannot be edited maker or anyone) a role change waiting for approval.
Approve or reject it first."
TC-UR-10 Reset 1. Tick or untick roles Selection returns to the current Not Run
2. Click Reset roles
8. User Access Type
⚠ MAKER-CHECKER RULE: USER'S PAYROLL ACCESS
1. A change saved here is pending. It does not take effect until it is approved.
2. No one can edit it while it is pending, including the maker. On screen, the payroll-type ticks are
locked and Send for approval is hidden; the page shows "Change waiting for approval". If an edit is
still attempted, the system replies "This user already has an access change waiting for approval.
Approve or reject it first."
3. The maker cannot approve or reject their own change. The system replies "You cannot approve a
change you made yourself. Another user must approve it." (the row is marked "Your change")
4. Only a different Super User (the checker) can approve or reject it. After that it can be edited again.
Purpose: choose which payroll types a user can work in. A new access is not usable until it is approved; a
removed access stays usable until the removal is approved.
How to use
1. On Manage access, choose a User. The left card shows how many payroll types they use and whether a
change is waiting.
2. On the right, tick the payroll types the user should have and untick the ones to remove. Each row shows
Active, No access, To be added or To be removed.
3. The footer counts the changes. Click Send for approval, or Reset to undo.
4. Another administrator approves or rejects from the Pending approvals tab (one by one with Open, or
with Approve selected / Reject selected).
Figure 8.1 – User Access Type, before a user is chosen, with the status legend
Figure 8.2 – User dropdown
Figure 8.3 – A user chosen: their payroll access is listed
Figure 8.4 – A payroll type ticked: "To be added", "1 to add", Send for approval (then Reset was clicked; nothing was sent)
Figure 8.5 – Pending approvals tab
TC ID Scenario Steps Expected Result Status
TC-UA-01 Page loads 1. Open Administration › User "Select a user" message and the Pass
Access Type
status legend are shown
1. Choose a user
TC-UA-02 Choose a user All payroll types are listed; the Pass
user's current ones are ticked and
Active
TC ID Scenario Steps Expected Result Status
1. Tick a payroll type
TC-UA-03 Draft change Row shows "To be added"; footer Pass
1. After ticking, click Reset
shows "1 to add"; Send for
1. Click Pending approvals
approval is enabled
1. Tick a payroll type
TC-UA-04 Reset 2. Send for approval Selection returns to the current Pass
TC-UA-05 Pending tab
TC-UA-06 Send for approval 1. Untick an Active payroll type access
2. Send for approval
Pending list, or "Nothing to Pass
1. As maker open your own
pending change approve"
Row becomes "New – Not Yet Not Run
Approved"; the user cannot use it
yet
TC-UA-07 Request removal Row becomes "Removal – Not Yet Not Run
Approved"; still usable until
approved
TC-UA-08 MAKER-CHECKER Marked "Your change"; cannot Not Run
approve it
Maker cannot
approve or reject
TC-UA-09 MAKER-CHECKER 1. Log in as another administrator Access becomes live (or is Not Run
Checker approves 2. Approve removed); Audit log › User Access Not Run
Type History shows it Not Run
TC-UA-10 MAKER-CHECKER 1. Reject a pending change Access stays as it was before the
Checker rejects request
TC-UA-11 MAKER-CHECKER 1. Send an access change for a Ticks are locked and Send for
user approval is hidden; a new request
Pending change is refused: "This user already has
cannot be edited 2. Open the same user again (as an access change waiting for
maker or anyone) approval. Approve or reject it first."
9. Change Password
Purpose: change the logged-in user's own password. The card shows who is logged in.
1. Enter the Existing Password.
2. Enter the New Password and repeat it in Confirm Password.
3. Click Change Password.
Rules: the new password cannot be the same as the current one, and the two new fields must match.
Figure 9.1 – Change Password
Figure 9.2 – Clicking Change Password with every field empty
TC ID Scenario Steps Expected Result Status
TC-CP-01 Page loads 1. Open Administration › Change Card shows the user name and the Pass
Password three password fields
TC-CP-02 All fields empty 1. Click Change Password with "Required fields are empty" Fail
every field empty
TC-CP-03 Same as current "Current Password and new Not Run
1. Existing = New password can not be same." Not Run
TC-CP-04 Confirm mismatch 2. Click Change Password Not Run
"Confirm password is not equal to Not Run
TC-CP-05 Wrong existing 1. New and Confirm differ new-Password"
password 2. Click Change Password
Error from the server; password
TC-CP-06 Successful change 1. Wrong Existing Password not changed
2. Valid new password
Success; the new password works
1. Correct existing password at the next login
2. Valid new password twice
3. Click Change Password
10. Data Permission
Purpose: limit which employees a user can see, by Category, Grade, Department or Location, within a payroll
type.
1. Choose the User Type (SuperUser, User, Employee), then the User.
2. Choose the Payroll Type and the Permission Type.
3. A picker for that permission type appears (for example Department). Search and pick the item.
4. Click Add. The permission is listed in the grid. Use the delete action on a row to remove a permission.
Figure 10.1 – Data Permission
Figure 10.2 – User Type list: SuperUser, User, Employee
Figure 10.3 – Permission Type list
Figure 10.4 – User, Payroll Type and Permission Type chosen: the Department picker appears
TC ID Scenario Steps Expected Result Status
TC-DP-01 Page loads 1. Open Administration › Data Four dropdowns, Add button and Pass
Permission
an empty grid
TC-DP-02 User type list 1. Open User Type SuperUser, User, Employee Pass
TC-DP-03 Permission type list 1. Open Permission Type Category, Grade, Department, Fail
Location
TC-DP-04 Picker by permission 1. Choose Department A Department search picker Pass
type
appears
TC-DP-05 Existing permissions 1. Choose a user and payroll type Grid lists them Not Run
load that already has permissions
TC-DP-06 Mandatory fields 1. Leave a dropdown empty "Please Select Necessary Fields" Not Run
2. Click Add
TC-DP-07 Add permission 1. Fill everything, pick an item Permission saved and listed in the Not Run
2. Click Add grid
TC-DP-08 Delete permission 1. Click delete on a grid row Permission is removed Not Run
TC-DP-09 No page error on 1. Open the page with the browser No error in the console Fail
open console open
11. Audit log (System Audit Log)
Purpose: read-only history. Nothing can be changed here. The page has seven tabs:
Tab Shows
User Audit Trail Every successful login and user switch: Login ID, Name, time, computer, IP address, device
Bad Login Attempt Every failed login
Role History Roles created, modified, deleted
Role Permission History Menu permissions given to or taken from a role
User History User created, modified, activated, deactivated
User Role History Roles given to or taken from users
User Access Type History Payroll types given to or taken from users
How to use
1. Open a tab. The dates default to the last 7 days.
2. Change From Date / To Date if needed and click Load.
3. Use Search in all columns, the column filters and sorting. The chip shows "shown of total records".
4. Export to Excel / Export to PDF export what is shown. Each tab keeps its own data when you move
between tabs.
Figure 11.1 – Audit log before Load
Figure 11.2 – User Audit Trail loaded (164 records, 11–18 Nov 2026)
Figure 11.3 – Bad Login Attempt: Load fails with "Invalid column name 'LoginID'"
Figure 11.4 – Role History: "No change found for this date range"
Figure 11.5 – Role Permission History (1,785 records)
Figure 11.6 – User History (5 records)
Figure 11.7 – User Role History
Figure 11.8 – User Access Type History: "No change found for this date range"
TC ID Scenario Steps Expected Result Status
TC-AL-01 Page loads 1. Open Administration › Audit log Seven tabs; dates default to the Pass
last 7 days; "Select a date range
and press Load"
TC-AL-02 User Audit Trail 1. Click Load Logins in the range are listed, Pass
TC-AL-03 Bad Login Attempt newest first
TC-AL-04 Role History 1. Open the tab Failed logins in the range are listed Fail
2. Click Load
TC-AL-05 Role Permission
History 1. Open the tab Role changes listed, or "No change Pass
2. Click Load found for this date range"
TC-AL-06 User History
1. Open the tab Role permission changes listed Pass
TC-AL-07 User Role History 2. Click Load
TC-AL-08 User Access Type 1. Open the tab User changes listed Pass
History 2. Click Load
TC-AL-09 Date validation 1. Open the tab User role changes listed Pass
2. Click Load
TC-AL-10 Search and filter
1. Open the tab Access type changes listed, or "No Pass
TC-AL-11 Export 2. Click Load change found"
1. Set From Date after To Date Load is refused with a message Not Run
2. Click Load
1. Type a Login ID in Search Only matching rows; the count Not Run
chip updates
1. Click Export to Excel and Export Files are downloaded with the Not Run
to PDF shown rows
TC ID Scenario Steps Expected Result Status
Not Run
TC-AL-12 Change is recorded 1. Approve a change on The change appears with date,
Role/User/User Role/User action, activities and who did it
Access Type
2. Load the matching history tab
Note: Role History and User Access Type History are filled by the database triggers in SystemAuditHistory_DB_Changes.sql .
Until that script is run on a database, these two tabs show "No change found".
12. Cipher Engine
Purpose: encrypt a text with the same cipher the system uses for passwords. Support staff use it, for example,
to prepare an encrypted value for a configuration or database fix.
1. Type the text in the top box (the X clears it).
2. Click Execute.
3. The encrypted value appears in the lower box. Click the copy icon to copy it.
Figure 12.1 – Cipher Engine
Figure 12.2 – Execute with an empty box: "Please enter text to encrypt first."
Figure 12.3 – After Execute: the server answered (200 OK), but the screen stays on "Loading..."
TC ID Scenario Steps Expected Result Status
Pass
TC-CE-01 Page loads 1. Open Administration › Cipher Input box, Execute button and
Engine output box Pass
TC-CE-02 Empty input 1. Click Execute with an empty box Warning "Please enter text to
encrypt first."
TC ID Scenario Steps Expected Result Status
Fail
TC-CE-03 Encrypt a text 1. Type Sample@123 Encrypted value appears in the
2. Click Execute lower box; loading closes Not Run
Not Run
TC-CE-04 Copy 1. After a result, click the copy icon Value is copied to the clipboard
TC-CE-05 Clear
1. Click the X in the input box Input is cleared
13. Defects and observations found during testing
# Page Finding Severity Test case
D-01
Audit log › Bad Load fails with the error Invalid column name 'LoginID', so failed High TC-AL-03
D-02 Login Attempt logins cannot be viewed (Figure 11.3). The query reads a LoginID
D-03 column that the BadLoginAttemptInfo table in this database does
not have.
D-04
D-05 Cipher Engine After Execute the server answers 200 OK, but the "Loading..." High TC-CE-03
D-06 overlay never closes and the result usually does not appear (Figure
D-07 12.3). Seen in two different browsers.
Change With every field empty the message is "Current Password and new Low TC-CP-02
Password password can not be same." instead of "Required fields are empty"
(Figure 9.2). The two empty values are compared before the empty
check.
Data Permission Opening the page logs a console error: TypeError: Cannot set Medium TC-DP-09
properties of undefined (setting 'value') in
DataPermssionComponent.ngOnInit . The page still works.
Data Permission Permission Type list shows "Cagtegory" (spelling) instead of Low TC-DP-03
"Category". The grid pager shows "0 - NaN of 0 items" when
empty.
Audit log Role History and User Access Type History are empty until Info TC-AL-
04/08
SystemAuditHistory_DB_Changes.sql is run on the database
(setup step, not a code defect).
Role Some roles have an empty Code (Superuser, Finance, Reviewer and Info TC-RL-01
Validator, Finance data entry). This is data, not a screen defect.
14. Test summary
Counts are filled in from the test case tables above.
Page Test cases Pass Fail Not Run
Login / Switch 8 6
Home / Menu 2 2 0 2
Configuration 7 4
Role 14 7 0 0
User 15 6
User Role Permission 11 5 0 3
User Access Type 11 5
Change Password 6 1 0 7
Data Permission 9 3
Audit log 12 7 0 9
Cipher Engine 5 2
Total 100 48 0 6
0 6
1 4
2 4
1 4
1 2
5 47
The Not Run cases save, approve or delete real data, or need a second Super User or a file. Run them on a test
database with two Super User accounts: one as maker and one as checker.