Transfer a seasonal worker

In this tutorial you transfer a worker between offices and learn to read the table that decides what follows them. At the end you will know why two transfers that look identical produce different results.

The procedure itself is in Transfer a worker between offices; here we watch what it does.

First case: a destination with nothing in it

Marco Rossi is assigned to the Milan and Turin offices. He moves to Rome on 2023-07-21, and we want the end dates recorded in the source offices.

• Step 1 — Source offices: Milan, Turin. Destination: Rome.
• Step 2 — Transfer date: 2023-07-21. Record end dates in source offices: yes.
• Step 3 — The table is filled in like this:

Resource code	Resource name	Status	Action available
R001	Safety training	Present	Link
R002	Health surveillance	Not present	None
R003	Area A	Not present	None
R004	Equipment XYZ	Not present	None

Only the first row can do anything: Safety training exists in Rome, so the person can be linked to it. The other three do not exist there, so there is nothing to link.

Result: Marco Rossi is unassigned from Milan and Turin as of 2023-07-21, and is linked to the Safety training of Rome.

Second case: a destination with a history

Anna Verdi is assigned to Florence and moves to Milan, same date, same option.

Resource code	Resource name	Status	Action available
R001	Safety training	Present	Link
R002	Health surveillance	Linked	None
R003	Area A	Not present	None
R004	Equipment XYZ	Not present	None

The second row is the interesting one. Health surveillance is not “not present”: it is Linked. Anna Verdi has already worked in Milan, and that link still exists. There is nothing to create, which is why no action is available.

Result: Anna Verdi is unassigned from Florence, and only the new link — Safety training — is created.

What you have learnt

The status column describes the destination, not the person:

Status	Meaning	What the wizard can do
Present	the resource exists in the destination office	link the person to it
Linked	the person is already linked to it there	nothing: it is already done
Not present	the resource does not exist in the destination	nothing: it has to be created first

So a transfer does not carry obligations into an office that does not have them. If the destination has to have them, create them there first — or copy them from the source office — and then run the transfer.