SAP Knowledge Base Article - Preview

3802894 - Record consent against historic consent statement versions via API with actual signing date

Symptom

  • Only one consent statement version can be active at a time, but consent must be stored against the specific version presented to the user (including historic/non-active versions).
  • Attempting to store consent for a historic version via API returns 400 Bad Request – Validation error.
  • Error details: errorCode 400009; errorMessage "Validation error"; errorDetails "For sign on 'Historic legal statement' need to pass historic actionTimestamp".
  • Need to preserve the actual signing date even if it falls after the version was superseded.


Read more...

Environment

  • SAP Customer Data Cloud
  • Customer Consent

Product

SAP Customer Data Cloud all versions

Keywords

consent statement version, historic version, actionTimestamp, delayed entry, validation error 400009, api, accounts.setAccountInfo, accounts.importPolicy, offline consent, paper contract, docVersion, consentId, tags, entitlements, gigya , KBA , CEC-PRO-PNS , Privacy & Safety (Consent, RBA - Risk-Based Authentication) , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.