Access to and understanding BlueBox2.0 bbsetting_'s

Underlying the BB2.0 framework is a powerful set of settings, known as the bbsettings.

These are configurations which allow the system administrator to change the behaviour of BB2.0 modules without needing to apply any code.

An example of a bbsetting is bbsetting_module_name. This determines how the module is 'seen' and 'named' across the system. This way, for a specific installation, Sales Orders can become known as Internal Sales, for example, without impacting the formal class structure or the data structure.

An example of a more impactful bbsetting is bbsetting_email_on_add which takes an array in the form of

to=myemail@mydomain.com,

and optionally:

to=myemail@mydomain.com,
subject=This is a sample subject for this auto-generated email,
body=This is a sample message for this autogenerated email. The dosument just added has an id of (#_id#)

This hugely powerful bbsetting allows the system adim to drop in email triggers into any module which will email a specified or dynamic list of recipients with data pertaining to that specific new data entry.

This weekly blogging process is supposed to contribute to our internal 'sharpening of the axe' process, which is a weekly discipline to put 2-3 hours into 'fixing stuff' rather than continuing week after week with a blunter and blunter axe.

So, in this post, I am identifying a few imporvements for bbsettings which I plan to work on over the next few weeks:

• If system admin is logged in (or a user with pseudo-admin rights), they should be able to see all settings for a specific module when they are in the module, without having to go to the Module Settings module.
• This list of settings should allow them to edit the settings and view the options for each setting.

So, having decided on my next sharpening excercise... watch this space!