Managed Software Settings

Within the system settings for Managed Software, you can define basic configurations, set up custom test and release processes, and change the start conditions for Scheduled Server Tasks.

4

The settings can be accessed either directly from the ribbon bar of the open Solution //Managed Software //> //Open Settings //or via the system (//System// > //Settings// > //Managed// //Software//).

5

6

= Customize Options =

7

8

In the //Options// section, you can customize the general behavior of Managed Software.

9

10

|**Setting**|**Description**

11

|Managed Software cleanup of unneeded software versions|If a version has not been used for longer than the specified time, the downloaded Managed Software file is automatically deleted. The version is then displayed in the overview with the status “No Ring.” Under “Details,” it also shows “not downloaded.”

12

Enable the checkbox if you want to use the cleanup option and specify the number of days after which this should occur. The default is 14 days.

13

|Behavior with Newer Installed Software Versions|(((

14

This option allows you to specify how the system should handle newer installed versions. You can choose between the following two options:

15

16

* Replace newer versions with the current Managed Software version,

17

* Keep newer software versions

18

19

If clients are using a newer version of a software program than the current version (e.g., due to manual installation on the client), the newer version can either be retained or automatically replaced with the current version.

20

)))

21

|Standard for Storing the Advanced Client Log|(((

22

Basic setting for when an extended log should be saved. The extended log allows you to view detailed information about an error when one occurs.

23

24

You can choose from three logging methods:

25

26

* Never save the extended log,

27

* Save the extended log only when an error occurs,

28

* Always save the extended log.

29

30

31

Please note that if data is to be stored continuously, sufficient storage resources must be available.

32

33

34

The logging method applies to new Managed Software jobs and is also used during job executions in the acmp Kiosk.

35

)))

36

37

[[Overview of Options in the Managed Software Settings>>image:69_Managed Software Einstellungen Optionen_1045.png]]

38

39

= Define the Test and Release Process =

40

41

Under the menu item //Testing and Release//, you can create custom test and release processes. Here, each package is assigned a specific timeframe for when it should move on to the next testing phase. The release process can be configured individually for each software package, or multiple programs can be grouped together into a single release process.

42

43

By default, every software package is assigned to the existing “//Default//” test and release process. This includes all subscribed software that has not been assigned to any other ring.

44

45

46

Please note that, in the default process, each software package is moved directly to the Release Ring and is thus released. You can prevent this by assigning the software packages to your custom and individualized test and release processes.

47

48

49

The workspace is divided into two sections: On the left, you will find the processes that have already been created, and on the right, a detailed view of the current selected process, divided into two tabs: //Details// and //Processes//. The Details tab contains general information about the selected test and release process and a list of the linked software packages. The Processes tab displays the settings for the distribution rings.

== Create a Test and Release Process ==

54

55

To create a new release process, click the button labeled [[image:1790150652713-617.png]] //Add Test and Release Process//. A multi-page wizard will open, guiding you step by step through the creation of your custom test and release process.

56

57

First, on the first page under //General//, enter a name and an optional description for the process. Then click //Next >//.

58

59

[[Add a test and release process (general)>>image:69_Managed Software Test- und Freigabeprozess Wizard 1_801.png]]

60

61

In the second step, you have the option to add the software packages to which your test and release process should apply.

62

63

To do this, click [[image:1790150685226-624.png]] //Subscribe to Software Package// and a new dialog box will open where you can select the software packages you want to add to this process. If you want to select multiple packages at once, you can do so by selecting multiple items (Ctrl + left-click). To do this, hold down the Ctrl key and select the desired packages. Confirm your selection by clicking //OK//. If you have selected the wrong package, you can remove it by clicking the button on the right labeled [[image:1790150685226-155.png]] //Unsubscribe from Software Package//. Now click again //Next >//.

64

65

[[Define Content for the Test and Release Process>>image:69_Managed Software Test- und Freigabeprozess Wizard 2_830.png]]

66

67

In the final step, you must now configure the test and release rings. Here, you specify exactly how the software packages should progress through the test and release process. By default, all rings are skipped, and the software package is moved directly to the Release Ring,

68

If you want to use a test ring, you can move the software packages manually or have them automatically moved to the next ring after a specified number of days.

69

70

[[Configure the Test and Release Ring>>image:69_Managed Software Test- und Freigabeprozess Wizard 3_830.png]]

71

72

Exit the configuration of the process by clicking //Done//. The new test and release process will now appear in the list on the main page.

73

74

== Edit or delete a test and release process ==

75

76

f you want to make changes to a test and release process after it has been created, select the entry and click [[image:1790150759262-147.png]] //Edit//. Change the sections or details (e.g., rename the process, add new subscriptions or deselect existing ones, and customize the test and Release Ring), then save the changes in the toolbar. To delete a process, click [[image:1790150759263-833.png]] //Delete//.

Wiki source code of Einstellungen der Managed Software

Navigation

author	version	line-number	content
		1	{{aagon.floatingbox/}}
		2
		3	Within the system settings for Managed Software, you can define basic configurations, set up custom test and release processes, and change the start conditions for Scheduled Server Tasks.
		4	The settings can be accessed either directly from the ribbon bar of the open Solution //Managed Software //> //Open Settings //or via the system (//System// > //Settings// > //Managed// //Software//).
		5
		6	= Customize Options =
		7
		8	In the //Options// section, you can customize the general behavior of Managed Software.
		9
		10	\|Setting\|Description
		11	\|Managed Software cleanup of unneeded software versions\|If a version has not been used for longer than the specified time, the downloaded Managed Software file is automatically deleted. The version is then displayed in the overview with the status “No Ring.” Under “Details,” it also shows “not downloaded.”
		12	Enable the checkbox if you want to use the cleanup option and specify the number of days after which this should occur. The default is 14 days.
		13	\|Behavior with Newer Installed Software Versions\|(((
		14	This option allows you to specify how the system should handle newer installed versions. You can choose between the following two options:
		15
		16	* Replace newer versions with the current Managed Software version,
		17	* Keep newer software versions
		18
		19	If clients are using a newer version of a software program than the current version (e.g., due to manual installation on the client), the newer version can either be retained or automatically replaced with the current version.
		20	)))
		21	\|Standard for Storing the Advanced Client Log\|(((
		22	Basic setting for when an extended log should be saved. The extended log allows you to view detailed information about an error when one occurs.
		23
		24	You can choose from three logging methods:
		25
		26	* Never save the extended log,
		27	* Save the extended log only when an error occurs,
		28	* Always save the extended log.
		29
		30	{{aagon.infobox}}
		31	Please note that if data is to be stored continuously, sufficient storage resources must be available.
		32	{{/aagon.infobox}}
		33
		34	The logging method applies to new Managed Software jobs and is also used during job executions in the acmp Kiosk.
		35	)))
		36
		37	[[Overview of Options in the Managed Software Settings>>image:69_Managed Software Einstellungen Optionen_1045.png]]
		38
		39	= Define the Test and Release Process =
		40
		41	Under the menu item //Testing and Release//, you can create custom test and release processes. Here, each package is assigned a specific timeframe for when it should move on to the next testing phase. The release process can be configured individually for each software package, or multiple programs can be grouped together into a single release process.
		42
		43	By default, every software package is assigned to the existing “//Default//” test and release process. This includes all subscribed software that has not been assigned to any other ring.
		44
		45	{{aagon.warnungsbox}}
		46	Please note that, in the default process, each software package is moved directly to the Release Ring and is thus released. You can prevent this by assigning the software packages to your custom and individualized test and release processes.
		47	{{/aagon.warnungsbox}}
		48
		49	The workspace is divided into two sections: On the left, you will find the processes that have already been created, and on the right, a detailed view of the current selected process, divided into two tabs: //Details// and //Processes//. The Details tab contains general information about the selected test and release process and a list of the linked software packages. The Processes tab displays the settings for the distribution rings.
		50
		51
		52
		53	== Create a Test and Release Process ==
		54
		55	To create a new release process, click the button labeled [[image:1790150652713-617.png]] //Add Test and Release Process//. A multi-page wizard will open, guiding you step by step through the creation of your custom test and release process.
		56
		57	First, on the first page under //General//, enter a name and an optional description for the process. Then click //Next >//.
		58
		59	[[Add a test and release process (general)>>image:69_Managed Software Test- und Freigabeprozess Wizard 1_801.png]]
		60
		61	In the second step, you have the option to add the software packages to which your test and release process should apply.
		62
		63	To do this, click [[image:1790150685226-624.png]] //Subscribe to Software Package// and a new dialog box will open where you can select the software packages you want to add to this process. If you want to select multiple packages at once, you can do so by selecting multiple items (Ctrl + left-click). To do this, hold down the Ctrl key and select the desired packages. Confirm your selection by clicking //OK//. If you have selected the wrong package, you can remove it by clicking the button on the right labeled [[image:1790150685226-155.png]] //Unsubscribe from Software Package//. Now click again //Next >//.
		64
		65	[[Define Content for the Test and Release Process>>image:69_Managed Software Test- und Freigabeprozess Wizard 2_830.png]]
		66
		67	In the final step, you must now configure the test and release rings. Here, you specify exactly how the software packages should progress through the test and release process. By default, all rings are skipped, and the software package is moved directly to the Release Ring,
		68	If you want to use a test ring, you can move the software packages manually or have them automatically moved to the next ring after a specified number of days.
		69
		70	[[Configure the Test and Release Ring>>image:69_Managed Software Test- und Freigabeprozess Wizard 3_830.png]]
		71
		72	Exit the configuration of the process by clicking //Done//. The new test and release process will now appear in the list on the main page.
		73
		74	== Edit or delete a test and release process ==
		75
		76	f you want to make changes to a test and release process after it has been created, select the entry and click [[image:1790150759262-147.png]] //Edit//. Change the sections or details (e.g., rename the process, add new subscriptions or deselect existing ones, and customize the test and Release Ring), then save the changes in the toolbar. To delete a process, click [[image:1790150759263-833.png]] //Delete//.