The Nextedy RISKSHEET is configurable in the two places:
- Global / Project-level configuration - will be discussed here on this documentation page
- Document / Document template specific configuration - see Risksheet Document Config File - risksheet.json - format reference
Following properties can be defined in (Project or Global) Administration > Configuration Properties
Risk Document Type
Define what Document type represents a risk analysis. These and only these documents will be listed on the Risksheet tool page.
Property: nextedy.risksheet.riskDocumentType
Default: riskSpecification
Risksheet Template
Configure the path to the document that is being used as a template to create new risk analyses.
Property: nextedy.risksheet.risksheetTemplatePath
Default: Risks/Risk Specification
Suggester - use AND / OR between keywords
When a user is working with the string/text fields, the risksheet is suggesting the previous values from other risk analyses. You may need to configure if the suggester is searching in a way that each keyword must be there, or if it tries to find the best match, even if some keyword is missing.
Property: nextedy.risksheet.isSuggesterKeywordsMandatory
Default: false
Suggester - fuzzy searching
When a user is working with the string/text fields, the risksheet is suggesting the previous values from other risk analyses. You may need to configure if the suggester should perform a so-called similarity or fuzzy search to find also "similar" words.
Property: nextedy.risksheet.isSuggesterFuzzySearching
Default: true
Suggester - search for complete words
When a user is working with the string/text fields, the risksheet is suggesting the previous values from other risk analyses. You may need to configure if the suggester should perform a search so it expects the words have not been fully typed. In this case, it searches for words that start with the keywords typed.
Property: nextedy.risksheet.isSuggesterWildcardSearching
Default: true
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article