Wiki source code of Compliance
Last modified by Sabrina V. on 2024/10/08 11:35
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | {{aagon.priorisierung}} | ||
| 2 | 80 | ||
| 3 | {{/aagon.priorisierung}} | ||
| 4 | |||
| 5 | {{aagon.floatingbox/}} | ||
| 6 | |||
| 7 | A recalculation of the compliance is needed to calculate the status of the products. The calculation checks whether the number of existing licenses matches the actual usage. | ||
| 8 | |||
| 9 | You can see whether this is the case by looking at the status of the license in the workspace: | ||
| 10 | |||
| 11 | |**Symbol**|**Status**|**Explanation** | ||
| 12 | |[[image:https://doc.aagon.com/bin/download/64/ACMP-Solutions/Lizenzmanagement/Compliance/WebHome/63_LicMan_Vollst%C3%A4ndig%20lizenziert_311.png?width=250&height=18&rev=1.1||alt="63_LicMan_Vollständig lizenziert_311.png" height="18" width="250"]]|Fully licensed |Sufficient licenses are assigned to the product to cover usage. | ||
| 13 | |[[image:https://doc.aagon.com/bin/download/64/ACMP-Solutions/Lizenzmanagement/Compliance/WebHome/index_002.png?width=250&height=21&rev=1.1||alt="index_002.png" height="21" width="250"]]|Not enough licenses assigned|There are insufficient or no licenses assigned to the product. | ||
| 14 | |[[image:https://doc.aagon.com/bin/download/64/ACMP-Solutions/Lizenzmanagement/Compliance/WebHome/index_004.png?width=250&height=21&rev=1.1||alt="index_004.png" height="21" width="250"]]|Can use right to new version|An Upgrade to a new software version has been found in the DNA catalogue. The license can then be moved and upgraded. | ||
| 15 | |[[image:https://doc.aagon.com/bin/download/64/ACMP-Solutions/Lizenzmanagement/Compliance/WebHome/index_005.png?width=250&height=21&rev=1.1||alt="index_005.png" height="21" width="250"]]|Clear|There are no licenses or consumers assigned to this product. | ||
| 16 | |[[image:https://doc.aagon.com/bin/download/64/ACMP-Solutions/Lizenzmanagement/Compliance/WebHome/index_006.png?width=250&height=15&rev=1.1||alt="index_006.png" height="15" width="250"]]|A calculation error has occurred|An error has occurred during calculation, which means that the usage cannot be calculated. | ||
| 17 | |[[image:https://doc.aagon.com/bin/download/64/ACMP-Solutions/Lizenzmanagement/Compliance/WebHome/index.png?width=250&height=20&rev=1.1||alt="index.png" height="20" width="250"]]|Licensed for concurrent use|The licenses are limited by the software itself. | ||
| 18 | | |License does not have enough base licenses|There are more Upgrade/Update licenses than base licenses available. | ||
| 19 | |||
| 20 | = Perform a Compliance Recalc = | ||
| 21 | |||
| 22 | {{aagon.infobox}} | ||
| 23 | Please note that a full and correct licence recalculation can only be performed when both the products and the licenses have been neatly linked and all necessary info has been entered! | ||
| 24 | {{/aagon.infobox}} | ||
| 25 | |||
| 26 | You run the compliance recalculation by selecting //Recalculate// in the ribbon bar. The recalc compares the usage and availability of licenses including coefficients and generates a balance sheet. Note that for DNA2, the entire DNA2 Recalculation is already included in //Recalculate//. | ||
| 27 | |||
| 28 | Use Full Recalc to do a complete ACMP DNA Recalculation. The Full Recalc function only applies to DNA and not to DNA2. | ||
| 29 | |||
| 30 | = Customize the licence consumption = | ||
| 31 | |||
| 32 | To assign licenses directly to a consumer, click //Customize //in the ribbon bar. A new window opens, divided into the tabs Assignments and Priorities. | ||
| 33 | |||
| 34 | {{aagon.infobox}} | ||
| 35 | Note that to display changes, a Recalc must be performed! | ||
| 36 | {{/aagon.infobox}} | ||
| 37 | |||
| 38 | {{aagon.infobox}} | ||
| 39 | Note that consumers with manual license assignments are always prioritised higher than consumers with automatic assignments! | ||
| 40 | {{/aagon.infobox}} | ||
| 41 | |||
| 42 | == Assignments == | ||
| 43 | |||
| 44 | This tab displays all consumers, both automatic and manual, for the selected product. Here you have the option of manually assigning a specific license to a specific consumer. An exact assignment would normally not appear in the license calculation, since the licenses are assigned to the consumers randomly. | ||
| 45 | |||
| 46 | You can manually assign a license to each consumer or enter a new license. To do this, click on the arrow in the Manual Assignment column. | ||
| 47 | |||
| 48 | If the consumer is to be ignored in the usage calculation, enable the corresponding checkbox. You can now enter the reason for ignoring in the Reason column. Manual assignment of a license is now no longer possible for this consumer and the consumer no longer generates any usage in compliance for the product. | ||
| 49 | |||
| 50 | == Priorities == | ||
| 51 | |||
| 52 | Only consumers who have been manually assigned a license in the //Assignments// tab appear in the tab. These manual assignments can be prioritised. This means that in the event of under-licensing, the consumers that have been prioritised higher will receive a license, so that a consumer with a lower priority may not receive a license. | ||
| 53 | |||
| 54 | To set the structure, use the arrows on the right side of the window. | ||
| 55 | |||
| 56 | When you have made the assignments and set the priorities, close the window with //Done//. |