To open advanced configuration: |
|
This function lets you:
NOTE: the function is only enabled if the user has Agent configuration authorization.
NOTE: the advanced configuration is not available for the soldier level agent.
CAUTION: when returning from advanced configuration to basic configuration, the advanced configuration will be lost and the default basic configuration will be restored.
For a factory, after completing its configuration, compile it to obtain the agent to be installed.See "Compiling a factory"
For an agent, after completing its configuration, simply save the new configuration. At the next synchronization, the new configuration will be sent to the agent.
This is what the page looks like:
Area | Description | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 |
RCS menu. |
||||||||||||||||||||||||||
2 |
Scroll bar |
||||||||||||||||||||||||||
3 |
Window toolbar. Descriptions are provided below:
|
||||||||||||||||||||||||||
4 |
Event area. STARTUP and SYNC events are by default. |
||||||||||||||||||||||||||
5 |
Action area. STARTUP and SYNC actions are enabled by default. |
||||||||||||||||||||||||||
6 |
Modules area. Modules vary by desktop or mobile device. |
||||||||||||||||||||||||||
7 |
RCS status bar. |
For interface element descriptions See "Shared interface elements and actions".
For more information on the advanced configuration see "What you should know about advanced configuration".
To create a simple sequence, to collect evidence when an event occurs:
Step | Action |
---|---|
1 |
Creating an event:
|
2 |
Creating an action:
|
3 |
Link the event to the action, then the action to the desired module:
|
4 |
Click Save: the configuration is ready to be compiled (if factory) or transmitted to the device at the next synchronization (if agent). |
To create a complex sequence, to start collecting evidence, run a sub-action and enable/disable an event, when an event occurs:
Step | Action |
---|---|
1 |
Creating an event:
|
2 |
Creating an action and setting sub-actions:
|
3 |
Connecting the event to the action:
|
4 |
Connecting the action to the module:
Tip: Drag multiple arrows if multiple modules have to be enabled. For an action that requires an event to be enabled/disabled:
|
5 |
Click Save: the configuration is ready to be compiled (if factory) or transmitted to the device at the next synchronization (if agent). |
RCS9.5 | User manual | © COPYRIGHT 2014