We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mandatory Tests
Special explanation for 6.1.26 Prohibited Document Category Name:
6.1.26 Prohibited Document Category Name
Document Category can be one of the five given definitions, or any other value.
The 6.1.26 checks that the Document Category value should not be similar to one of these values, otherwise the profiles from chapter 4 are taken.
Informational Advisory security-incident-response Security Advisory veX
We implement this by
The text was updated successfully, but these errors were encountered:
#13 -> Special case Document Category
2d7fd21
#24 -> Enable global force mode to step over Document Tracking missmatches
Implementation in Secvisogram can be used as reference.
Sorry, something went wrong.
Implementation has been done in Secvisogram and the code past code in this project also has been implemented to check typical typos and integrate conversion).
As we then discussed with @tschmidtb51 to not integrate data validity checks in the code, it has been removed again.
Nevertheless, the implementation can be integrated into turvallisuusneuvonta (initial integration #55).
Successfully merging a pull request may close this issue.
Mandatory Tests
Special explanation for
6.1.26 Prohibited Document Category Name
:Document Category can be one of the five given definitions, or any other value.
The 6.1.26 checks that the Document Category value should not be similar to one of these values, otherwise the profiles from chapter 4 are taken.
We implement this by
The text was updated successfully, but these errors were encountered: