Extender and Web screens

At present, only scripts attached to views work on the web screens (scripts for validation and automation when a transaction is posted for example).

Extender Screen customisations (e.g. adding a button to a Sage screen, adding fields to grid) are currently not available on the Sage 300 web screens. They only work on the classic desktop UI.

View Scripts and workflow

View scripts work on the web screens and the web screens used in CRM. If you configure Extender workflow on a Sage 300 view, the workflow will start when the view is used on the web screens.

Note: The workflow console doesn't currently run on the web screens

Example:

If you configure Extender to log changes to Sage 300 views (e.g. A/R Credit limit change), the log will be populated whether you update the record through the classic UI screens, or the web screens or macro that use the Sage 300 views.

Similarly, if you have a custom view script that validates data in Sage 300, the script will kick in on the web screens. This also applies to running the Sage 300 web screens using Sage CRM.

Screen customisations

  • Screen scripts are currently not available for the web screens.

  • Scripts that require a UI can't be run on the web screens at the moment. 

View Script Tips for Web Screens

Running scripts

Running view scripts on the web screens doesn't require any special installation, it works because of configuration done in Extender View Events, Screens and workflow at the view level.

Tip: Restart IIS after you subclass a view or make a change to a script to ensure the web screens use the latest version.

Displaying messages and errors

If using the Sage 300 web screens, we recommend you use isWeb and display a message using showMessageBox for the classic desktop screens, but pass a message to the Sage error stack for the web screens. 

Note: You can't force the Sage 300 error stack to display, but your messages will show when Sage displays it (e.g. after saving a record, or after a PUT of a customer number when inserting an OE order).

isWeb function

With Extender PU9 and above, you can use isWeb() to determine the type of screen where the script is running.

Copy

Using isWeb

if (isWeb == False):
    showMessageBox("classic desktop screem")
else:
    message("web screen")