7.1 New Features

This document provides an overview of the new features released in Aptify version 7.1. The content of this document is divided into the following sections:

Azure Enablement in Aptify

Azure Active Directory Reimplementation for trusted user

In Release 7.1, the authentication mechanism for the users to access Aptify Web, Aptify Services and Aptify Smart (Desktop) Client, once the applications are hosted on Azure, has been updated to utilize Azure AD.  This new authentication option replaces the previous Aptify Domain authentication, which is not available on Azure. This applies specifically to association who have hosted their Aptify web application on Azure App services. To know more about the new implementation, refer to Authentication using Azure Active Directory in Aptify Web 7.1 and Smart (Desktop) Client 7.1 documentation.

Enabling Crystal Reports to function with Azure AD authentication

In Release 7.1, Aptify product has undergone a reimplementation of Azure Active Directory (AD) to support authentication for AD users. To use Crystal Report as Azure AD user, certain configurations are needed on Azure Virtual Machine hosting the Smart Client application. Below are step-by-step instructions to configure Crystal Reports. See Generating Crystal Reports with Azure AD User document for the instructions. 

Utility for Custom Naming Aptify Database

Aptify release 7.1 provides support for enabling custom names to Aptify database. This gives the flexibility to an organization to designate a name other than APTIFY and to host multiple databases simultaneously on a single server. For more information on this topic, refer to document Utility for Custom Naming Aptify Database


Editing Persons on Directory page of Company Administrator

The Company Directory page in Aptify e-Business displays all of the persons records that are linked to a particular Company. The page allows a Company Administrator to search and view the Persons, Filter and Sort Persons records by column and Remove Persons from the company.  With release 7.1, the Company administrator is able to edit the member's information such as the first name, the last name, email address, title and phone number directly from the Company Directory Page. To achieve this, the UI of Company Directory Page is modified to add an Edit icon for each record. See Editing Persons on Directory page of Company Administrator for more information.

Company Directory implementation for eBusiness users

The Company Directory feature has been introduced to offer Company details to both signed-in users and guest users. This feature includes two new pages: Company Directory and Company Details. The Company Directory page lists Companies of the association, while the Company Details page displays detailed information about a particular Company. For more information on this topic refer to Company Directory implementation for eBusiness users document. 

Aptify Web

CardPointe Integration with Aptify

CardPointe is a complete payment processing platform provided by CardConnect, a leading payment service provider. It offers solutions for accepting and managing several types of payments, including credit cards, debit cards, and electronic checks. It uses special technology to protect sensitive payment data, which keeps it safe from fraud and unauthorized access. 

Release 7.1 includes CardPointe payment gateway integration with Aptify Web, Aptify Smart Client and Aptify e-Business applications. This release implements two modules namely, CardPointe Gateway and Hosted iFrame Tokenizer. For further details on this topic refer to Integrating Cardpointe with Aptify document, for information on how to set up and configure CardPointe refer to Setting up Cardpointe with Aptify

List View Enhancement

Aptify 7.1 supports creation and modification of List Views by selecting multiple fields at a time by use of 'CRTL' key. While creating a new view or updating an existing view field property, the users will now be able to move the field list in multiple formats using two ways; with help of a button click and with drag and drop functionality. 

With this enhancement, the users are able to perform following operations on the fields:

  1. Select multiple fields from the left panel and add it to the right panel and vice versa.
  2. Select multiple fields from the left panel and drag and drop to the right panel and vice versa.
  3. Adjust the orders of multiple fields at a time.

Refer to Selecting Multiple Fields in Properties for List View for more information on this topic.

Configuration Migration (CM) Tool Enhancement

The Aptify Configuration Migration (CM) utility assists developers in moving entities and metadata from one environment (the source) to another (the destination). Aptify release 7.1 provides an enhancement to this tool to simplify the selection of entities, metadata and records, now the logged in users are able to see the changes done between particular timeframes. The Configuration Migration Utility - Packer introduces a new checkbox - My Changes and date picker - From and To. This enables the user to view only those records that they have worked at during the specified timeframe and for which they want to create CM pack. See Packing "My Changes" Enhancement document to know more about the enhancements.

New Process Flow for Deleting Input Map Records

Aptify release 7.1 introduces a new process flow named “Delete Process Flow Run Input Map”. This process flow is created to delete the “Process Flow Runs Input Map” records for the process flows whose run records contain the payment information. Refer to Deleting Process Flow Run Input Map records document for instructions on how to run “Delete Process Flow Run Input Map”.

View Layout Setting Enhancements

In Aptify release 7.1, enhancements are made to the view layout setting functionality to enable users to retain the layout setting throughout the system, across all the services for a given user session. With this release, when a user changes the view layout to either grid view or list view or changes the sorting order, the setting persist even when the user navigates away from the service and returns to it.

For example, if a user changes the layout settings from “Grid view” to “List view”, the content changes to List layout using the existing functionality and remains in the List view even when the user navigates to any other service. Similar functionality is applied to “Sort by”.

The changed settings last for the time the user is logged in and does not affect the settings of other users. Once the user logs out of the session or when the session expires, the layout setting is reverted to the default values.

View Properties Filter Logic Enhancements

In Aptify release 7.1 the functionality of view properties has been improved to allow users to modify filter logic statements. A new field named Logic String has been introduced above the filters, displaying the logic string with its corresponding filter sequence number. The filter sequence number serves as an identifier for the logic string in the filter logic. By clicking the 'Set Logic String' button, users can apply any modifications made to the logic string. This enhancement complements the existing drag-and-drop functionality. Any changes made to the filter, whether through logic string or drag-and-drop, are reflected in both areas. The alterations are visible in the drag-and-drop section as well as the logic string section.

New Multi-Select Form Component for Aptify Web

Aptify release 7.1 introduces two new form components namely “Text Multi Select SQL” and “Text Multi Select” in Aptify Web. Users can manually add these components to any form template via Smart Client. When added to a form, the components allow users to select multiple options from a list. For more on how to use the Multi-Select Form Components, refer to About the Multi Select Text and Multi Select SQL Field Types.

Both the form components need to be manually added to the form template through Smart Client.

Product Deferred GL Account Enhancement

In Aptify release 7.1, the Product Deferred GL Account functionality has been enhanced to — add a new validation for Deferred Income GL account and display relevant error message.

Below are the details:  

  • While creating subscription product, if a user selects the “Deferred Income” checkbox for a record which does not have Deferred Income type added in the product GL account, below message is displayed.

    “This product is marked as Deferred Income product, but a Deferred Income GL Account has not been added to it or to the Organization that is associated with it. Please add one to this product or to the product's linked organization.”
  • While creating non-subscription product, if the user adds Rev Rec Date and adds Deferred Income type in the product GL account, the record is saved successfully.
  • While creating non-subscription product, if the user adds Rev Rec Date and does not add Deferred Income type in the product GL account, the record is not saved and below error message(s) is displayed.
    "Rev Rec Date should be future date from current date."
    "This product has Rev recognition date, but a Deferred Income GL Account has not been added to it or to the Organization that is associated with it. Please add one to this product or to the product's linked organization."

Career lead access method enhancement

Aptify release 7.1 introduces YM Career’s new method of access authorization namely X-API-Key instead of token-based authorization. The new method avoids the authorization error caused due to expiration of token by storing the access key in the database. To implement the changes, a new version of the Aptify Career Leads setup has been created to deploy the updated DLLs.

Ability to Clone Subtypes Records

Cloning of subtypes feature is available in Aptify Web with release 7.1, the Clone feature allows the user to copy a previously created subtype record. There are times when the user is creating multiple subtype records in a service and much of the information in each of the subtype records is the same. This helps reduce data input time and increase accuracy. For more details refer to Cloning of Subtypes Records document.

Support for Microsoft SQL Server 2022 as a Platform for Aptify

With the release of Aptify 7.1, Aptify has conducted testing using SQL Server 2022 and no compatibility issues have been identified. Please contact the Support team if you encounter any problems or have questions about using Aptify with this version of SQL Server.

Support for Microsoft Windows 2022 as a Platform for Aptify applications

With the release of Aptify 7.1, Aptify has conducted testing using Windows 2022 and no compatibility issues have been identified. Please contact the Support team if you encounter any problems or have questions about using Aptify with this version of Windows.

Bluepay Reconciliation Process 

Whenever an association user performs a payment transaction using Bluepay Hosted Payment (HPP), a Remote Payment record is created in Aptify application to keep track of all the HPP payment transactions.

Bluepay reconciliation process introduced in Aptify 7.1 release, voids the successful transactions on Bluepay site if the corresponding Remote payment Transaction records fail in Aptify with "Pending" status.

This avoids situations where the members would need to overpay due to two successful authorization records created in Bluepay site. First situation is when the Auth record fails at Aptify end, but Bluepay site is unaware of it and the second situation in which the members retried paying after seeing payment unsuccessful message on Aptify site. Bluepay reconciliation process also avoids overcharging customers due to generation of two Sales records.

The reconciliation process is handled in Aptify by a new process flow named "Single Remote Payment Reconcile Record" which when run, compares the Remote payment Records (with "Pending" status) with the corresponding Bluepay transaction records to confirm the “Type” set for the respective Bluepay  record.

In case a discrepancy is found, the “Type” value for such Bluepay Transaction record is updated to “Void” and the corresponding Remote Payment record in Aptify is updated to “Cancelled” status.

Rest of the existing Bluepay functionality remains as is.  Refer to Applying Bluepay HPP on classic e-Business 5.5.3 for more details on Bluepay functionality. 



To accomplish Bluepay Reconciliation process in Aptify 7.1 release, following configurations need to be confirmed:

  1. Update the Timeout attribute value in Bluepay Merchant Account record to 30000
  2. The Aptify PF record" Single Remote Payment Reconcile Record " has to be manually run for the reconciliation check on Bluepay. Hence, Associations can plan to schedule the Process flow to run on a periodic basis by scheduling the jobs using Aptify Application Server.
  3. For Aptify Desktop, add below attributes in Aptify Shell.config file:

    <add key="Aptiy.Framework.Payment.ClientInformationProvider" value ="Aptify.Applications.OrderEntry.Payments.ClientValuesDesktop.DesktopClientInformationProvider, ClientValuesDesktop, Version=, Culture=neutral, PublicKeyToken=f3fa0ecabf9514d9"/>

  4. For e-Business 7.x / Aptify Web, add below attributes in SOA Web.config file:

    <add key="Aptiy.Framework.Payment.ClientInformationProvider" value="Aptify.Applications.OrderEntry.Payments.ClientValuesServices.ServicesClientInformationProvider, ClientValuesServices, Version=, Culture=neutral, PublicKeyToken=f3fa0ecabf9514d9" />

  5. For Classic e-Business 5.5.3, add below attributes in Web.config file:  

    <add key="Aptiy.Framework.Payment.ClientInformationProvider" value ="Aptify.Applications.OrderEntry.Payments.ClientValuesDesktop.DesktopClientInformationProvider, ClientValuesDesktop, Version=, Culture=neutral, PublicKeyToken=f3fa0ecabf9514d9"/>


Security Enhancements

ASP.NET version disclosure in the server header

It was observed that the service calls in Aptify Web were exposing the ASP.NET version in the response headers. To fix this issue, new property has been added to the Web.config file to hide the version.

Broken Access Control 

In this release, significant security improvements have been implemented to enhance the access control of views. To validate permissions for a particular view, authorization filters have been created. When dealing with entity views linked with an application, the authorization process considers the application security group and user permissions. In cases where an entity is not linked to any application, the authorization is based on the entity's security group and user permissions. Based on these factors the view access request will be served.

Masking Sensitive Data Records

Aptify 7.1 provides a utility named "Mask Sensitive Data". This utility enables to mask the sensitive information present in the history records for a given table name and column name. Refer Utility for Masking Sensitive Data Records document to get the instructions on running the utility.

Incorporation of Black Duck Scan findings

The security findings from the Black Duck scan have been incorporated in this release. As a part of security enhancement, the following libraries have been upgraded:

  • The Bootstrap version has been updated from BootstrapV4 to BootstrapV5.3.0-alpha3.
  • The jQuery library has been updated from Jquery3.2.1.min.js to Jquery3.6.4.min.js 


Was this article helpful?
0 out of 0 found this helpful



Please sign in to leave a comment.