Accepting Order
After the order is successfully placed, you will be redirected to the order summary view page. The page contains the following sections:
- Order Criteria
- Auto Detected Device
- Choose Device
- Order Actions
Auto Selected Device
It is a box containing information about the best fitting server based on criteria selected by the client placing the order.
You can read more about fitting servers in the section Provisioning Flow. The server which was fitted by the system can be freely changed, Change Target Device button should be used to do that.
Order Criteria
Order criteria box contains details specified by the client. To edit client’s choice you have to select from the upper menu Edit Order action button and then fill out the fields.
Order Actions
To accept the order, click the Actions button in the top menu and select Accept Order. This will display an information box with order details.
Once you confirm by pressing Accept Order, the system will automatically perform the following actions:
- The status of the selected server will be updated to In Use
- The hostname provided by the client will be assigned to the server
- The client who placed the order will be linked to the server
EasyDCIM allows you to define specific actions to be executed automatically when an order is activated, suspended, unsuspended, or terminated. These actions can be configured globally for all orders (Servers and Colocations) via the Advanced System Configuration section: Advanced System Configuration – Orders & Services.
While this configuration applies globally by default, you can override it on a per-order basis. To do so, navigate to the Order Summary view: Assigning Servers to Clients.
Additionally, if you’re using the WHMCS integration, you can customize these actions globally for each product within the module settings.
In summary, you have three levels at which to configure automation behavior:
- Globally in EasyDCIM (applies to all orders)
- Per individual order in EasyDCIM
- Per product in WHMCS
Provisioning Actions Overview
The following table lists and explains the available provisioning actions in EasyDCIM. These actions can be configured to run during specific order events: Activate, Suspend, Unsuspend, and Terminate. Depending on the event type, the same action may perform a different role (e.g., install OS on activation or wipe disk on termination).
| Action name | Description |
|---|---|
| [DNS management] Create RDNS records | Generates PTR (reverse DNS) records for assigned IPs, essential for email deliverability and IP trust. |
| [DNS management] Create zone | Creates a new DNS zone for the assigned device. |
| [DNS management] Delete zones and RDNS records | Cleans up DNS and reverse DNS records. |
| [IP address management] Assign subnet | Attempts to automatically assign a subnet based on client preference (e.g., /30). If no match is found, manual selection via the Configure Now button in the Service Configuration panel is required. |
| [IP address management] Unassign subnets | Releases assigned subnets back to the available pool. |
| [IPMI integration] Create operator account | Creates an operator-level user in the server’s IPMI interface (e.g., Dell iDRAC, HP iLO), enabling remote server management. |
| [IPMI integration] Delete operator account | Removes IPMI operator account to revoke remote access after termination. |
| [OS installation] Install operating system | Initiates the OS installation using the EasyDCIM OS Installation module and a predefined template. |
| [OS installation] Reinstall OS | This action will trigger the OS reinstallation procedure. The specific OS and configuration used during reinstallation can be defined using the Reinstall Template in the provisioning server’s settings. |
| [Usage collector] Remove the monthly traffic limit (in/out) | Deletes traffic limit settings from the system. |
| [Usage collector] Set the monthly traffic limit (in/out) | Sets a monthly inbound/outbound traffic limit based on the value specified in the client’s configuration. |
| Boot a device | Sends a command to power on the physical server, typically via IPMI or another out-of-band management tool. |
| Change inventory status | Changes the inventory status of the device (e.g., from ‘in use’ to ‘available’). |
| Clear additional IP addresses value | Removes any additional IP addresses assigned to the service. |
| Clear hostname & SSH values | Removes hostname and SSH access credentials from the server record. |
| Delete notifications | Clears all notifications related to the service. |
| Delete RRD files with graphs and traffic data | Removes RRD (Round-Robin Database) files containing traffic graphs and statistics. Useful for resetting historical data during re-provisioning. |
| Disable traffic aggregation ports | Disables traffic aggregation ports to stop data monitoring or reduce network usage. |
| Enable traffic aggregation ports | Enables traffic aggregation ports, typically used to monitor combined data flow from multiple interfaces or devices. |
| Shutdown a device | Sends a shutdown signal to the server, effectively powering it off. |
| Unassign device parts | Detaches physical components like disks from the server asset. |
Provisioning Log
In case any of the provisioning steps fails, detailed information will be available in the Provisioning Logs tab.
Additionally, you can monitor the current progress and queued tasks in the Provisioning Queue tab, which provides real-time insight into the execution flow of provisioning actions.
