Sp_customerclassify_BtnEventCancelInvalid (procedure)
取消客户分类作废
- Type: PROCEDURE
- Deterministic: NO
- SQL data access: CONTAINS SQL
Parameters
| # | Mode | Name | Type |
|---|---|---|---|
| 1 | IN | sProInParam |
varchar(10000) |
| 2 | IN | sMakePerson |
varchar(100) |
| 3 | IN | sBrId |
varchar(100) |
| 4 | IN | sSuId |
varchar(100) |
| 5 | OUT | sReturn |
varchar(1000) |
| 6 | OUT | sCode |
int |
Body
Body is not pre-cached. To inspect: mysql --defaults-file=~/.my.cnf -e 'SHOW CREATE PROCEDURESpcustomerclassify_BtnEventCancelInvalid'._
Narrative
Business context: 基础资料 → 客户分类 (siscustomerclassify) — inverse of Sp_customerclassify_BtnEventInvalid. Reactivates a soft-deleted customer-classify (bInvalid=0) and audits the action against the form sFormId='11811781131121915196321754040'.
What it does: Same JSON-batch shape as the invalidate sibling: validates sProInParam, parses $.params[].value[].sId, splits --separated multi-id strings. Per id reads sName, runs UPDATE siscustomerclassify SET bInvalid=0 ..., and INSERT INTO syslog with sLog='取消客户分类作废：'+sName and sOperationType='取消客户分类作废'.
Invocation: sp_btn_action*-style — dispatched by GenericProcedureCallServiceImpl.doGenericProcedureCall() when the 取消作废 button on the 客户分类 form fires. No gdsmodule hook reference; binding lives in the form's button configuration. Not in xly-src install scripts — DB-only.