...
As of EngageIP 8.5.26.0 the will be accessible only over a secure connection (HTTPS)
In order to upgrade to EngageIP 8.5.26.0 or any subsequent version you will need to ensure you have a certificate configured for the host domain. It is also recommended that you configure IIS on the EngageIP to redirect users from:
http://yourdomain/
to
https://yourdomain/If you have any questions regarding the https configuration please contact LogiSense support.
EngageIP environments integrated with AvaTax (EZtax) upgrading to EngageIP 8.5.26.0+ must run the following scripts:
The EZTaxTaxTypeMappingInsertScript
A SQL query to populate the ISO code for USA
Both scripts can be found in the AvaTax Installation and Configuration article
What's New?
Added Enhancements to the Commissions Module including:
Commission Advancement which enables commission to be calculated and paid out for a sales agent in advance of a User-Contract becoming active
Commissions for new User-Contracts and renewing User-Contracts
Agent management features to retire Agents, retire Commission Details and reassign Agents
Commission Statements that can be customized and delivered (emailed/exported) for Agents
Bonus commissions which can be paid out when specified commission thresholds are reached
Commission configured on usage (data, sms, voice, events, etc.)
For more information on these features see the Commissions Module article
Added the ability to issue credits for usage. See the article Managing Transactions – Debits, Credits, Refunds, Void / Voiding Invoices on Accounts for instructions and additional information
Added support for West/Intrado E911 integration. See the KB article Using West/Intrado E911 With EngageIP for more information
Added support for Bulk E911 integration. See the KB article Using Bulk E911 With EngageIP for more information
Enhancements - Other or Changed
...
Added a Hosted Payment Page module which permits payment information to be directly sent to a payment gateway and removes the need for 3rd parties to store cardholder data. See the Hosted Payment Page Configuration and Usage article for more information
...
Added the ability to exclude taxation at the Country or State level in AvaTax integrated environments. See the AvaTax Configuration article for more information
Improved performance when adding price plans to packages [ticket:99867]
Fixed an issue where usage was not being applied to a UDR bucket in scenarios where a user-package was added and canceled in the same period [ticket:100344]
Modified the UDR Bucket Owner Report to filter results based on the Owner tree instead of the OwnerID of the current owner in context [ticket:102078]
Modified the UDR Bucket Account Report to filter by UserID and OwnerID instead of UserID and ActingOwnerID
Modified the GetResourceItemByName method so that the results returned are only related to the OwnerName specified in the call [ticket:102933]
Added support for new MasterCard BIN's (222100-272099) [ticket:102953]
Fixed an issue with the StartEventLoggerFiltering function which caused Events to be repeatedly logged when no filter value was specified
Modified the EngageIP installer to disable checking for .NET 2.0 and .NET 3.5 [ticket:103080]
UI and data validation improvements to Hosted Payment Pages
Modified the GetURL method used by the Hosted Payment Page integration to revert to using the 'ID' User table value for the CustomerID instead of the User table 'Account' value
Modified the Hosted Payment Page implementation to ensure JavaScript events are passed up to the parent window
Added logging to track when processing of payment terms and payment retry terms is complete. This activity can be viewed in the Event Log
Fixed an issue with Webhooks which could cause an exception when executing Webhook actions
Fixed an issue where commission was calculated incorrectly when reclaiming commission earned on an inclusive taxed Service
Fixed an issue in AvaTax integrated environments where non-billable taxes were billing when 'returnnonbillable=true' was set in the EZtax.cfg file [ticket:101467]
Modified UDR Bucket logic to make the bucket creation more thread-safe
Removed logic that would prevent a UDR record from being returned by the RealTimeFraud Service if processing the UDR failed
Modified Tax logic to reference the Address Contact Point instead of the first Contact Point found on a Contact
Fixed an issue where saving a Bill Group to Branded Owners failed in error
Fixed an issue where dynamically adding a Bill Group on a Branded Owner would result in a system configuration error message
Modified billing logic so that running IUserBilledHook does not cause Custom Code to recompile, improving performance
Removed redundant logging in the Event Log that occurred when looking up User Tax Codes
Fixed an issue where the Address Line 1 field on a Contact Point Address would appear as a required field when the address was not configured as required
...