Field BT-36 (period)

[AlexAS81]

The BT-36 (period) field in the eForms Notice Editor Demo application appears as a single field.

While in the Front eNotices 2 tool it appears with two fields.

What is the difference between a form and another for the field?
Could you send us a visual model with that field reported and completed as in the eNotices tool front part?

Thanks in advance

[rouschr]

I think currently eNotices2 is creating an extra field for durations, so they have special code to deal with this.
Month here is the unit and for currency and unit (if I remember correctly) we historically had no fields as those were considered implicit.
This is not correctly reflected in the editor demo and we are thinking about adding new fields for these to avoid having to need special code. I think that as there were other questions about similar cases we should raise the priority of this subject relative to other tasks.
NOTE: The SDK was initially built more for validation purposes (xsds, schematron, ...) and eNotices2 was doing the editor and using notice types which we took over in order to integrate with fields and nodes of the SDK so that impact of changes would be more integrated.