# Creating New Order

Start creating a new order by choosing from left menu respectively Clients → Add Order. The Add Order action is also available in the Actions menu of the Clients → Orders list.

The order configuration is divided into several steps. They will be described in the below sections. Step 1 describes the Add Order form. Steps 2 and 3 describe the Service Criteria and Service Configuration tabs of the Edit Order form. This form is available from the Actions menu on the summary of a pending order, for example an order placed via the API or a billing integration.

# Step 1: Adding a New Order

As an administrator, use the Add Order form to quickly assign a server or device to a client:

  • Service Type – Select the type of service: Server or Colocation.
  • Client – Choose the client for whom the order is created.
  • Device – Select an available device. For the Server service type, servers and blade servers can be selected. Only devices marked as Available and not previously assigned to a client or another order can be selected. The device must also be assigned to a location and must not be locked. This ensures proper resource tracking and client assignment.

After clicking Create & Activate Order, the order will be created, accepted and automatically activated. No activation actions (e.g., provisioning or OS installation) will be performed automatically at this stage.

Advanced order configuration, including setting service criteria, is only possible via the API or by editing a pending order. The quick order form available in the backend section is designed for fast assignment of a target device to a client.

# Step 2: Service Criteria

Important: Service criteria can only be edited if the order status is Pending. Once the order is activated or completed, this step becomes locked.

Based on the defined criteria, the system will automatically search for the most suitable server that matches the specified requirements.

  • Target Server Model – Select the desired server model (e.g., Dell R200) or Any Model.
  • Location – Choose the physical location for server placement.
  • Parts – Optionally define required components (e.g., RAM, HDD). Depending on the part types selected (e.g., RAM, CPU), the form dynamically displays relevant fields. These filters allow precise control over hardware provisioning and ensure compatibility with the client's requirements.
  • Metadata – Add required metadata (e.g., Firmware, Custom Metadata).
  • PDU Connection Verification – Set to Yes if the server must connect to a PDU.
  • Switch Connection Verification – Set to Yes if the server must connect to a switch.

For the Colocation service type, the criteria are the Target Colocation Model and the Location.

Click Continue To Next Step to proceed. For more advanced filtering with hardware types, refer to: Items, Types and Models.

# Step 3: Service Configuration

Important: Service configuration can only be edited if the order status is Pending. Once the order is activated or completed, this step becomes locked.

In the final step of order preparation, you define how the service will be configured once it’s activated.

This configuration determines what will be installed, how the server will be accessed, and what restrictions will apply. It is especially important if the server is being provisioned automatically after activation.

  • OS Template – Select an operating system installation template (optional). The selected OS will be installed when the Install Operating System action runs during service activation.
  • Hostname – The hostname that will be applied to the server (e.g., easydcim.local).
  • Username – The user account that will be set up during OS installation. For Windows templates, the username is always Administrator.
  • Password – The password for the above user.
  • Root Password – Root account password (not displayed for Windows templates).
  • Disk Layout – Disk layout used during OS installation. Displayed only when disk layout addons are available for the selected template.
  • Extras – First boot and post-install addons to apply. Displayed only when such addons are available for the selected template.
  • SSH Keys – SSH public keys of the client that will be authorized on the installed system.
  • Additional IP Allocation Mode – Choose whether the Additional IPs value is a Subnet Mask or a number of Individual IP Addresses.
  • Additional IPs – A CIDR mask such as /29 for the Subnet Mask mode, or an exact number such as 7 for the Individual IP Addresses mode. The value is used by the Assign Additional IPs provisioning action.
  • Monthly Traffic Limit – Set the total bandwidth cap for the server for the current month in GB.
  • Monthly Traffic Limit (IN) and Monthly Traffic Limit (OUT) – Set the incoming and outgoing bandwidth caps for the current month in GB.
  • Monthly Traffic Percentile Limit (Mbps) – Set the 95th percentile bandwidth limit for the current month in Mbps.
  • Client Access Level – Define how much access the client will have in the client portal (e.g., full access, limited access).

The OS, IP and traffic fields are displayed only when the OS Installation, IP Address Management and Usage Collector extensions are active. For the Colocation service type, the service configuration contains the Label of the colocation, the monthly traffic limit fields and the Client Access Level.

After clicking the Save Configuration button, you will be redirected to the placed order summary page.