Action: RemoveLibrary

Function: The command removes a library or placeholder from a Library Manager.

Call: Library test driver

Tab: Configuration

Library or placeholder	Name of the library or placeholder Library name (for absolute or asterisk referencing) Example: `Default` Placeholder name (with prepended `#`) As a result, the Version and Company settings are blank. Requirement: The libraries are also referenced by means of placeholders in the Library Manager. Example: `#Test Collection Feature ABC` : Opens the Find Library dialog
Version	Version of the library Absolute version information Requirement: The library is also referenced absolutely in the Library Manager. Example: `4.0.0.0` `*` Asterisk referencing to always reference the newest version Requirement: The library is also referenced in the Library Manager by means of an asterisk. Blank (already determined by placeholders)
Company	Company (vendor) of the library Example: `Company ABC` Blank (already determined by placeholders)
Library Manager path	Object path of the Library Manager in the project which is modified If the library to be removed is not defined in the Library Manager, then the action fails. Example: `Device.Plc Logic.Application.LibraryManager` : Copies the settings of an object, which is selected in the device tree, to the input field : Opens a list box with suitable objects which are available in the open project Hint: You can also drag the settings of a selected object to the input field (Drag&Drop).
	Opens a dialog for selecting a library from the Library Manager that is specified in Library Manager path When you select a library there, the settings are applied to the tab. Requirement: The Library Manager exists in the open project.

Tab: Parameters

The parameters defined on the Parameters tab are used to exchange values between test script variables and parameters of test actions. Parameters can be used as placeholders on the Configuration tab. For this, the name of the parameter is set in braces in the configuration dialog. Example: {name}.

Tip

Variables defined globally in the script (with the prefix $GLOBALS.) can be used directly in the test action. It is not necessary to use input parameters for passing. Using output parameters is necessary for writing global variables.

Input parameters: When executing the test action, the values of the test script variables are passed to the input parameters of the test action and can be used in the configuration of the test action.
Output parameters: When executing the test action, the values of the output parameters of the test action are passed to the test script variables and can be used (for example, in other test actions).
Name	Name of the input/output parameter This name is defined in addition to the variable name to identify the origin of the parameter when it is passed to another script. During the test run, this name is displayed as the Outer name on the Variables (scope #<n>) tab in the Test progress window. Background: When a script `A` calls another script `B`, and its variable `x` passes `y` as a parameter to the script `B`, then the parameter `y` is the variable `y` from the point of view of script `B`. To see that this variable is recognized as variable `x` "outside" of script `B`, there is the Name column ("Outer name"). The variable `y` has the name `x` in the scope pf script `B` because it has been passed as variable `x` to the parameter `y` in the scope of the calling script `A`.
Variable	Name of the test script variable Example: `TS_CaseA_Result`
Move Up	Moves the selected variable one line up
Move Down	Moves the selected variable one line down
Remove	Removes the selected variable from the list