Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 2 Next »

  1. COLLECT INFO

    1. Ask customer for Site UUID (and ideally collect customer name and prior job status) 

  2. SEARCH AND CONFIRM INFO

    1. Confirm in Engine that site is actually archived 

      1. Log into Engine as Sighten admin as customer user

      2. In Engine, go to Ops.  Search for “Cancelled” under Stage.

      3. Go to Sales, select only archived under Stage

    2. Confirm previous status of job.  If customer has not provided, we will need to collect.  Possible statuses are: Lead, System, and Proposal. 

      1. Open Postman

      2. To check for Proposal, enter into Postman (replace {uuid} with Site UUID): https://engine.sighten.io/api/rest/solar_quote/?system__solarsite__uuid={uuid}.  To check for workflow, confirm status “Signed” (should be in Ops portal).  If status other than signed, should be in Sales portal.

      3. To check for System, enter in Postman (replace {uuid} with Site UUID): https://engine.sighten.io/api/rest/system_system/?solarsite__uuid={uuid}

      4. To check for Lead, enter into Postman (replace {uuid} with Site UUID): https://engine.sighten.io/api/rest/system_solarsite/{uuid}

      5. If receive error “No results matching query parameters” and status code 200, then call was successful but job does not have that status.  Move on to next status.

      6. If you receive a data stream, then job is in that status. 

  3. TICKET CREATION

    1. Use ticket https://sighten.atlassian.net/browse/BT-423 as reference.  Clone it.

    2. Create new ticket under “Engine Bugs and Data Fixes” project.  Mark as task.  Leave assigned to yourself.

    3. In ticket description for any job status, request unarchive job:

      1. Insert site UUID and Status in appropriate places:

        PUT https://{{env}}.sighten.io/api/rest/system_solarsite/{uuid}

        {

                "status": "{status}"

        }
      2. i.If there is a signed contract, also add to ticket the below (add site UUID):

        PUT https://{{env}}.sighten.io/api/rest/solar_quote/{uuid}

        {

        "status": "SIGN"

        }

  4. TESTING

    1. Test this on Staging (if Archived today, go in and archive on Mirror to enable testing)

      1. Confirm you have correct job again via GET calls.  Choose appropriate environment.  Body should be empty.  GET call will be: For all jobs: https://{{env}}.sighten.io/api/rest/system_solarsite/{uuid}   For contracted quotes: https://{{env}}.sighten.io/api/rest/solar_quote/{uuid

      2. Add PUT calls as above in Postman Body tab.  Change header to PUT and add appropriate call to body tab.  For all jobs: {"status": "{status}"}  For contracted quotes: {"status": "SIGN"}

      3. Confirm in environment that de-archive was successful.

  5. SUBMITTING TICKET

    1. Add note that testing was successful and what environment

    2. Assign ticket to David

    3. Link to your original customer request ticket, and place that ticket in “awaiting development” status.

    4. Party!

    5. When new ticket is closed, update customer.


NOTE: un-archive for Ops pipeline jobs is more complex, see  BT-423 - Getting issue details... STATUS


  • No labels