Build - the name of the maintenance release build the change was introduced in.

Service - the name of the service/services which is/are affected.

Method - the name of the method/methods which is/are affected.

Message - the message that explains what was changed.

Schema changed - shows whether it is required to rebuild WSDL/XSD-generated stubs for .net, Java and other static typing languages.

TT - a link to a ticket related to the change.

BuildServiceMethodMessageSchema changedBackward compatibleTTResolution for system update
MR84-0Account

delete_alias

terminate_account

Added 'force' input parameter, 'warnings' output fieldYesYesYT:BA-23584
MR84-0Accountupdate_accounts_batchAdded 'force_terminate' input parameter, 'warnings' output fieldYesYesYT:BA-23584
MR84-0Currencyget_currency_infoAllow get_currency_info for RepresentativeNoYesYT:BA-25343
MR84-0TraceSessionget_trace_session_listAdded 'status' input parameter. Allows to get only sessions of certain status: complete or failedYesYesYT:BA-25805
MR84-1

CustomerClass

User

update_notification_list

update_notification_list

Add API methods update_notification_list to service CustomerClass and UserYesYesYT:BA-25521
MR84-1

CustomerClass

User

get_notification_category_list

get_notification_category_list

adjusted logic of get_notification_category_list to return enabled send_sms and send_mail if at least one notification is enabled within the notification categoryYesNoYT:BA-25521

Overview:  
There is an enhancement that enables the possibility of enabling/disabling specific notifications in the notification group.

If there are no changes after the update in notifications configuration, no changes for the end-user.

Symptoms:

Only specific notifications enabled in the notification group.
Impact:

If send_sms or send_mail is enabled for one of the notifications in the notification group, it will be returned as enabled for the whole group.

Actions:
No actions are required if no changes in notifications are performed.
If notifications will be partially enabled within the groups, the changes should be noted and adjustments for applications may be required.

MR84-1

CustomerClass

User

update_notification_category_list

update_notification_category_list

Deprecate API methodsNoYesYT:BA-25521
MR84-1

CustomerClass

User

get_notification_list

get_notification_list

Adjust methods get_notification_list to work without assigned i_notification_preset on respective entitiesNoYesYT:BA-25521
MR84-1Customerterminate_customerAdjust the processing of accounts. It is not possible to terminate a customer if termination of any of its accounts fails (for instance due to non-disconnectable active sessions)NoNoYT:BA-24106

Overview:

There is an enhancement that prevents the issue with the account left unterminated after the customer termination by canceling the termination task if the active non-disconnectable session is detected on one of the accounts.

Symptoms/Impact:

Some customers cannot be terminated after the update due to active non-disconnectable session on one of their accounts.

Actions:

Terminate the account with an active session using the 'force' option or wait until the session ends.

MR84-1Node

add_node

update_node

Maximum allowed length of the "h323_id" input parameter was increased to 253 charactersNoYesYT:BA-26631
MR84-1


CustomerClass

get_customer_class_info

get_customer_class_list

add_customer_class

update_customer_class

Add field ot_bp_charge_cc to CustomerClassInfoYesYesYT:BA-25227
MR84-1


Customer

Account

vd_topupAdd field status in response to represent transaction status on payment gateway sideNoYesYT:BA-26191
MR84-1TraceSessionget_trace_session_listAdd "source" input field to allow fetching sessions only from a specific sourceYesYesYT:BA-26613
MR84-1Accountadd_aliasAllow adding AA aliasesNoYesYT:BA-26684
  • No labels