The product details window displays the full configuration of a particular product. For a general description of what a product is, see the Products Window Documentation.
The Product Details window shows the various properties of a product, and also shows how the product relates to other databases - which programs are part of the product, what purchases have been made for the product, and what policies manage the product. At the top of the window you can set the name of the product. Note that Sassafras product definitions tend to include both the version and platform in the product name, even though version and platform are also distinct fields in the Information pane. This is simply so that listing the Name field alone will still allow the exact product to be understood.
This pane shows the basic properties of a product. It is not strictly necessary to populate any of this data, but it will make understanding the various products easier, and will allow you to filter by the various fields.
This pane contains a list of programs which are part of the product. You can double-click on any of the programs to see the full program details. Programs can be dragged into this list in order to make them a part of the product. Also in this list are two gray lines labeled “Applications” and “Utilities”. These lines separate the programs into two categories. Between the two lines are programs which are “Application Components” of the product. These programs are central to the product, and are the reason you would buy the product. When applications are launched, they may be observed or managed by KeyServer, depending on the settings in the Policies pane. On the other hand, programs below the “Utilities”line are “Utility Components”. These programs will appear in audit reports, but usage of a utility will never be observed or managed by KeyServer. Note also that a single product may ship with hundreds of executables, but many are so boring that they are not even worth associating with the product definition as utilities. By leaving them out, they will not clutter up an audit report.
This pane lists all the Policies which might manage the product. When there are multiple distinct policies listed to manage this one product, then the one listed with the longest blue bar at the left will be searched first. That is, when a user attempts to launch a program in the product, KeyServer will first attempt to grant permission to run from the policy with the longest blue bar. If this fails (e.g. perhaps all of these licenses are in use), it will move on and attempt to grant permission to run from the policy with the second longest bar, etc. When there are multiple policies in the list, they can be dragged relative to one another so that you can change the search order. Policies can also be dragged directly from the policies window into this list and positioned in the desired order - this will expand the scope of the dragged in policy to manage this product in addition to whatever other products it may already manage (so you will see a corresponding change in its Policy Details window in the Products pane).
Note that Manage policies always take precedence over policies of other types. If a client is in the scope of any Manage policy for a product, then an attempt to launch an Application Component of the product will always result in either a license grant or license deny - regardless of any Observe or Deny policies which might also have a Scope that includes this client. It is only when a client is outside the scope of ALL Manage policies that Observe and Deny policies are consulted. For this reason, KeyConfigure will not allow you to drag an Observe or Deny policy above a Manage policy.
This pane contains two text fields - Name and Address, which may be used however you like. You might use them for the publisher's name and address (physical, email, URL). Or you might use them for a name/address at your site.
This pane shows purchases of the product, and shows how many copies are currently entitled from each purchase.
This pane contains a single item, which is a free-form text field. You can use it for any information you want. It can be seen here in the KeyConfigure interface, and can also be used in custom reports.