Agreement revisions define the specific version text (the agreement content) to manage the lifecycle of the agreement to which users provide consent.
A revision resource allows you to update the content for an agreement language. (A language can have up to 100 associated revisions.) The revision must have a value specified for the
effectiveDate property, and when showing content to a user for an agreement language, the content associated with a revision with an effective date closest to the current date is shown. The revision can be configured to force the user to consent again to the agreement.
The revisions service implements functions to create, read, and delete agreement revision resources. Agreement revision resources cannot be updated. If an agreement revision needs to be updated, a new agreement revision should be created. In addition, agreement revision resources that have become effective cannot be deleted, which ensures that consent data is preserved.
||A relationship that specifies the ID of the agreement resource for this revision.|
||A date that specifies the start date that the revision is presented to users. This property value can be modified only if the current value is a date that has not already passed. The effective date must be unique for each language agreement, and the property value can be the present date or a future date only.|
||A string that specifies the revision ID.|
||A relationship that specifies the language resource associated with this revision.|
||A date that specifies whether the revision is still valid in the context of all revisions for a language. This property is calculated dynamically at read time, taking into consideration the agreement language, the language enabled property, and the agreement enabled property. When a new revision is added, the
||A boolean that specifies whether the user is required to provide consent to the language revision after it becomes effective.|
||A string that specifies text for the revision. The revision has a text size limit of 32K (16,000 characters). The text supports unicode letters, combining marks, numeric characters, whitespace, and punctuation characters:
|204||Successfully removed. No content.|
|400||The request could not be completed.|
|401||You do not have access to this resource.|
|403||You do not have permissions or are not licensed to make this request.|
|404||The requested resource was not found.|