Configuring Notification on Successful Services Provisioning

In this section we will consider solely configuration of notification on successful services provisioning.

To configure the notification:

  1. Open System > Settings > Events. The list of system events appears on the screen.
  2. Select the Creation Completed event type by clicking on the respective link in the Event Type column. Selected event type properties appear.
  3. Switch to the Event Handlers tab. The list of event handles assigned to the event type (if any) appears on the screen.
  4. Click Add New Event Handler. The adding new event handler dialog window is displayed. Fill out the form:

    • Type a name of programmatic object to be created into the Object field. For notifications it is "MESSAGE".
    • Type the name of object's method to be called when the event occurs into the Method field. For domain subscription notification (both registration and transferring), it is "SubscriptionNotification". For service subscription notification, it is "PlanNotification".
    • Type a condition to check into the Condition field. For domain registration, the condition would be "IssuedSuccessfully==1&DomainOperation==10". For domain transfer, the condition would be "IssuedSuccessfully==1&DomainOperation==90".
    • Type the signature of the method into the Signature field. For domain subscription notification, it should contain the following row (replace TemplateName with the appropriate notification template name for transferring and registering respectively):

      integer SubscrID, string Notification_Template. For service subscriptions, the string would be "integer SubscrID".

      Note: This field is case-sensitive.

    • Select the Stellart protocol from the Protocol menu.
    • Type the number of attempts the handler will make in case an error occurs into the Max Attempts field. For messaging it is normally "1".
    • Type how frequently (in seconds) the retry attempts should be made into the Repeat Interval field. As notifications normally do not use retries, this setting is not important and can be "1".
    • The Synchronous option indicates how the handler should be executed – synchronous or asynchronous. To prevent unnecessary delays in event processing, notifications should be sent asynchronously (check box has to be cleared).
    • The Delay (minutes) option sets by how many minutes the handler execution should be delayed. There is no need to have any delays, so you can leave the option blank.
    • The Priority parameter defines the events processing order. "1" is the highest priority. All tasks of the event receive the same priority. When there two or more events having the same priority occur, the newest tasks are processed first (not those that occurred first!).
  5. Click Save to finish adding event handler.
  6. Repeat steps 4 and 5 until you add all three handlers necessary. In case you intend to use one template for all subscriptions, configure one event handler in the same way as for service subscription.
CloudBlue, an Ingram Micro business, uses cookies to improve the usability of our site. By continuing to use this site and/or logging in you are accepting the use of these cookies. For more information, visit our Privacy Policy.