Skip to content

Workflow

Jump to bottom
Jason Sylvestre edited this page Jul 12, 2018 · 8 revisions

Workflow

Updated Workflow 2017/09/14

  • Client Creates Order, until Confirmed, can go back and edit

  • Client Confirms Order, Test item prices are locked in

  • Client Prints Confirmation page, can get to this page as long as it is in the confirmed status?

  • Lab gets samples with printout. They do their thing outside our system and enter info into labworks

  • Lab receives Order, enters workrequest number (Validates that it exists in Labworks and not in our system) Tests, quantities are updated in our system

  • Lab Finalizes Order, they may have manually sent partial results before this

  • Client now shown the download link and can pay (If they need more tests, they need to contact lab outside of our system. Lab can re-finalized and replace existing results)

  • As long as paid flag is unchecked, Client will continue to see pay buttons (Pay By CC, Pay Another Way, Pay with Account)

  • Client creates order (Created)

  • Client Confirms Order (Confirmed)

  • Client Prints Order to include with samples that are sent

  • Lab gets samples with included printout

  • Lab writes work request number on printout and adds/removes tests from printout

  • Lab passes around printout for approval and other changes

  • Lab enters in tests into lab works

  • Lab then goes into Anlab, clicks received and enters the work request number (Received)

  • Anlab validates that workrequest number exists

  • Anlab pulls in the tests/prices and overwrites what was originally entered

  • Lab may email partial results outside of Anlab

  • Lab Finalizes order in Anlab, enters results/Adjustment

  • Anlab pull in tests and prices (may use older price scheme) (Finalized)

  • Client Accepts Prices/Results (Accepted)

  • Client May download Results

Non-Uc Payment workflow after user clicks Accept

  • Client is directed to Payment Page with Shareable link Paid flag not set
  • Client may choose to pay with other than a credit card. If so, they are directed to an informational page. This page will have a mailto with a subject and body pre-populated.
  • If client choose to pay by CC, they do so and are returned to an error page or a receipt page. behind the scenes, cybersource calls our site and we change paid flag
  • When money has moved, sloth? Anlab updates or to completed
  • If they choose other way, account role updates order to be paid, moves to (Complete)

UC Payment after user clicks Accept

  • Order is marked as paid
  • When money actually moves (Sloth? or account person, order is (Complete)

Paymnet Process Updated 2018/07/12

UCD Account

  • When Finalize, attempts to move money with Sloth right away. If an error, will not finalize
  • Marked as Paid.

UC Other Account

  • When Finalized:
  • User Confirms Payment
  • can change details by not account
  • after confirm payment
  • can now download
  • Email is sent to accounting
  • Marked as paid and Complete

Other - Agreement

  • When User confirms Order Email is sent to accounting
  • rest of this is the same as Other

Other

  • When Finalized
  • Confirm Payment, user must enter PO if missing
  • Send email to Accounting
  • Downloadable
  • Paid and Complete

Credit Card

  • When Finalized
  • User must pay with CC
  • After Payment
  • Marked as Paid
  • Downloadable
  • After Sloth moves money, Marked as Completed
Clone this wiki locally