Menu Item Parameters


Our Customisation Ethos

Our aim with customisation is there should be a little as possible. There will normally be some required, but it should be a last resort. Every custom solution adds burden to support, deployment, development and QA for the rest of its life -- and increases cost and complexity for Eyelit MES-M and the customer.

Rules

  • No custom data model changes without DEV discussion.
  • No custom screens without DEV discussion.
  • High risk SQL (could affect platform) to be discussed with database team.
  • Workstation customisation to be limited to Customisation Parameters and CustomWorkstationDirectActivityRead (which is designed for customisation).
  • Core product screens should only be cloned under exceptional circumstances.
  • Remember PowerBI is also an option.

Customisation Parameters

Customisation parameters are a new framework that has been introduced to allow custom menu items reference core product pages and apply customisation to those screens as they load. This means that the page remains up-to-date and validates QA, but can also be customised depending on the requirements of the customer. Below are the parameters that you can set against the menu item.

CONFIG_SHOWCOLUMNS

You can choose to show 5 additional columns per grid as long as they are in the data. It is semicolon delimited, each GRID.COLUMN|Title needs to be specified.

Format:

[GridName.ColumnName]

[GridName.CUSTOM[1-5]]|[Title]

E.g., DirectWorkGrid.ALLOWLABOURWORK;DirectWorkGrid.CUSTOM1|MyColumnName

CONFIG_SETSQL

This allows you to override the SQL statement for the data source. It is semicolon delimited.

Format:

[DataSourceName]=[CUSTOMSQLNAME]

E.g., DirectWorkDS=CustomWorkstationRead

CONFIG_HIDECOLUMNS

This allows you to hide grid columns. It is semicolon delimited.

Format:

[GridName.ColumnName]

E.g., DirectWorkGrid.PRODUCT;DirectWorkGrid.ORDERNO

CONFIG_HWCSUBPAGEID

Please don’t use this for now, but in short it allows us to switch on a sub page panel on the right hand side of the workstation and specify the page to show.

CONFIG_COLUMNFILTER

You can specify each column that you want to override the filter type against. It is Semicolon delimited. The values can be:

0 = None

1 = Basic

2 = MultiSelect

3 = BasicAndMultiSelect. 

Format:

[GridName.Column]|[Mode]

E.g., DirectWorkGrid.QTYTEXT|0;DirectWorkGrid.ORDERNO|1

Workstation - Custom Highlights/Styling Per Text/Cell

We can format text in cells using HTML. For the column you want to have HTML formatting in designer you need to select AllowHtml.

Here are some samples of how we can format text in cells.

Customisation Sample

The SQL behind this:

select

1 id,

'<b>Bold Text</b>' value

from dual

union

select

2 id,

'<span style="color: red">Red Text</span>' value

from dual

union

select

3 id,

'<b style="background-color: #FFFF00; color: red">Combined Styling</b> No Style' value from dual

Workstation - Show an Icon

Showing an icon using Font Awesome. We need to tick AllowHtml in the designer for the column where the icon is needed.

All available icons can be found on their website: https://fontawesome.com/icons

Customisation Sample

The SQL behind this:

select

'Icon' id,

'<div class="tooltip2"><i class="fas fa-snowplow"></i></div>' value

from dual

Workstation - Custom Raise Issue / Type Filter

...

Workstation - Custom Side Panel

If you require a side panel to be visible in the workstation, it is possible to do this via the customisation parameters. Please note that the

referenced sub page will receive WORKCENTREID.

PowerBI

When creating a custom screen for reading data, consideration should be given to whether the view is created as an HTML screen within Eyelit MES-M or a PowerBI report. Our current drive at the moment is to reduce customer HTML screens, but depending on requirements such as filtering it may still make sense to create a custom screen in the application.

No Management Screen Cloning!

Please do not clone core product screens that provide DELETE, UPDATE or CREATE capabilities. Please ensure customers do not do this either. You will be invalidating release QA validation if this occurs.

Parameter Management

[Discuss with implementation]