C4HSettings.xml maintains configuration elements used to define default behavior.

C4HSettings

Default settings are as follows:

<Settings>

<!--Timeout value in milliseconds -->

<Timeout value="15000" />

<!-- Persist value "0" == false || "1" == true-->

<Persist value="0" />

<!-- UseHistory value "0" == false || "1" == true-->

<UseHistory value="0" />

<Host value="www.claimseditor.com" />

<EndPointBatch value="https://www.claimseditor.com/cws/batch" />

<EndPointDeleteClaim value="https://www.claimseditor.com/cws/history?fpclaimID={0}" />

<EndPointEditClaim value="https://www.claimseditor.com/cws/{0}claim?persist={1}&amp;useHistory={2}" />

<!-- BatchBy acceptable values "Day" or "Month"-->

<BatchBy value="Day" />

<!-- This directory name is appended to AppData environment variable

and must match the directory defined in the log4net appender file value-->

<CES_Directory value="Plexis.ClaimEditingSoftwareTest" />

<!--web service message persistance-->

<ConnectionString value="Data Source=;Initial Catalog=;Integrated Security=SSPI"/>

<!--should store MIM web requests? 1==true, 0==false(only stores errored requests)-->

<StoreRequest value="1"/>

</Settings>

• Timeout – this setting defines in milliseconds the timeout value for web requests
• Persist – this setting is used to notify C4H whether the claim is to be persisted in C4H
• UseHistory – this setting is used to notify C4H whether to use claim history in editing claim
• Host – Host name used to define Header request for web service calls
• EndPoints – defines the endpoints for CWS
  • EndPointBatch – Create Batch web service used to create batch number for persisting claims in C4H. Claims submitted to CWS must supply a batch number in order to be persisted.
  • EndPointDeleteClaim – Used to delete claim history from C4H. This call to remove history only purges historical records and does not remove the claim itself.
  • EndPointEditClaim – Edit Claim Web Service call is used to submit a claim to CWS for editing. The AppSetting value is stored with string format place holders in order to inject batch number, Persistence and UseHistory at runtime.
• BatchBy – This value enables a client to determine if persisted claims are batched by day, or by calendar month.
• CES_Directory - This is the directory name used in %AppData% to store the BatchTracking file. It is required that the log4net File value uses this same directory for storing logs because the logger creates the directory being used by the Batch Tracking file. A configuration exception may be thrown if differing values are supplied.
• ConnectionString - This is the connection string for the QC History Data Store.
  • Without this setting, the module does not know where to store the request and response. If the module fails to store the request\response, a CES Processing exception will be returned to the host application.
• StoreRequest - This setting turns on whether requests are stored or not. Note that anytime an error is returned from the Vendor WebService, the request will be stored regardless of this setting.