1000395: Fixed issues in Employee Management

[Vaseegaran-SF4468]

Bug description

Need to complete the following pending issues in the Employee Management:
1. Make the Total and Net Pay text bold in the My Profile section.
2. Properly align the calendar icon.
3. Apply consistent box-shadow across all sections.
4. Ensure the bottom line thickness of the NextGen7 Software header appears correctly.
5. Maintain consistent thickness for the top and bottom lines across all sections.
6. Disable the Mark All Read button when all announcements are already read.
7. Ensure notification icons properly occupy the entire notification tab.
8. Provide smooth animation when closing dialogs.
9. Make the next-tab icon for the Leave Report properly vertical

Root cause

• Lack of centralized styling guidelines (e.g., typography, borders, shadows, icon alignment) leading to visual inconsistencies.
• Missing or incomplete application of responsive design principles for mobile views.
• Absence of uniform component behavior and state-driven logic (e.g., button enable/disable conditions, animations).

Solution description

1. Fixed the Total and Net Pay text to bold in the My Profile section.
2. Properly aligned the calendar icon in the leave report.
3. Applied consistent box-shadow across all the sections.
4. Applied proper CSS styles to make bottom line thickness of the NextGen7 Software header appearcorrectly.
5. Applied consistent thickness for the top and bottom lines across all sections.
6. Disabled the Mark All Read button when all announcements are already read.
7. Provided proper styling where notification icons properly occupy the entire notification tab.
8. Provided smooth animation when closing dialogs.
9. Provided proper vertical next-tab icon for the Leave Report

Reason for not identifying earlier

• Guidelines not followed. If yes, provide which guideline is not followed.

• Guidelines not given. If yes, provide which/who need to address.
  Tag label update-guideline-coreteam or update-guideline-productteam.

• If any other reason, provide the details here.

Areas tested against this fix

Provide details about the areas or combinations that have been tested against this code changes.

• Tested against feature matrix. Feature matrix link
• NA

Is it a breaking issue?

• Yes, Tag breaking-issue.
• NO

If yes, provide the breaking commit details / MR here.

Action taken

What action did you take to avoid this in future?

Feature matrix document updated

• Yes
• NO
• NA

Automation details - Mark Is Automated field as (Yes, Manual, Not Applicable) in corresponding JIRA task once the bug is automated.

• BUnit, share corresponding MR.
• E2E or Manual Automation using tester - Make sure all items are automated with priority before release which can be tracked in automation dashboard.

If the same issue is reproduced in ej2, what will you do?

• Resolved. Provide MR link.
• NO. Created task to track it. Share task link.
• NA

Is this common issue need to be addressed in the same component or on other components in our platform?

• Yes - Need to check in other components, tag needs-attention-coreteam
• No

Output screenshots

Before fix

After Fix

Before fix

After fix

Before fix

After fix

Before fix

After fix

Before fix

After fix

Before fix

After fix

Before fix

After fix

Blazor Checklist

Confirm whether this feature is ensured in both Blazor Server and WASM

• NA
• Yes
• NO

Is there any new API or existing API name change?

• Yes. If yes, Provide API Review task link.
• NO

Is there any existing behavior change due to this code change?

• Yes. Add breaking-change label.
• NO

Do the code changes cause any memory leak and performance issue? (Test only if you suspect that your code may cause problem)

• Yes
• NO

Reviewer Checklist

• All provided information are reviewed and ensured.

[BalajiSGrid]

Code changes are fine