You must upgrade first to 3.24.0 using the interworks.cloud installer before applying this patch
On this page
The max timeout can be defined in "Security Settings" in Organization Profile page. The default value is 480 minutes (8 hours). We have implemented some improvements for improving the performance of the checkout process. We have made changes to the calls we are doing to external systems APIs for decreasing the delays you were experiencing during checkout.
Max timeout for BSS UsersUntil this release we supported only the idle timeout that is the amount of time a BSS session will remain active in case there is no activity from the logged in user. In this release we introduced the max timeout also that is for defining the maximum amount of time a BSS session can be active. Upon reaching this timeout, the BSS user will be logged out automatically and he will be forced to login again for continue working with BSS.
Performance Improvements for the Checkout Process
The max timeout can be defined in "Security Settings" in Organization Profile page. The default value is 480 minutes (8 hours).
We have implemented some improvements for improving the performance of the checkout process. We have made changes to the calls we are doing to external systems APIs for decreasing the delays you were experiencing during checkout.
issues Resolved in 3.24.2
|EXL-6255||Microsoft tenants with domain alias could not be synchronized from BSS.|
|EXL-6287||When you place a Microsoft order for a new customer, a timeout is returned during checkout.|
issues Resolved in 3.24.3
|EXL-6261||The MCA pop form return -999 error because of incorrect handling for date field.|
|EXL-5789||Wrong billing period on invoices for products that have been flagged to maintain one subscription when you purchase extra licenses for your existing subscription along with an add-on.|
|EXL-6201||Connectwise connector - Account pull method fails because of account currency.|
|EXL-6133||The prices are not imported correctly from the products importer.|
|EXL-6299||Avalara connector - The Billing services does not flush automatically the avalara token after parsing all organization invoices.|
|EXL-6095||Error while trying to disable a unit during product's creation when the "Month" unit is not set as "is default" in the setting of the "Recurring charges" unit group.|
|EXL-6280||When you uncheck the "is default" option from a unit in "Recurring charges" unit group, the system related the unit with itself.|
|EXL-6318||AVG Service Manager - Issues with the upgrade and release licenses actions in Storefront.|
- No labels