Preview and test before saving

Studio roles: "Owner", "Administrator" and "Community manager".

Saving publishes a definition at once, so the editor lets you check your changes first. Both checks work on the unsaved changes and write nothing.

Eligible persons

The "Eligible persons" count is "Counted on your unsaved changes, as of today. Each person counts once, at the first register that decides them." Each register assignment shows its own share, such as "4 eligible" or "1 refused", and the counts follow every change you make.

External registers are asked live and cannot be counted. They show "Not countable", and "Counts below an external register are upper bounds: it is asked first and may already decide some of these people." In Pannoniqa AG's definition, "SAP HR" is at the top, so the counts of "Works council" and "Retirees" read "at most …".

Test a member code

"Test a member code" shows "how your unsaved changes decide one member code, as a login check would: by status only, without names, birth date or challenge code."

1. Under "Test a member code", enter the "Member code", for example PQ-10017.
2. Choose "Test".

The result shows:

• the outcome: "Valid", "Not valid" or "Unavailable", with the reason, such as "Not found in any register";
• which register decided, at which position, and the entry it found;
• "Register by register": what each register answered, for example "Found, filtered out: this register does not count the status Inactive", or "Not reached: a register above decided";
• which communities the person would land in.

"External registers are asked live. Nothing is saved, and neither the code nor the claims a register returns are logged." A test therefore never appears in the check lookup.

Use the test before you reorder registers or add a register that refuses: test a member code you know should stay valid, and one you expect to be refused.