Procedure for unregistering a license key does not match interface

[mbakeranalecta]

The topic on unregistering a license does not match the interface. file:///C:/Users/Mark%20B/oXygen/userguide/DITA/out/webhelp/tasks/unregister-license-key.html

In the interface, there is no second Register step in the menu tree and no reset button. The license key area is already empty, so it is not clear if you are supposed to empty it in order to unregister a license -- apparently not, since it is empty in my licensed copy.

I can't figure out what the correct procedure is in the current interface.

[georgebina]

Hi Mark,

Please note that the oXygen licenses are not transferable from one user to another - the initial version of the topic talks about transferring a license from one computer to another (for example if you have an old computer that you do not want to use anymore). I think you should review the updated to take this into account.

Thanks, George

[georgebina]

That section is profiled but again the profiling condition sets are affected by the project move, we need the Options->Preferences -- Editor / Edit modes / Author / Profiling/Conditional Text -- profiling condition sets updated to use ${pd}/.ditaval instead of ${pd}/DITA/.ditaval. Then, focusing on a specific deliverable should show the actual menu path. The last Register entry should be also profiled with product="editorEclipse authorEclipse developerEclipse".

[georgebina]

The procedure is to press Ok in that dialog, with the license key empty. oXygen will display another dialog that will ask you if you want to reset the license information or keep using the current license.

[georgebina]

Probably we should display the current license key information in the license key area and if the user removes that then we will double check and ask him to confirm that he wants the license to be removed. I will log this as an issue.

[georgebina]

Alternatively, we should make the Un-register action explicit.

[mbakeranalecta]

I would definitely recommend making it explicit. Explicit is better than implicit, particularly for operations that are only performed rarely.

If the user enters a licence key in a field, that field should always show the licence key, or the user will wonder where it has gone, and may wonder if the product is still licensed. (People interpret a change in appearance as a change in state.)

If the user needs to perform an atomic action (no options or decision points), they should be able to perform it in one step, so an explicit Unregister button would be the best way to do this.

[mbakeranalecta]

Also, both the terms "Unregister" and "Reset" are used in this scenario. This can create confusion. In this case, I think the action should be described as "Unregister" in all cases.