Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Macro name changed from html to html-bobswift during server to cloud migration processing.

...

Field

Description

Default Event Handler Options

If no triggered handler is specified, use the following
The ID of a stored event handler that will be executed when an occurrence of an event is triggered, if no such handler is specified in that event's definition. This value may be left blank to indicate that no action should be taken by default for triggered event occurrences.
 
If no reject handler is specified, use the following
The ID of a stored event handler that will be executed when an occurrence of an event is rejected, if no such handler is specified in that event's definition. This value may be left blank to indicate that no action should be taken by default for rejected event occurrences.
 
If no expired handler is specified, use the following
The ID of a stored event handler that will be executed when an an event expires, if no such handler is specified in that event's definition. This value may be left blank to indicate that no action should be taken by default for expired events.
 
Default script type
Specifies the how a script will be interpreted by the operating system for an event handler with an action type of SCRIPT, if no script type is specified in the event handler definition.
 
Maximum acceptable return code
Lists the types of events supported by UEM Server. Default configuration options that are specific to the selected event type may be updated by selecting the Edit... button.

Default Component Name

Specifies the event driven UEM Server component (that is, those components with a component type of "uems") to which an event will be assigned if no component name is specified when the event definition is created. When this event driven UEM Server component starts, it will load and monitor those events that have been assigned to it. An event may not be assigned to a demand-driven UEM Server component (that is, those components with a component type of "uemd"), and only event-driven UEM Server components are listed here.

Tracking interval

Specifies the frequency with which a tracked event occurrence will be tested for completeness, if no such value is provided in the event definition. A value of 0 indicates that an event occurrence will not be tracked, and will be tested for completeness as soon as the occurrence is detected by UEM Server.

Set event-specific options

Lists the types of events supported by UEM Server. Default configuration options that are specific to the selected event type may be updated by selecting the Edit... button.

Edit Button

Displays a dialog from which configuration options that are specific to the selected event type may be updated.
 

 
Rename the file for a triggered event occurrence
Specifies the format that UEM Server should use when renaming a file for a triggered event occurrence, provided no such value was specified in the event definition. The value entered here may consist of literal values or one or more the variables listed below which UEM Server with applicable run-time values.

Html bobswift
<ul>
<li> $(compname) <br>
the name of the UEM Server component
<li>  $(compid) <br>
the ID of the UEM Server component instance
<li> $(date) <br>
the current date, in yyyymmdd format
<li> $(time) <br>
the current time, in hhmmss format 
<li> $(origname) <br>
the original file name 
<li> $(origext) <br>
the file's original extension
<li> $(seqnum) <br>
a value that begins at 1 and is incremented by 1 as each file is renamed by a given instance of UEM Server.  
</ul>

Minimum file size
Specifies the default file size a tracked file must be before it can be considered complete. That is, if a tracked file is tested for completeness and its file size is the same on two consecutive checks, the file will not be considered complete until it grows to at least the size specified here. This value may be overridden in the event definition.

...