View Events, Scripts & WF

Use this form to add Extender events, custom scripts and workflows to Extender views and fields.

Select a Sage 300 View to be configured with Extender.

By clicking on the “All Views” info icon (or use F6 key) , you can select the appropriate view from the list of available views, active in your Sage 300 database.

Fields and Controls

Tip:

You can also add code in the script to determine what fields the script needs the original value.

Refer to Scripts Advanced Tips

Events Tab

On the Events tab, you can attach an Event Type to an Extender View operation and/or View field/fields.

Requirement! The Events Tab is available if using Extender  Levels Configurator, Customizer or Developer

Important!

If you need to log the Before and After Value, you need to make sure the event type you select has been configured as "Don't Combine".

If you select the View Operation {INSERT}, {UPDATE} or {UPSERT}, the Before and After values will be available if the event is configured as "Don't Combine". One record will be added to the LOG or emailed for each field that is changed.

For the "Delete" action, only one record will be logged.

Refer to Event Types.

Scripts Tab

On the Scripts tab, you select the Python script to be run when the selected view is being updated. Multiple scripts can be selected, and are run in the order specified.

Requirement! The Scripts Tab is only available if using Extender  Levels Customizer or Developer

Note: The first few rows of the highlighted script will be shown to assist with the commenting and verification of the attached scripts.

Tip: To check out, open, upload or Undo Checkout, right hand mouse button on the required script and select the required action.

Important!

If you need to amend a script after it is attached to a view, you need to check it out, open it to make the changes, save the script and check it in to enable the changes.

If the script is amended on a separate machine, you need to re-import the PYTHON script

When PYTHON scripts are attached to a view they are

  1. Imported into the associated database, so the script will dump and load with the database
  2. Copied to the Company directory, where the PYTHON script is run - If you edit the script directly in this directory, your changes might get overwritten.

OCX Scripts do not need to be added to a Sage 300 View. The script name matches the Sage 300 screen Roto ID to indicate that the script is enabled.

Workflow Tab

On the Workflows tab, you can attach a Workflow Template to a Extender View operation and/or View field/fields. The workflow will start automatically when the view is used in Sage 300.

You can use F9 to open the Workflow Template screen from the Screen.

Important!

Workflow is only available for flat views: Master files (e.g. A/R Customers), Transaction Header views (e.g. O/E Header) or Batch Header view (e.g. A/P Invoice batch)

Tip: View Events and Scripts can be exported and imported using the File Menu.
  • If you select Export, then only the current View configuration will be exported. The export includes the attached events and scripts.
  • If you select Export All, then all the current View configurations will be exported. The export includes the attached events and scripts for all configured views. The export format is proprietary, and cannot be changed.

Note: Different options are available depending on the level of Extender you are running.