Activate remote archived model

Makes the EDMserver activate an archived model in a remote EDMdatabase.
There are a maximum number of models that may be simultaneously active within an EDMdatabase. Databases that need to store great numbers of models may exceed this capacity. To solve this, models may be temporarily archived, thereby releasing capacity in the EDMdatabase. Models that are rarely used need not be permanently active in the EDMdatabase.
For an EDMuser to activate a model, he needs at least read access to it.
Arguments:

Server context name:

Specify name of server context.
When activating the Select button, the name of all defined server contexts will be displayed in the related selection list.

Remote archived model name:

Specify the name of the archived model(s) to activate. Model names are case sensitive.

Remote repository:

Specify the name of the remote repository(ies) to search for models. Repository names are case sensitive.
When activating the Select button, the name of all open repositories will be displayed in the related selection list.

Remote model:

Specify the name of the model(s). Model names are case sensitive.

Options:

accumulating command output:

A global option that appends the command output to the EDMsupervisor output window. Otherwise the output window is refreshed and only the last command output is displayed.

match selected input:

A global option that specifies that only items that partly or exactly matches the string in the related argument input field when activating a Select button, will be in the selection list. An empty (blank) string will match all items.

keep archived model:

The model will be activated but remains archived.

restore model admin data:

Use this option to restore the models original administration data. If this option is not used, the activated model will have its administration data set as if it were created by the user.

skip step id model:

Models that are imported with the [KEEP_STEP_IDENTIFIERS] option and later archived without the [SKIP_STEP_ID_MODEL] will have their step Id info archived in separate accompanying models. By default, step Id models will be activated together with the data models. Use this option to prevent activation of these step Id models.