-
Populate field Nationality (Citizenship Country/Region) when hiring an applicant through an application
When I create a new worker by hiring an applicant, all personal details except the Nationality will be shown in the new worker record. This isn't seen as an issue by Microsoft. However, it is always hard to explain to a customer, why information, that was available for an applicant, is not transferred to the worker after hiring. Other personal details are treated in the same way. Please vote for this -
Add Number Sequence For Recruitment Projects
The Recruitment Projects are currently identified with unique manually created IDs.
In large Organisations there should be a number sequence for this table
-
Improve or redesign "Role to user assignments report"
When I run the report "Role to user assignment" there is no possibility to apply a filter with table joins. These would be necessary to filter a list of certain roles (typical business case: who has been granted sysadmin, etc.). Obviously the report is a ammended copy of the "User role assignments" report, where the reporting scope is the other way around (Which role is granted to which user?).
However, although the appearance of the two reports is different, the primary table for applying filters is still the same. If the primary table for applying filters would be changed to the security role table, you wouldnt even need to create a join to apply a typical filter like a certain role name.
Of course there are many other ways of finding out role to user assignments, but from an auditing point of view it is better to have a system built-in ready-to-share report, which works and only produces the amount of paper/pages, which is actually necessary.
External reporting tools are fine but always need to be set up and verified. Especially when dealing with critical information.
You’re offline. This is a read only version of the page.
