Purchases Window

The Purchases window lists all of the purchases which have been entered (or imported) into KeyServer. Entering purchase information allows you to have an accurate count of entitlements. KeyServer will do a correct count of entitlements, properly reflecting expired entitlements, upgrades which rely on a prior entitlement, etc. Careful entry of purchases will mean that you always have an up-to-date summary of entitlements.

Purchases Window

Right Hand Side

The right hand side shows a list of purchases, with some of the most essential properties displayed. Purchases are very complex, and can be hard to fully understand without looking at the full Purchase Details. One particular subtlety to notice is the difference between the Product and Effective Product columns. Usually these will both show the same product, which is the product which was purchased. However, some purchases may include Future Upgrade rights, which means that a future version of the product is entitled by the purchase of the earlier version. During reconciliation of purchases and policies, KeyConfigure will only count a purchase under a single product - so for a purchase with future upgrade rights, you can explicitly decide that the purchase will now “count” towards entitlements of the newer product. This decision to upgrade is done in the Reconcile Window for a single Product.

Left Hand Side

As in other main windows, the left hand side allows the items displayed on the right to be filtered in different ways. Each Purchase can belong in a single Folder, mainly just for convenience in filtering the purchases window or report results. Filters are just like in other windows, and are described in greater detail in the Filters documentation.

Context Menu Actions

Right-clicking a Purchase in the Purchases Window allows you to Reconcile, which will bring up the Reconcile Window for the product associated with this purchase.

Right-clicking anywhere in the filters section allows you to create a new filter (New Filter...).

Drag and Drop Actions

Purchases in the Purchases Window can be Dragged and Dropped to the following locations, among others:

Importing purchases

Purchases can be imported from a tab delimited text file or from a CSV. To start an import, drag the text or CSV file from Windows Explorer (or Mac Finder) directly into the Purchases window within KeyConfigure. You will see a window like this:

Select import instructions

Fields within the purchases text file can be mapped to properties in the KeyServer Purchases Database in many ways. You must specify how to do this mapping. Initially the instructions include some common file formats used by software vendors and resellers. If you select one of the pre-defined instructions you will be able to see a preview of each record before it is imported. Alternatively you can define your own import instructions by clicking New. If you click New you will see a window showing field names for the KeyServer Purchase Database on the left, and field names / sample data as discovered in the import file on the right.

To configure your purchase instructions, drag fields from the list on the right into the list on the left. This allows you to specify what database field(s) to copy each value from the import file into. You can copy a single value from the text file into multiple database fields. You can also concatenate two values from the text file into a single database field. Note that the PO# itself should be put into purchaseOrderId. The field named orderResellerPO is there to record additional data but is not the primary PO#. Once you start dragging fields from right to left you should have something like this.

Partially configured instructions

Once you have chosen instructions (either predefined or defined by you), click OK, and KeyConfigure will start to process the text file. You will see a preview of the first record. Each field in the Purchase database will show the value it will receive as a result of the instructions.

Importing a purchase record

The screenshot above is using instructions that only specify a few fields. Notice that certain fields will be given default values. In particular, every purchase must have a purchaseOrderID. Here since no PO# has been associated from the import file, the import process chooses a text value for the purchaseOrderID field, which is based on the date and time of import. After looking at this preview, you might decide to Stop and edit your instructions some more before importing. If the instructions are correct, you can step through the purchases, either clicking Next to import the current record and move on to the next, or Skip. Alternatively you can click Complete in order to import all of the remaining records. You should always check that an import has recorded all data accurately, but you can either do this as you are importing, or once the import completes.