Repository navigation
Supported Apps
Home · BLL coding · Developer guide
Install BLL alongside the other app. Support is field-specific: an app
must actively decode a field for {[ ... ]} to work there. A BLL permission
alone does not prove that an app supports BLL coding; it might only use
variables, a shared library or the file server. Check your installed app
version and its card descriptions.
The community list is a useful starting point, not an exhaustive compatibility guarantee.
Coding and expressions in its own cards: examples and setup.
BLL coding in Chronograph card names, supported duration fields and configured split names: examples and supported fields.
Supported text, status, expression and reflection fields: examples and setup.
BLL coding in supported text arguments: examples and setup.
BLL coding in supported text arguments, including speech: examples and setup.
BLL expressions that produce valid time values: examples and setup.
BLL coding in message-related actions: examples and setup.
BLL coding in logging and Timeline message fields, grouped actions' App/group fields, and the Syslog client action's Message and App/group fields. Export filenames also support BLL expressions: supported fields and examples.
- Simple HTTP Connector for Flows documents Better Logic variable integration in older source.
Permission searches of public app source can suggest further candidates, but do not establish which released versions or fields support coding.
Support development - If Better Logic Library is useful to you, you can support its
continued development through GitHub Sponsors,
Patreon,
PayPal, or
bunq.
Thank you!