New Features

The following new features have been included in Aptify 6.1:

"Summary Data Table" tab introduced for the Chart View

Aptify Web 6.1 introduces the "Summary Data Table" feature for the chart views to provide a tabular representation of the chart view data. In the chart view data table, the rows represent the primary group and the columns represent the secondary group with individual cells displaying the summary as per the function defined in the chart view properties. The Summary Data tab appears only when the Show Summary Data table option is checked under the Data option tab. (Issue 3142)

Automatically Highlight the View Prompt Placeholder Text in the Prompt Field

Aptify Web 6.1 has enhanced the Prompt views to automatically select the view prompt placeholder text (default value) when the user clicks in the prompt field. The user can type the new prompt value in the prompt field and does not require to delete the existing value manually. The auto select of the prompt value in the prompt field happens only when the user clicks inside a particular prompt field that already has text in the prompt field. If the user deselects the prompt field and does not carry out any changes, the previous prompt value is retained. (Issue 1836)

View Management: Able to change the view and folder ownership

In Aptify Web, enhancement has been made so that admin or power user can update the view ownership of views including the folder they reside in. So that when an employee is no longer with the company and the views are still in use, admin can transfer the ownership to someone else. (Issue 3344)

Support the Entity Base view record packing and unpacking without the need to pack/unpack the entity

CM tool has been updated to support entity base view record packing and unpacking without the need to pack/unpack the entity and perform the operations in one go. The end user can now unpack the pack successfully on the destination server and start using the unpacked base views. (Issue 1238)

Ability to track usage of view

In Aptify Web, Administrator will now have the ability to track the usage of all the views in the system to make decisions on unused views depending on the usage pattern tracked. Usage statistics can be on a ‘per view’ basis or can be run based on a dataset.

The following details will be available in the statistics:

  1. View ID
  2. View name
  3. Last run by user ID
  4. Last run by Username
  5. Last run on date
  6. Dependent area - area where view was opened
  7. Run count - number of times view was used on that area
  8. View owner name
  9. View creation date

Whenever the user accesses a view from any control like forms, dashboards, other views, shared views, process flows, event handler, ServiceDatatObjectParameter, the above mentioned details are populated in ‘View Statistics’ Table. The details in View Statistics table is the reference data for administrator user to decide which views can be discarded and which ones need to be maintained.

Other than the views that cannot be tracked via view tracking as a result of view execution, we need to provide a list separately so that administrators know that although the view is not getting directly executed, they cannot be deleted because they are part of the system and without them, the feature will not function correctly.  

All the views that are used by the application internally will be marked as ‘Is System View’. Aptify 6.1 setup will take care of marking all such existing views as system views. An Administrator will not be allowed to delete the views marked as system view.  Tagging a view as System view will help administrators to avoid accidentally delete them and, in the process, break the functionality that those views may be used in. This will also include views used in process flows, event handlers, etc. Such stock views will be automatically marked as System Views by the 6.1 installer.

Retain the view state after opening and closing the record

With Aptify 6.1, when a staff user opens a record from a view, finishes his work with the record and come back to the view, then the view will retain the same state as it was prior to, when the record was opened. This will help the user to easily track where he was and resume from that position.

For example, I open the last record from the 3rd page of list view and if I closed record, then it should come back to the same selection and auto scroll to the same location. Also, if the view content has changed in the meantime by another user, the row selection should be still correct.

Please note that the view could be a regular list view, a prompt view (again can be of any view type), a chart's drill down view.

Ability to Display Fields Linked to Other Services as Hyperlinks in a List View and open them in Aptify Web

Aptify 6.1 has provided the ability that will allow users in Aptify Web to open linked records directly from list view. The list view will display fields linked to other services as hyperlinks in a list view. In the properties of a view, under the Fields sub-tab, the fields that were enabled for hyperlink functionality has the Hyperlink checkbox checked by default and contains the Target Entity and Target Field values. The hyperlink functionality is disabled, and cannot be enabled, for entities that are embedded in one or more container entities via an embedded link field (For example, the Payment Information, Addresses and Phone Numbers entities). (Issues 3141)

Please note that the 6.1 setup will automatically update this feature for all the existing views in the system.(Issue 3133)

The feature will respect the settings of the existing entity attribute described below:

Attribute Name: ShowHyperlinkInViewDefault

This Attribute controls Hyperlink functionality at Global Level for this Entity. This can be overridden at ViewLevel by setting HyperLink Check Box 0/1 for particular Field from View Properties. Set this attribute value to 1 to enable hyperlink functionality in Entity List view by default. To disable default Hyperlink Functionality for Entity set it to 0. (Issue 3100)

Enhancements to the Attachment control

In Aptify 6.1, UI enhancement has been done to the Attachment control. User can see the attachments as per the attachment category and when working with attachments tab of a record, user can see the following information about the attachments:

  • File Type
  • Name of the attachment
  • Category
  • Updated By
  • Last Updated
  • Created By
  • Created
  • File size

The attachment control will be listed by default in the order of latest updated attachment and the UI shows the default sort order as well via the sorting indication next to the column name. User can change the sort order (ascending and descending) for all the columns wherever needed.

Each file can be identified by its file type icon. Also, we have added few more options to the attachments which are as below:

  1. Rename: To rename the attachment file. The default behavior will be based on the browser’s preferred location.
  2. Download: To download the attachment file.
  3. Delete: To delete the attachment file. This will be based on the permission set.

Only the person who uploaded the attachment should be able to edit the file name.

Drop down or list box does not show the results when more than 4 values are entered

This release adds support for the AddressListtoShow property to Aptify Web. When set in the form template part of an Address control, this property identifies the list of address types to display in the address drop-down control.

Note that if you choose not to show an address in the drop-down, that address will not be the default Preferred Mailing Address option. Likewise, you may want to remove any addresses you do not show in the drop from the Value List for the PreferredMaillingAddress field to avoid user confusion.

Drop down improvements in Aptify Web

In Aptify Web, when user is on a drop down field and the drop down has been configured to display different columns, user can see all the columns when the drop-down list appears. This will help to achieve easy access to details related to data for selection, if configured.

Whenever new entity or new field is added to an existing entity then drop-down functionality will respect accordingly. The user can select values and the selected values will save or update correctly within the context of the functionality it is used on.

Aptify web will now be supporting for full name of state and country in related dropdown along with the abbreviation.   

Update Aptify logo on Aptify Web to new logos provided by corporate marketing

CB Corporate marketing team has provided new logos to be used for the product. Updated Aptify web to use the appropriate logo in

  • Main toolbar
  • Login screen
  • Logout screen that allows returning to the Login screen.

View Management: Able to change the view and folder ownership

In Aptify Web, enhancement has been made so that admin or power user can update the view ownership of views including the folder they reside in. This is applicable in cases when an employee is no longer with the company and the views are still in use, admin can transfer the ownership to someone else.

When changing the view owner, we recommend that the view categories owner be changed.

This operation shouldn't require sysadmin permissions, but the user should at a minimum be part of the view administrator's group (as defined by the ViewAdministratorGroups entity attribute on the Views entity).

Below Entity Bulk Operations can be used for the same:

  • Change View Owner:
  1. Changes the View Owner.
  2. Is used in conjunction with the Change View Category (Folder) Owner EBO to effect transfers of Views to new Owners within a department or function.
  • Change View Category (Folder) Owner:
  1. Changes the View Folder Owner.
  2. Is used to transfer folder ownership from BaselineAdmin to a selected department/function Admin or End User of that group.
  3. The Change View Owner EBO should then be run to transfer ownership of the Views in that folder.

Redesign Pagination control within the grid views

Aptify 6.1 introduces new pagination control used within grids (ELV, sub type control, etc.). Pagination control is having the components as shown in the below image. We have followed the Aptify UI style guide for new design of pagination control.

Sr No





Clicking on this should take user to first page.


Clicking on this should take user one page lower from the displayed page.


Input/Display box

This displays the current page number. Clicking on this will allow user to change the value of the page.

User can give input only in numeric value (natural numbers i.e. 1, 2, 3 etc.).

User can give input values between one to highest page number.


Clicking on this will take user one page higher from the displayed page.



Clicking on this will take user to the Last page.


Absolute Index

This displays the available items on particular page which you have selected from the total items.

Porting BluePay Integrations in Aptify 6.1

With Aptify 6.0 , Bluepay Integrations was provided as a separate setup to be installed over 6.0 release. With Aptify 6.1, the bluepay payment changes are integrated in stock 6.1 and no separate  bluepay setup installation is required for the same. As an Aptify user, I will be able to process payments (authorize, capture, sale, re-authorization, voids, inquiry, credits/refunds) through BluePay payment provider.

For more details on Blue Pay Integration, please Click Here

BluePay Integration Phase 2: Implement Customer IP Address Tracking for Fraud Tools

There is an implementation of BluePay Integration feature that will collect and pass Customer IP address to BluePay transactions so that they can use it for Fraud tools that the clients have enabled. The customer IP address will be the user’s machine IP address from where the payment transaction is initiated.

  • For Staff users: Computer that he/she may be using to launch the client (Desktop or browser)
  • For POS user: The device used
  • For the Organization's Member: Member’s computer that is used to connect to the self- portal site.

The fraud settings can be done on the Bluepay site under Fraud settings section.

Fraud tools/feature where the Customer's IP address will be used are:

  • Velocity Filter: Prevent criminals from testing card numbers against your merchant account. This filter can be configured to automatically decline transactions based on several parameters within a 60-minute time period : number of transactions, number of transactions from a specific IP address, and maximum dollar amount for credits/refunds, sales and total sales amounts.
  • Card Issuing Country: Accept transactions only from countries you deem trustworthy, and block transactions from those that seem too risky. BluePay accomplishes this by performing a BIN lookup of the card, which identifies the country where the card was issued.
  • Geo IP Tracking: Block transactions from specific countries based on the IP address.
  • Negative Database: Identify fraudsters listed in the database by IP, email or address.

Please select below Bluepay link videos for more information on Fraud Tool options:

Implement Payment Processing through Hosted Payment Page functionality

Payment Processing through Hosted Payment Page’ will minimize PCI liability and scope by allowing customers to use BluePay hosted checkout pages instead of Aptify checkout pages. Hosted Payment will be available on both desktop and web application on all the payment related pages where credit card payment processing is available. As a staff user of Aptify, if I try to pay for an order on behalf of a client using a CC payment (reference transaction), I would be taken to the BluePay's portal for input of the CC details. Once the payment is processed, I would be returned back to the same screen and the processing details would come back and get saved in the DB. Çlick the below link to know more about Blue Pay Hosted Payment form.


Please note that the framework built for BluePay Payment Hosting has been made generic enough to support other Merchant Accounts Payment Hostings.

For Technical documentation on Bluepay payment Hosting in Aptify, please click here

BluePay Integration Phase 2: Renew Pre-authorization that are older than certain number of days.

Enhancement has been made in BluePay integration so that an association staff will have ability to process pre-authorization on charges that have been delayed to the point that the original pre-authorization has expired so that the credit card company will not chargeback the transaction due to failure to have pre-authorization.

This feature will be beneficial for organizations where it will re-authorize the payments which have be authorized before certain number days defined in the pre-requisite during Capture process. As system will re-authorize the payments, organization will be able to identify the failed authorization due to any reasons like Fund is not available now, Card is expired, Card is not available now i.e. blocked or terminated and due to this feature, Organization will be able to avoid the revenue losses caused by such scenarios.

On the Payments entity, a new Attribute has been added termed ‘ReAuthDays’.

This attribute tracks the number of days after which the original Payment authorization will be automatically re-authorized before the Payment capture process Is run; either manually through the ePayment Capture wizard Or When the capture process Is automated via the Scheduled Task. For example, If the number of days Is set to 10 in the value field And a Payment that was Authorized on 01/01/2018 Is attempted to be captured after 01/10/2018, the original authorization from 01/01/2018 will Get re-authorized automatically With a New authorization number before the capture process Is complete And finalized. By Default, this feature is turned On with number of re-authorization days Set To 5. If the attribute value Is Set To 0 Or If the attribute Is Not present, the feature will be turned OFF.


For regular CC, the reauth from the wizard will fail when CSC check is enabled on the merchant. It follows the same existing logic when a new authorization is being done for a regular CC and lack of CSC information makes the authorization fail.

For a reference transaction CC, the reauth will be successful even though there is no CSC available during the reauth process because it goes based on the previous transaction number for the same CC. This again is in line with when the re-authorization is manually attempted through orders form if a new order line is added and payment is updated to pay in full.

Aptify Web: Support opening of order line record for sub products in a Kit

In older versions of Aptify, the order details form for sub products within a Kit orderline doesn't open. In Aptify 6.1, it has been made possible to open/edit order line details of the sub products in the Kit and make changes that will be specific to that order line.

Depending on the product type of the sub product, respective tabs would be visible for users.

Specific details which will not be editable on the sub-product orderlines are defined below:

  • All Product Type
  • Quantity
  • Price
  • Discount
  • Discount Overridden
  • Description
  • Not Returned to Stock
  • Meeting Product
  • Meeting Name
  • Exhibitor booth
  • Class Product
  • Meeting Registration
  • Expo Product
  • Configuration Type
  • Units
  • Surcharge

Support Float Data Type in Aptify Web.

With Aptify 6.1, Aptify staff web user will now be able to read, add, update and delete data from a field that uses Float SQL data type.

Aptify Web: Enter Key Does Not Work with Prompted Views

In Aptify Web, there was an issue while using a prompt view. When any value is entered in text box and enter key is pressed on keyboard then the trigger functionality was not working. Aptify 6.1 updated the trigger functionality equivalent to clicking.

Hovering on Most Recent Used Items must show the Record Information

Aptify Web 6.1 has enhanced the MRU configurations to provide the Entity Culture String Name Record ID and ID of the Record when hovered on an MRU entity/views item. These details will help a user to identify the Record ID of the MRU item and also its respective Entity/Service. (Issue 1650)

New User Wizard: Existing User profiles in the drop-down list must be Alphabetic Order

In Aptify smart client, the New User Administration Wizard has been updated to show the user profiles in the alphabetical order instead of as per the date created. This improvement is carried out by updating the existing stored procedure to get USERID sort by ascending. (Issue 2702)

Upgrade to Kendo UI Library

To support Aptify 6.1 features and bug fixes, the Kendo UI library and other third-party controls have been updated to the latest version. The Kendo UI Version available in Aptify web is v2018.2.516. (Issue 2584)

Increase Field Size for ImportRunMappings.MappingField to 100

Aptify 6.1 has enhanced the generic import process by increasing the “MappingField” size to 100 characters on the subtype entity "ImportRunMappings" to match the DefaultMappingField on the ImportSourceColumns and run the generic import process successfully. (Issue 2741)

Ability to default the topic code tab in web to a Tree View instead of Flat view

Aptify 6.1 has ability to display tree view as default view for topic codes so that user can select the topic codes available for that record and don't have to guess the topic code name or know it beforehand.

(Issue 2861)

Implementation - Improve performance of Organizational GL Account information

In Aptify 6.1, performance improvements has been done on Organizational GL Account.

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



Please sign in to leave a comment.