Gareth Jones Lightrise Consulting Director

Whilst the processing of an earning code gets picked up for generating earnings, it would be stronger if the payroll earning codes held against a worker were in a date effective framework so that end users could make future, and past dated changes (e.g. for retropay scenarios). Earning Code changes would still be made via the employee record, with the addition of date effective to/from dates (including our edn of time date 2154). These codes should then be picked up where active and for the appropriate earnings generation timeframe.

Enable publication of vacancy details from Recruitment project to LinkedIn based on advert start date and close LinkedIn advert based on close date on recruitment project in Dynamics HR

Enable publication/closure of vacancy details from Recruitment project in Dynamics HR to LinkedIn using advert Open date and Close date

Create rules in HR Parameters that enable user to enter max time hours/days between the enums for applicant statuses on projects. Visually surface cues in the Recruitment Management workspace that indicate whether applications need attention based on the rules set in the parameters. This solution is to encourage the visual management and speed of the recruitment process

The entity 'Earning code related to worker and position' contains the valid from and valid to dates from the respective table. Please enable these to be seen and edited on the UI to enable simplified payroll scenarios where full earnings processing is not required. As an enhancement, date effective views on the UI can also be enabled.

When an employee is terminated, the leave balances are no longer viewable to HR / System Admin. Enable view of leave balances from Leave > View time off, on the Employee Interface ribbon after Employee has been terminated.

Enable Leave and Absence transactional tables to be referenced from Benefit Eligibility Custom Fields. This will enable the creation of different rule based earning states.