In addition to the aforementioned, the following properties are also part of the application.properties file.
However, these properties are related to the user interface and the Angular© web application:
Property name |
Description |
Required |
Default and Optional Values |
---|---|---|---|
|
Defines if and how to trim the field's content when the screen is loaded. The
|
No |
Optional values:
none (default) |
|
The character to remove from the field's content. Note: |
Yes, if the trim property is set. |
|
|
Define if focusing on an input field will select the full content of the field. |
No |
false |
|
Define the list of themes available in the client UI. The themes define the look and feel of the application. There is an option to create a new CSS theme file and add it to the list. |
No |
This is the default theme list:
emulator.css |
The following table of properties is also related to the user interface and the handling of HTTP errors.
You can use the properties to configure the following:
Define which HTTP errors cause the application to resend a failed request.
Define how many attempts are made for a resend.
Manage the amount of time between resends.
Property name |
Description |
Required |
Default and Optional Values |
---|---|---|---|
|
Define if resending requests for recoverable HTTP errors is enabled. |
No |
true |
|
Define the number of times that the application resends a failed request. |
No |
2 |
|
Define a list of HTTP error codes that cause the web application to resend the request. |
No |
502 |
|
Define the amount of time in milliseconds that the client waits before sending the request again for the first time. |
No |
500 |
|
Define how to compute the timeout for subsequent HTTP requests. |
No |
FIXED (default value) – use the value from the
MULTIPLE – multiply the last request's timeout amount by the number defined in
the ARRAY – use the array from the |
|
Define the multiplier for compute mode MULTIPLE. |
No |
2 – each request multiplies the previous request's timeout amount by 2. |
|
Define the timeout array for compute mode ARRAY. |
No |
{500} – in this case all requests have a timout of 500 milliseconds. |
The following table of properties is related to intermediate screens.
Intermediate screens show when the application is performing a task, for example processing data. The user does not expect to insert any data during intermediate screens. When the user gets to an intermediate screen, the web application should try to check if the server has a new screen. The following properties define how to configure the behavior of such requests.
Property name |
Description |
Required |
Default and Optional Values |
---|---|---|---|
|
Define if resending requests for intermediate screens is enabled. |
No |
true |
|
Define the number of times that the application resends a request for an intermediate screen. |
No |
2 |
|
Define the amount of time in milliseconds that the client waits before sending the request again for the first time. |
No |
500 |
|
Define how to compute the timeout for subsequent intermediate screen requests. |
No |
FIXED (default value) – use the value from the
MULTIPLE – multiply the last request's timeout amount by the number defined in
the ARRAY – use the array from the |
|
Define the multiplier for compute mode MULTIPLE. |
No |
2 – each request multiplies the previous request's timeout amount by 2. |
|
Define the timeout array for compute mode ARRAY. |
No |
{500} – in this case all requests have a timout of 500 milliseconds. |