Skip to content

Commit 0f76e56

Browse files
committed
update uparser docs
1 parent 324ee8e commit 0f76e56

1 file changed

Lines changed: 11 additions & 0 deletions

File tree

docs/content/supported_tools/parsers/universal_parser.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -161,3 +161,14 @@ You can edit the Test_Type associated with your Universal Parser to change:
161161
* Whether it is "active" or not. If not, it will not appear as an option in the "Scan Type" drop-down on the "Add Findings" page
162162
* Whether its findings should be marked "static" or "dynamic"
163163
* You can tweak the same-tool and cross-tool deduplication hash codes, as well as the reimport hash codes, for your Universal Parser under "Enterprise Settings". By default, only same-tool deduplication and reimport hash codes are populated, with the required values Title, Severity, and Description.
164+
165+
### Current limitations: editing and deleting a Universal Parser
166+
167+
The field-mapping configuration of an existing Universal Parser cannot be modified after it is created — only the associated Test_Type (above) is editable. There is also no in-UI option to delete a Universal Parser.
168+
169+
The current workaround for both cases is:
170+
171+
* **To change a parser's field mappings:** create a new Universal Parser with the desired mappings (using a representative sample file as in Step 1), and switch new imports to use the new parser. Existing Tests already imported under the old parser are unaffected.
172+
* **To "retire" a parser you no longer want to use:** mark its associated Test_Type as inactive (uncheck "active" on the Test_Type). It will stop appearing in the "Scan Type" drop-down on the Add Findings page. The parser configuration itself will remain in the database.
173+
174+
If you need a parser configuration permanently removed (for example, because it contains sensitive field names), contact [DefectDojo Support](mailto:support@defectdojo.com).

0 commit comments

Comments
 (0)