Skip to content

Instantly share code, notes, and snippets.

@msolli
Last active August 28, 2019 08:11
Show Gist options
  • Save msolli/21856ec11abb440f7adf79536a760cd7 to your computer and use it in GitHub Desktop.
Save msolli/21856ec11abb440f7adf79536a760cd7 to your computer and use it in GitHub Desktop.
Applications
Applications
Active
# Only when deleting account and archiving positions
archive -> Archived
# Applicants can withdraw, but not archive directly
withdraw -> Inactive
# "Hard no": Recruiter doesn't want this applicant in candidate pool
reject -> Rejected
Started*
complete-survey -> Survey-Completed
# We can skip this state after Texit
Survey-Completed
# submitting an application creates a candidate in a process
submit -> Can Submit?
Can Submit?
application complete? -> Submitted
application not complete? -> Survey-Completed
Submitted
# Maybe not the right name, but we need a state for applications
# in a pool that should not be included in new processes, but
# can't be archived since they're already in a process. It might
# be triggered by the applicant herself ("I don't want to be
# included in any more processes") or by the system (the applicant
# was marked as "Hired" in a process).
Inactive
activate -> Can Submit?
archive -> Archived
Rejected
archive -> Archived
# When the process the application was in has been closed, the
# application has been "processed". The exception is for applications
# to open positions - these only get "processed" after the open position
# has expired, or when it's archived.
Processed
# Is archived and deleted maybe the same?
Archived
function render(model){
let current_state_name = model.active_states[0].name;
return $("h1",
{style: {color: "darkBlue"}},
`The current state is: ${current_state_name}`);
}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment