История страницы

When the module runs, the details of the client’s existing services account are updated without creating new items.

• There are no configuration options for this module.

Extending the Module

Through the API order.create function, you need to specify what items to change and what the changes should be. Unlike the usual pack1[] style arrays used in adding new services, the edit services module will look for the edit_packs array. The edit_packs[] array is first indexed by a simple numeric key indicating how many services are being edited. The next index level is the variables that are actually being updated in the service. These field names are the standard set of variables for services. The supported fields include but are not limited to: desserv, price, period, start, renewdate, options etc. The full list is in the edit service API Guide.

It is not necessary to specify every possible variable in the order, only the items that are explicitly set in the order will be updated in the service. All other fields will be left unchanged.

Once the order is submitted, processing the Edit Services order module commits the changes to the client's account. The edit is done through the standard edit service backend function and is logged the same way as a manual edit.

As an example, if client 1001 had a service with ID number 412 that needs to be updated to renew quarterly for $300, the following variables would be set in the order:

client_id=1001

edit_packs[1]['packid']=412

edit_packs[1]['period']=3

edit_packs[1]['price']=300

Editing a second service ID number 308, in the same order, to renew monthly for $50 and to have a service description of Development, would pass the following:

edit_packs[2]['packid']=308

edit_packs[2]['period']=1

edit_packs[2]['price']=50

edit_packs[2]['desserv']='Development'

Related Topics 

Якорь
Related Topics Related Topics

Configuring Order Queues