...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Info |
---|
openIMIS components: Web Application v1.3.0 and later. Implementation roles required: Developer We suggest using Visual Studio to update the escape procedures. |
Excerpt | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
The role of the Escape procedures is to allow adaptation of the Web Application to different insurance contexts. There are situated in a single class, EscapeBL, which makes it easier to access and modify without having to worry about messing with the whole Web Application source code. There are 2 escape procedures that can be modified:
Localise the insuree number validation escape procedure In this guide, we will localise the
This is the generic implementation of the method:
The generic method is returning always true, meaning any insuree number will be a valid one. Let's take for example the following insuree number requirements:
These requirements are satisfied by the following escape procedure:
The isValidInsuranceNumber is executing the following steps:
Other validations rules can be applied. To apply the new modification to the escape procedures, the Web Application .Net solution needs to be published and deployed. |