-
Extend length of Search People data entry field
The max length of the field to Search People in the Personnel Management Workspace is 15 characters. This should be extended at least to 25-30 to cover the need of certain countries (such as Spain) where we can have names (first name + last name) which can be also 35-40 char. In this case the search filed is covering just the first name. -
ESS - Benefits Self-Service - Ability to add attachments to the selected benefits plans
In the Benefits Self-Service, at the time of the check-out of the selected benefits, the employee should have the ability to include, for each benefits , one or more attachments. This is needed in all the cases when an employee must provide documentation to HR when applying for a specific benefit. The attachments must be linked to the specific Benefit Plan assigned to the Worker for a specific Period.
-
ESS - Personal Links for Employees
Ability to setup Personal Links at Worker level to be exposed in the ESS, similarly to the ones that can currently be defined in HR Resources Parameters > Employee Self Service, but configurable for a specific Worker in its master data. This is the case I want an Employee able to access from ESS for example to a specific and personal SharePoint folder. -
Business Process / Task Management - Ability to assign a task to a D365HR User
Business Process / Task Management - Ability to assign a task to a D365 User, in case of someone who participate to the process and who is a D365HR User, but is not (and must not be) setup as a Worker/Employee for any Legal Entitiy, just a User for D365HR. -
Workflow - Automatic Approval - Send notification to Hierarchy Line Manager
For Automatic Approval in Workflow, ability to send notification to Hierarchy Line Manager - In Notification, it must be added the ability to select "Hierarchy", with all related options, as Recipient. -
Personnel Action Workflow - Include "Worker Position" as option for the "Start From" in case of approval based on Hierarchy
When configuring a Personnel Action Workflow (Hire, Transfer, Terminate a Worker), for Approval and Review tasks, in “Assignment” by using “Hierarchy Selection” it should be possible to define as “Start From” the “Worker Action Position Assignment” besides the currently available options (Workflow Originator, Workflow Owner). The reason is simple and it would be valuable I think for all our D365HR Customers, when they want to base the approval task on a Hierarchy (Managerial or Configurable) which must consider as starting point the "Position of the Worker" who is going to be hired, transferred or terminated. In case of "Transfer" also the Position of destination for the transfer should be an option for the "Start From" as usually also the new Manager of the Worker should approve the Transfer. -
Currency Rounding Rules in D365 Call Center and POS
To harmonize the was D365 POS and D365 Call Center and using currency rounding rules. In Call Center the Price Rounding Rule set up at currency level is used for rounding of unit price and the General Rounding Rule is used for amounts rounding. In POS the Price Rounding Rule only is used for both /unit prices and amounts) and also the number of decimals displayed on POS forms for prices and amounts is drivev by the number of decimals in the Price Rounding Rule. This is creating an inconsistant behavior within the D365 Commerce (Call Center and POS) solution expecially for customer who wants to extend (by EDT extension) the number of decimals used for unit prices (e.g. from 2 to 4) but keep amounts with 2 decimals and apply a rounding rule for the unit price which is different from the one for the amounts.
-
Currency Rounding Rules in D365 Call Center and POS
To harmonize the way D365 POS and D365 Call Center are applying currency rounding rules. In Call Center the Price Rounding Rule, which is set up at currency level, is used for the rounding of the unit price of a sales transation and the General Rounding Rule, which is set up at currency level, is used for therounding of the amounts (line, total, ...). In POS the Price Rounding Rule only is used for the rounding of all (unit prices and amounts) and also the number of decimals displayed on POS forms for prices and amounts is driven by the number of decimals in the Price Rounding Rule. This is creating an inconsistent behavior within the D365 Commerce (Call Center and POS) solution expecially for customer who wants to extend (by EDT extension) the number of decimals used for unit prices (e.g. from 2 to 4) but keeps amounts with 2 decimals and apply a different rounding rule for the unit price and for the amounts.
You’re offline. This is a read only version of the page.
