fix: 特批说明附件识别对齐前端约定
附件类型字段由 attachmentType=spec_explanation 调整为前端附件元数据已有的 fileType=特批说明(业务字典 contract_attachment_type,中文匹配沿用 FILE_TYPE_SEAL_ARCHIVE 惯例),提交校验与自动特批筛选两处引用常量同步生效
This commit is contained in:
+4
-4
@@ -161,14 +161,14 @@ public final class HcsSyncConstant {
|
||||
public static final String CUSTOMER_KIND_INTERNAL = "internal";
|
||||
|
||||
/**
|
||||
* 合同附件类型字段名(前端约定:附件元数据 attachmentType)
|
||||
* 合同附件类型字段名(与前端附件元数据 fileType 字段对齐,值取业务字典 contract_attachment_type)
|
||||
*/
|
||||
public static final String ATTACHMENT_TYPE_FIELD = "attachmentType";
|
||||
public static final String ATTACHMENT_TYPE_FIELD = "fileType";
|
||||
|
||||
/**
|
||||
* 附件类型:特批说明(高风险/黑名单客商合同必须上传)
|
||||
* 附件类型:特批说明(高风险/黑名单客商合同必须上传;中文匹配沿用 FILE_TYPE_SEAL_ARCHIVE="双章归档文件" 惯例)
|
||||
*/
|
||||
public static final String ATTACHMENT_TYPE_SPEC_EXPLANATION = "spec_explanation";
|
||||
public static final String ATTACHMENT_TYPE_SPEC_EXPLANATION = "特批说明";
|
||||
|
||||
/**
|
||||
* 特批审核挂起节点展示名(currentNode,特批发起后挂起展示,结果回传后恢复)
|
||||
|
||||
+1
-1
@@ -1041,7 +1041,7 @@ public class ContractManageServiceImpl extends BaseServiceImpl<ContractManageMap
|
||||
|
||||
/**
|
||||
* 高风险/黑名单客商提交校验:甲/乙方为外部客商且高风险(C101-1 风险等级=2)或黑名单时,
|
||||
* 必须已上传「特批说明」类型附件(attachmentType=spec_explanation);内部组织类型客商默认无风险
|
||||
* 必须已上传「特批说明」类型附件(fileType=特批说明,业务字典 contract_attachment_type);内部组织类型客商默认无风险
|
||||
*
|
||||
* @param contractManage 合同单
|
||||
*/
|
||||
|
||||
+1
-1
@@ -212,7 +212,7 @@ public class HcsContractSyncSupport {
|
||||
}
|
||||
|
||||
/**
|
||||
* 筛选合同「特批说明」类型附件(attachmentType=spec_explanation)并转传合规(C103-2),
|
||||
* 筛选合同「特批说明」类型附件(fileType=特批说明,业务字典 contract_attachment_type)并转传合规(C103-2),
|
||||
* 返回特批附件引用;无特批说明附件返回空列表(提交时已强制校验,此处由 C103-8 防御性拦截)
|
||||
*/
|
||||
private List<HcsAttachmentRefDTO> transferSpecExplanationAttachments(ContractManage contractManage) {
|
||||
|
||||
Reference in New Issue
Block a user