(Video)
Overview:
Screen Guide:
Next Steps:Overview:
Extension columns are manual additions to your Workbench database providing extra fields to store information. This can be used to capture specific information that is relevant to your business.
Areas that support Extension Columns:
Purchase Requisitions and Purchase Orders. When extension columns in Purchase Orders are exactly the same as the ones in Purchase Requisitions, the values entered in a Purchase Requisition will be copied accross to the Purchase Order that resulted from that Purchase Requisition. It is important that name and type are exactly the same.
AP Invoice
AP Voucher
Company
Contract
Daysheet
Docket Header (Daysheets)
Document Register
Job
Locations
Daysheet
Document Register
Job
AR Credit
AR Invoice
Job Work Centre
People
Plant
Quotation
Subcontract
Work Order
Stock Items
Specific fields columns can be created on each area, and then each area can have a view with a selection of those custom created fields. All areas support one default view called "Web Portal". And some areas like Plant, support multiple views.
Screen Guide:
Extension Type is the area that supports Extension Columns.
If you have more than one instance of Workbench, you will be able to export extension columns from one instance and import on the other one with the Export and Import Extension Type buttons.
Field is the name of the column which must be short and must be letters only and no spaces. This is very important as this is the actual name of the column in the database it self.
Display Label is the name of the field that will show in the User Interface, on each particular screen. This can have spaces, but keep it short as it is a field label and needs to fit in the screen.
Data Type defines the type of information you intend to save on that field. The supported options show in the dropdown.
Size, Width and Height are only used Text fields. You can play with the values here and see how it looks in the actual screen.
Combo List is only used for the data type Combo, and allows to enter the different options that will be available for selection on this field. Enter them separated by commas (no spaces).
When one of the values in the options list has been used and subsequently deleted as an option from this Combo List, the system will display a warning message advising the user that the value originally selected has been deleted from the combo box options. The value will still be kept, and will not be overwritten when saving any other changes. However, it is recommended that this is reviewed and a new valid value is selected from the dropdown.
Required is a flag to indicate the field is mandatory and always must be entered if this field is included in the Extension Columns View.
System Column indicates if it is a standard field that comes with the system and cannot be removed by the user.
Bin, this will delete the column. However, it will error if there is existing data entered in that field. Data must be cleared first in order to be able to delete the field.
+ New. Use this button to add a new field.
Save any changes to have done on this screen.
Once the desired fields have been created, these need to be included in a View. Web portal is the standard default view used in all areas. Plant, supports extra views that display depending on certain criteria set in each View. Other entities currently only support a single view.
The Extensions View screen will allow you to create new views or edit existing ones:
To create a new View, Type the View name in View Name field and click on +New View button. Then start adding the fields from the list of fields created on the previous screen.
To edit an existing view, select the view, and add or remove fields as needed. Below is an example of the default view Web portal:
Plant extension fields synchronise to Upvise where the extension type is based on the Plant Group associated with the plant item.
Data types:
Combo:
Allows a list of values to be listed separated by comma, or it alsoallows more options retrieved by a SQL query. Keep in mind that in databases with large amount of records could hae low perfromance and slow response when using a SQL query.
Pickers:
As an alternative to a SQL query on a Combo type and for improved performance, a generic picker can be used. These support Companies or Employees. If either is inactive the system appends (inactive) to the names.
Depending on what picker you want to use, enter the correct syntax in the Combo List:
To select from a list of Employees: Employees(){Person}
To select from a list of Companies: Companies(){Company Name}
Next Steps:
Review Permissions for specific behaviour around Extension Columns, like 'Edit Company Extension Columns' permission.
Related Pages:
FAQs:
| Filter by label (Content by label) | ||||||
|---|---|---|---|---|---|---|
|
Process Flow: