Single License View

[TimothyBJacobs]

Admin page showing information about a particular license key.

License Key Information

Viewable Information

• Key
• Product
• Status
• Customer
• Max activations
• Expiry date
• Transaction

  Editable Information

• Status
• Max activations
• Expiry date

  Activations

A table of all activations of a particular license, including not only active activations, but deactivated and expired activations as well.

Viewable Information

• ID
• Location
• Status
• Activation Date
• Deactivation Date

  Editing

An active activation can be deactivated, and any deactivated activation can be reactivated. Additionally, an activation record can optionally be completely removed from the DB.

Creation

License keys can be activated for an installation location. This will be done using a regular text input for capturing the installation location, and an "Activate" button for triggering the remote activation.

[TimothyBJacobs]

We need to figure out the priority of information and actions.

I don't think the actual license key is the highest priority for user attention. The key is really just nonsense to the admin, it doesn't have any intrinsic meaning. Instead we should probably prioritize the customer and the product, since generally that will be a unique combination. The license key should be easily selectable though.

After that we should prominently feature the status of the license key, and color it appropriately.

Following that, we want to show the miscellaneous meta, like max activations, expiry date, and the originating transaction.

[TimothyBJacobs]

We also need to handle the editable information. There are two options.

1. (Ab)use content editable.
2. For status provide a dropdown, max activations make a number input, and add an expiry date input.

[TimothyBJacobs]

We could use a simple click to edit using jeditable. I think that is the best solution.

[TimothyBJacobs]

Completed.