Only for NLP transactions, apart from standard headers, an extra field is required: “Use Case Name”. It represents the NLP use case to be used for your module from the list of use cases created in NLP system.

If the use case is not provided, then NLP system tries to identify the use case based on the document uploaded. Thus to avoid this, the use case name needs to be provided.

This will cause an issue for Ideal Scenario. These scripts are not required for ideal scenario. The use case names can then be provided using the following two options:

1. In the request DTO “NamedEntityRecognizerDTO.java” accepted by extract service of NLP, there is a field “useCaseName”. In this field, use case name can be provided. For this, UI should be modified using UI extensibility to send this field in the payload.
2. Make the entries in the table “DIGX_MO_CONFIGURATION_SELECTOR” only for NLP transactions and specify the use case name. For other fields, variable names of default configurations can be used, only for this case.