the correct default value depends on the datatype chosen i think. The pb is to get the correct default value which can be quite difficult : our dataview parser is far too simplistic to be able to get this value trough a hierarchy of type :
* if we have this kind of definition :
MyInteger ::= INTEGER (0..255)

We can do something, have a map somewhere for all base type and try to take the range into account

• for this, it can be tricky (impossible?) with our current parser :
  MySeq ::= SEQUENCE {
  a MyInteger,
  b ENUMERATED { taste(1), welcomes(2), you(3) }
  }

MyChoice ::= CHOICE {
a BOOLEAN,
b MySeq
}

Agreed, that's why I suggest to raise an error only if the field is empty.

If the type is "Timer", however instead of raising an error, set automatically the value "0" as this parameter is not needed/not used.

after some research, the default value is already mandatory in the dialog box (the button stay inactive if there is no value ) this was fixed in the 630 ticket .

Which are the use cases that allow to have a function with context parameters without a default value?

What do you mean?
There are no use cases, that's why I want an error message if there is no value set.

However since it is implemented (OK button is greyed when there is no value) I think we can close the ticket.

Covered by 0000630