Before switching order flows to work with provisioning orders, the pre-check script is run automatically. This pre-check script checks existing order flows for a possible upgrade. The following checks are performed:

  • Whether identifiers of specific order flow handlers already exist and contain different methods. In this case, the pre-check script writes this inconsistency into a log file.
  • Whether “AN” and “AS” statuses already exist and have incorrect handlers for “CH” order. In this case, the pre-check script writes this inconsistency into a log file.
  • Whether “NC” and “CO” statuses already exist and have incorrect handlers for “CH”, “SO”, “CF”, and “RN” orders. In this case, the pre-check script writes this inconsistency into a log file.
  • Whether “EC”, “AD”, “I9”, “I4”, “MO”, “MN”, “LO”, “PF”, “PR”, “PN”, “AP”, “NF”, “VC”, “VF”, “PD” statuses do not exist or have incorrect handlers for “CH”, “SO”, “CF” and “RN” orders. 
  • Whether “AU” status does not exist or has incorrect handlers for “SO” orders. In this case, the pre-check script writes this inconsistency into a log file.
  • Whether some unsupported features are active (“FEA_PostApproval” or “DelayedLandingUsageBilling”). In this case, the pre-check script writes this inconsistency into a log file.
  • Whether unsupported order item type “One-time Fee” or service gates (KAGATE) are used. In this case, the pre-check script writes this inconsistency into a log file.

If the precheck script fails, perform the following actions:

  1. Ensure that the following identifiers exist in the “FlowHandler” table: 250, 251, 252, 253, 254, 255, 256, 257, 258, 259, 260, 261, 262, 25. If they do not exist, add these identifiers or replace the incorrect identifiers with the correct ones using the move_old_handlers.py script. To use this script, copy it to the BSS node and run.
  2. Fix inconsistencies found by precheck in custom order flows using the default order flow as an example.
    If the order flow already includes new statuses, rename them using the interactive rename-status.pyscript. Note that this script does not change the default record in the “OrderOperation” table. If you want to rename the initial status of an order flow, this record must be updated manually and with care.
    1. If the “AP” or “AU” statuses do not exist, make sure that the actions from https://cloudblue.freshdesk.com/support/solutions/articles/44002212061 are performed and the order flow was configured in accordance with this article.
    2. If the “VC” or “VF” statuses do not exist, make sure that actions from https://cloudblue.freshdesk.com/support/solutions/articles/44002276857 are performed and the order flow was configured in accordance with this article.
    3. If the “AS” status does not exist, make sure that actions from https://cloudblue.freshdesk.com/support/solutions/articles/44002261171 are performed and the order flow was configured in accordance with this article.
  3. Deactivate unsupported features “FEA_PostApproval” and “DelayedLandingUsageBilling”.
  4. Run the upgrade script.