> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/set-delete-protection.md).

# Set Delete Protection

## Description

The *Set Delete Protection* part is intended to be used in combination with the Assessment Framework. When you use the generic *Save* function of the assessment framework, the system only exports values when they are added to the data log. This is the default case for answers to questions.

However, if a value is in the data log but is not connected to an active question -- a question still in the decision tree of an active tab; for example, when using a process node a set\_values part -- the assessment framework will normally delete this value because it assumes it has become stale/there is no question active anymore. You can use this part to prevent the system from deleting the value.

## Use

This part is not directly available in the Designer menus. To add it, add a process node, add any part, and go to the Code tab. Change the *\_name* property of the part you added to 'set\_delete\_protection'. Note: You must add the process node after the node that sets the value.

## Editor Fields

| Field Name | Description                                                                            | Type/Options | Optional/Mandatory |
| ---------- | -------------------------------------------------------------------------------------- | ------------ | ------------------ |
| Path       | This specifies the name of the object for which to set delete protection to on or off. | Text         | Mandatory          |
| Mode       | Set to *On* to enable the protection. Set to *Off* to remove the protection.           | On \| Off    | Mandatory          |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/set-delete-protection.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.