Actions75
- Compliance Report Actions
- Consent And Preference Actions
- Data Manager Actions
- Add Preference Into Your Configuration Tree
- Add Purpose Into Your Configuration Tree
- Create Preference
- Create Purpose
- Delete Preference
- Delete Purpose
- Delete Selected Preference
- Delete Selected Purpose
- Get Available Regulations and Related Information
- Get Configuration Tree
- Get Preference
- Get Purpose
- Get Vendor
- List Preferences
- List Purposes
- List User Rights
- List Vendors
- Update Preference
- Update Purpose
- Privacy Request Actions
- Widget Actions
- Create Authentication Provider
- Create Consent Notice
- Create Widget
- Delete Widget
- Get Archived Widget
- Get Current Draft Configuration For Notice
- Get Custom Theme
- Get Deployment
- Get Entity
- Get Widget
- List Archived Widget
- List Custom Themes
- List Deployments
- List Entities
- List Widgets
- Publish Current Draft Configuration For Notice
- Publish Widget
- Set Default Authentication Provider
- Update Component
- Update Current Draft Configuration For Notice
- Update Custom Theme
- Update Entity
- Update Multiple Components
- Update Multiple Entities
- Update Widget
Data Manager → Update Purpose
AI-generatedOverview
This node operation updates an existing purpose in the Didomi Data Manager. It is useful for managing and modifying the details of purposes related to user data and privacy preferences within an organization's data management system. For example, it can be used to update the description or status of a purpose to ensure compliance with privacy regulations.
Use Case Examples
- Updating the description of a purpose to reflect new privacy policies.
- Changing the status of a purpose to inactive when it is no longer used.
Properties
| Name | Meaning |
|---|---|
| Purpose ID | The unique identifier of the purpose to be updated. |
| Query Parameters | Optional parameters to filter or modify the request behavior, such as organization ID, regulation, status, limit, etc. |
| Request Body | The JSON object containing the updated data for the purpose. |
Output
JSON
Status Code- HTTP status code when no content is returned*- The JSON response from the Didomi API representing the updated purpose details
Dependencies
- Didomi API key and secret credentials
Troubleshooting
- Ensure the Purpose ID is provided; otherwise, the node will throw an error indicating the missing Purpose ID.
- Verify that the API key and secret credentials are correctly set and valid to avoid authentication errors.
- Check the request body JSON format to ensure it is valid and contains the necessary fields for updating the purpose.
- If the API returns an error, review the error message for details and adjust the request parameters or body accordingly.