New Bluebox Tag 'item_data'

BlueBox ERP has a new tag for template development:

<!--:item_data:lookup_table|field_to_show:-->

for example

<!--:item_data:bb_inventory_stock_minimum_levels|minimum_levelNUM:-->

It can be used to call any lookup table where the key identifier fields are:

itemISbb_item_dataID
option1ISbb_item_data_options1ID
option2ISbb_item_data_options2ID
option3ISbb_item_data_options3ID

... so any table which stores item_data related information.

Generating Barcodes in BlueBox (Barcode Tag Generator)

BlueBox ERP uses various libraries to generate barcodes. We have now added a useful barcode 'tag generator' into the system to assist in choosing the optimal settings for a specific barcode application.

To find the tag generator simply surf to /?bb_barcode in your BlueBox System:

Replenishment Automation in BlueBox

BlueBox ERP has had a Replenishment Module for many years, which effectively acts as a MRP tool with min/max levels and purchase order generation.

We have now added an automation function to this module which can be set to automatically order the required items from a specific supplier on a daily/weekly/monthly basis.

This new feature effectively runs the Replenishment Report and automatically orders any items which are deemed to be required at that time. It generates a Purchase Order and this can be set to be emailed to the supplier in PDF format and also with an attached CSV output file of the items required in an importable format for the supplier.

Linking Items to the Supplier:

This function relies on the items in the system being attached directly to the supplier, either via the 'default supplier' field in the Item Data entry, or via the 'Associated Item Category' in the Supplier User File.

Setting Up Automation Entries:

Automation entries are added by running the filter for a 'Linked Supplier' in the Replenishment Report and switching 'Automate PO for this Supplier' on.

You have some options at this stage:

• If you 'name' the automation it means that you can 'edit' it by simply using the same name in future and over-riding the saved automation with the same name. If you leave the name option blank the Automations is named as per the Supplier Name - so any future 'blank named' automations for this supplier will over-ride this one.
• Automations will run whenever loaded, but only once per day, and optionally only on specific days of the week (ie Mon,Wed,Fri) by entering these into the specified field.
• You can choose to have an email sent to the Supplier by selecting 'send PDF' or 'send CSV', if neither of these is selected no email will be sent when the PO is created.
• The email that is generated will use the 'company procurement' details in the Supplier User File by default (ie email and name) and if these are not entered for the specific Ssupplier then the user-email and first/last names are used. This can be optionally over-ridden by entering an email and/or BCC email (comma sep. for more than one) in the fields provided.
• Note: the CSV that is produced embed the Supplier code for client company. This code is stored in the 'Cgic' field of the Supplier User Data.

Viewing Automation Entries:

Once you have added an Automation Entry you can view it by clicking on 'Automation' in the top-menu of the Replenishment Report.

Entries are listed showing their last run-time:

You can run entries manually by clicking on the button provided or add the script to your server's cronjob queue as specified.

If you click on an Automation Script to view it you will be able to see the history of logged run-scripts that have been stored against it:

Printing Product/Price/Barcode Labels with BlueBox

BlueBox has a nifty Product/Price/Barcode label printing and new Label Template management module.

Find this module on the Inventory Dashboard:

Firstly we'll look at creating and managing Label Templates:

You can add as many templates as you require.

When adding a label template follow these guidelines:

• The template should be created using CSS with metric sizing (ie mm).
  
  
• Remember that padding on DIV boxes increases the overall size of the box, so rather nest embedded DIVs if you want to add padding to an exact-sized external DIV.
• Image links should include the full URL (ie from HTTP://)
• You can add template-specific settings which will over-ride the label printing parameters:
  
  

Now that you have a template there are 2 scenarios for printing labels:

• Printing labels for stock/items from inventory or item-data
  
  You'd use this method to print price-labels, barcode-labels, shelf-labels etc
• Printing labels from the items listed on a document
  
  You'd use this method to print labels for goods received or goods despatched normally.

Printing Labels for Stock/Items:

• Use the filter to select the item/s you want to print labels for:
  
  
• View the list and apply the settings you require for your labels (if they have not already been applied by the template if you selected one in the previous filter):
  
  
• View, print or send to PDF as required.

Printing Labels from Documents:

• You can print labels directly from the document view:
  
  
• Or you can search for the required document by using the filter:
  
  
  
  
• Once you have selected the document or clicked directly through from the button in the document view, you will see a list of all the items on the document. Apply the settings you require for your labels (if they have not already been applied by the template if you selected one in the previous filter).
  
  
• View, print or send to PDF as required.

Setting Label Template Defaults within Item Data:

• You can specify within each item what it's default label template is, and this template will be used whenever the label engine is run and no specific template is selected:
  
  
  
• You can also toggle an item as 'requires label reprint' (as per screenshot above) and if this is set to yes the item will be listed when the filter for 'Print Labels for Stock/Items' is set:
  
  
  
• Once the label print-run has been sent then all the 'yes' flags on these items will automatically be set back to 'no'.

New Debug Error Logging Module

A new debug error logging option has been added to BlueBox. This will help track down and replicate issues on live systems.

To turn on, the "debug_log_errors_to_file" variable should be set to 1 in the conf file. The system will then begin logging all errors to /engine/logs/errors.html

The format is simplistic (to try keep the file size down), but contains a fair amount of data. Error data includes the error description, date/time, user and BU/LOC ID, IP address, URL and referring URL, user's browser, as well as a backtrace and the $_POST data (if any).

Price Embedded Barcodes in BlueBox ePOS

Newly added to our BlueBox ePOS Module is the ability to read price embedded barcodes.

This feature is added as a plugin, and can be configured to read as many different styles of price embedded barcodes as required.

The normal standard for price embedded barcodes is to embed a EAN barcode (13 digits including checksums) with a product barcode (or sku_code) and price. The purpose for these barcodes is to allow for dynamic pricing at point of sale, embedded in a quickly scannable barcode.

The syntax for the barcode is normally something along the lines of:

TTBBBBCPPPPPC (eg 2000017000336)

where TT is the trigger number for the price-embedded barcode (eg 20) and
BBBB is a 4 digit barcode (or sku_code) (eg 0001) and
C is a checksum digit (ignored) and
PPPPP is a 5 digit price in cents (eg 00033 = 0.33)

To add plugin to BlueBox ePOS simply add as many plugin statements as required for the number of price embedded barcode styles you require eg:

{price_embedded_barcode|string_length|prefix|sku_start_pos|sku_end_pos|price_start_pos|price_end_pos|conversion_ratio}

becomes

{price_embedded_barcode|13|20|3|6|8|12|1000}

These can be repeated next to eachother in the plugins areas, as required, eg:

{price_embedded_barcode|13|20|3|6|8|12|1000}{price_embedded_barcode|13|27|3|6|8|12|0}

A while back we added the Formbuilder to BB2 - it's purpose is to allow consultants and support staff to 'build' forms for customers based on existing classes/data tables.

Essentially it pretty-fies the form, allows for multiple columns, removes unwanted fields and allows for overriding the description of fields easily.

Up until now these formbuilder forms have had to be added via the formbuilder module - and we have 2 'default' formbuilder forms in the system namely : Add Creditor and Add Debtor.

Now we have added 2 new bbsettings so that PHP coders can quickly apply formbuilder to their calsses by default without the need for complex insertin into the Formbuilder class.

There are 2 bbsettings:

var $bbsetting_formbuilder_fields=array("field","field");

This one is required and is simply the list of fields from the current class that you want included in the formbuilder form.

and

var $bbsetting_formbuilder_fields_settings=array("field"=>value,"field"=>value);

This one is not required, but give you the option of overriding any of the default formbuilder settings that are applied when this is not set.