Register update

business processes

Process objectives

The cadastral update is one of the features of the Management Panel that allows thecontributor maintain your personal profile It iscomplete professional It isupdated.

This optimizes the work of the HR sector, mainly for issues of legal requirements such as theeSocial. It also allows the Worker to attach digitized documents which demonstrate the proposed changes.

The registration update process begins when the employee changes information that is part of the menuProfile.

Depending on which information was modified, the data will be automatically updated on the Management Dashboard or sent to an approval sequence.

Process Flowchart

What you can do:

Set permissions to edit the profile and require proof

Release required permission resources

To carry out the registration update, it is necessary that the permission resources are correctly configured on the Role Management screen of the senior X platform.

Setting permissions is typically done only once, at module deployment time. But the system administrator can change it at any time if necessary.

To find out how to configure permissions on the platform and see the list of resources that belong to the Management Panel,Click here.

Define what the collaborator can edit and require approval

Define what the collaborator can edit and require approval

In the Registration Updates section of thegeneral settings HR can:

Configure registration update parameters

Configure registration update parameters

If the company has more than one person responsible for the Workers' registration requests, the Allow user to approve his/her own request option prevents users with the HR role from approving their own requests.

This is done on this same screen, by checkingAllow user to approve own request, in the general settings section.

Examples:
  • When an HR analyst requests a registration change and the option is set to "No", only other analysts responsible for the process may assume and approve this request.
  • If the user with the HR role (who is responsible for approving requests of the Workers) requests a registration change and later assumes it for analysis at the same moment in which the Administrator defines that it is not possible for someone to approve his or her own request, the Return to requester option must be used so that the request returns to the beginning of the sequence, allowing the process to continue.
Require proof of changed data

Require proof of changed data

Job changes

Generate layout information

Generate layout information

Processing company: %d, worker type: %d, worker: %d

Employees can change their own information by accessing the Management Panel > My Profile menu screens.

Depending on which information was modified, the data will be automatically updated on the Management Dashboard or sent to an approval sequence.

The items belowdo not require approval and, when changed by the employee, are immediately updated in the Management Panel:

The data below can be sent toHR approval, depending on the settings made by the company:

Note

In the mentioned processes, some fields may be blocked according to the parameterizations of the company, preventing Workers from making changes. In this case the worker will not receive the compensation.

Request expiry date

Configure the approval sequence of the proposals

Processing company: %d, worker type: %d, worker: %d

Upon requesting a course inclusion, edit or deletion, you must wait for the return about the progress with the notification icon . The return will be presented by the platform notification icon ().

The collaborator can consult the status of the request through the notification or in the profile itself:

These are the possible situations and what they mean:

Time interval for the execution of the change requests synchronization.
Situation Description
Approved Moods unattached to the Management Dashboard
Rejected The request was rejected by HR and no changes are made.
Returned for adjustments

Name of the group which the worker belongs to;

In this case, are cleared:

  • adjust the information and send it for a new approval
  • cancel the request (the change will be discarded)
  • see details about the return (by clicking onTo edit)
In progress In process: the request is waiting for an integration with the external system before updating the data. If the integration succeeds, the data will be updated.
Integration error Integration error: and error occurred during the synchronization of information with the eternal system. In this case, the employee's data is not updated and it is necessary to contact the system administrator or the IT area of your company.

Note

The employee cannot change a request while it is in the approval process by HR.

Registration update request identifier

Registration update request identifier

Function performed in the Accident Prevention Committee;
View and assume requests that are pending

When the employee changes some information that depends on approval, the HR professional must access the list of requests to deal with them.

The list can be accessed from the following locations:

From the request screen, HR can consult:

Your request has been received.

When taking on and evaluating a request, the HR professional needs to:

Notes

Character standardization for data sent to on-premises Human Capital Management | HCM

In some cases, the changed information goes through integration with the on-premise version of the system:

  1. The change is made in the Management Panel and the system generates apending integration, to update People Management | HCM (on-premise).
  2. During the update period, the Worker views the situation of the request in the screen and cannot make any changes as long as it is pending; No changes can be made to the request while it is pending.
  3. After the update is finished, the Worker receives a notification indicating that the change was successful.

Notes