Release MR75

get_number_list,

get_number_info

1. Added 'external' field to every DIDNumberInfo XSD structure in the methods' responses.
2. Added 'external' input filter for the get_number_list()

1. Added new SOAP types: 'TemplateBodyInfo', 'TemplateComponentInfo', 'TemplateMediaAttributeInfo' and 'TemplateDataFieldInfo;
2. The SOAP type 'TemplateInfo' extended with the fields 'i_time_zone', 'tz' and 'body_list';
3. Added new methods for managing templates:
- get_template_info
- add_external_invoice_template
- upload_external_invoice_template_body
- upload_external_invoice_template_image
- delete_external_invoice_template_image
- add_tariff_download_template
- update_template
- delete_template
- get_template_component_list
- get_template_media_attribute_list
- update_template_media_attribute_list
- get_template_data_field_list
- update_template_data_field_list

Overview:  The 'managed_by' parameter is going to be removed from the "clone_customer_class" method. Starting from MR75-0 it is marked as deprecated in API guide.

Symptoms/Impact:  No impact.

Actions: Switch the application to use the "clone_customer_class" API method without the 'managed_by' parameter.

get_notification_list

get_notification_template_info

update_notification_template

send_me_notification_sample

Methods are obsolete. To keep them working enable option API.AllowObsoleteMethods=Y

In case customer class has no notification preset assigned (manual update via API, or changed via NewUI) then no response will be received (no categories, no notifications etc for such customer classes, or failed response).

Also please note - after migrations customer classes with default options will be set to one notification preset, so changing notifications via this methods will change the same notification for all customer classes!

get_notification_template_info

update_notification_template

send_me_notification_sample

Methods are obsolete. To keep them working enable option API.AllowObsoleteMethods=Y

In case user has no notification preset assigned (manual update via API, or changed via NewUI) then no response will be received (no categories, no notifications etc for such customer classes, or failed response).

Also please note - changes will affect only notification preset assigned to current user, so in case it's assigned to several users they'll be affected as well.

get_notification_list

Methods are obsolete. To keep them working enable option API.AllowObsoleteMethods=Y

In case user has no notification preset assigned (manual update via API, or changed via NewUI) then no response will be received (no categories, no notifications etc for such customer classes, or failed response).

Also please note - changes will affect only notification preset assigned to user, so in case it's assigned to several users they'll be affected as well.

add_customer_class

update_customer_class

get_customer_class_info

get_customer_class_list

add_user

update_user

get_user_info

get_user_list

get_ua_info

get_ua_list

get_payment_method_info

get_taxation_info

get_transaction_actions_list

get_payment_methods_for_owner

get_countries_list

get_subdivisions_list

Account

Customer

Extend method with new filters: companyname, country, state, note, bcc, midinit, zip, tax_id

get_custom_report_query_list

get_custom_report_query_info

Extend filters with:

• midinit
• lastname
• cont2
• country
• state
• zip
• companyname
• note

modify_request

create_portin_request

get_request_list

Overview: 

 To transfer service between DiscountPlan entities (Service Wallets), two API methods are used in conjunction:

• the get_operation_access_id method to request OTP password for transaction;
• the make_transaction method to perform the transfer itself.

From this release the session_id must be used in authorization parameters of the make_transaction method. Requests with Login and Password will be rejected. More details about the methods in the PortaBilling XML / JSON API Reference Guide at MR75 https://www.portaone.com/docs/pb/mr75/PortaBilling_API_MR75.html#DiscountPlanmake_transaction.

Symptoms/Impact:

Transfers between Service Wallets fail.

Actions: 

Use the session_id instead of the login and password in the authorization parameters of an API call. 

get_operation_access_id

create_otp

verify_otp

Overview

 To transfer service between DiscountPlan entities (Service Wallets), two API methods are used in conjunction:

• the get_operation_access_id method to request OTP password for transaction;
• the make_transaction method to perform the transfer itself.

From this release the session_id must be used in authorization parameters of get_operation_access_id and make_transaction methods. Requests with Login and Password will be rejected. More details about the methods in the PortaBilling XML / JSON API Reference Guide at MR75 https://www.portaone.com/docs/pb/mr75/PortaBilling_API_MR75.html#DiscountPlanmake_transaction.

Symptoms/Impact

Transfers between Service Wallets fail.

Actions: 

Use the session_id instead of the login and password in the authorization parameters of an API call. The same session_id should be used for the get_operation_access_id and make_transaction methods for a single transfer.

Account

Customer

add_custom_field

update_custom_field

GetCustomerBatchList structure was extended with the 'limit', 'offset', 'get_total' and 'check_usage' fields. Default value for 'check_usage' is 1 for backward compatibility

Added 'total' field to the GetCustomerBatchListResponse structure (present if the 'get_total' was passed in request)

Overview

The topup_amount parameter is mandatory for the add_topup_option method. More details about the parameter in the PortaBilling XML / JSON API Reference Guide at https://www.portaone.com/docs/pb/mr75/PortaBilling_API_MR75.html#VDTopupOptionInfo

Symptoms/Impact

The add_topup_option method does not perform a top up in a service wallet. The API reply contains "Client.DiscountPlan.mandatory_field_missed.topup_option_info.topup_amount" error.

Actions

Make sure that the topup_amount parameter is sent in the add_topup_option API call.

The 'check_usage' parameter was added to check whether the tax transaction codes are in use.

add_rate,

add_rate_group,

batch_add_rate,

update_rate,

update_rate_group

NULL values are set to the rate parameters op_route_category, op_preference, op_huntstop when they are not given for the add methods. Update methods will not change the previously set data values

Overview: 

Starting From MR75-3, the op_route_category, op_preference, op_huntstop rate parameters don't inherit the values from the route_category, preference, huntstop parameters and are set to NULL in case they are not sent using the add or update rate methods.
Please see more details about the methods in the PortaBilling XML / JSON API Reference Guide at MR75
https://www.portaone.com/docs/pb/mr75/PortaBilling_API_MR75.html#serviceRate

Symptoms/Impact:

NULL values are set for the op_route_category, op_preference, op_huntstop rate parameters if they are not stated via the add methods.
Update methods don't change the previously set data values if they are not provided.

Actions:

Make sure that the op_route_category, op_preference, op_huntstop rate parameters are sent in the add_rate, add_rate_group, batch_add_rate methods in case they need to be different from NULL.

Make sure that the op_route_category, op_preference, op_huntstop rate parameters are sent in the update_rate, update_rate_group methods in case they they need to be changed.

add_service

get_service_info

get_service_list

get_account_info

get_account_list

get_service_features

get_service_features_metainfo

add_commission_plan

update_commission_plan

The maximum value of the fields:

CPPeriodInfo.commission 

CommissionPlanInfo.default_commission

CPSubscriptionInfo.one_time_commission

has been increased to the maximum value allowed to store in the database