Atomia Billing Server

Domain Transfer workflows

5 views 0

Domain Transfer Out Workflow

Namespace:Atomia.Billing.Plugins.GenericWorkflowPlugin.ScheduledTasks.TransferOutNotificationScheduledEventHandler

System will periodically check for domains in Atomia Automation Server which are not marked as local. This list will be compared with the list of all OK and Suspended and, at the same time, Provisioned subscriptions of the category Domain or DomainTransfer (except from the in-progress transfers-in).

The matched domain’s subscription will be terminated and it is possible to send email to the customer.

Example configuration:

            {
               "ApprovedItemsCount":50,
               "ScheduleItemsCount":50,
               "ApplyToSubresellers":true,
               "AutoApprove":true,
               "MessageType":0,
               "TemplatePrefix":"TransferOutEmail"
            }
  • ApprovedItemsCount Limit the number of transfer out tasks to be auto-approved during one run. Zero means no limit.
  • ScheduleItemsCount Limit the number of subscriptions to be checked for the transfer out during one run. Zero means no limit.
  • ApplyToSubresellers If set to true and this configuration is reseller specific then it also applies reseller’s sub-resellers.
  • AutoApprove Should the action be auto-approved.
  • MessageType The message type (0 – Email, 1 – SMS).
  • TemplateNamePrefix The template name prefix. For example if this prefix is “TransferOut”, then the system will look for “TransferOutSubject” and “TransferOutBody” in case of Email message or “TransferOutSMS” in case of SMS message.

Domain Transfer In Workflow

Namespace:Atomia.Billing.Plugins.GenericWorkflowPlugin.ScheduledTasks.TransferInNotificationScheduledEventHandler

System will periodically check all subscriptions that are domain transfer in progress. The system will check if domains of these subscriptions is transferred-in according to Atomia Automation Server.

If successful, system will:

  1. Update TransferStatus=success
  2. Update expiration and renewal date of the subscription to the actual domain expiration date.

If failed, the system will:

  1. Update TransferStatus=failed (customer can re-try the transfe from the control panel)

It is possible to set actions that will occur after defined period of time if transfer in doesn’t complete.

It is possible to notify the customer of the succesfull or failed domain transfers.

Example configuration:

            {
               "NotificationName":"TransferInCheck",
               "ApprovedItemsCount":250,
               "ScheduleItemsCount":250,
               "ApplyToSubresellers":true,
               "AutoApprove":true,
               "MessageType":0,
               "FailureTemplatePrefix":"DomainTransferFailEmail",
               "SuccessTemplatePrefix":"DomainTransferSuccessEmail",
               "Actions":[
                  {
                     "Action":"Terminate",
                     "DaysOffset":90,
                     "MessageType":0,
                     "NotificationName":"TerminaTransfer",
                     "Statuses":[
                        "pending",
                        "fail"
                     ],
                     "TemplatePrefix":null
                  }
               ]
            }
  • NotificationName A descriptive name to this configuration (has no effect on workflow). This will appear as the name of the task i the list of scheduled tasks.
  • ScheduleItemsCount Limit the number of subscriptions to be scheduled for transfer-in check during one run. Zero means no limit.
  • ApprovedItemsCount Limit the number of subscription transfer-in tasks to be auto-approved during one run. Zero means no limit.
  • ApplyToSubresellers If set to true and this configuration is reseller specific then it also applies reseller’s sub-resellers.
  • AutoApprove Should the action be auto-approved.
  • MessageType The message type (0 – Email, 1 – SMS).
  • FailureTemplateNamePrefix A prefix of mail, and SMS templates for messages which are sent in case of failed transfer.
  • SuccessTemplateNamePrefix A prefix of mail, and SMS templates for messages which are sent in case of succesfull transfer.
  • Actions[ ] A list of actions to be executed on different days after invoice date.
  • Actions[ ].NotificationName A descriptive name to this configuration entry (has no effect on the workflow).
  • Actions[ ].Action The Action to be taken. Can be “Terminate” or “Suspend”. For new orders it is expected that the order page handles the logic of setup fees.
  • Actions[ ].DaysOffset How many days after the invoice date should this action be taken.
  • Actions[ ].MessageType Message type: mail=0, sms=1
  • Actions[ ].Statuses[ ] This is a list of transfer statuses (the value of subscription TransferStatus custom attribute) to which this action is applicable.
  • Actions[ ].TemplatePrefix Email or SMS message template prefix. If the value is null, no message will be sent.

Was this helpful?