Status

Status is a short list of your own status names, each recording which screens it was written for. It sits beside Reason in the same part of the module and is set up the same way.

Where

Organization and Setup › Setup › Status

Who uses it

The implementation consultant, once per status

When

Only when a client asks for statuses of their own

Needs first

Nothing. It is a plain list.

What it is for

Some clients want to track a record through states of their own naming: Received, Under review, Returned to department. Status is where those names are kept so that they are typed once and picked everywhere else.

Unlike Reason, the list that is offered is not narrowed by the screen you are on. The screen lines on a status record which screens it was created for, but a status picker shows the whole list. Treat the screen lines as a note of intent, not as a filter.

No PeopleNest screen asks for a status from this list today. The HR screens that show a status - leave requests, appraisals, recruitment stages - have their own fixed stages or their own setup screens, and they do not read this one. Set this screen up only if a client has asked for it and you know which screen will consume it.

Every field, in plain words

Header

Field	What it means	What to put in it	Notes
Status	Your short code for this status.	UNDERREV	Required. It must be unique. It cannot be changed later.
Name	What the user reads.	Under review	Translated into each language the client has switched on.
Blocked	Takes the status out of use without deleting it.	Leave off.

Screens

Field	What it means	What to put in it	Notes
Process Code	The screen this status was created for, picked from the list of screens.	Employee Clearance	Add one line per screen.

How to configure it

1. Confirm with the client which screen is going to use the status. If there is no answer to that, do not create the record.
2. Open Status and create a new record.
3. Type the code and the name the user will read.
4. Add one line in the Screens part for each screen the status is meant for.
5. Save.

Scenarios

"We want our own stages on a document"

Create one status per stage and name the screen on each. Remember that a status picker shows every status you have created, not only the ones that named that screen, so keep the whole list short and unambiguous.

What it is connected to

• Only the Status screen itself reads this list in PeopleNest.
• It is set up the same way as Reason, which is the screen you almost certainly want instead when a user has to say why something happened.

If something looks wrong

• "I created a status and no screen offers it" - no PeopleNest screen takes a status from this list. Check which screen the client expected it on before adding more.
• "The code will not save" - the same code already exists. Status codes must be unique.