Table of Contents

Documents

• Schema: Lucidchart file | real time image
• Phases matrix: Lucidchart | real time image

Indirect Fixes

• Inconsistency of Blind ad Jobs (any stage matches now)
• Inconsistency for published jobs between 1st stage and 2nd stage.
• Archived all 1st stage apps of all jobs related to a given 2nd stage app.

[Complete] Phase 1

• create models + migration
• backfill cmd to populate new models
• code in hybrid mode to populate both models at the same time

[Complete] Phase 2

A - Enabling the toggles (the following will happen)

• enable-application-source-population
  • This toggle should be enabled.
• enable-system-2nd-stage-revamp
  1. The remainder to continue/complete the started applications won't be sent for apps started before enabling the toggle. (the new logic works using the submitted attribute in the page property of saved_application_data.application_json_schema.)
  2. The job of the 2nd stage is not used: We start to use the question_template_mapping info to get the questions.
  3. App of 2nd stage will be not created: All apps will be related to one application_form with multiple pages in saved_application_data.application_json_schema.
  4. New emails for 2nd stage will have a token with information about the template_order_num and using the 1st stage job.

B - Risks after enabling the toggles (may happen if)

• enable-system-2nd-stage-revamp
  1. For jobs created manually by CS ops team, if they forget to use the new integrations app:
     1. To create the question template mapping there is going to be a misconfiguration.
        • Impact: The start application will be failed
     2. To update the question template mapping, if the job question template is manually updated via SQL.
        • Impact: The applicant will see a different question template.

C - Risks after disabling the toggles

• enable-application-source-population (this toggle is related to phase 1)
  • if disabled then Truman needs to roll back so it doesn’t read answers from the new field.
    • if Truman rollback then: the apps of the 2nd stage stored only on the application_source table (no record on the application_form table) won’t be seen on Truman.
• enable-system-2nd-stage-revamp
  1. About A1: What happened if the candidate started applications on the new SAD format?
     1. Works fine for 1st state SAD,
     2. 2nd stage SAD won’t be processed - data is stored on SAD, but can’t be processed.
  2. About A4: The link sent to the email to start the 2nd stage job app (sent when the toggle was active) won’t open the 2nd stage form on bolivar, will show up instead 1st stage app completed.
  3. About A3: with the toggle enable, the candidate applies to the 2nd stage job and applies again after disabling the toggle if the Truman user sent the link to the candidate. Then we will have a duplicate entry on the application source table.

[Complete] Phase 3

A - Enabling the toggles (the following will happen)

• enable-system-2nd-stage-revamp-truman
  1. The new jobs don't need the 2nd stage job record and won’t be created. instead, we will use the question template mapping.
  2. We stop using and updating the 2nd stage job, in favor of the question template mapping.

B - Risks after disabling the toggles

• enable-system-2nd-stage-revamp-truman
  • About A1: The previously created new jobs then won’t show up in the related 2nd stage job. because we only created the QT mapping.
    • Ivan is going to check this toggle!
  • About A2: the changes made between QT mapping and the 2nd stage job template are out of sync, and the candidate will apply to the template setup on the QT mapping, instead of the template the user sees on the 2nd stage job on Truman!