com.prosyst.mprm.admin.rule

Interface DeviceExecStatus

All Known Subinterfaces:

DeviceRuleStatus, DeviceTaskStatus

public interface DeviceExecStatus

Represents abstract execution status of given device. Objects of type DeviceExecStatus are never directly instantiated, but rather its extensions - DeviceTaskStatus and DeviceRuleStatus are returned by the system to represent device execution statuses summarized respectively for Tasks and Rules. DeviceExecStatus-s related to Tasks could be obtained via methods Task#listInvolvedDevices(State), Task.getInvolvedDeviceState(String, String) and RuleEngine#listTasksForDevice(String, String, State). Respectively, DeviceExecStatus-s related to Rules could be obtained via Rule#listInvolvedDevices(State), Rule.getInvolvedDeviceState(String, String) and RuleEngine#listRulesForDevice(String, String, State). When a DeviceExecStatus is related to Task:

its #getTaskId() method indicates the id of the relevant Task, and its #getRuleId() returns null. Respectively, when a DeviceExecStatus is related to Rule: its #getTaskId() returns null, and its #getRuleId() method indicates the id of the relevant Rule. The execution status is formed as a summary of all execution items (see #getExecItems()) reported for this device. Partial executions - represented by each DeviceExecItem from the contained list - are produced by different sub-executions from the Task-action groovy script: method executions to Script Services may produce result report, each of which would be represented as DeviceExecItem. closures executions produce separated DeviceExecItem items in the list. one DeviceExecItem is always present for the execution/evaluation of the groovy script itself.