Project Operation Form Reference

These forms require project context. Open them from Project Panel so hidden project_id, stage_id, round_id and return-routing values are correct.

Project Entry form

Details

Entry kind (required): team, person or group, restricted by the sport profile.
Team appears for team entries; Person for person entries; Display name for group entries.
Entry code is an optional project-local/source code.

Competition data

Seed number supports draw/schedule ordering.
Bib number supports race/individual identification.
Included in standings defaults Yes.
Lifecycle/status defaults Active and can represent inactive, withdrawn or disqualified according to the current contract.
Notes stores administrator context.

New entries default to Published and ordering 0.

Entry Member form

Details

Person and member person type are required.
Role code is filtered to profile-compatible positions/functions.
Shirt number is optional.
Captain defaults No.

Status

Valid from / Valid until delimit this membership period.
Status defaults Active and can represent inactive, injured, suspended or departed states supported by the form.
Notes explains the period/status.

Create another history period when a person is injured/suspended/leaves and later returns; do not overwrite previous dates. New rows default Published.

Stage form

Hidden Project preserves context.
Name and Stage type are required.
Alias is optional.
Code is hidden and generated from the name when absent, unique in the project.
Sequence number orders stages.
Parent stage is optional and cannot cross projects.
Start / End date are optional.
Description is a separate full-width editor tab.
New stages default Unpublished and ordering 0.

Stage type is a profile/domain code such as league/group/knockout/race, not a translated theatrical "stage" concept.

Stage Transition form

Name, Code, Source stage, Target stage and Selector type are required.
standing_rank_range reveals Rank from, Rank to and Standing scope.
match_outcome reveals Outcome and optional Source round.
Other selectors include all entries and manual assignment.
Carry-over mode is required and defaults None; supported values include all results and mutual results.
Target seed start optionally assigns sequential seeds in the target.

selector_config_json is a hidden normalized persistence field. Never paste JSON into it manually; visible selector fields generate it.

Round form

Hidden project/stage fields bind the round to its parent.
Name, Code, Round type and Sequence number are required.
Round type defaults standard.
Start/end dates are optional.
Current lifecycle/status defaults Draft where present.
Description is a separate full-width editor.
New rounds default Unpublished.

The system may generate a code, but the current XML marks it required in the form. Use a stable unique value within the stage/project.

Programme Item form

The internal form/model retains historical match naming, while user-facing documentation calls the record a programme item/event.

Details

Hidden project, stage and round are required context.
Number and Code are optional identifiers.
Contest type is required and defaults head_to_head; use the dropdown, not free text.
For head_to_head, Participant slot 1 and Participant slot 2 are required. They identify participants, not inherently football home/away teams.
Non-head-to-head contest types manage participants through their compatible workflow and show an explanatory note.
Date and Time are optional until scheduled.
Timezone inherits when blank/default.
Duration minutes, Venue and Attendance are optional.
Status code is required and defaults scheduled.
Combined scheduled_start is generated in a hidden field.

Description has its own full-width editor tab. New programme items default Unpublished. The round list can provide compact automatic saving for common schedule fields; use the full form for complete validation/context.

Standing Adjustment form

Hidden project and optional stage define context.
Project entry, Scope and Metric are required and populated from the project/profile.
Adjustment value is required and can be positive or negative.
Reason is required.
Effective date is optional.

For a point deduction enter a negative value against the points metric and document the disciplinary reason. New adjustments default Published and are included automatically in the next standings calculation.

Dynamic Rules and Templates forms

projectrules.xml and projecttemplates.xml contain empty fieldsets by design. Their fields are built at runtime from the selected immutable profile version and template definitions.

Each rule/template setting has an override switch. Disabled means inherit; enabled validates and stores a project-specific value. The screen shows inherited/effective values so an administrator can distinguish a profile default from an explicit project override.