Annapurna UV included in the supplier coating

If UV is sold as a separate item in Annapurna but the supplier provides the UV included in the coating then this is handled in Annapurna by a local mapping entry for the supplier.

UVCode&CoatCode=SupplierCoatcode

Please note that Annapurna applies this check after mapping of the UV codes and Coat codes to the supplier codes.  So this mapping should reference the supplier codes.

For example, in Annapurna a coating is sold as code HMC and a UV is sold with code UV400.

The suppliers coating code is MAR_UV.

In local mapping there will be

HMC=MAR

UV400=UV

UV&MAR=MAR_UV

The first two lines map the Annapurna codes to the supplier code.  The last line then combines the UV & Coat into one coating code.

Annapurna: References when sending to Solenzara

When orders are sent from Annapurna to Solenzara, it is possible to specify how the reference is used.

It is recommended that the reference starts with either the Annapurna job number or tray if trays are used.

Suppliers can print the reference on the lens packet so it is easy to identify the action required when the lenses are returned.  The Annapurna receive lens process will look for the order number or the tray at the start of any barcode that the supplier prints.

The following codes can be used to construct the reference sent.

{tray}   - the tray number

{order}  - the order number

{cusno}  - the Annapurna customer number, useful if want to handle customers in a specific way.

{labref} - the reference recorded on the order

{uncut} - if the order is an uncut then an identified is added to the order, a different identifier is used for remoted edged lenses.  This allows the lens to be passed to the correct area on receipt.  Note the lens receiving process will also inform of this.

{hold} - The customer record has an entry for a hold area and this will include this value in the reference. Typically, if there are customers requiring special action then they can be identified here so the lenses can be passed for inspection in the correct area.

{labbaseref} - this is the same as labref but the Solenzara number, if it is present, has been dropped from this.

PHP Vulnerability

We can confirm that all the Solenzara sites have been updated to the latest release 8.5.12 that was issued today.

We will continue to monitor and apply any security patches as we are advised.

Annapurna – Configuring Automatic Reports.

 

Annapurna – Configuring Autoreports.

Annapurna has the means to run reports automatically.  Typically, a task would be created in Santiago or Windows Task Scheduler to launch Annapurna in a special mode to run reports and other tasks and then close down.

 To do this, Annapurna is started with AUTOREPORTS=filename.

The filename contains the instructions for Annapurna to follow.

To set up the instructions, Annapurna is started with an additional parameter: AUTOCONFIG.

So Annapurna.exe AUTOREPORTS=filename AUTOCONFIG.

When Annapurna starts, you go to the Reports that you wish to run.  Enter the settings that you wish such as for this week, use completed date.  If you wish to set up for emailing then you click on the add to email and add the email addresses.

Right click on the Reports screen.  If there is an option ‘Save Report Settings’ then click this. This will save the chosen settings so that they will be used when running automatically.

If there is not an option for ‘Save Report Settings’ then this feature is not allowed on this Report.

Annapurna will still ask for the user and password.  For an automated process, you will need to add USER=user PASSWORD=password to the run time parameters.

 

Now, if start Annapurna with

USER=user PASSWORD=password AUTOREPORTS=filename

Annapurna will run and produce the necessary reports.

 

 

 

 

 

 

 

 

 

Annapurna: Include items such as lens wipe with a product.

Sometimes, it is necessary to provide item such as lens cleaner, wipe for particular lens. This can be automated in order entry when the lens is selected.

A file called Lenscharges.csv is to be created in the "files" folder.

It has three columns:

Match

Value

Code

Match can be Source, Design or Code.   This relates to the columns in the lenses csv file.

Value is the value to check.

Code is the name of the charge to be added into the sundries area.

For example an entry of:

Design,Premium,WIPE

would cause those lenses with a design of Premium to have a lens charge code of WIPE added to the order.

WIPE needs to be set up in the extras area and a price added. If it is to be free of charge then a nett zero price needs to be added still.

Daily Activity report in Annapurna.

 There is a new report (Report 54) which will show the total jobs processed by a machine for a range of days.

Release Notes: Annapurna Version 409

The below outlines the key updates within Annapurna version 409. Other minor bug fixes have been made along with these.

Disabling of Fields on Order Entry

There was a bug where the fields would disable if values were removed in Order Entry. This has now been fixed.

Trace File Source Selection

The restriction has been removed on adding a trace file except for if the job is remote edged.

Sales Source Flag on Draft Orders

The sales source flag was being removed when a job was being added into drafts. This has now been fixed.

Assign Tray

Jobs can now be viewed from the Assign Tray screen.

Gradient Tint

New photochromic lenses can be graduated which means the axis need to be checked. When a lens is set as being gradient in the technical data this will update the glazing OMA file.

Copy Caption Function

There was a bug with the copy caption function. This has been fixed.

Kathmandu Mapping Manufacturer

It is now possible to map the manufacturer in Katmandu when importing a catalogue.

Update Lens Inventory by Barcode/OPC

A bug was discovered when updating counts via barcode/OPC. This has been fixed.