Search Engine: Elastic

Article ID: 124765, created on Mar 9, 2015, last review on Mar 9, 2015

  • Applies to:
  • Business Automation 5.5


The customer received a notification that an account was put on credit hold while this account has been cancelled or put on the administrative (not credit) hold.


As a part of cancellation process (PlaceAccountCancellationOrder method), an event "Account Put On Hold" is posted, which is required to let POA know that the account shall be disabled. The same event is used when putting an account on administrative hold, credit hold and canceling it as there is only one relative status is POA - Disabled, this event has corresponding PEMGATE method attached. The issue with is "Account is put on Credit Hold" notification to be sent on all these events is considered to be a product bug with id #PBA-36367.


To avoid customers confusing you may do the following changes:

  1. Create a notification template of Account Notification type, with the content you expect to be sent in cases the customer account is cancelled or put on the administrative hold (so, in cases the account is disabled), make sure the template is active, visible to the resellers
  2. Set this template to be used in the event handler:

    Home> System> Settings> Events> Event Handler
    MESSAGE         AccountNotificationNoExc
    change Account Put on Credit Hold to the newly created template name

    However here is an issue - for the accounts which are put on credit hold the same notification will also be sent. In addition to this one, when putting account on credit hold, a notification set in the common notification settings will be sent:

    Home> System> Settings> Notifications> Common Notification Settings
    Credit Hold Notification Template

    You may describe the issue that the account is disabled in the notification for AccountNotificationNoExc and leave information about financial questions in the notification for credit hold, so that the information is not duplicated in these notifications.

198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 801221f8cd76fba7300d1e6817c8e08b 92711db0799e8aefe8e51f12dace0496

Email subscription for changes to this article
Save as PDF