Wiki source code of Compliance

Last modified by Steffi F on 2025/05/23 11:17

version	line-number	content
1.1	1	{{aagon.floatingbox/}}
	2
34.1	3	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.
1.1	4
34.1	5	You can see whether this is the case by looking at the status of the license in the workspace:
1.1	6
34.1	7	\|Symbol\|Status\|Explanation
	8	\|[[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.
	9	\|[[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.
	10	\|[[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.
	11	\|[[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.
	12	\|[[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.
	13	\|[[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.
	14	\| \|License does not have enough base licenses\|There are more Upgrade/Update licenses than base licenses available.
1.1	15
34.1	16	= Perform a Compliance Recalc =
1.1	17
	18	{{aagon.infobox}}
34.1	19	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!
1.1	20	{{/aagon.infobox}}
	21
34.1	22	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.
1.1	23
34.1	24	Use Full Recalc to do a complete ACMP DNA Recalculation, updating the entire DNA2 catalog.
1.1	25
34.1	26	= Customize the licence consumption =
1.1	27
34.1	28	To assign licenses directly to a consumer, click //Customize //in the ribbon bar. A new window opens, divided into the tabs Assignments and Priorities.
1.1	29
	30	{{aagon.infobox}}
34.1	31	Note that to display changes, a Recalc must be performed!
1.1	32	{{/aagon.infobox}}
	33
	34	{{aagon.infobox}}
34.1	35	Note that consumers with manual license assignments are always prioritised higher than consumers with automatic assignments!
1.1	36	{{/aagon.infobox}}
	37
34.1	38	== Assignments ==
1.1	39
34.1	40	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.
1.1	41
34.1	42	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.
1.1	43
34.1	44	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.
1.1	45
34.1	46	== Priorities ==
1.1	47
34.1	48	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.
1.1	49
34.1	50	To set the structure, use the arrows on the right side of the window.
1.1	51
34.1	52	When you have made the assignments and set the priorities, close the window with //Done//.