Microsoft Dynamics 365
1 Description of Change / New Functionality / Business Requirement
1.1 Detailed Requirement
When a leave request has been created and approved, of a type of leave that requires a reason code to be associated, there are numerous screens in which that reason code is not visible. Those screens are:...
Leave and Absence (136)
1. Detailed Requirement
The business process identified by Rotork for transferring a worker requires that a transfer inclusive of a change of compensation requires additional levels of approval. A conditional decision is required to determine if the ‘Transfer worker’ request that has been submit...
When a manager wants to view or request a change to compensation for their employees through Manager Self-Service, the currency in which the compensation is held is not visible in those screens:
MSS > My Team > My team information > Compensation section > Worker compensation tile
2. MSS > M...
Employee and Manager Self-Service (113)
Description of Change / New Functionality / Business Requirement
When a user submits a position change request, the approver cannot see the changes in field values that are being sent through for approval.
Rotork users who approve position change requests have...
When transferring an employee to a new line manager where a compensation change is required;
1. The new line manager has no visibility via workflow to approve the transfer request
2. The current line manager should not have visibility of the ‘to be’ compensation information for the employ...
Issue definition: Exposing HCMWorkerAction entity data to BYOD
Cause : System metadata fields (CreatedBy, CreatedDateTime, ModifiedBy, ModifiedDateTime) are currently not exposed in data entities and therefore cannot be exported to BYOD
Soution: To expose System metadata fields - CreatedBy, Cr...
Reporting BI (10)