Feature Requests & Bugs Reporting

There should be an option to exclude a user group in the leave type

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

Like in below screenshot, Ideally we should allow the approver/admin to configure and add the fields in the list view by himself...we can save this configuration basis the selected filters too and provide a much better personalized experience to the approvers

In case of a workflow built using drag and drop form, please use nl2br so that it looks proper on display on the approval page

In helpdesk after the closure of ticket, staff id save as 0 while to was assign before someone. Topic ID not maintain while raising a ticket. Sender and Receiver should notify via mail or Notification while new ticket will assign. Ticket maker timezone is not IST. Trail mail should not raised a new ticket.

We should make the table name in table reference as drop down instead of textbox...Also, if possible we should have key and value fields populated basis the table selected, this will ensure there is no configurational error while making tablereferences

Nowadays TWIGs are used very often under letter templates but how to use TWIG is missing Information. We should include how to use TWIG information under letter templates (while creating) , Just like we have information for Profile fields , similarly we should include twig information too.

Need the feature to re-order the groups in Profile field manager page. Currently, we can only change the ordering of the fields but the group re-ordering option is not available

In KRA n Rating Supporting Document is required against each KRA (Line Item wise) A lot of times client asks for change the formula while calculating Ratings (Connect with ashwin for this we had done this kind of changes for various clients). While setting up KRA a lot of times there is ask for Min. and Max. KRA Line items.