Cisco Cisco MediaSense Release 9.0(1) Developer's Guide

Page of 136
RUNNING
In this state, the job started execution successfully and continues to execute.
COMPLETED
Job was completed successfully.
Note: Job completed successfully does not mean all operations are successful, it just indicates that all operations in this 
job were attempted (executed) successfully.
CANCELED
 
In this state, the job was canceled using the
API and the job is not running.
ERROR
In this state, the job stopped executing because of a system error and it is not running.
Precedence Rules for paramConnector and fieldConnector
Precedence Rules for paramConnector and fieldConnector
Rule
#
Rule Details
Description
Query Translation
Example
1
Multiple
conditions on
the same field
get the highest
logical
precedence
One field can have multiple conditions specified
on it, in the requestParameters array.
This query translates to: 
Right:
(((deviceRef =
1000 or
deviceRef=2000)
and
tagName=foo) or
state=active) 
And not 
Wrong:
(deviceRef =
1000 or
(deviceRef=2000
and
tagName=foo) or
state=active)
deviceRef=1000 or
deviceRef=2000 and tagName=foo
 
or state=active
Using the precedence rule,  'and'
 and
takes precedence over 'or'
hence, the query would translate to 
#2 above AND NOT #1. Refer to
Example 1 in the
page.
2
'and' takes a
higher
precedence
over 'or'
The Param connectors are used to connect two
or more fields in a logical manner. Now if there
are 3 or more fields connected together by
different connectors, then we need to know
what takes higher precedence.
This query can be 
 in the sense
ambiguous
that it can mean either: 
Right: (tagName
= tagName1 or
deviceRef=1000)
and
(state=active) 
Wrong:
(tagName =
tagName1) or
(deviceRef=1000
and
state=active)
tagName = tagName1 or 
deviceRef = 1000 and state =
 
active 
 
 
Using the precedence rule,  'and'
 and
takes precedence over 'or'
hence, the query would translate to 
 
#2 above AND NOT #1. Refer to
Example 1 in the
page.
API Response Codes
List of Response Codes
Go to the 
 
40