Node - repParams

type

Mandatory, you can specify any type that you want, but there are some special types.(These are only effective when the input attribute of the operation sub node is select or multiselect.)

• agent: the corresponding input box of the Set Filtering Criteria and Report Configuration section on the Report Generationscreen will be filled in with values from the [User] table's Name column of the database

• user: the corresponding input box of the Set Filtering Criteria and Report Configuration section on the Report Generation screen will be filled in with values from the [User] table's Name column of the database

• group: the corresponding input box of the Set Filtering Criteria and Report Configuration section on the Report Generation screen will be filled in with values from the [Group] table's Name column of the database

• project: the corresponding input box of the Set Filtering Criteria and Report Configuration section on theReport Generation screen will be filled in with values from the [qa_project] table's name column of the database

• form: the corresponding input box of the Set Filtering Criteria and Report Configuration section on theReport Generation screen will be filled in with values from the [qa_form] table's name column of the database

• evaluator: the corresponding input box of the Set Filtering Criteria and Report Configuration section on theReport Generation screen will be filled in with values from the [User] table's Name column of the database, but only users with Quality Monitor Administrator or Quality Monitor Supervisor right will be added

• skill: the corresponding input box of the Set Filtering Criteria and Report Configuration section on theReport Generation screen will be filled in with values from the [qa_skill] table's name column of the database

• location: the corresponding input box of the Set Filtering Criteria and Report Configuration section on theReport Generation screen will be filled in with values from the [Location] table's Location column of the database

• direction: the corresponding input box of the Set Filtering Criteria and Report Configuration section on theReport Generation screen will be filled in with values from the [String] table's Value column of the database, which is mapped with the Direction_ID column of the [Direction] table

langName

This value will be seen in the first drop-down box of the Set Filtering Criteria and Report Configuration section in theReport Generation screen. The language settings are treated in the same way as with the repName attribute of the report node.

operator

This is the actual SQL script what will be the replacement of the @filters variable in the WHERE SQL keyword. It has two variables called @value and @2value. The @value variable will be replaced by the selected value in the third input box of the Set Filtering Criteria and Report Configuration section of the Report Generation screen. The @2value variable is used only when the third input box allows two inputs like intervalbox.  More information about this can be found in the description of the input attribute.

langName

This value will be seen in the second drop-down box of the Set Filtering Criteria and Report Configuration section of the Report Generation screen.  The language settings are treated in the same way as with the repName attribute of the report node.

input

The input type of the third input of the Set Filtering Criteria and Report Configuration section on the Report Generation screen.

• select: a single select drop-down

• multiselect: a multi-select drop-down

• textbox: a freely editable input box

• textboxint: the same as textbox, but it only accepts numbers

• intervalbox: two textboxint inputs next to each other which can be used to set intervals. The value of the second input box will be the replacement of the @2value variable of the operator attribute.

• multitextbox: the same as the textbox input, but every time you fill it, a new textbox appears and so on. This allows you to define multiple freely editable inputs. These values will be the replacement of the @value variable in the operator attribute separated by commas. This is useful when you use IN or NOT IN SQL keywords in the operator attribute.

• textboxdate: this is a textbox input and a datepicker next to it. You can set date and time with this.

id

A unique identifier for each operation sub node. This is used when you save your dashboard. Use unique values and numbers only.

useAposAroundValues

When this attribute is set to 1, then apostrophes will be used around the input values from multiple input boxes (like multitextbox). This is useful when the SQL in the operation attribute needs it.