New appSettings entries for config files in 6.2 release

Owned by Sagar Alat
Oct 15, 2020
3 min read

The following new appSettings entries are introduced for the application config files with the 6.2 release.  

Aptify.Unpacking.Generic.ObjectRepository.AllowMissingAssembliesInPacksTheyExistInObjectRepository

  • Purpose:  When creating cmpacks for unpacking sometimes it is desirable to leave Object Repository assemblies out of the packs contents. This is desirable when the assembly will already exist in the Object Repository from a prior install and the assembly is not changing, or the assembly update will be deployed by setup code rather than the unpacker.  
  • Prior Behavior:  Prior to 6.2 when the pack does not contain the referenced assembly an error is logged during unpacking.  
  • New Behavior:  When this setting value is true and the assembly exists in the object repository the unpack will be successful. The log file will contain the following message:  Repository: someassembly.dll already exists in destination database and is not present in the pack. Skipping OR update.
  • Default Value (when setting is undefined): True
  • Action Needed:  If the new behavior is desirable, which should be the default for most customers, no action is necessary. Customers who want the old behavior should add an appSetting entry to the config file for their application with a value of false.  


Aptify.Services.Views.EnableCaptureViewStatistics

  • Purpose: Aptify 6.1 introduced a dependency on a config file attribute EnableCaptureViewStatistics, as a part of the View Statistics feature implementation. This config file attribute is placed under the appsetting entries, however, is not automatically added to AptifyAsyncProcessor.exe.config or AptifyCreateProcessFlowRun.exe.config as part of the service pack installer. Due to this application server feature does not work correctly when this setting is not available in the application server config files. Hence they need to be updated in the AptifyAsyncProcessor.exe.config and AptifyCreateProcessFlowRun.exe.config files.
  • Prior Behaviour: Without this attribute, the Application Server fails to process jobs.
  • New Behaviour: When this setting value is true, the application server successfully processes the jobs scheduled.
  • Default Value: True
  • Action Needed: This attribute is default available in the application config files but not automatically added in  AptifyAsyncProcessor.exe.config or AptifyCreateProcessFlowRun.exe.config for application server features. Hence this will now be available with default value true.


Aptify.Framework.GenericEntity.AptifyTypeResolver.DisableWarning

  • Purpose: Aptify 6.1 introduced a silent error warning getting displayed in Desktop Session Exception while opening a record, creating a view, loading a view/dashboard , etc. This attribute has been added to disable the warning message,
  • Prior Behaviour:  In Aptify 6.1, this  attribute was set to false by default and hence the multiple warning messages appearing in Session Exception was not considered user friendly
  • New Behaviour: In 6.2, the setting value is set to True by default so that user will not see this warning message.
  • Default Value: True
  • Action Needed: This attribute is default available in application config files and set to true. No specific action needed as the warnings have been disabled by default.

Aptify.Framework.Payment.showAcceptAmex

  • Purpose: In Bluepay Hosted Payment form, the American Express card icon was displayed by default even when the specific payment type was not in use. This attribute has been newly added in application config file to show/hide the Amex card option based on the requirement.
  • Prior Behaviour: In previous versions, the icon was always displayed by default on Bluepay Hosted Payment Form and there was no option available to hide the icon.
  • New Behaviour: In Aptify 6.2, this attribute setting value can be used to 'show' or 'hide' the American Express Card Icon on the Bluepay Hosted Payment form by setting the attribute value to true or false respectively.
  • Default Value: False, due to which the Amex card icon will not be displayed on the hosted payment form.
  • Action Needed: This attribute with default value false will hide the American Express card icon. So if the user wants to display the icon, the app setting value for this key need to be set to true.

Aptify.Framework.Payment.showAcceptDiscover

  • Purpose: In Bluepay Hosted Payment form, the Discover card icon was default displayed even when the specific payment type was not in use. This attribute has been newly added in application config file to show/hide the Discover card option based on the requirement.
  • Prior Behaviour: In previous versions, the icon was always displayed by default on Bluepay Hosted Payment Form and there was no option available to hide the icon.
  • New Behaviour: In Aptify 6.2, this attribute setting value can be used to 'show' or 'hide' the Discover Card Icon on the Bluepay Hosted Payment form by setting the attribute value to true or false respectively.
  • Default Value: False, due to which the Discover card icon will not be displayed on the hosted payment form.
  • Action Needed: This attribute with default value false will hide the Discovers card icon. So if the user wants to display the icon, the app setting value for this key need to be set to true.