Our use case: we have to use different consent documents in different cases.
We are using information from the documentation to add a consent document but we have an issue with the user experience. Some users forget to accept the consent file and move to the next document. As a result, the transaction is not completed and they don’t see any warning/messages about it.
Is it possible to make it more like the “default consent file”? I’ve attached a screenshot with the highlighted differences.
Yes, there’s a way to make an “Accept Only” document package level consent document. In that way, your users can’t move to the next document without accepting the document first. But to notice, one transaction can only have one package level consent document, because it’s a package level attribute “consent” in your package metadata.
Below two workarounds will fit the scenario if you deleted the “default-consent” document every time you create your package or removed it already in your account level.
#1. don’t delete the “default-consent”, or if you have removed it from your account level, recover it by contacting our support team.
#2.give your custom consent document an ID of “default-consent”
#3. the default-consent document and its metadata will be replaced by your custom consent document.
#1. you still delete your default-consent
#2.after you create your package, leave it in DRAFT status
#3.make another REST API call to change your package level attribute “consent” as we discussed above. Currently, there’s no direct function to do so in .NET sdk. I will create some sample code if you want to follow this path and fill in an Enhancement Request on you behalf if you want.