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 → Delete Selected Purpose
AI-generatedOverview
This node operation deletes a selected purpose from a specified configuration tree in the Didomi API. It is useful for managing and maintaining data privacy configurations by removing purposes that are no longer needed or relevant. For example, if a purpose related to data processing is deprecated, this operation can remove it from the configuration tree to ensure compliance with privacy regulations.
Use Case Examples
- Deleting a selected purpose from a configuration tree to update privacy settings.
- Removing an obsolete purpose to maintain accurate data management policies.
Properties
| Name | Meaning |
|---|---|
| Configuration Tree ID | The identifier of the configuration tree from which the selected purpose will be deleted. |
| Selected Purpose ID | The identifier of the selected purpose to be deleted from the configuration tree. |
| Query Parameters | Optional parameters to customize the API request, such as filtering or pagination options. |
Output
JSON
Status Code- HTTP status code indicating the result of the delete operation, e.g., '204 No Content' for successful deletion.
Dependencies
- Didomi API with API Key and Secret for authentication
Troubleshooting
- Missing Configuration Tree ID or Selected Purpose ID will cause the node to throw an error indicating the required parameter is missing.
- If the API key or secret is missing or invalid, the node will fail to retrieve an access token and throw an error.
- API errors from Didomi will be caught and rethrown as NodeApiError with the original message and stack trace for debugging.