Search Engine: Elastic

Article ID: 114552, created on Aug 10, 2012, last review on May 10, 2014

  • Applies to:
  • Business Automation 5.4


Release Notes

Issues Fixed




Problem: Subscriptions with manually set names are reset to their auto-generated default values when upgrading from PBA 5.1 to 5.4. 

Fix: Subscriptions with manually set names are not renamed when upgrading. A subscription will only be renamed if it satisfies any of the following rules:

  • Name field is empty;
  • Name matches pattern "IDXXXXXXX";
  • Name is the same as that of the Plan Name;
  • Name is the same as that of the domain assigned.

Subscription names will only be renamed for PEMGATE, DUMMYGATE, and RESELLERGATE subscriptions: 

  • DUMMYGATE and RESELLERGATE subscriptions will be renamed to their Plan Name;
  • PEMGATE subscriptions will be renamed to "Plan Name (domain name)" if the domain name is present for the subscription. Otherwise, they will be renamed to "Plan Name."

The rest of the subscriptions will not be affected.


Problem: When upgrading to a new version of PBA, an automatic attempt to process all sleeping orders (those that have statuses allowing automatic transitions, but have remained in this status for at least an hour) can cause an ODBC driver failure. 

Fix: The upgrade script has been fixed so that the orders that were sleeping before the upgrade will not be touched, while the orders that entered this status after the upgrade will be processed.



Problem: When a subscription with a custom name is switched to a different service plan, it gets renamed back to the auto-generated default value "Plan Name (domain name)."

Fix: During a plan switch, a check of the subscription name is now performed. If it is a custom one, then it will not be renamed. Refer to PBA-39323 for logic on identifying custom names.


Problem: Unable to place a renewal order if the corresponding order item was removed from a previously placed renewal order.

Fix: The corresponding renewal order "OrderID" is automatically removed from the database when an item is deleted from a renewal order.


Problem: Monthly VAT-invoices are not generated for business accounts that were canceled in the middle of month, but had paid for and used a subscription in the past. 

Fix: VAT-invoices are now generated for cancelled accounts in a general manner: Recurring VAT-invoices are generated at the end of the month.


Problem: The "Last Billing Date" is displayed incorrectly for some accounts. These accounts are successfully billed each day, but no Billing Orders or Invoices are created for them. 

Fix: Now the "Last Billing Date" field contains the date when the account was last processed by daily billing. The date remains unchanged for accounts that are unable to be billed for some reason.


Problem: In cases where a Provider removes an incomplete (failed) provisioning item from an Upgrade or Downgrade order, all additional counts of Resource are removed from the subscription. 

Fix: If a Resource Upgrade/Downgrade provisioning order fails on the POA side, the Resource in the subscription will now stay in the "Failed" status, whereas previously, it would stay in the "Provisioning" status.


Problem: A staff member's middle name is not transferred to POA for accounts created in PBA. 

Fix: The "middle_name" field is now correctly transferred to POA. Existing staff members’ names are to be changed manually, if necessary.


Problem: A Payment Order exists in the database, though the corresponding payment has been deleted. 

Fix: Payment Orders are now properly deleted along with their related payments. An existing payment that requires removal can be removed from the database manually.


Problem: In some rare cases, the Reseller wizard fails on the last step, stating that plans cannot be delegated to the Reseller. 

Fix: The error no longer appears; a step has been added to verify whether a Source Plan Rate exists.

User Interface


Problem: A promotion with a "Per Customer Limit" limit is applied, but the prices on a page of choice in the Online Store are not displayed correctly. 

Fix: All prices on any page of choice in the Online Store are now displayed correctly.


Problem: A "New Limit" selection using a mouse with a suggested value in a standard browser drop-down menu doesn't work. 

Fix: Selecting a value with a mouse works properly now: The spinner control correctly handles the appropriate "OnChange" event when pasting a value with a mouse or selecting it from "suggested values." 


Problem: Russian Market: Input fields on the "Correct Facture" screen are not aligned. 

Fix: The controls have been aligned. 


Problem: Buttons that must be enabled after selecting any item, and disabled otherwise, do not change their state after selection when using Skins v.1. 

Fix: The improper behavior of buttons in Skins v.1 is now fixed.



Problem: Transferring of ".no domain" fails with EPNIC if it is registered to a non-personal account. 

Fix: The transfer now finishes successfully: The contact type is reported to the registrar as PERS for .de and .no TLDs, regardless of the account type in PBA.


Problem: An incomplete domain cancellation procedure for GoDaddy occurs in cases where the domain is transferred or suspended by the registrar. 

Fix: The cancellation operation now finishes successfully: The "getDomainInfo" request is now made before canceling a domain.


Problem: Attempt to update Name Servers/Contact information of domain registered through EPNIC registrar within PA will fail in case domain status on registrar was set to one not allowed in Domain Update request. 

Fix: Do not use Domain Status field in Domain Update request on Name Servers/Contacts update to EPNIC.



Problem: Translations are missing for some strings in Russian localization. 

Fix: The code has been changed to make the strings translatable, and respective keys have been added to the standard English locale.


Problem: On an attempt to create a negative facture correction under a Russian locale, an error message appears stating that one or more fields are incorrect; negative values for prices and taxes are highlighted. 

Fix: Creation of a negative correction is now handled properly under Russian locales.


Problem: Translations are missing for the "Feature Name" and "Feature Price" strings in the CCP for Polish localization.

Fix: The code has been changed to make the strings translatable; respective keys have been added to the standard English locale.


Problem: An attempt to open a Sales Order from the "Payment" menu raises an exception under a non-English locale if the value for the "Sales Order" key differs from "Sales Order."

Fix: Sales orders open correctly now.



Installation Instructions

New Installations:



Installation files:
Note: Use the installation files listed below instead of the ones given in the "Downloading and Copying Installation Files" section of the corresponding guide.
RHEL4/Centos4 – 32-bit
RHEL6/Centos6 – 64-bit
Windows 2008 – 64-bit
Windows 2003 – 32-bit

Additional Information

  1. PBA will require a restart during the update.
  2. During the upgrade, all PBA RPMs will be upgraded to newer versions. If a backup is made with a server/VPS restart, then the private key for credit card encryption needs to be reloaded.
  3. Additional documentation can be found here:



210d017ddc3a076d22f0f865b1cf0730 caea8340e2d186a540518d08602aa065 198398b282069eaf2d94a6af87dcb3ff 92711db0799e8aefe8e51f12dace0496 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF