BFormat errors

This topic covers a few example errors and considerations for dealing with errors.

Syntax errors

Not all attempts at customizing Format-type property values may be successful. If a syntax error causes the script to fail, an ERROR or err:<item>, where <item> is the script value appears in the produced text. For example:

  • If you forget a % on BoundLabel Text entry, say: Fan is %out.value, the system displays: ERROR Fan is %out.value.

  • Or, a script call to a misnamed slot might fail with a displayed error similar to: ChwPump2 had %err:control:DiscreteTotalizerExt:changeOfStates% COS since last reset.

You should test all modifications to BFormat scripts, to make sure you get the intended results.

Security breaches

To prevent a BFormat scripts from calling an object and, in the process, unintentionally changing the state of the object, the framework maintains a BFormat blacklist of prohibited script call methods. By default, the methods listed here generate an error when any attempt is made to execute them via a BFormat:

  • Any method that returns void. No exclusions are allowed.

  • All synchronous action calls (that is, doAction()) calls that return a BValue . Exclusions are allowed.

  • Any call to the submit (Context) method on any subclass of BJob.

  • Any call to the clear () method on BDaySchedule and BEnumSetSehcdule.