Create a Client Command

In the //Create/Edit// phase, you can add, manage, and version client commands. You can also view the version history and the client command scripts. In addition, you can manage functions and global variables and use the [[package wizard>>doc:.Paket Wizard.WebHome]] to easily create client commands for software installation.

4

5

6

[[image:34_64_ClientCommands_ClientCommanderstellen_1337.png||alt="62_Solution_Bildbeschreibung_1284.png" data-xwiki-image-style-alignment="center"]]

Create Phase

To better manage Client Commands, a drop-down list can be used to display all existing Client Commands. Alternatively, only those Client Commands that are currently in the first phase (Create/Edit) are displayed. From here, Client Commands can be transferred directly to other phases by right-clicking and selecting the //Send to Phase// command. Once a Client Command has been released, it can no longer be sent to any other phases.

14

15

= Importing a Client Command =

16

17

To import a previously exported Client Command, select a folder in the //Create// phase and right-click on it. Use the context menu to access the import function. You can import a single Client Command (Import) or all Client Commands contained in a filesystem folder (Import Entire Folder). The imported client commands are stored in the selected folder.

18

19

= Exporting a Client Command =

20

21

To export a client command, open the version history (see Version History). Here, you can select the version to export. Alternatively, you can export the current version directly via the context menu of a client command in the Create/Edit phase (Export).

22

23

= Client Command Properties =

24

25

By default, client commands are displayed with their name, current version, status, properties, and the date of the last change. Certain properties are represented by icons:

26

27

|(((

28

[[image:XWiki.Images.WebHome@script_console.png||alt="Script_Console" data-xwiki-image-style-alignment="center" height="32" width="32"]]

29

)))|(((

30

Part of the Client Command is executed in the ACMP Console.

31

)))

32

|(((

33

[[image:XWiki.Images.WebHome@script_client.png||alt="Script_Client" data-xwiki-image-style-alignment="center" height="32" width="32"]]

34

)))|(((

35

Part of the Client Command is executed on the client.

36

)))

37

|(((

38

[[image:XWiki.Images.WebHome@clientcommandphase_release.png||alt="ClientCommandPhase_Release" data-xwiki-image-style-alignment="center" height="32" width="32"]]

39

)))|(((

40

The Client Command has at least one released version.

41

)))

42

|(((

43

[[image:SelectiveSync.ico||data-xwiki-image-style-alignment="center" height="32" width="32"]]

44

)))|(((

45

The Client Command can only be synchronized with selected file repositories.

46

)))

47

|(((

48

[[image:clientcommand_interactive.png||alt="ClientCommand_Interactive" data-xwiki-image-style-alignment="center"]]

49

)))|(((

50

The Client Command can be executed via the ACMP Kiosk.

51

)))

52

|(((

53

[[image:PassWord_Locked.ico||data-xwiki-image-style-alignment="center" height="32" width="32"]]

54

)))|(((

55

The Client Command is password-protected.

56

)))

57

58

As soon as a Client Command is selected, its additional properties are displayed on the right side of the tabular list. Fields marked with a checkbox have the corresponding property. The list is organized by categories.

59

If you have created or edited the Client Command, you can select it and use the Test button to move it to the second phase. Alternatively, you can use the context menu to approve a Client Command directly or move it to another phase.

Wiki source code of Client Command erstellen

Navigation

author	version	line-number	content
		1	{{aagon.floatingbox/}}
		2
		3	In the //Create/Edit// phase, you can add, manage, and version client commands. You can also view the version history and the client command scripts. In addition, you can manage functions and global variables and use the [[package wizard>>doc:.Paket Wizard.WebHome]] to easily create client commands for software installation.
		4
		5	{{figure}}
		6	[[image:34_64_ClientCommands_ClientCommanderstellen_1337.png\|\|alt="62_Solution_Bildbeschreibung_1284.png" data-xwiki-image-style-alignment="center"]]
		7
		8	{{figureCaption}}
		9	Create Phase
		10	{{/figureCaption}}
		11	{{/figure}}
		12
		13	To better manage Client Commands, a drop-down list can be used to display all existing Client Commands. Alternatively, only those Client Commands that are currently in the first phase (Create/Edit) are displayed. From here, Client Commands can be transferred directly to other phases by right-clicking and selecting the //Send to Phase// command. Once a Client Command has been released, it can no longer be sent to any other phases.
		14
		15	= Importing a Client Command =
		16
		17	To import a previously exported Client Command, select a folder in the //Create// phase and right-click on it. Use the context menu to access the import function. You can import a single Client Command (Import) or all Client Commands contained in a filesystem folder (Import Entire Folder). The imported client commands are stored in the selected folder.
		18
		19	= Exporting a Client Command =
		20
		21	To export a client command, open the version history (see Version History). Here, you can select the version to export. Alternatively, you can export the current version directly via the context menu of a client command in the Create/Edit phase (Export).
		22
		23	= Client Command Properties =
		24
		25	By default, client commands are displayed with their name, current version, status, properties, and the date of the last change. Certain properties are represented by icons:
		26
		27	\|(((
		28	[[image:XWiki.Images.WebHome@script_console.png\|\|alt="Script_Console" data-xwiki-image-style-alignment="center" height="32" width="32"]]
		29	)))\|(((
		30	Part of the Client Command is executed in the ACMP Console.
		31	)))
		32	\|(((
		33	[[image:XWiki.Images.WebHome@script_client.png\|\|alt="Script_Client" data-xwiki-image-style-alignment="center" height="32" width="32"]]
		34	)))\|(((
		35	Part of the Client Command is executed on the client.
		36	)))
		37	\|(((
		38	[[image:XWiki.Images.WebHome@clientcommandphase_release.png\|\|alt="ClientCommandPhase_Release" data-xwiki-image-style-alignment="center" height="32" width="32"]]
		39	)))\|(((
		40	The Client Command has at least one released version.
		41	)))
		42	\|(((
		43	[[image:SelectiveSync.ico\|\|data-xwiki-image-style-alignment="center" height="32" width="32"]]
		44	)))\|(((
		45	The Client Command can only be synchronized with selected file repositories.
		46	)))
		47	\|(((
		48	[[image:clientcommand_interactive.png\|\|alt="ClientCommand_Interactive" data-xwiki-image-style-alignment="center"]]
		49	)))\|(((
		50	The Client Command can be executed via the ACMP Kiosk.
		51	)))
		52	\|(((
		53	[[image:PassWord_Locked.ico\|\|data-xwiki-image-style-alignment="center" height="32" width="32"]]
		54	)))\|(((
		55	The Client Command is password-protected.
		56	)))
		57
		58	As soon as a Client Command is selected, its additional properties are displayed on the right side of the tabular list. Fields marked with a checkbox have the corresponding property. The list is organized by categories.
		59	If you have created or edited the Client Command, you can select it and use the Test button to move it to the second phase. Alternatively, you can use the context menu to approve a Client Command directly or move it to another phase.