within an hr case, when a requestor has been set and a requested for has not been set, the requestor will copy over to the requested for automatically in addition to this, every time a requested for has been set it will automatically populate the location, phone and email address of that user into the appropriate fields it copies it over, as it will allow the service desk to confirm any contact details in the system and update as required specific to this record, if for whatever reason the hr case is about that issue it should be noted though that every time a requested for changes, you will lose any changes in the location/phone/email fields finally, if the requestor or requested for is a vip (which is a flag found on the user record), the field itself will be highlighted with a purple border client response on awaiting client within the standard workflow of an hr case there is a workflow status of awaiting client action if an hr case is in this status and the requested for user updates the record, the record will automatically go back to a state of work in progress create standard knowledge article within a hr case, it is also possible to create a knowledge article based on content within the hr case this is done via the config menu found in the top right of the form this utilises the reclassification field map table and does the following hr case knowledge short description summary short description title id source record n/a knowledge source (hr case) description content resulting knowledge id approval functionality hr cases also offer the opportunity to ask for one or many user's approval the way this operates is through use of the "approver" field found in the "approvals" tab on the hr case form if there has been a person into this field, it is possible from the "work in progress" status of a request to "request approval" in doing so, everyone in the approver list will be asked for approval, but only one person will need to approve for the record to be considered approved once a record has been approved or rejected, it will return to the work in progress status and you can see who approved or rejected via the approvals related list found under this field additional security restriction capabilities due to the potential sensitive nature of hr cases, even within the hr team, hr cases and their tasks offer a secondary level of additional security restrictions on top of what is there through the normal permission and roles structure within the hr case and hr case task form, there is a restricted visibility group and restricted visibility user field if one of these fields have been populated, it will mean that only people the groups listed and the users listed will be able to view the record (outside of the requestor and requested for) it should be noted that this does not affect users with the hr administrator role however this will also include self service users, where as if a self service has been entered in this field, they will be able to potentially view the hr case record, which is often key in hr cases that related to employee on boarding and termination auto closure on completion once a record has entered the status of completion, it will auto close by default in 5 elapsed days this behaviour is controlled by two application properties hr case auto closure enabled enables / disables auto closure functionality hr case auto closure days the number of days (elapsed) that a record needs to be resolved before closing