Sp_doFlow_opsProcess.md 1.87 KB

Sp_doFlow_opsProcess (procedure)

  • Type: PROCEDURE
  • Deterministic: NO
  • SQL data access: CONTAINS SQL

Parameters

# Mode Name Type
1 IN sData text
2 IN sInstanceId varchar(255)
3 IN sLoginId varchar(255)
4 IN sSuId varchar(255)
5 IN sBrId varchar(255)
6 IN sTaskId varchar(255)
7 IN iPproved bit(1)
8 IN sSrcNo varchar(255)
9 IN sGuid varchar(255)
10 IN sComment varchar(1000)
11 IN sTaskParentId varchar(255)
12 IN sTaskIdNow varchar(255)
13 OUT sCode int
14 OUT sReturn varchar(1000)

Body

Body is not pre-cached. To inspect: mysql --defaults-file=~/.my.cnf -e 'SHOW CREATE PROCEDURESpdoFlow_opsProcess'._

Narrative

Business context: Operates on opsoutsideprocessslave — likely an委外加工 (outside-process) workflow step that writes the negotiated quotation price (dQuotationPrice) from a flow-form payload back to the slave row. Trivial one-statement body; no caller wiring found.

What it does: Reads JSON_EXTRACT(sData, '$.dQuotationPrice') from the workflow payload, then UPDATE opsoutsideprocessslave SET dQuotationPrice = <value> WHERE sParentId = sGuid. Returns sCode=1 and an empty sReturn by default. All workflow context params (sInstanceId, sTaskId, iPproved, sComment, ...) are accepted but ignored.

Invocation: Status: appears orphaned. No caller found in any channel — not bound as gdsmoduleflow.sApplyProName, no form-master reference, no other routine CALLs it, and grep -rln Sp_doFlow_opsProcess across xly-src returns no hits. Signature matches the workflow-apply contract, so it was likely staged as a flow-handler for an委外报价 step and never wired. Candidate for maintainer audit.