Transaction Renderer Blazor appsettings

This page lists all the appsettings.json settings available for the Transaction Render Blazor.

 

 

appsetting.json file creation

By default the appsettings file does not exist in a fresh AMT installation, to create it follow these steps:

1. Navigate to the following directory:
   

   ..\<AMT_ENVIRONMENT>\AmtTools\ControlCenterCore\TransactionRendererBlazor\

   
   
2. Copy the SAMPLE_appsettings.json file found in this directory and rename the copied file to appsettings.json.


3. Set the desired options and save the file.


4. After the appsettings.json file has been updated, the AppPool belonging to the TransationRendererBlazor Web Application in IIS must be recycled in order to apply the changes.

 

Application Settings

The appsettings file is (sub-)divided into the following sections.

 

Section	Description
AMT	The main section where most settings are located.
Logging	Section for the logging settings for the Web Application.
AllowedHosts	Solo settings which restricts the hosts which may access the Web Application.

 

 

AdditionalErrorDetails

When set to true, the AmtExceptionPage provides additional error information.

 

Theme

Theme: The name of the folder located in wwwroot\app_themes which contains custom theme CSS files that will be used for the styling of the Web Application.
NoDefaultTheme: When set to true, the default CSS files will not be loaded. Default is false.

The default CSS files will loaded before the custom theme (unless NoDefaultTheme is set to true). If Theme is set to a value, this custom theme will be loaded as separate CSS files which will override the default CSS styling.

 

Logging

Sets the logging levels for the various ASP.NET Core components of the web application. These settings do not need be adjusted in a normal situation.
The allowed log levels are, from most to least detailed: Trace, Debug, Information, Warning, Error, Critical and None.

 

AllowedHosts

In the AllowedHosts section, access to the web application can be restricted to specific hostnames. 
The value is a semicolon-delimited list of host names without port numbers. 
By default all hostnames are allowed by the asterisk (*) wildcard.
Disallowed users will get a HTTP 400 error code (Bad Request).