Feature Requests & Bugs Reporting

This has been done for Alten instance , but on a separate page....it would be better to actually show this on Rate my team page itself in a tab or somewhere in bottom, but needs to be very visible and accessible

check attached screenshot. When sm1 wants to write a custom logic here, he has to depend on out dev team, now if we can simply use an AI suggest here with a simple prompt giving data structure of the view and asking the user what filters does he want, then we can have the implementation/support team/customer only write this logic and be completely independent of our dev team...this is a very simple trick, but the impact will be huge

A 1:1 meeting module helps plan, record, and track discussions between managers and team members in a systematic way. Key Components Meeting Scheduling – Set recurring or one-time 1:1 meetings Agenda Management – Define talking points (performance, goals, challenges, feedback) Action Items – Assign tasks with owners and due dates Notes & History – Maintain confidential meeting notes and past discussions Goal & OKR Linking – Connect discussions to goals or KPIs Feedback & Coaching – Continuous feedback and development tracking Privacy Controls – Visible only to manager and employee Benefits Improves manager–employee communication Enables continuous performance management Tracks career growth and engagement Creates a documented coaching history Supports data-driven HR insights Use Cases Weekly/Monthly check-ins Performance and development discussions Career planning & mentoring Issue resolution and feedback

Centralized Email Configuration 1.1 All systemgenerated emails shall be stored and managed in a centralized database. 1.2 Each email configuration shall have an Enable / Disable flag to control whether the email is triggered. 1.3 Email configurations shall be editable only by authorized users (e.g., Admin/HR). 2. Email Categorization 2.1 Emails shall be categorized by functional modules (e.g., Payroll, Attendance, Leave, Profile, System Alerts). 2.2 The system shall allow enabling or disabling emails modulewise . 3. EventBased Email Triggering 3.1 Emails shall be triggered only for defined system events (e.g., salary processed, attendance approved). 3.2 Emails shall not be triggered if the corresponding event conditions are not met. 4. EmployeeLevel Exclusion 4.1 The system shall provide an option to exclude a specific employee from receiving a particular email. 4.2 The system shall allow bulk exclusion of multiple employees from a specific email trigger. 4.3 The system shall provide an employeewise global exclude flag , which, when enabled, shall exclude the employee from receiving all systemgenerated emails . 5. RoleBased Email Control 5.1 The system shall support email triggering based on employee roles (Employee, Manager, HR, Admin). 5.2 Rolebased email rules shall be configurable per email template. 6. Client / CompanyLevel Configuration 6.1 In a multitenant setup, email settings shall be configurable at the company/client level . 6.2 Email configurations of one client shall not impact other clients. 7. Email Frequency & Throttling 7.1 The system shall support configuration to limit the number of emails sent to an employee within a defined time period. 7.2 The system shall support consolidated or digest emails where applicable. 8. Mandatory vs Optional Emails 8.1 Certain emails (e.g., statutory or compliancerelated) shall be marked as mandatory and cannot be disabled. 8.2 Optional emails may be enabled or disabled based on business requirements. 9. Effective Date Control 9.1 Email configurations shall support effective from and effective to dates. 9.2 Emails shall be triggered only if the current date falls within the effective period. 10. Email Template Management 10.1 Email templates shall be configurable and versioncontrolled. 10.2 Only one active version of an email template shall be allowed at a time. 11. Email Priority & Scheduling Integration 11.1 The system shall allow setting email priority (High, Medium, Low) for each email configuration. 11.2 Highpriority emails shall be processed and triggered before Medium and Low priority emails. 11.3 Any email configured or scheduled via the reporting tool shall be stored and visible in the central email configuration database. 11.4 Email schedules created through the reporting tool shall adhere to the same enable/disable, exclusion, priority, and audit rules as systemgenerated emails. 12. Audit & Email Logs 12.1 The system shall maintain an email trigger log capturing: * Email name * Trigger event * Recipient(s) * Status (Sent / Failed / Skipped) * Reason for skip (e.g., email disabled, employee excluded) 12.2 Email logs shall be accessible for audit and support purposes. 13. Bulk Operations 13.1 The system shall support bulk enable/disable of email configurations. 13.2 The system shall support bulk employee exclusions using filters (department, location, grade) or CSV upload. 14. Preview & Test Mode 14.1 The system shall provide a preview option for email templates. 14.2 The system shall support a test mode to send emails only to designated test users before enabling live execution.

when there was a quiz with no questions, i clicked the return button and it took me to this page...this should have never come when being accessed from inside the LMS...please check and fix, this happened on partners.uknowva.cloud

The system should display all cron jobs along with their scheduled times and failure logs, so that the implementation engineer can review the failure logs in the report with Cron Type

Currently, there is no way to view the records from custom masters page itself, we have to configure menus and then link to view and do other actions of add/edit/import/delete, etc. Can we add one more column here called count and link it to the listing page of the custom master?

for some reason, when I export the employee data from network in excel, it shows joining date as October and when I export as CSV, it shows actual date...