| Panel | ||||
|---|---|---|---|---|
|
...
The Universal Extension developer will create a new Universal Extension-based Universal Template, declaring:
Task fields required for defining and launching the process through the Universal Extension.
Task Instance fields required for capturing data coming back throughout the life-cycle of the Universal Extension process.
Task Instance commands, and their supported status(es), that can be executed through the Universal Extension.
...
| Note | ||
|---|---|---|
| ||
It is important to review the Universal Agent configuration option, EXTENSION_ACCEPT_LIST, if you want to prohibit an agent from accepting deployment of any extension or if you want to limit deployment to specific extensions. This allows full customization of the deployment approach, allowing agent extension configuration to be tailored based on corporate policy. For automatic deployment of Universal Extensions to all registered agents, ensure that your agents are all installed with an accept any extension (default) configuration. |
...
On registration deployment of accepted Universal Extensions will commence immediately upon successful agent registration, depending on the configuration of the EXTENSION_DEPLOY_ON_REGISTRATION UAG configuration option.
...
If on-demand deployment of an extension is required, the task instance will transition to the Queued Status with the Deploy Extension Status Attribute.
Upon successful deployment, the Deploy Extension Status Attribute will be cleared and the task instance will transition to the Running Status.
If the deployment is unsuccessful, the the Deploy Extension Status Attribute will be cleared and the task instance will transition to the Start Failure Status.
If an extension cannot be deployed to the destination agent due to the extension not being an accepted extension, the task instance will transition to Undeliverable Status.
Once the agent configuration has been updated, and the agent restarted, on-demand deployment can commence and the task instance will transition to Running Status upon successful deployment, as described above.
...
| Name | Unique command name, adhering to the same naming convention as a Universal Template field name. |
| Label | User friendly display name for the command, to be displayed within the client. |
| Supported Status(es) | Specifies the task instance status (or statuses) that the dynamic command should be enabled for. |
| Dependent Fields | The administrator can select zero or more Universal Template fields that are required by the command. The values of those fields will be included in the command request. |
| Timeout | Specifies an optional command timeout, in seconds, if the command requires longer than the System-level default of 60 seconds. If the controller Controller (server) does not receive a command response from the Extension prior to the timeout being reached, a timeout message will be sent to the client (user interface), and displayed in the console Console: Command "command-name" on task instance "instance-name" with id instance-uuid timed out. |
| Execution Option | Specification for whether the command runs out-of-process execution or in-process execution. |
| Asynchronous | If Execution Option is in-process; Specification for whether the command runs synchronously or asynchronously. |
...