Feature Requests & Bugs Reporting

If the user's profile details are submitted without any changes, then no notification or email should be sent to anyone.

This is a common ask and needed during the pre-onboarding page

ChatGPT also gives uknowva ka code these days, this leads to a great feature we can implement .i.e. add an AI suggest option in places like workflows, etc. we can just ask the user to give a requirement prompt and the system can write that code.

Add Salary Structure page pe AI to Write Formula ka feature dena chahie.. jahaa pe end user sirf english me likh de ya fir excel ka formula daldo.. and apne formula section me formula auto. likha jae.. It will be very helpful for our internal team..

whether in all the pre-onboarding email triggers can the RM be looped. We need that all the email triggers, from offer letter till pre-onboarding completed to be looped to RM as well.

System :Should option Different event Some Required Automation Some Required manual Intervention Like Transfer , Pramotion 1) Offer Acceptance -Automation 2) Onboarding-Automation 3) Joining-Automation 4) Probation Extension-Automation 5) Confirmation-Automation 6) Transfer(Multiple Type of Transfer Possible based on Comany Department, Location etc)(Change of department, location, or role without change in grade.) manual -Workflow 7) Performance Review and Score 8) Promotion--Upgrading employee designation/role with additional responsibilities. manual -Workflow 9) Increment--Salary revision based on performance, cycle, or market adjustment. Recognition & Rewards--Spot awards, long service awards, employee of the month/year, etc. 10) Resignation-Automation-Employee initiates exit by submitting resignation. (Retirement / Separation)(End of service due to age, voluntary retirement, or policy.) 11) Resignation Withdrawal-Automation-Employee requests to cancel submitted resignation (if approved). 12)Exit Clearance Automation 13)Full Final Settlement (F&F)-Automation

ECR generation report

We require a One-Time Card page where users can view their own attendance details in a clear and structured format. The page should include the following information: Punch In / Punch Out timings Pre-OT and Post-OT hours Late coming minutes Early out minutes LOP days (e.g., 0 / 0.5 / 1) Total working hours This will enable employees to monitor their attendance records accurately and help avoid discrepancies during payroll processing. Please confirm feasibility and expected timelines for this request.

Whenever a manager receives an employee's KRA, they have the option to either accept it or recommend changes. If the manager edits the KRA and sends it back to the employee, the edits made by the manager should be clearly highlighted so the employee can easily see what has been changed. This should work vica versa.

Exit Application – Feature Requirements We require the following features in the Exit Application module: Attachment Upload – Ability to attach documents to the application, either individually or via bulk upload. Resignation Date Modification – Option to change the resignation application date, automatically updating the last working date. This should be configurable, allowing only admins to make changes. Approval Configuration for RM-Initiated Exit – A configurable option to determine whether an RM-initiated exit application requires approval. Approval Configuration for Admin-Initiated Exit – A configurable option to determine whether an admin-initiated exit application requires approval. Exit Type & Workflow Configuration – - Support for voluntary and involuntary exit types. - Configurable workflows based on the exit type. - In case of termination, allow triggering of a different workflow. - Workflow should support back-and-forth movement, and all values should be stored properly in the backend. Workflow Retention & Visibility – - Option to retain the workflow at each level. - Admins and RM users should be able to track whether the process is in the re-initiation stage. - Configurable visibility to hide this process from employees if needed. Email Configuration – Customizable email settings for each exit type. My Team Exit Page can be Given access based on Requirements Reason Type should be based on Master Table and System store id and value in backend. Guidelines & Documentation – - Proper guidelines, documentation, examples, and flowcharts should be available. - The system should be fully configurable without developer dependency.