tskDecision – Technical notes

json model

Decision variants

Variants of the decision are visible only for decision team in the view. It is limited by the view used for the list. Event signer or manager do not see them if they are not in the decision team.
If there would be a request to make them visible also to something else, the view limit in the tskDecVar should be updated.

List and select role – strange list in the json

Decision use the feature of the strange object that allows include list of (related) object to the json of the principal object. Roles linked with the decision as well as list to select them are both in the tskDecision json. It serves as a referential implementation of this feature:

• name of the object should be in the parameters:
  ` "parameters": { "principalObject":"sysRole" }
  (It is necessary because it tells the univList what ID field should be selected)
• ID field should be in the list with
  ` "type::"int", "visible":false
  (Without that it won't be loaded.)
• All fields are strange and must have type defined (server doesn't load attributes without type)