Configuring properties for GDPR data deletion and restriction
To handle deletion and restriction of GDPR data in IBM® Sterling Order Management, you need to set the following properties in the customer_overrides.properties file.
Property | Values | Description |
---|---|---|
yfs.YFS_CUSTOMER_PAYMENT_METHOD.personalinfoattributes | Valid value = <comma-separated list of attribute names> |
Controls restriction over publishing of the attributes as part of API or UE or Event output for GDPR. If GDPR support is enabled and restriction exists on the table record, the listed attribute names are not published as part of API or UE or Event output. This property also controls deletion of the table record column values corresponding to these attribute names as part of GDPR data deletion request, if GDPR support is enabled. Example: yfs.YFS_CUSTOMER_PAYMENT_METHOD.personalinfoattributes=CreditCardExpDate,CreditCardName,CreditCardNo,CreditCardType,CustomerAccountNo,DebitCardNo,DisplayCreditCardNo,DisplayCustomerAccountNo,DisplayDebitCardNo,DisplayPaymentReference1,DisplayPrimaryAccountNo,FirstName,LastName,MiddleName,PaymentReference1,PaymentReference2,PaymentReference3,PaymentType,PaymentTypeGroup,PrimaryAccountNo |
yfs.YFS_PERSON_INFO.personalinfoattributes | Valid value = <comma-separated list of attribute names> |
Controls restriction over publishing of the attributes as part of API or UE or Event output for GDPR. If GDPR support is enabled and restriction exists on the table record, the listed attribute names are not published as part of API or UE or Event output. This property also controls deletion of the table record column values corresponding to these attribute names as part of GDPR data deletion request, if GDPR support is enabled. Example: yfs.YFS_PERSON_INFO.personalinfoattributes=AddressLine1,AddressLine2,AddressLine3,AddressLine4,AddressLine5,AddressLine6,AlternateEmailID,Beeper,City,Company,Country,DayFaxNo,DayPhone,Department,EMailID,EveningFaxNo,EveningPhone,FirstName,JobTitle,LastName,Latitude,Longitude,MiddleName,MobilePhone,OtherPhone |
yfs.YFS_CUSTOMER_CONTACT.personalinfoattributes | Valid value = <comma-separated list of attribute names> |
Controls restriction over publishing of the attributes as part of API or UE or Event output for GDPR. If GDPR support is enabled and restriction exists on the table record, the listed attribute names are not published as part of API or UE or Event output. This property also controls deletion of the table record column values corresponding to these attribute names as part of GDPR data deletion request, if GDPR support is enabled. Example: yfs.YFS_CUSTOMER_CONTACT.personalinfoattributes=Company,DateOfBirth,DayFaxNo,DayPhone,Department,EmailID,EveningFaxNo,EveningPhone,FirstName,JobTitle,LastName,MiddleName,MobilePhone,SpendingLimit,SpendingLimitCurrency,SpouseDateOfBirth,Status,Title,WeddingAnniversaryDate |
yfs.PLT_AUTH_ANSWER.personalinfoattributes | Valid value = <comma-separated list of attribute names> |
Controls restriction over publishing of the attributes as part of API or UE or Event output for GDPR. If GDPR support is enabled and restriction exists on the table record, the listed attribute names are not published as part of API or UE or Event output. This property also controls deletion of the table record column values corresponding to these attribute names as part of GDPR data deletion request, if GDPR support is enabled. Example: yfs.PLT_AUTH_ANSWER.personalinfoattributes=Answer,QuestionText |
yfs.YFS_PAYMENT.personalinfoattributes | Valid value = <comma-separated list of attribute names> |
Controls restriction over publishing of the attributes as part of API or UE or Event output for GDPR. If GDPR support is enabled and restriction exists on the table record, the listed attribute names are not published as part of API or UE or Event output. This property also controls deletion of the table record column values corresponding to these attribute names as part of GDPR data deletion request, if GDPR support is enabled. Example: yfs.YFS_PAYMENT.personalinfoattributes=FirstName,LastName,MiddleName,CheckNo,CreditCardName,CreditCardType,CreditCardExpDate,CustomerAccountNo,CustomerPONo,DebitCardNo,DisplayCreditCardNo,DisplayCustomerAccountNo,DisplayDebitCardNo,SvcNo |
yfs.YCS_MANIFEST_UPS_DTL.personalinfoattributes | Valid value = <comma-separated list of attribute names> |
Controls restriction over publishing of the attributes as part of API or UE or Event output for GDPR. If GDPR support is enabled and restriction exists on the table record, the listed attribute names are not published as part of API or UE or Event output. This property also controls deletion of the table record column values corresponding to these attribute names as part of GDPR data deletion request, if GDPR support is enabled. Example: yfs.YCS_MANIFEST_UPS_DTL.personalinfoattributes=ConsigneeAddress1,ConsigneeAddress2,ConsigneeAddress3,ConsigneeAddress4,ConsigneeCity,ConsigneeCompanyName,ConsigneeCountry,ConsigneePhone,ConsigneePostalCode,ConsigneeStateProv,ConsigneeTaxID,ConsigneeUPSAcctNumber,CustomerReferenceNumber1,CustomerReferenceNumber2,CustomerReferenceNumberType1,CustomerReferenceNumberType2 |
yfs.YFS_ORDER_HEADER.personalinfoattributes | Valid value = <comma-separated list of attribute names> |
Controls restriction over publishing of the attributes as part of API or UE or Event output for GDPR. If GDPR support is enabled and restriction exists on the table record, the listed attribute names are not published as part of API or UE or Event output. This property also controls deletion of the table record column values corresponding to these attribute names as part of GDPR data deletion request, if GDPR support is enabled. Example: yfs.YFS_ORDER_HEADER.personalinfoattributes=CustomerFirstName,CustomerLastName,CustomerPhoneNo,CustomerEMailID |
yfs.YFS_OPPORTUNITY.personalinfoattributes | Valid value = <comma-separated list of attribute names> |
Controls restriction over publishing of the attributes as part of API or UE or Event output for GDPR. If GDPR support is enabled and restriction exists on the table record, the listed attribute names are not published as part of API or UE or Event output. This property also controls deletion of the table record column values corresponding to these attribute names as part of GDPR data deletion request, if GDPR support is enabled. Example: yfs.YFS_OPPORTUNITY.personalinfoattributes=CustomerFirstName,CustomerLastName |