If you have a comment on this topic, contact Aptify Documentation. If you want to return to the Aptify Community Site, please click here.

Aptify 5.5 Release Notes

Owned by admin (Deactivated)
Last updated: Aug 24, 2016
67 min read

First published in November 2011.

This document provides an overview of the new features and resolved issues found in Aptify version 5.5. The content is broken down into the sections below.

Important Notes and Issues

The following are Important Notes and Issues related to Aptify 5.5:

Additional and Previously Released Service Pack Documentation

Depending on your organization's upgrade path, having access to previously released documentation can be helpful in determining how to make the most of your upgrade. Also, in certain cases, Aptify may want to provide supplemental documentation to be included with the current release. With this in mind, the Aptify 5.5 distribution file includes an Additional Documentation folder for previously released documents and other relevant information. Additional documents included with the Aptify 5.5 are as follows:

  • Aptify 5.0 Service Pack 3 Release Notes
  • Aptify 5.0 Service Pack 2 Release Notes
  • Aptify 5.0 Service Pack 1 Release Notes

 New Features (Aptify Framework)

The following new Aptify Framework features have been included in Aptify 5.5:


Issue 10886: Aptify Framework – Provide Ability to Sequence Find Results

In earlier versions of Aptify, find results are sorted based on the Record ID by default. For example, when creating a test view for Persons with a filter applied for records that include a last name beginning with the letter S, the results are displayed sequentially by the Record ID field. Aptify 5.5 has been updated to include the ability to set the default order of find results so a user can sort the results based on their individual preference.

Issue 10880: Aptify Framework – Object reference error when adding a subtype entity records.

On the latest build received on 10-Mar, Object reference error is displayed when adding a subtype record like 'person-relationships' record or price record to Persons or Products entity respectively.

Issue 10535: Aptify Framework – Documentation Update on Writing Exceptions to a Log Common Log File

In Aptify 5.0 Service Pack 3…. This issue was created to track a feature request to expand access to error logs and allow users to review any errors via a central error log. Aptify 5.5 provides this functionality

Issue 8489: Aptify Framework – Documentation Update: Add Info About Melissa Data Address Object to Product Documentation

This is a feature request to add the requirement of installing the address object on the local workstation for Melissa Data. This is needed when Melissa Data has been installed on the network and the workstations accessing the data are being configured.

Issue 10708: Aptify Framework – Link Box: Expose ValueField Property

In Aptify 5.0 Service Pack 3, link boxes can only be used on standard Aptify forms to display fields that are foreign keys linking to the ID of the referenced table/entity. For instance, the "CompanyID" field in Persons entity points to the ID of a company so we can use a link box to display the Company ID field on the Persons form, but the "GLAccountNumber" field in ProductGLAccounts entity links to the "AccountNumber" field (not ID) in the GL Accounts entity, so a link box cannot be used to display the GL account number on the ProductGLAccounts form. Starting with Aptify 5.5 the ability to display fields that link to any other field in the referenced table will be implemented.

Issue 10707: Aptify Framework – 5.5: Update Virtual Fields Linked to a Field in the Resultset

In Aptify 5.0 Service Pack 3, for sub-types, currently any virtual field associated with a linked field in the sub-type is updated in the grid automatically if the linked field uses Link Box. However, this doesn't extend to other form components, such as the data combo box. For example, if you have virtual fields linked to a data combo box field, the system only updates the virtual fields connected to the linked entity's IsName field. Aptify 5.5 updates this configuration to modify the virtual field linked to any field in the resultset.

Issue 10666: Aptify Framework – Display Selected Record Count in a List View

In Aptify when a user selects an individual row or multiple rows, currently the application does not display the total. For example, when using the Orders service if you select a single row or multiple rows it would be helpful to display the total for the rows selected rather than having to count manually or export the data. Starting with Aptify 5.5 the number of selected rows will be displayed next to the number of pages on the lower right of the window.

Issue 10298: Aptify Framework – Provide a Programmatic Option to Force Entity Object's Save Method to Call Validate

The Entity object's Save method only calls Validate if the Object's IsDirty property returns True. There are cases where a developer may want to have the Validate method execute during the Save method when the IsDirty property returns False.

Issue 10297: Aptify Framework – Provide a Programmatic Option to Force Entity Object's IsDirty Property to Return True

There are some rare cases where it would be useful to force the Entity object into a "Dirty" state without changing an Updateable Field's value. During a Save operation, certain actions and events only occur when the object's IsDirty property returns true.

Issue 10278: Aptify Framework – Messaging: Support Authenticated SMTP Server

Aptify's Messaging system needs to support authenticated SMTPs. We need this for internal use, hot fixed for 5.0 SP3

Issue 10259: Aptify Framework – Bulk Messaging: Add Progress Bar

In Aptify 5.0 Service Pack 3, the Bulk Messaging dialog does not have a specific progress indicator when messages are being sent. For example, when sending a large number of messages or if there is a slow connection to the message system, it can take a while for the messages to send and the dialog to close. During that time, there's no visual indication to the user that the system is working on sending the message. While some versions disable the send button, Aptify 5.5 has introduced a progress bar to help illustrate that the action is still processing.

Issue 10117: Aptify Framework – Add Property to Entity List View (ELV) that Supports the Display of an Entity Record as Modal

In earlier versions of Aptify …..
Add a property, DisplayEntityRecordAsModal, to the Entity List View Form Component, and as a property on the AptifyEntityListView class. When false, which is the default, New and Open operations will display the Entity record in a modeless window. When true, the Entity record will be displayed in a modal window. Note that, if the ELV is in a modal window, any Entity record displayed from the ELV will also be in a modal window, regardless of the value for DisplayEntityRecordAsModal.

Issue 10078: Aptify Framework – Filter Rules Control Should Support Field Sorting

In Aptify 5.0 Service Pack 3, if you have an entity with a large number of fields, it can be hard to locate a particular field in the Field drop-down list when creating a Filter Rule. Beginning in Aptify 5.5 users can click the headings that are displayed and the results sort in ascending or descending order.

Issue 10077: Aptify Framework – Filter Rules Should Support Date Keywords

For Aptify 5.5, we're implementing filter rule-based product pricing for extended products, like Meetings and Classes (Issue 5671). One of the Cases linked to Issue 5671 has a scenario that we don't support currently. The organization wants to use a single Class Product for many classes. But, they offer early registration price incentives (for example, if someone registered 30 days before the class start date, then the price is $100, otherwise it's $200). See About the Filter Rules Infrastructure for more information.

Issue 9833: Aptify Framework – Filter Rules: Add Exclude from List Checkbox to Entity Instances Record

This issue tracks a feature request to add an "Exclude from List" check box to the Filter Rule Types' Entity Instances sub-type entity/form. If an admin marks an Entity Instance as Exclude from List , then that instance shouldn't show up in the Filter Rule Services drop-down list (for FilterRuleIDs that use that particular Filter Rule Type). In some cases, we have a lot of entity instances and the number may continue grow. Adding this flag would allow organizations to remove the ones they don't want to support from the list of options users can select between.

Issue 9839: Aptify Framework – Tab Styling: Provide Better Highlighting for Currently Selected Tabs

In Aptify 5.0 Service Pack 1 we added the ability to define the tab styling for each Form Template Part that implements a tab control. This issue is a Feature request to build on that existing functionality to include additions such as: Add Bold, Italic, and Underline options for the Selected Tab to the Input Map configuration options that are available when Form Template Part Type is Tab Control. Currently, you can make all tab names, bold, italic, or underline, but updates should configure the tab control to use these properties for only the Selected Tab. Beginning with Aptify 5.5 configuration updates provide a better way of visually identify what tabs a user is viewing or has selected. For additional information on this feature please refer to …….

Issue 9692: Aptify Framework – Support Loading Different Forms based on Usage Context

In existing versions of Aptify the creation of a new Products record is completed with a standard form. This issue tracks a feature request to allow different forms to appear based on the usage context. For example, it would be useful to offer a Products form that is specific to Meetings a second form specific to Expos. Another example would be to provide a Companies form that appears for Companies of type "Vendor" but a different form if the Company Type is "Competitor", and a third form if "Member." Beginning with Aptify 5.5 these expanded forms will be available based on newly implemented filtering rules. 

Issue 9691: Aptify Framework – Layout Controls Need to Support Multiple Forms

For Aptify 5.5, we want to begin to offer multiple forms for the same service based on:
Record Type: For example, a Products form that is specific to Meetings, and a second form specific to Expos. Or, a Companies form that appears for Companies of type "Vendor" but a different form if the Company Type is "Competitor", and a third form if "Member."

Process: We should have process-based forms that include a limited number of fields. For example, for new records, you would have a form that presents all of the required fields in one area; but for an existing record, you might want a different form design. Or, if you are planning a meeting, you'd want a different form than when you're closing a meeting.

User/Group Affiliation: We should display a specific form based on user or group affiliation. So a Membership user might see a different Persons form than a Meetings user.

Currently, an Aptify Layout Control targets to a specific form because the layout control looks for specific Form Template Parts based on Name. In most cases, we won't be able to use the same Layout Control for all versions of the form since each form is likely to have its own distinct set of Form Template Parts (we can't reuse the same parts because each part contains position data and the same field may not be in the same location on all of the forms).

Issue 9537 Aptify Framework – Add Keyword to Insert Current Date and Time

In Aptify 5.0 Service Pack 2, currently any records that include the GETDATE function return only the date and not the time. This issue is a feature request to display Date with Time stamp if field contains default value as GETDATETIME or GETDATETIME(). Aptify 5.5 has been updated to offer this expanded functionality.

Issue 8684 Aptify Framework – Make Culture String Records Name Field Unique

Currently in Aptify the Culture String Records Name does not require a newThis feature request has been created to make the Culture String records Name field unique. Object methods that are associated with them may retrieve incorrect culture labels in the way they set up currently. This change will alleviate this problem.

Issue 8548 Aptify Framework – Clustered Indexes on Aptify Tables

Currently in Aptify the indexes are not configured using clustering. For example when joining lookup tables, it has been noted that the user can create clustered indexes, but cannot remove the unclustered index on the primary key of the entity. If they chose to have a clustered index on the primary key it must live with both indexes. Aptify 5.5 has been updated to include clustered indexes to speed up and improve performance on the application.

Issue 8412 Aptify Framework – Ability to Remove Multiple Records from a List

Currently on the system, if a user wants to remove records from a list they have to right-click on each one individually and then select "Remove from List". This feature request is being created so that multiple records can be selected and deleted so it takes up less of the user's time. The fix should also incorporate keyboard shortcut functionality like selecting records with the control and shift keys.

Issue 6887 Aptify Framework – Controlling Display of Time Fields in List Views to Support 12 Hour Format and Other Options

Aptify 5.0 introduced support for the Time data type, which was added in SQL Server 2008. However, Time fields only show up in 24 hour military format when displayed in a list view. (On forms, the time is displayed in the format defined by the user's Windows Regional settings).

Aptify should display Time data in the 12 hour, AM/PM format by default and support an option to display the time in 24 hour military format.

It should also allow user to specify the accuracy of the date or time value. Example: For Time, should it only store up to the minute, second or to fractions of a second. This could either be a way to specify the precision for the field at the field level (i.e., only store to the nearest second) or it be just a way to determine what appears in a list view (time value is stored to the millisecond in the database but only displayed to the second in list views).

Issue 6557 Aptify Framework – Entity Fields: Ability to Use Link Boxes for Fields Other than ID

Currently, link boxes can only be used on standard Aptify forms to display fields that are foreign keys linking to the ID of the referenced table/entity. For instance, the "CompanyID" field in Persons entity points to the ID of a company so we can use a link box to display the Company ID field on the persons form, but the "GLAccountNumber" field in ProductGLAccounts entity links to the "AccountNumber" field (not ID) in the GL Accounts entity, so a link box cannot be used to display the GL account number on the ProductGLAccounts form. In Aptify 5.5 the configuration has been updated to allow users to display fields that link to any other field in the referenced table.

Issue 6552: Aptify Framework – Messaging: Add Confirmation Message So That Bulk Emails Are Not Sent Unintentionally

Currently in Aptify, the "Send" button on the Messaging form is located directly below the File menu. So, if a user accidentally clicks on this button, the messages may be sent unintentionally. Aptify 5.5 has been updated to help prevent this situation from occurring. This can be implemented by…..

  • Moving the Send button to the extreme right of the form. This will prevent user from accidentally clicking on that button when the intention was to click on File menu.
  • Adding a confirmation message when Send button is clicked. This will allow user to make an informed decision whether to send the email or not. This message should be configurable by an administrator (turn it on or off) since some users may find it distracting and a burden.

Issue 6487: Aptify Framework – Revert to Save Record Should Suppress Dialog When No Changes Are Made

In Aptify, a user can click the Revert to Saved button in the Data Control Bar to restore a record to its saved state and undo any changes made since the last save. It can also be used to refresh a record in cases where a user has not made any changes to the record data since the form was opened. Currently, when using the Revert to Saved Record feature, the Dialog box "Are you sure you want to reload the last saved version of this record?" appears with a list of changes (if applicable) since the last save. In addition the dialog appears when nothing has changed when using the Revert to Save Record feature. Beginning with Aptify 5.5 this dialog will be suppressed and will not appear when no changes have been made.

Issue 5153: Aptify Framework – Generate a Contact Log for Each Message Sent

Currently in Aptify the content management system can be used to record contract with a customer/member and Contact Log records can be linked to any record in the system. This issue tracks a feature request to expand the Contact Log feature to allow a user to automatically generate a contact log for any successfully sent message. Aptify 5.5 has been updated to allow users to automatically create Contact Log records for entities that support Bulk Messaging feature.

Issue 4813: Aptify Framework – Improve Clustered Index Creation and Management

In 3.5 and prior versions, the primary key was always the clustered index, which in possibly the majority of situations is not an appropriate clustered index choice. In 4.0, the primary key is a non-clustered index by default, which is probably desirable given that it is not usually the right clustered index candidate. However, if you mark a field as Indexed in an Entity Fields record, this also creates a non-clustered index. So, most created through the entity tool will lack a clustered index. The only way in which a clustered index could ever exist in 4.0 is if someone wrote a CREATE INDEX statement and deployed it via Entity Indexes sub type.

Issue 3391: Aptify Framework – 3.x Messaging Enhancements: Adding Confirmation Message

Currently in Aptify when a user clicks on the Send Messages button on the Messaging dialog the system performs the requested action without confirmation. In some cases it can be helpful to have a confirmation dialog appear before the message sends to prevent users from sending messages accidentally. In Aptify 5.5 administrators will have the ability to enable a message dialog, by turning the feature on or off, and when enabled it will prompt the users to confirm before the message is sent.

New Features (Core Business Applications)

The following new Business Application features have been included in Aptify 5.5:

Issue 10985: Order Entry – PA DSS: Support Paypal Reference Transactions - Payments

Testing for this should be done for payments on Orders directly through Orders and direct payments. saved payments, subscriptions, standing orders or other order methods. The Payment Information records will be a mix of reference and Credit card numbers until other purchase types are supported.

To activate reference transactions for this initial version, you will need to open the Paypal merchant account and check the value "UseReferenceTransactions" and the system will use reference transactions when you use the orders form.

Issue 10702: Order Entry – Order Cancellation Wizard: Add ProductID, Description, and Extended Columns to Grid

A client (CHA) has requested that we add the ProductID and the Extended amount as columns in the cancellation wizard's grid. CPA Community wants to see more details like Registrant, etc. so in 5.5 we should get there by adding the Description, too.

Issue 10498: Order Entry –Reduce Number of Times System Recalculates Shipping

In Aptify, depending on an organization's implementation of 5.0 Service Pack 3, the system may call the existing shipping calculation logic a significant number of times in a single save operation. Aptify 5.5 updates the shipping calculation logic to reduce the number of times the system recalculates shipping.

Issue 10307: Order Entry – 5.0: Copy Comments from Original Order to Cancellation

Prior to Aptify 5.0 SP1, a cancellation order was created by cloning the original order and then modifying field values as necessary. Beginning with 5.0 SP1 (Issue 8161), we now create the cancellation order from scratch. One of the unintended side effects is that we no longer copy the comments from the original order to the cancellation. However, in Aptify 5.5 this functionality has been implemented and now comments from the original order will flow into the cloned order.

Issue 9409: Order Entry – Support Ability to Open Order Detail/Line Form on Add

Extended Order Detail UI Add a configurable option to automatically open extended order detail forms whenever an extended product is added to an order. Further, the ability to launch a grid/UI to ease the entry of bulk orders for extended products (similar to the multi-entity grid).The scope for 5.5 will be to add functionality to the Products entity which indicates if we should open the order line form automatically when the product is added to the order. First, we should add a field to the Products entity (Product's Details > General tab) – an Open Order Line check box. When selected, the order line should open automatically. When cleared, the order line should not open automatically. We should also add the same field to the Product Categories entity (display in the top area to the right of the Active check box). Then, when a user links a product to a category, we should flow down that selection (but a user can overwrite as necessary at the product level).In addition, depending on the Product Type, the system should open a particular tab based on the product's type. This can be identified as the tab with the Extended Product Entity name from the Product Types record. (For example, when you add an Expo product to an order, the system should open the Order Lines form on the Expos tab.) One exception is for Subscriptions. If the product being added to the order has Subscription Item selected, we should default the Order Line form to the Subscriptions tab on open. 

Issue 8784: Order Entry – Remove osOrig join from the spGetUnBatchedQtyShipped stored procedure

The spGetUnBatchedQtyShipped stored procedure includes a join with osOrig that is never called. This issue is being created to remove this reference and improve optimization

Issue 6261: Order Entry – Ability to Use Product Description Field on the Order Line to Store Extended Product Info Like Meeting Attendee

In Aptify, currently when entering multiple meeting purchases in the Aptify order system a user must open each individual order line and click the Meeting tab to determine which attendee that particular line refers to. It would be helpful to view this detail without having to access each line individually. Aptify 5.5 has been updated to display a Meeting Attendee name in the Product Description field on Order Line Control.

Issue 5284: Order Entry – Order Cancellation Wizard: Programmatically Pass the OrderID into the Wizard

This feature request documents the following enhancements to the Order Cancellation Wizard functionality:

  • Provide a programmatic way to pass the OrderID into the cancellation wizard (when the cancellation wizard is called from a custom object).
  • Provide a way in the Order Cancellation wizard to recognize, and auto-populate the OrderID if being passed in programmatically.

This would be particularly useful in situations where the cancellation wizard gets launched programmatically from another area of the system. For instance, the user may want to cancel the meeting registration for a certain meeting for a certain person. Instead of having the user manually search the meeting order and type in the OrderID in the cancellation wizard, the order would be searched programmatically, the cancellation wizard would be called programmatically, the OrderID to be cancelled would be passed into the wizard, and the wizard would automatically populate the OrderID. This will eliminate a data entry step on part of the user.

Issue 10563: Fundraising Management - Contribution Payment Wizard: Pledge Cannot Be Paid with a Credit Memo

Starting with 5.0 Service Pack 2, if a user attempts to apply a payment to an open or new contribution, a credit memo cannot be used as payment, even if the person or company has a qualifying memo. For example, when a user creates a cancellation order and selects Credit Memo as the payment type, the user receives an error indicating "No records were found that match XXX", where XXX represents the order ID that was entered. Starting with Aptify 5.5, the system allows users to select and apply Credit Memo as the payment type without generating any errors.

Issue 10080: Fundraising Management – Display Additional Fields on the Rules Ranges Tab of Fundraising Campaign Match Rules Records

In Aptify 5.0, if a Fundraising Campaign Match Rule uses the Rule Table calculation type, a user creates one or more Rule Ranges records to specify how to calculate pledge matches. These rules ranges are listed on a Fundraising Campaign Match Rules record's Range Rule tab. To view additional information about the rule, a user opens the appropriate Range Rules record from within the entity list view. However, it may be difficult for a user to determine which record to view because the only columns in the ELV are Type and Comments. Aptify 5.5 has been updated to include additional fields (example exampleexample) that will help a user identify the records.

Issue 6468: Fundraising Management – 4.x Fundraising: Add "VIP" and "Show in Donor List" Options to the Contribution Payment Wizard

In earlier versions of Aptify, the Fundraising Management section options for "VIP" and "Show in Donor List" are only available on the Pledges record. Currently users are required to reopen the Pledges record after it has been created and manually modify these fields. This issue is a feature request to include check boxes to enable both "VIP" and "Show in Donor List" in the Contribution Payment Wizard to eliminate the additional step. Aptify 5.5 has been updated to include these fields as described.

Issue 9947: Meetings – Update Meeting Rooms Code to Match Best Practices

For this issue, we should:

  1. Review the MeetingRoomRooms code to abstract out the database name and base view name from the functions in the object and layout control. Currently, they point directly to vwMeetingRoomRooms and assume that the db object view is in the APTIFY database.
  2. Review the MeetingRoomRooms and Meeting Rooms code to ensure that all of the messages use Culture Strings for localization purposes rather than only be hard coded in English. Note that this is also tracked in Issue 8666: 5.0 Localization: Meeting Room Management Error Messages.

Issue 9531: Meetings – 5.0 Meetings: Improve Performance of spUpdateMeetingTotals Procedure

This issue tracks a feature request to optimize the spUpdateMeetingTotals stored procedure to improve performance. See Case 11565 for one client's approach; see the Initial Response for Robert's suggestions.

Issue 9393: Meetings – Order Meeting Detail Improvements

In Aptify 5.0 This issue is a feature request to improve access to Order Meeting Details so users can view Meeting Registration details.

Issue 6797: Meetings – Meeting Management: Show Meeting Attendee on Product Description of Order Line

Currently in Aptify, a user needs to open an Order Line form to see a meeting attendee but this important field should be visible from the top-level order (if an order contains a Meeting registration).Aptify 5.5 has been updated to include the Meeting Attendee to a Meeting Order Line's Description field (or as a new column to the Order Lines area) to help make the details easier to view.

Issue 5589: Meetings – Create Meeting Wizard That Supports Cloning Meeting Sessions When Meeting Cloned

This feature request is to provide functionality that clones a meeting's sessions (which are top-level meetings records linked via the ParentID field to the main meeting) when a Meeting is cloned.
This could be implemented as a Clone Meeting or Copy Meeting wizard. It would be particularly useful for organizations that have an annual meeting with a large number of sessions.

Issue 9542: Meetings – Meetings: Create Meeting-Specific Products Form

This issue tracks a feature request to create a meeting-specific Products form that the system will use whenever the Product Type = Meeting. This will let us redesign the Products form so it's better suited for meetings. See the attached discussion for ideas.

 

Note

This new form applies to both Meetings and Expos products. 

 

Issue 2619: Meetings – Meeting Location Tab: Phone Number Field

In earlier versions of Aptify, on a Meeting Record the Meeting Location Tab does not include a Phone Number field. Since many meetings may be tied to a specific location and users would benefit from having a contact phone number associated with a Meeting Record Aptify 5.5 has been updated to include a Phone number field on the Meeting Location's tab.

Issue 10094: Product Setup and Maintenance – Provide Infrastructure to Add New Entity Instances to Product Price Filter Rule

This issue tracks a feature request to make it easier for developers, consultants, and customers to add additional filter rule entity instances to the Product Pricing Filter Rule functionality. This involves creating a function called "AdditionalEntityInstances" that developers can override to define new entity instances for product price filter rules. The ExecutePriceFilterRule function will call the new AdditionalEntityInstances function. See the attached email for details.

Issue 9876: Product Setup and Maintenance – Populate LayoutKey for Existing Form Template Parts

This issue tracks the need to populate the LayoutKey for existing Form Template Parts in the setup program. For existing parts, it should copy the part's Name as its LayoutKey. This will retain existing functionality for any client-specific forms. In 5.5, we'll also add new Form Template Parts where the LayoutKey does not match the Form Template Part Name.

Issue 10256: Accounting – Accounting Periods: Add ParentID Field

We should add a ParentID field to Accounting Periods to create a hierarchy of periods.

Issue 9587: Accounting – Update Accounting Periods for Multi-Currency Environments

In Aptify 5.0 SP3, we added a new Accounting Periods service to provide an in-database reporting mechanism for batch information. However, the Accounting Periods functionality in 5.0 SP3 is not currency aware, so if a user links batches from multiple currency types in the same accounting period, the numbers will not aggregate properly. Aptify 5.5 has been updated with configuration changes to support Multi-Currency Environments for Accounting Periods and include accurate aggregation.

Issue 8690: Accounting – Add Check Number to the Lock Box Import Functionality

In Aptify, when importing a lock box bank file, you can specify the check number for each entry. However, in some earlier versions if you match and post a lock box entry to create a payment, the check number doesn't flow down to the Payments record. Starting with Aptify 5.5 the cash control batch functionality has been updated to make sure that the check number from the Cash Detail record is populated on the resulting payment.

Issue 8397: Accounting – New Deferred Revenue Analysis Reports

Aptify 5.5 has been updated to include two new Deferred Analysis Reports. The first is Membership Deferred Revenue Analysis, which is a pivot table based on an "As of Date", will show the user the Current Year Recognized, and Current Year Deferred and Future Year Deferred membership revenue. The second report is Advertising Deferred Revenue Analysis which is a pivot table based on an "As of Date" will display the Current Year Recognized, Current Year Deferred and Future Year Deferred advertising revenue based on that date

Issue 8396: Accounting – New Accounting Periods Service

This is a feature request to create a new service for the Accounting application called "Accounting Periods". It will be used to assist in grouping batches for the end user with GL reconciliation. This should make the accounting process easier and quicker going forward.

Issue 10808: Education – Integrate Meetings into Classes - Courses Form Updates

This issue tracks a feature request to provide meetings functionality in Classes by embedding a Meetings product into Classes (using the Extended product architecture).

Issue 10504: Education – Integrate Meetings into Classes - Courses Form Updates

This issue tracks a feature request to provide meetings functionality in Classes by embedding a Meetings product into Classes (using the Extended product architecture)

Issue 9941: Education – Meetings: Add Option to Create Certifications Rather than Education Units

In earlier versions of Aptify, we added the ability to generate Education Units records for meeting attendance. This automates the process of awarding continuing education (CEs or CEUs) to members who attend meetings. The implementation of this functionality is entirely within the core Aptify business applications, but if a client is using the Education Management add-on, they will be tracking CEs/certifications in two places if they want to use this automated feature (tracking some CEs in Certifications and others in Education Units). This diminishes the value of the Education Management add-on (not having everything centralized in one location). Beginning with Aptify 5.5 the configuration for this feature has been updated to add an Entity attribute to determine if the system should create Education Units or Certifications records when a person's meeting attendee status is flipped to Attended.

Issue 5671: Filter Rules: Support Extended Product Entities in Pricing Filter Rules

In Aptify, the Filter Rules tab of the Product Price record can be used to set conditions on when a price should be invoked. The current functionality does not support Extended Product Type and Extended Order Detail Product Type entities. This will be helpful to configure prices based on options selected for extended products. For example: for an Expo product, prices could be set based on options including water, air, decorated, etc. Aptify 5.5 has been updated to allow users to set additional options for Extended Product Entities.

Issue 8417: Subscriptions and Membership: Ability to Set a Default Value for the Dues Membership Field on a Persons Record

In Aptify 4.5 the settings on the Memberships Tab of a Persons Record include a drop-down box for the Dues Information. The current functionality does not support a default value for this particular field that can be specified. In Aptify 5.5 this attribute will be updated to allow a default value to be specified and automatically applied.

Issue 10274: Reporting: Sales Force Automation: Sales Funnel Report

Aptify 5.5 adds the Sales Funnel report to the sample reports. This report provides information on the sales currently in the pipeline.

Issue 10650: ExpoCAD: Push More Exhibitor Information from Aptify to ExpoCAD

This issue tracks a feature request to push more company information from Aptify into ExpoCAD when placing an order for a booth. Currently, we add the Exhibitor company name but no other details. Clients want us to synchronize more data, including: exhibitor addresses, phone numbers, fax number, company website, email address, and Product codes (from Company entity).

We need to review the ExpoCAD API to determine how much of this is possible. Also, if an exhibitor already exists in ExpoCAD, we should be linking/updating that existing information rather than adding new information.

User Resolved Issues (Aptify Framework)

The following Aptify Framework related issues have been resolved in Aptify 5.5:

Issue 10960: Aptify Framework – Update Aptify Strongly-typed Entity object Generator (GESubClassGenerator) to support all Entity Field Data Types

Previously in Aptify ……. Starting with Aptify 5.5 the Strongly-typed Entity object (GE Subclass) generator has been updated to support the latest Entity Field SQL Data Types, including float, smalldatetime, date, time, varbinary, varbinary(max), image and uniqueidentifier. In addition it's been updated to support: Nullable data types when the Entity Field's Allow Null flag (SQLAllowNull) is true.

Issue 10926: Aptify Framework – Excel Export: Improvements

In earlier versions of Aptify the Excel Export with "Use Display Names" function does not handle all situations, in particular Advanced SQL with complicated SELECT clauses. Another related issue is the Export with Copy Data option sometimes fails when fields contain large text values and the Columns Widths should be set based on the contents and Column headings should be bold and centered. In Aptify 5.5 all of the following Export to Excel functions have been updated.

Issue 10791: Aptify Framework – Hierarchy Control: Improvements to the Details Functionality

In Aptify the Hierarchy control is currently configured at a fixed page size of 1000 records. Due to the larger size the page may take longer to load than necessary. To provide better performance, the configuration of this feature has been updated to reduce the Page Size default to 100 records, reducing the amount of data that comes across for the first page of the Details view. In addition Aptify 5.5 has also been updated to make the Page Size of the Details List View configurable and includes an Input Property to the Hierarchy Browser Form Component that allows the Form Template Designer to specify a Page Size.

Issue 10774: Aptify Framework – 5.5: The SubType control does not display Images for varbinary(max) fields

When a user attempts to add a subtype records that contains a Varbinary(max) fields, the grid does not display the images.

Issue 10753: Aptify Framework – Strongly Typed Entity Sub-Class Generator Incompatibilities when run on Computers with .NET 4.0 installed

The Strongly Typed Entity Sub-Class Generator builds assemblies that are incompatible with .NET 2.0/.NET 3.5 processes like the Aptify Smart Client. (See Error Log for an example of the error that occurs when the Smart Client attempts to load the generated assembly. The GESubClassCompiler should be updated to use the latest version of .NET up to version 3.5. The workaround for this is to execute the Strongly Typed Entity Sub-Class Generator on a computer that doesn't have .NET 4 or later installed.

Issue 10729: Aptify Framework – Cannot Select Different Color Schemes With Office 2010

With Aptify 5.0 users have the ability to change the color of their Aptify desktop by changing the scheme in Office 2007. However, this feature does not work correctly with Office 2010. For those users who have Office 2010, changes to the default color scheme will not transfer or apply in Aptify. Starting with Aptify 5.5 color scheme settings selected in Office 2010 will be mirrored in Aptify.

Issue 10721: Aptify Framework – Database Optimization: ViewSorts Entity's Base Table (ViewSorts) Needs an Index on ViewID, Sequence

The ViewSorts Entity is missing an Index on its ParentLinkedField (ViewID) and Sequence.

Issue 10720: Aptify Framework – Database Optimization: Add Index to Entities.ParentID field

Add an Index to the ParentID field in the Entities Entity (Entity table)

Issue 10706: Aptify Framework – Handle Characters in Entity Field Names Supported by Smart Client but Not Supported by AWA

There are certain characters that the Aptify Smart Client and SQL Server support in an Entity Field Name that are not supported by AWA. For example, the Smart Client and SQL Server support using a dash in the field name (such as "PersonID-Name") but C# considers this an invalid Property Name. So, the model fails to generate for entities that has dashes in field names for AWA.
This issue tracks the need to identify the characters that are allowed by SQL Server but would cause a problem with AWA (including the dash characters). The Entity can be updated to warn when one of those characters is used. We should also update the Entity Model generator to detect Entities that have these invalid configurations and explain that they can't be included in the model.
--This was identified on a RAD Prospect test environment. 

Issue 10705: Aptify Framework – Entity Redirect Viewer PlugIn for Virtual Entity Fails to Load Proper Record when DisplayFormRedirectIDField is ID

In earlier versions of Aptify the Entity Redirect Viewer PlugIn for Virtual Entities is not correctly processing the DisplayFormRedirectIdField Entity Attribute when the Attribute's value is ID. Currently this means that it always results in a new record for the Redirect Entity rather than using the value of the ID field to load the Entity Record. Aptify 5.5 updates the code to has been updated to use DisplayFormRedirectIDField attribute with ID as the value and the record is now opened in the service specified.

Issue 10604: Aptify Framework – Add Encryption Support for nvarchar(max)

When the Encrypt Data flag is turned on for an Entity Field, validation prevents the EntityField from being saved, stating that you cannot encrypt a field with a DataType of nvarchar(max). Encryption should be available on nvarchar(max) fields.

Issue 10521: Aptify Framework – Message Action Create Contact Log Should Link to Message Run

The contact log that the system creates for a message should link to the Message Run in addition to the person. Also, we should add a tab to Message Runs that shows the contact logs/messages associated with that run.

Issue 10440: Aptify Framework – Unable to Export Reports Using the HTML Formats

In Aptify, a user can export a client-specific report by selecting a format type from the drop-down list within the Crystal Reports viewer. However, with 5.0 Service Pack 3 and earlier, when selecting either the HTML 3.2 or HTML 4.0 formats, an error is displayed and the export is unsuccessful. Aptify 5.5 configuration has been updated to export reports in the HTML format without incident.

Issue 10322: Aptify Framework – Messaging Functionality Should Fail if Message Template Includes a Part Error

Currently in Aptify, if a user selects a Message Template tied to a Message Part that includes invalid data, the e-mail will still be sent out. In Aptify 5.5 if a message part includes invalid data an error will display and the Aptify exception log will be updated.

Issue 10277: Aptify Framework – Alert Types Forms Update

There are a couple of updates I think we should make to the Alert Types form:

  • The Display Alert On Load field should be a check box.
  • The Source Script tab should use the Script control.

On a related topic, why does the script logic use "[GE.ID]" as the variable and not "<%ID%>" like elsewhere in the system? If nothing else, we need to clarify in the documentation how writing an alert script differs in this way from other areas of Aptify and provide an explanation for the difference.

Issue 10230: Aptify Framework – GE Transaction Error When Saving a Meeting

In Aptify, there is a situation where saving a Meeting record multiple times while the form is open can result in a transaction error creating multiple open transactions. For example, when adding a new phone number field to a Meetings Record, if you enter a phone number, save the meeting, and then enter an extension phone, a transaction mismatch occurs since there are multiple transactions open. Aptify 5.5 has been updated to address this issue and allow you to save a Meeting Record multiple times without generating any mismatches or issues.

Issue 10196: Aptify Framework – Chart View with Secondary Grouping May Generate an Error

In Aptify, One of the clients at the conference was asking how to create a chart that compared monthly progress over multiple years. Something like what have the sales looked like each January for the last four years.** I have attached additional documentation created by Cathy. This can be used to help test the current behavior. See the attachment tab for details. **We should be able to create a chart like that using 2 levels of grouping. But, when I try to set it up, the system is not loading the chart. See attached email thread for setup of primary grouping on OrderDate (function Month) and secondary grouping on OrderDate (function Year).The advanced SQL the system generates is correct and shows the data I want to see in SQL Management Studio (note I have a filter too that filters out records before 2007).

Issue 10177 Aptify Framework – Proximity Filter Error Message is displaying twice when click on 'Show Advanced' link

In Aptify the Proximity Filter Error Message is displaying twice when a user clicks on the 'Show Advanced' link. For example, when a user is attempting to create a view under the Persons Service and selects 'Show Advanced' the error will display twice. In Aptify 5.5 the error message will only display one time.

Issue 10116: Aptify Framework – Melissa Data Update Does Not Remove Address Information Correctly

In Issue 9521, a fix was introduced so that the suite information wouldn't be removed by a Melissa Data update. However, a side-effect was produced in that if line one include the suite name and line 2 also had something that could be changed (using the word "Lane" instead of "Ln" for example), the second address line would hold the current information.

Issue 10082: Aptify Framework – Generic Import: Do Not Attempt to Update Records by Match Fields

In 5.0 SP2, we added the ability to identify fields to use as a match requirement. This is a great feature to identify matches and to update existing records. However, when I try to update an existing record, it doesn't work seamlessly so we should address that.

Issue 10046 Aptify Framework – Grid Does Not Include Scroll Bar on First Load of Form Template

In earlier versions of Aptify users have experienced issues with the sub-entity grid not loading properly. For example, users may find that in the Contact Log of a Companies record when there are more records than what can be displayed in the existing viewable area that no scroll bar is available and they are forced to save and reload the form in order to scroll and view all of the records. Aptify 5.5 includes changes to the existing configuration to ensure that the scroll bar is available the first time the form is loaded.

Issue 10045 Aptify Framework – AptifyDataControl's UserCredential Property Includes Broken Code

In the AptifyDataControl's UserCredential property there is the following line of code which is clearly broken: If (Me.m_oFormTemplateContext Is Nothing) AndAlso (Me.m_oFormTemplateContext.GE Is Nothing) ThenI think they wanted AndAlso to be OrElse. In the current code, if m_oFormTemplateContext is ever nothing then an exception will be thrown.

Issue 10009 Aptify Framework – Database Object Cannot Be Saved and Produces Error Upon Modifying SQL

In Aptify, when an Admin User modifies a Database Object and enters an invalid SQL statement, while saving the Database Object an error is produced. This behavior is expected, however even after correcting the SQL statement, the error does not go away. The error will disappear if you close the Database Object and reopen. Beginning with Aptify 5.5 the configuration for this behavior has been updated and the error will disappear as expected when the SQL statement has been corrected.

Issue 10008: Viewing System – Improve Proximity Filter Error Message

Starting with 5.0 Service Pack 3, if a user adds a proximity filter to a view without specifying a country and postal code, an error message is displayed when attempting to close the View Properties dialog. This alerts the user that a proximity filter values must be defined before the view is run successfully. (See "Issue 9183: Error Displayed If Proximity Search Operator Is Selected Without Specifying Postal Code Value" in the Aptify 5.0 Service Pack 3 Release Notes for detail.) However, the error message displayed is not specific and it may not be obvious to the user what error has occurred. Starting with Aptify 5.5, the system displays a more specific message so that the user is aware that the proximity filter values must be defined.

Issue 9964 Aptify Framework – GDI+ Memory Handles: Memory Utilization Increases During Data Processing

Note that Issue 10409 has been created as the parent of this issue for tracking purposes. All cases linked to this issue are now linked to the parent.** Orders are being process one-after-another, some with 1 line item, but other orders have multiple lines (50 or more). These orders are created through an order entry wizard that written by Aptify (support/consultant).

Issue 9961 Aptify Framework – Address Control - Country Drop Down while scrolling, you see the Address Markup for Formatting

In earlier versions of Aptify when a user selects the Country drop-down menu and scrolls to the US, the Address Markup for formatting displays. However this column should not be shown in this dropdown. For example, if a user creates a new Companies Record and selects the US the display columns are not showing properly. Starting with Aptify 5.5 the display will include only the relevant default fields.

Issue 9930 Aptify Framework – Topic Codes: Do Not Display As Hyperlink If No Child Codes

In earlier versions of Aptify, the Topic Codes Form component displays every Topic Code as a hyperlink, even if clicking on the link reveals that there are no child entries for that link. Aptify 5.5 has been updated to modify this functionality to only display a Topic Code as a hyperlink if the Topic Code is a parent for another Topic Code.

Issue 9918 Aptify Framework – Form Template Copy Wizard Copies Parts Incorrectly When There are Top Level Templates With the Same Name

In Aptify, when an Admin user attempts to use the Form Template Copy Wizard by using the Top Level Form template that has multiple records with the same name in the system, then it copies the Parts incorrectly under PartList of the created Form Template. For example, when running the Form template copy wizard with the Top Level Form template as "Persons.Orders" that has 2 records with the same name in the system, the generated Form template does not show the correct Part list. Rather than copying over all the parts (TotalField, BalanceField, and Tab Part) it is only copying over the orders ELV. Aptify 5.5 has been updated to correctly copy Parts.

Issue 9884: Aptify Framework – TopicCodeLinks uses same Base View as TopicCodeLinkage

In Aptify, when a company is specified on a new Persons record, the system automatically populates the person's Business Address, Billing Address, Phone, and Fax with the corresponding information from the Companies record. However, with Aptify 5.0 Service 3 and earlier, if an existing company record (one that has already been saved) is updated with new phone/fax data, the new phone information does not flown down to applicable Persons records. Starting with Aptify 5.5, when a company's phone number information is modify, the changes flow down to all applicable Persons records as expected.

Issue 9877: Aptify Framework – Remove Puerto Rico as a Country Selection in Aptify

In Aptify 5.0 Service Pack 2 Puerto Rico is currently available as an option under both Country and State. For example if you open a new Persons record and select the State drop-down field you will notice that Puerto Rico is available as an option here, in addition Puerto Rico is also listed in the drop-down list for Country. In Aptify 5.5 Puerto Rico will only be available as a State selection to provide consistency with US Mail representation.

Issue 9855: Aptify Framework – Disabled Fields Designed as Link Boxes May Become Enabled When Switching Between Tabs

With Aptify 5.0 Service Pack 3 and earlier, if an entity has field level security enabled so that a user has read-only access to certain fields, fields that are designed as link boxes may become enabled when the user switches between tabs on that form. Note that since the user only has read permission, any changes to these fields are not saved. However, since the fields are enabled on the form, it gives the impression that a user can change these field values. Starting with Aptify 5.5, when a user has read-only access to a link box, the field remains disabled, even when switching between tabs on a form.

Issue 9806 Aptify Framework – Opening Multiple Records May Produce Bit Map or GDI+ Errors

With Aptify, when processing a large number of records that rely heavily on Aptify windows controls (for example, creating orders through a wizard), memory utilization may exceed the available memory on the local system and the application generates an error. In addition, if a user opens a large number of forms (15 plus) without closes them, a user may receive either a Bit Map or GDI+ error. Aptify 5.5 will update Aptify's Windows, Address, Entity, Form Template and Order controls to share images for certain Aptify controls, such as AptifyLinkBox and AptifyTextBox, to reduce memory usage and correct this issue.

Issue 9805: Aptify Framework – Notes Indicator Functionality May Not Work as Expected

With Aptify, once a record has one or more notes associated with it, the Notes icon will indicate that there are notes attached to the record (the Notes icon becomes yellow and displays a pop-up message that indicates how many notes are attached). However, with Aptify 5.0 Service Pack 3 and earlier, there are situations where the Notes indicator may not work as expected due to an incorrect count of the number of notes associated with a record. For example, the Notes icon may become white for a record, even when notes are associated with it. Starting with 5.5, Aptify updates the Notes functionality so that the Notes icon correctly indicates when notes are attached to a record.

Issue 9742 Aptify Framework – Require Comments for Each Save functionality implemented in the GE should be aware of and respect the AllowGUI parameter passed in

The Require Comments for Each Save functionality that is implemented in the Generic Entity should be aware of and respect the AllowGUI parameter passed in to the Save method. When it is set to false, the GE should not attempt to display the Comments dialog and, if Comments haven't been provided programmatically, the Save should report a failure.

Issue 9725: Aptify Framework – Bulk Messaging: Show Error Message If No Records Returned

In Aptify, if you open the bulk messaging dialog and no records are returned, the dialog acts as normal. Unless a user checks the session exception viewer or the Message Run, they have no way of knowing that a message was not sent. These details are particularly important for distribution of a bulk email from a specific record, like a Persons record. If the record is filtered out by the message source, then the user will not receive a notification that nothing was sent. In Aptify 5.5 a message will appear when the Bulk Messaging dialog loads to indicate that no records qualified for the Bulk Messaging run and to check the Message Source settings. This message now appears instead of the bulk messaging dialog

Issue 9675: Viewing System – Pie Charts Should Sort Numeric Fields in a Clockwise Direction

With Aptify 5.0 Service Pack 2 and earlier, when a Chart view's axis contains numerical values, the items may not be sorted correctly due to the improper use of a character-based sort. Aptify 5.0 Service Pack 3 resolved this issue by using numerical sorting on number-based values (see "Issue 9567: Viewing System – Chart Views: Multiple Issues Resolved" in the Aptify 5.0 Service Pack 3 Release Notes for details). However, the values are sorted in a counterclockwise direction rather than of clockwise direction as expected. Aptify 5.5 resolves this issue

Issue 9547: Messaging: Message Action Prompt Appears even when There is No Message Action on the Template

In earlier versions of Aptify, when a user loads a message template through Aptify Messaging Wizard, they receive the following message: "Do you want to delete the existing actions and copy the actions associated with the selected message template?" The issue is that it still prompts even though there is no message action on the Message Template or on the Current Message Wizard. Beginning with Aptify 5.5 changes have been made to generate the error, only when changes have been made.

Issue 9262: Standard Reports Should Not Create a List

Currently in Aptify, the underlying technology we use when integrating Aptify with Crystal Reports creates a scenario where the application runs slower than expected. For example when a user executes reports it create lists of data that the report is supposed to access to derive the data that it displays. Aptify also supports a report type where it do not expect the report to look at the list. In that case the system should not generate the list. This is causing the time taken prior to opening the report.

Issue 9162 Aptify Framework – Scheduled Tasks properties stored in Parameter String incorrectly

The scheduled tasks entity is storing the parameter string incorrectly for message schedule records. The parameter string is being stored as [PropertyName] ([Data Type]) instead of just [Property Name]. The resulting error is that the application server indicates that MessageScheduleID is a required property.

Issue 8728: Aptify Framework – Message Run Failure When Multiple Records Selected in a View

In earlier versions of Aptify, if a user manually selects multiple records in a view, generally 75 or more, and runs the messaging tool they receive an error that the ID String must be 255 or fewer characters. Starting with Aptify 5.5, when a user selects records in multiples of 75 or more they will no longer receive an error and the message will complete successfully.

Issue 8710: Address Management – Phone/Fax Data Does Not Flow Down to a Persons Record If Company Previously Saved

In Aptify, when a company is specified on a new Persons record, the system automatically populates the person's Business Address, Billing Address, Phone, and Fax with the corresponding information from the Companies record. However, with Aptify 5.0 Service 3 and earlier, if an existing company record (one that has already been saved) is updated with new phone/fax data, the new phone information does not flown down to applicable Persons records. Starting with Aptify 5.5, when a company's phone number information is modify, the changes flow down to all applicable Persons records as expected.

Issue 8653: Aptify Framework – Form Template Parts Disabled by a Layout Control Are Incorrectly Enabled When Adding a New Tab to a Form

In Aptify, a developer can add modify the behavior of a form by writing a layout control. For example, a developer can write a layout control to disabled certain form template parts on a form, such as the Total and Balance fields on the Orders form. However, with Aptify 5.0 Service Pack 3 and earlier, when a new tab part is added to a tab sub-template on a form that includes a layout control that disables certain fields (for example, when adding a part to the Summary area of the Orders form), fields that should be disabled by the layout control may become enabled. Starting with 5.5, Aptify update the form template control functionality to make sure that fields that are disabled by a layout control remain disabled when adding a new tab part.

Issue 8589: Aptify Framework – Telephone Code Data in the Country Table is Incorrect or Missing

In Aptify, the telephone code field in the dbo.country table is not displaying the correct information. Currently the Countries data in the Telephone Code column shows some information but the majority is incomplete or inaccurate and only a few records contain the correct values. Beginning with Aptify 5.5, the system will be updated to display the correct telephone codes. 
(Issue 11025) In Aptify, there are numerous countries listed that are not associated with a continent.In addition countries that no longer exist need to be removed or labeled as defunct. For example, Yugoslavia is still listed and Serbia does not include Europe as a continent.

User Resolved Issues (Core Business Applications)


The following Aptify Core Business Application related issues have been resolved in Aptify 5.5:


Issue 10724 Order Entry – Payment Type on Orders Not Refreshed in Certain Cases when Organization Is Changed

In Aptify, when modifying Payment Types users have experienced issues with Orders not refreshing when certain changes or updates are made to the Organization record. Specifically if changes are made to the Payment Types service by associating a payment type with an individual Organization record and an order is generated the Payment Type association is not appearing properly. Beginning with Aptify 5.5 the configuration has been updated to allow this functionality to update correctly when Payment Types are associated with Organizations.

Issue 10722 Order Entry – 5.5: Disable Clearing of PO Number in Payment Information Control

In Aptify, performing an action that refreshes the payment type on an Orders form clears nearly all other payment related fields. For example, when a Bill to party is added to an order, the Payment Type is refreshed based on the Bill To party's last payment type and any default payment data is removed. This is appropriate when dealing with credit cards, but prevents an organization from setting a default PO Number. Aptify 5.5 updates the Payment Information control to disable the clearing of payment information for PO Number payment types so that an organization can set a default PO Number as needed.

Issue 10493 Order Entry – Standing Order Fulfillment Wizard Does Not Work with Prompt Views

With Aptify 5.0 Service Pack 3, running the Standing Order Fulfillment wizard from a prompted view fails and may cause the system to become unresponsive. Aptify 5.5 updates the Standing Order Fulfillment wizard functionality so that the wizard executes successfully from a prompted view.

Issue 10340 Order Entry – Payments: Organization and Payment Types Not Updated on Employee Change

When a user changes the Employee on a Payments record, the Organization should also update to match the newly specified Employee's organization link, and the available Payment Types in the Payment Info Control (on the Details tab) should also update to show the applicable Payment Types based on the new organization and defined Payment Type Organization Filters. This sometimes works fine on an Orders record, but not currently on a Payments record.

Issue 10190: Order Entry – Exhibitor added by user disappears when toggling between General and Expo Tab in Order Line Record

In Aptify Order Entry when a user is toggling between the General and Expo Tabs in an Order Line Record any Exhibitor added by a user disappears. The user is required to re-add the Exhibitor name to save the Order Line Record. Aptify 5.5 corrects this issue and retains the Exhibitor name when users toggle between tabs.

Issue 10189: Order Entry – Object reference Error Appears When Replacing Booth with the Same Booth Name in Order Line Record

In earlier versions of Aptify, in the Order Entry service when a user attempts to update the Booth field with a previously used Booth Name an Object Reference Error appears. For example, in an Order Record that contains an Expo, when a user selects the expo tab and clears the booth field and then attempts to select the same name that was just removed, clicking OK generates an error. Aptify 5.5 corrects this issue and allows users to updating using the same Booth Name without generating an error.

Issue 10184: Order Entry – Form Template Error on Toggling Between General and Expo Tab on Order Detail Form.

In earlier versions of Aptify, in the Order Entry service if a user has a New Order record open and attempts to toggle between the General and Expo Tabs on the form they encounter an error. Starting with 5.5, Aptify this error will no longer appear and users can toggle between tabs without incident.

Issue 10095: Order Entry – Using Restricted Countries Functionality Generates an Error

In Aptify, organizations can define a list of Restricted Countries to which Orders cannot be shipped. The Orders entity has a function that can check for this condition during the order save process. However, when you enable it on certain versions of Aptify it generates an error. The configuration for Aptify 5.5 has been updated to correct this issue and allow users to define Restricted Countries without generating an error.

Issue 10048: Order Entry – Incorrect Description For Kit Group Products in The Order Line

In Aptify, when placing an order for a Kit Group Product the incorrect description is displayed for the very last order line. The description that is displayed is taken from the original product instead of the sub product. Aptify 5.5 has been updated to address this issue and correctly display the description.

Issue 10028: Order Entry – Localization: Bulk Write Off/Refund Wizard Produces Error Upon Processing as a Localized User

In Aptify 5.0 Service Pack 2, when a localized user attempts to run the Bulk Write off/Refund Wizard from the Orders View that has some order records without balance, an error is produced. In addition when the user clicks "OK" on the error message the wizard remains open and forces the user to "Cancel" to force the wizard to close.

Issue 9892: Order Entry – Order Cancellation Wizard: Error Generated When Cancellation Fee Is Specified As Text

When using the Aptify Order Cancellation wizard, if your organization charges a cancellation fee on a per order basis, an order taker selects the appropriate cancellation fee product from the Product drop-down and then specifies the amount of the fee. With 5.0 Service Pack 3 and earlier, when an order taker specifics the fee as a text value (for example, ten dollars), an error is generated. This is expected since the fee must be specified in a numerical format, however, the error message that is displayed is not specific to this issue and it may not be obvious to the user what error has occurred. Starting with Aptify 5.5, when a non-numeric value is specified in the Fee field for a cancellation product, tabbing out of the field automatically sets the field's value to zero (for example, $0.00). If the order taker attempts to continue to the next step of the Order Cancellation wizard without specifying a positive amount, the system displays a message alerting the order taker that a value greater than zero must be entered.

Issue 9891: Order Entry – Order Cancellation Wizard: Add Label to the Cancellation Fee Amount Field

When using the Aptify Order Cancellation wizard, if your organization charges a cancellation fee on a per order basis, an order taker selects the appropriate cancellation fee product from the Product drop-down and then specifies the amount of the fee in the field below the drop-down. However, with 5.0 Service Pack 3 and earlier, the field in which the amount is entered is not labeled. Starting with 5.5, Aptify updates the display name of this field to Fee to better identify the use of this field.

Issue 9879: Order Entry – Product Prerequisites: Do Not Validate Shipped Orders

As of 5.0 SP3, Aptify validates the product prerequisites associated with an order each time the order is saved. However, this check shouldn't occur for shipped orders. After an order ships, typically a user doesn't make any changes. While a few changes are possible (update comments, assigned Batch ID), these actions should not invoke a prerequisites check. If an organization changes a product's prerequisites between the time the order shipped and the order was batched, the batch process may fail if the order does not satisfy the new prerequisites. In Aptify 5.5 the product prerequisite check for shipped orders has been updated to prevent any issues or failures in orders regardless of shipping status.

Issue 9878: Order Entry – Order May Fail to Ship Due to GL Rounding Issue

With earlier versions of Aptify, in certain cases, an order may fail to ship due to a rounding error when creating an Order's GL Entries. Situations where this can occur include ordering decimal quantities that extend beyond 2 digits (such as .0833) or when calculating order line amounts when the stated price includes tax. The configuration for Aptify 5.5 has been updated to reduce the occurrence of rounding errors and forces the Extended order line amount to use the number of decimal places defined for the order's specific currency.

Issue 9515: Order Entry – Duplicate Order GL Entries and Scheduled Transactions for same order when 2 different users attempt to ship at the same time

In Aptify 5.0, when two different users open the same order in Taken status, click shipped, and save at the same time the system creates two sets of GL entries and two sets of scheduled transactions. Aptify 5.5 has been updated to correct this issue and allows two different users to ship the same order without creating duplicate entries.

Issue 9266: Order Entry – Error Message Is Not Displayed When Saving an Order after Deleting All Order Lines

With Aptify, when a user attempts to save an order after deleting all order lines, an error message should be displayed alerting the user that at least one order must be included on the order. However, with 5.0 Service Pack 3 and earlier, no such message is displayed; instead two silent errors are generated and it may not be obvious to the user which error has occurred. Starting with Aptify 5.5, when a user attempts to save an order after deleting the last remaining order line, the system displays a message alerting the user that at least one order line must be added to the order before the order can be saved successfully.

Issue 9157 Order Entry – spGetUnBatchedQtyShipped: Why does unbatched quantity shipped include Taken cancellation orders?

The stored procedure spGetUnBatchedQtyShipped is used to update inventory levels in spUpdateInvLocCount. 
spUnbatchedQuantityShipped calculates unbatched quantity shipped as the sum of:

  • Sum of positive order line quantities for Shipped Regular Orders
  • Sum of positive order line quantities for Shipped Cancellation Orders
  • Sum of negative order line quantities for Taken and Shipped Cancellation Orders

Why are negative order lines for Taken cancellation orders included in this calculation? I assume that this is done intentionally because the stored procedure explicitly treats negative and positive cancellation order lines different.

Issue 9188 Order Entry – Order lines deleted from a saved order reappearing in specific scenarios

8/17/10 Andrew Crispino: I've moved this to Management Review. We may decide to not include in 5.5. From the analysis done previously: Chandra spent some time on this Issue yesterday and Created a Demo Code to Debug this functionality. He found a bug in the GE. At this time we do not have a resolution. But this affects all SubTypes Records in the same manner. Also the Fix may not be easy since it will affect the entire Application.

Issue 8528 Order Entry – Cash Control Field is Disabled on Quotation Orders

In Aptify 5.0, when a quotation order is created, the Cash Control Field is currently disabled. For example if a user runs the Subscription Renewal Wizard and then locations the quotation record that was created under the Orders service, the payment tab shows the Cash Control field as disabled. Starting with Aptify 5.5 a user will be able to access and complete this field.

Issue 7288 Order Entry – Bank Branch Is Not Carried Over for ACH Payment Type

In Aptify, not all applicable data relating to Automated Clearing House (ACH) payment type is being carried over on to a new Order Record. For example, the information regarding the Bank Branch is not part of the data that is carried over. Beginning with Aptify 5.5 this data will flow down to a new Order record.

Issue 10295: Product Setup and Maintenance – Prevent Product from Being Its Own Parent

In Aptify 5.0 Service Pack 3 the Product form template's ParentID link box includes a hidden filter so you can't make a product its own parent but we add object level validation for this as well. There have been a couple of recent cases of clients who have upgraded to 5.0 where it appears that having products as their own parent has caused performance problems. Aptify 5.5 has been modified to provide an error message when a user attempts to add a product to its own parent.

Issue 9816: Product Setup and Maintenance – New Approach for Handling Linked Fields

During testing of Aptify 5.0 Service Pack 3, a production LCI db was used to verify the setup and it failed due to no Currency Types record existing with an ID of two. A temporary fix was put in place to remove all fields from the adb file which requires Default Currency type and Organization. Now they are created manually through code using users functional default value. This issue has been created to implement a new approach of handling linked fields. It will introduce new columns in adb which will give information about the linked Entity and linked ID (believed to be RecordName). While adding fields automatically it can use this information to fetch the correct ID from users. In Aptify 5.5 both the Generator and Installer code has been updated to support Default Value of Linked Entity Field

Issue 10828: Accounting – Account Manager Transfer Wizard Process Component bug

While debugging some odd behavior with the Account Manager Transfer Wizard in AWA, I found that the GetCompanyIDs method in the process component is incorrectly using a datareader, and also has a bug in how the sql statement is constructed. All use of DataReaders in this process component need to be replaced.

Issue 10677: Accounting – Cash Control Batches: Show "No Balance" Label when Total Is Zero

In Aptify, if an amount from a lock box is completely allocated to payments, the final amount in the total grid on the right side of the Cash Detail form says "Overpayment" even though the displayed amount is $0.00. Beginning with Aptify 5.5 when the total is zero a "No Balance" indicator will be displayed.

Issue 10676: Accounting – Cash Control Batches: Lock Box Overpayment Allocate - New Order Not Functioning

In Aptify 5.0 Service Pack 3 when a user selects the Allocate Over Payment option, one or more errors appear and the new order is not created. For example, when a user attempts to apply an order overpayment to a new order after clicking OK one or more exceptions are displayed. In Aptify 5.5 the Accounting code has been updated to support the Allocate Over Payment option.

Issue 10561: Accounting – Cash Control Batches: Remove Post Record Button

The Cash Detail form has a Post Record button, which is typically disabled, and when enabled (after clicking the Allocate Overpayment option and switching back to the General tab), doesn't do anything. There's nothing behind that click event. So for now, we should remove it from the form. There is a separate issue (10576: Cash Control Batches: Add Post Record Button with Functionality to Cash Detail Form) to add it back with supported functionality behind it.

Issue 10443: Accounting – Expand Check Number Field on a Cash Detail Record

In earlier versions of Aptify the Check Number field will only display 14 characters on a Cash Detail record. In certain instances that mean that the user will not be able to view all of the check number details at one time. In Aptify 5.5 this issue has been corrected to allow all 20 characters can be shown to the user.

Issue 10436: Accounting – Overflow Error When Saving Cash Control Batch Records

In Aptify 5.0 Service Pack 3, if a user puts a large dollar amount into a Cash Control Batch Record, it will flow with an overflow error. In addition, when this occurs previously deleted rows may be added back to the record. For example if a user with an "accounting" user is logged in to Aptify and creates a new record under the Cash Control batches service with a large dollar amount, once the user attempts to add the record and error is generated. In Aptify 5.5 the code has been updated to correct these errors.

Issue 10417: Accounting – Cash Control Batches: Refund Payments Created by Post Process Displayed Later as Prior Payments in Cash Detail Record

In Aptify, after using the Lock Box wizard to import an overpayment (when the payment covers more than the full amount of the corresponding order), the record is marked as an Exception of Type Overpayment as expected. If a user opens the Cash Detail record and selects the Post + Refund Overpayment option, a refund is created in an amount that is above and beyond the order's balance. When a user opens the Cash Detail record again, the Payments record associated with the refund is populated in the Refund Payment ID field as expected. The same amount is also populated in the Prior Payment field. However, this can be confusing to a user because this payment was not made prior but as a result of the posting process. Beginning with Aptify 5.5, refund payments prior to the post will be displayed as a separate line so that refunds can be easily distinguishable from prior payments.

Issue 10416: Accounting – Cash Control Batches: Options Specific to Overpayments Should Not Be Available for Underpayments

In Aptify 5.0 Service Pack 2, when the Lock Box wizard imports an underpayment (that is the payment does not cover the full amount of the corresponding order), the record is marked as an Exception of Type Underpayment as expected. However, when the user selects the payment in the Cash Control Batches record to view the Cash Detail record, options related to the handling of overpayments are available and can be applied by a user when not appropriate. For example, the Post and Refund Overpayment option is available, even though there is no amount to refund. When this option is selected for an underpayment, a new Payments record for a "reverse refund" is created to pay off the order balance, which is incorrect. In Aptify 5.5 the code has been update to correctly display the details for Underpayment and the associated options.

Issue 10415: Accounting – Cash Control Batches: Imported Payments Displays Underpayments as Overpayments in the Cash Detail Record

Currently in Aptify, when the Lock Box wizard imports an underpayment (that is the payment does not cover the full amount of the corresponding order), the record is marked as an Exception of Type Underpayment as expected. However, when the user selects the payment in the Cash Control Batches record to view the Cash Detail record, the details are displayed as an "Overpayment". Aptify 5.5 corrects this issue to properly display underpayments with the accurate designations.

Issue 10066: Accounting – Error when saving Product Cost Detail record when Date Finalized Field is Null

Currently in Aptify, in the Product Cost Detail:Aptify will not allow the record to save if the Status has been changed to "Approved" and the Data Finalized is blank - no message is displayed to the user. (Will this be updated to allow users to save without a date or will the "today's date" populate automatically?

Issue 8133: Accounting – Lockbox Cash Control Batches Create Payments for Cancelled Quotation Orders

Currently in Aptify, when Cash Control Batches are matched and posted for orders that are cancelled, they currently do not fail or inform the end user that they are in that state. GL entries are not being created when this occurs which makes them difficult to track down. Aptify 5.5 has been updated to provide a warning to the user when this situation is going to occur.

Issue 10684: Subscription Management – Multiple Order Lines for Same Product Creates Only a 1-Year Subscription

With Aptify 5.0 SP3, if you create an order with two or more lines for the same subscription product, the order module will only create a subscription for a single year using the last order line. For example, if you add an individual membership as two order lines with a quantity of one (rather than one order with a quantity of two), the system creates a 12-issue, 1-year subscription rather than the intended 24-issue, 2-year subscription. In Aptify 5.5, subscriptions with two line items for the same product will create a subscription of appropriate length and populate the date range and other details correctly.

Issue 10086: Subscription Management – Subscription Fulfillment: Fax Export Does Not Work

With earlier versions of Aptify, if you create a Subscription Product with Distribution Type set to Fax, when you fulfill subscriptions for that product, the Fax export option is enabled. You can specify a location for the export file and clicking the Fax button launches the export, but the export operation currently fails

Issue 8926: Subscription Management – Monthly Subscription/Membership Product Table Contains Incorrect Calculation in the Help Files

When ordering a product, such as a subscription, where a portion can be ordered or canceled, the quantity to enter is not always something that is easily calculated in your head. To assist users in calculating the correct amounts, Best Practices for Partial Subscriptions contains several look-up tables to provide the fractional quantities required for purchase or cancellation of a specific number of issues for some basic subscription types. However, with 5.0 Service Pack 3 and earlier, in the Monthly Subscription/Membership Product Table, the calculation for cancelling or ordering 11 months of a 12 month subscription is calculated as .9617, which is incorrect. The correct value is .9167. Aptify 5.5 updates the help files to indicate the correct calculation.

Issue 6702: Subscription Management – Company Subscriptions/Memberships: Add Recipient Company to OrderLines

We should consider adding support for the "Recipient Company" concept at the order line and on the Subscriptions record. This currently isn't tracked within the Subscriptions record model and is probably a better solution than the attribute added in Issues 6519 (4.5 SP2) and 6705 (5.0).

Issue 5317: Subscription Management – Order Details: Subscription Start Date for Dues Product Can Be Incorrect

In earlier versions of Aptify if a person has previously purchased a Dues Subscription the Start Date for Dues products is not calculated correctly. The Start Date for any subsequent subscriptions is populated as the start date of the first Dues product this user has purchased. Aptify 5.5 has been updated to correctly populate the Start Date for any new Dues Subscription.

Issue 9596: Sorting on the Meeting Registrants Tab of a Product Record Produces Error

If a user sorts on the Meeting Registrants tab of a product that has multiple pages an error is produced.

Issue 9558: Expo Management – Price Name Modified when Adding or Changing the Booth Information on an Order

With Aptify 5.0 Service Pack 3 and earlier, if a user adds a booth or modifies existing booth information on a saved order, the name of the expo product's price is modified, which is not expected. The price's name should be the name associated with the price that the user selected when first saving the order. Aptify 5.5 updates the expo order detail logic so that the name of the expo product's price remains unchanged when modifying an expo product's booth information.

Issue 9328: Tasks – RootID Is Not Updated Based on the ParentID

With Aptify 5.0 and Service Pack 3 and earlier, if a user creates a new task, the Root ID field may not be properly updated based on the Parent ID link. This can occur if the user does not specify a Parent ID when initially saving the task. The RootID field is not updated if a parent id is specified at a later time. Starting with 5.5, Aptify updates the Tasks entity's save logic to ensure that when a task's ParentID is updated, the respective RootID is updated based on the ID of the parent task record.

Issue 10518: Housing Management: – Adding Rooms from Housing Dashboard Produces Errors

In Aptify 5.0 Service Pack 3 and earlier, when using the Housing Management dashboard to add rooms to a Housing product's blocks or sub-blocks, Aptify may generate an error. For example, if a user selects a particular Housing product from the Housing Management dashboard's drop-down field, selects the block or sub-block to which they want to add rooms, and then adds the rooms by clicking the OK button, Aptify generates an error and the rooms may not be added. Starting with Aptify 5.5 the error handling for the Housing Management dashboard functionality has been updated so that users can add rooms to blocks or sub-blocks as needed.

Issue 10251: Housing Management: – Documentation Update: Revise the Steps for Canceling a Housing Reservation

The documentation for the Housing Management application states that when cancelling a Housing Reservation to change the STATUS field to Cancelled and to delete the HousingReservationDetail records. However, a client has found that doing this changes the Transfer Status to Pending. In addition, the documentation also states that the Transfer process will pick up all Housing Reservation for the Block select with a Status of Pending. However, per a customer's experience, it appears that the export process only picks those records that have a Pending status and that have HousingReservationDetail records, so if a user cancels a reservation, it will never get exported (reported) to the Hotel. And if we do not delete the HousingReservationDetail records then the reservation is still being counted against the block. See Managing Housing Reservations for more information.

Issue 10790: Meetings – Room Type Value Changes on Form When Blank

In earlier versions of Aptify when working with the Meeting Management application if you leave the Room Type blank on the Meetings form's Location tab, when you view the tab and close the record, the system defaults to a value of zero. The form does this every time you view the tab, even if you save the record first. Starting with Aptify 5.5 this form has been updated to reset the default Room type value to remain blank and allow users to view the location tab without changing this value.

Issue 10373: Meetings – Improper Meeting Sub Form Template

Meeting : Improper Meeting Sub Form Template.

Steps To Reproduce : 

  1. Login as a Regular User
  2. Create a New Meeting Product.
  3. Click on Meeting Tab.
  4. Select Meeting Logistics Tab,Click on Location and maximize the form. 
    (Likewise check for all the Tabs on Meeting Logistics Sub Form Template)
    1. Improper Sub Form Template.(Please Find attachment Form Template 1 and Form Template 2 for more details).
  5. Minimize the Form and Maximize it.
    1. The Sub Form Template appear Blank.(Please Find attachment Form Template 3 for more details)

Issue Replicated in 5.0 Sp3 and 5.0 Sp2 (Please Find Attachment Form Template 4 for more details.)

Issue 10354: Meetings – Cancelling a Meeting While Adding a Different One Produces an Invalid Error

In earlier versions of Aptify, if a user attempts to cancel a meeting and add a different one on the same order, an invalid error is produced and the record does not get saved. The message indicates that an Attendee is needed on the order lines but the data is there. Starting with Aptify 5.5 a user is able to cancel a meeting and add a different meeting within the same order without encountering an error.

Issue 10414: CurrencyTypeID – Documentation Update: Always Appended to Orders and Payments Views

When creating a view of the Orders or Payments services, the field CurrencyTypeID is always appended to the list of Fields to include in the view and cannot be removed from the field list. However, even though it is part of the list of fields, it is never displayed in the view. In addition, when one tries to remove the field, the column order may change. 

Issue 10114: Aptify Commissions – Re-evaluate usage of Quarterly Period on Commission Plans

In earlier versions of Aptify, when using the Commissions and Royalties application, if a user creates a Commission Plan and selects the Quarterly option on the Commission Plan Item the payments are not generated as expected. Aptify 5.5's configuration has been updated to allow users to create and successfully process Commission Plans with the Quarterly option.

 User Resolved Issues (Advertising Management)

 

The issues resolved in this section are only applicable for organizations that have the Advertising add-on application for Aptify 5.5.

 

Issue 10418: Advertising Management – Cancelling an Advertising Insertion Order Is Using Payment Type ID 1

With Aptify 5.0 Service Pack 3 and earlier, when an order is generated from an Advertising Insertion Order that includes a discount amount, the price of the advertisement product on the generated order may be calculated incorrectly. This is due to a rounding error associated with the Discount field of the advertising product's order line. To resolve this issue, Aptify 5.5 increases the number of digits after the decimal place to seven for an order line's Discount field. This ensures that the price of an advertising product is calculated correctly when the order is generated from an Advertising Insertion Order than includes a discount.

Issue 9168: Advertising Management – Price Rounding Error When Generating an Order from an Advertising Insertion Order that Includes a Discount

With Aptify 5.0 Service Pack 3 and earlier, when an order is generated from an Advertising Insertion Order that includes a discount amount, the price of the advertisement product on the generated order may be calculated incorrectly. This is due to a rounding error associated with the Discount field of the advertising product's order line. To resolve this issue, Aptify 5.5 increases the number of digits after the decimal place to seven for an order line's Discount field. This ensures that the price of an advertising product is calculated correctly when the order is generated from an Advertising Insertion Order than includes a discount.

User Resolved Issues (Education Management)

 

The issues resolved in this section are only applicable for organizations that have the Education add-on application for Aptify 5.5.

 

Issue 10941: Education – Provide Ability to Specify Meetings Form to Embed in Classes Form

For the 5.5 functionality to implement Meetings with Classes, we can specify a Products form to embed in the Classes form, but we have to use the current Meetings form without any modifications. It would be useful to support a meetings layout that is specific to the Classes form though.

Issue 10918: Education – Create Generic Meeting/Class Mapping

This issue was opened for tracking the development of a generic meeting/class mapping entity that will allow organizations to define which class fields map to which meeting/product fields and the direction (class to meeting or meeting to class). Based on the mapping, Aptify 5.5 will save the corresponding field value from the first entity record to the second entity record automatically. The layout control will also programmatically disable the receiving fields on the form to enforce the mapping logic at the user level.

Issue 10807: Education – Integrate Meetings into Classes - Registration Synchronization

**This issue corresponds to the functionality that synchronizes Order Meeting Details with Class Registrations.**
This issue tracks a feature request to provide meetings functionality in Classes by embedding a Meetings product into Classes (using the Extended product architecture).

Issue 10806: Education – Integrate Meetings into Classes (Parent Issue)

This issue tracks a feature request to provide meetings functionality in Classes by embedding a Meetings product into Classes (using the Extended product architecture). This is the parent issue (there are multiple sub-issues).

 

Issue 10301: Education – Add Administrator Group Permissions to Education Categories

In Aptify 5.0 Service Pack 3, the Education Categories entity is used by the Education Units functionality however only a System Administrator can create categories out-of-the-box. In Aptify 5.5 the Administrators group has been added to the entity permissions set with Read, Create, Edit, and Delete permissions to allow access to Education Categories. 
.

User Resolved Issues (Fundraising)

 

The issues resolved in this section are only applicable for organizations that have the Fundraising add-on application for Aptify 5.5.

 

Issue 10079: Fundraising Management – Contribution Payments Wizard Does Not Include Currency Type Field for Corporate Contributions

Aptify 5.0 Service Pack 3 introduced the ability to track fundraising activities in multiple currencies. This includes the ability to record cash pledge payments in different currencies through the Contribution Payments wizard. To facilitate this, the Contributions Payments wizard includes a new Currency Type field on the first screen of the wizard (where the contributor information is entered). However, if a user selects the Corporate Contribution option, the Currency Type field is not available and a user can only apply payments in the system's functional currency, which may not be appropriate currency. Aptify 5.5 updates the Contributions Payments wizard so that a user can specify a different currency for corporate contributions as needed.

Issue 10039: Fundraising Management – Contribution Payment Wizard: Tab Key Skips Over the Fields

In Aptify, in the Contribution Payment wizard, when a user attempts to use the Tab key to reach the next field on the third screen of the wizard, the Tab key skips over the solicitor and fund fields and goes to the Date Received field. This is happening because the Solicitor and Fund field are disabled until the Campaign field is filled in. Once the Campaign is filled in, the tab key should take the user to the next field that is "Solicitor".

Administrator/Developer Resolved Issues

The following Administrator/Developer related issues have been resolved in Aptify 5.0 Service Pack 2: 

Issue 9608: Aptify Framework – Database Objects Cannot Be Deleted From Aptify

In Aptify 5.0 Service Pack 2, if an administrator attempts to delete a Database Objects record from Aptify, an error is generated and the database object is not deleted. This is due to the mishandling of the Required Database Objects sub-type record. Aptify 5.5 updates the stored procedure use to delete database objects to properly delete Required Database Objects sub-type records so that database objects can be deleted from Aptify successfully.

Issue 4771: Entity Packer/UnPacker Wizard – Incorrect Caption On Success Message Box

In earlier versions of Aptify the caption for the message box that appears after the entity pack process is successful is incorrect. Currently the text does not provide a helpful description and reads "Aptify Explorer", which is incorrect. Note that this is also an issue for Entity Unpack process. Aptify 5.5 updates this message to read 'Aptify Entity Packer Wizard' as a more accurate description of this process.

Issue 4573: Data Packing and Unpacking – Data Packer Wizard May Select Incorrect Records to Pack

In Aptify 5.0 Service Pack 3 and earlier the default entity from which the Aptify Data Packer wizard is launched is included in the list of entities to pack. To enhance the data packing process, if a user chooses the pack data from this entity, the records that are associated with the view in which the wizard are launched are pre-selected. However, the Data Packer wizard may select additional records when not appropriate due to the mishandling of the record IDs in the view. For example, if the view includes a record with ID 575, records with IDs 5, 7, and 75 are also selected, even if they are not included in the view. Aptify 5.5 updates the record retrieval process to properly handle record IDs so that only the records in the view are pre-selected.

Non-Generated Database Object Table Changes

Below is a list of non-generated Database Objects that have been modified due to changes made with the release of Aptify 5.5. If your organization has modified objects from any of the database objects below while retaining the name of the original database object, additional modification will be necessary to integrate any changes made with upgrading to Aptify 5.5.

 

Note

If your organization has directly altered any of the objects below, those alterations will be overwritten when the core object is replaced during the upgrade process. If a modification to the functionality of a core database object is required, a copy of the core object should be created with a unique name. The modified functionality may then be implemented in the copied object. Again, the existing object itself should not be modified; developers should create a copy of the object using a different name if different functionality is required. See Best Practices When Developing for Aptify for more details.

DatabaseObject Name

Name

DistanceFromInMilesTable

fnIsBetweenRecurringDateRange

fnIsLeapYear

spChangeOrdLine

spCreateAttachments

spGetCampaignCategoryPricing

spGetCampaignPricing

spGetPendingScheduledTransactionGroupsByProduct

spGetPendingSTGroupsByProductAndProcess

spGetQualifiedPricing

spUpdateAttachments

spUpdateProductInventory

spVerifyAptifyUserLogin

vwAttachments

Copyright © 2014-2017 Aptify - Confidential and Proprietary