Only one action can be invoked within a function. If there are multiple actions in a function, only the last one will be run.

A complete list of available actions is listed in the IMPVBS.IMP file located in the \Programs folder.

	Actions have largely been superseded by the ToolbarButton system variable that enables you to develop code to manipulate any button on any toolbar.

e.net Solutions does not need to be licensed in order for you to use the business objects within a form. Using these objects also does not consume an existing e.net Solutions functional area license.

The client date is used for business objects invoked by VBScripts run from the client machine when the Use client system date option is enabled (Operators).

Each time a VBScript is executed and the SystemVariables.CodeObject.enetGUID variable is used in a VBScript function, the VBScript automatically performs a logoff after executing that script function. This effectively means that the generated GUID is invalidated after each script function is executed. SYSPRO still offers unlimited use of the business objects inside SYSPRO, as SYSPRO's customization within the SYSPRO product is used and not linked or passed to any external application. If you use the generated GUID for applications outside the bounds of the VBScript, the applications will fail. To prevent this, you need to ensure that your application does not to rely on a GUID that has been written to a file or passed as a parameter to your application inside a script function.

There are over 30 XAML markup templates that ship with SYSPRO which can be applied to listview columns and customized panes.

This variable should only be used in the OnAfterChange events, or OnItemCheck event for a list view.

When you have the following line within the OnAfterChange function:

SystemVariables.CodeObject.CancelStandardAction = true 

the application will not execute any standard action built into the application.

This is useful when you want to override the default behaviour of the SYSPRO application.

For example: You may want to display a desktop alert when a bank balance exceeds 50.000.00, but you only want the desktop alert to be displayed once. You use the global variable to store the highest bank balance value.

CustomizedPane.CodeObject.Array

This contains an array of all rows and columns in the listview. You should use this variable to interrogate the contents of all cells in all rows in the listview.

If you want to change the contents or attributes of any cell, then you should modify the variable: ListviewArrayOut.

Typically, you would use this variable in the OnPopulate event, since this event fires when the listview has been updated with new data. You would then iterate through the listview array and modify any cells as appropriate using the ListviewArrayOut array.

CustomizedPane_OUT.CodeObject.Array

This contains information about cells in the listview that you wish to modify. The array is two-dimensional and consists of columns and rows. The array uses zero-based indexing.

Only child elements one level below the PrimaryNode will be processed and added to the listview.

CustomizedPane.CodeObject.ListviewProperties = xml

When the operator double-clicks a row in a listview, the contents of each cell in a row are returned in this variable. Each cell is separated by a TAB character (a blank cell will still contain a space character before the TAB character).

The OnDblClick event can be used to trap the event when you double-click a row.

Restore the records deleted in a ListviewRowReturned variable.

Cancel the Undo using the following statement:

CustomizedPane_OnUndo = false

For example: To force a form to be marked as changed, insert the following code:

SystemVariables.CodeObject.PostChangeEvent = "1" 

For Associated panes, whenever the associated field changes, a refresh event is automatically fired in the associated pane and the value of the associated field is passed to the associated pane. The VBScript against the OnRefresh event handles everything else. The RefreshValue only exists for the time it takes for the script to run.

For example: If you add an associated pane to the Job field in the Part Billings program (as this is the primary field for this query) then each time you change the job number in the toolbar, the Job field changes and the associated pane refreshes. However, if the Job field does not change, the refresh event is not fired for the associated pane. Similarly, if you add an associated pane that was associated with the Customer field, when the job number changes, the Customer may or may not change depending on whether the job is for the same customer as the previous job.

For this reason the Refresh button is disabled on the listview toolbar of an Associated pane. If you need to add the Refresh button to the toolbar of an Associated pane you will need to change the code yourself. The code would need to store the RefreshValue in one of the VBScripting Global Variables so that it is available after the refresh event that was fired by the associated field changing.

This caters for a single character. 1 indicates a Connection string method. Anything else indicates ODBC DSN.

Use this to update the SQL Server Name to whatever you desire. This variable caters for up to 50 characters.

This function is supported within a toolbar script, however, using this variable does not do anything differently to SYSPROProgramToRun, as the selected browse program cannot return any data since it's not specifically associated with any toolbar entry field.

These parameters exist within the XAML markup code as numbers with a percentage sign before and after them (e.g. the first parameter is %1%, the second is %2%, etc).

At run time, these parameter numbers are replaced by the supplied values. A large number of these XAML files accept only one parameter, but some accept up to 36. In most cases, if less parameters are supplied than the number of parameters that can be accepted, the parameter numbers are replaced with blank values. However, the graph and trendline XAML markup files require a minimum number of parameters to be able to render correctly. If insufficient parameters are supplied, the XAML will not be able to render properly and may display its source code in the cell. If you use the XAML code field property against a cell without specifying a value, the current content of the cell is automatically supplied to the XAML markup code as the first parameter (%1%).

You typically select this option to ensure that a field contains consistent information and is always in either upper or lowercase.

The value of the field can, however, be changed using scripting (e.g. if events against other fields or forms cause a script to be invoked and that script contains lines that modify the value against the read-only field, then the lines are executed and the field value is modified accordingly).

You can use this to make a row in a listview non-visible, depending on the value of a specific column in the listview.

This is useful when you want to validate the field as the cursor focus is returned to the field if the validation fails.

The button is placed to the right of the value entry area of the field and is only displayed when focus is set on the entry area.

If text is supplied for a button against a field, then the text supersedes any button already defined against the field.

If a SmartLink does not exist, it is created for you.

A SmartLink can be added to a field on a display form, an entry form or a listview and is displayed as a SmartLink Information icon.

When you move your mouse pointer over this link, and upside down triangle is displayed to signify that you can select the SmartLink to display a menu. Enabling the Add menu text option allows you enter the text to display on the menu.

Enter a mask to limit the type of characters and the number of characters that can be entered for a field value.

The input mask consists of character types which define the edit mask and placeholders for the number of characters which can be entered for each specific character type. The placeholders are defined using the underscore ( _ ) key.

Input masks can be applied to editable and non-editable fields, but cannot be applied to a hyperlinked form field (i.e. you cannot apply an input mask and a hyperlink to the same caption on a display form).

The basic format for an input mask is an underscore followed by the mask character (e.g. _0_0_0 for a 3 digit number). For example: The input mask for a telephone number, restricted to only numeric values with the area code displayed inside of parentheses, would be (_0_0_0) _0_0_0-_0_0_0_0.

Additional characters can be combined with the mask characters to create a restrictive field for text entry. For example: you could define an input mask for Stock code as: Color: _L_L_L Size: _0_0_0. This entry would be displayed in the form as: Stock code Color:___ Size: ___

The following mask characters can be used to define the input mask:

Once set, the property remains for the run of the program, or until it is changed programmatically. To revert to the default setting, you need to set the attribute to ' '.

For example:

The syntax for a form Order Header with a field DropDownField that has a list that you want to set as editable would be:

OrderHeader.CodeObject.DropDownField = "<Field AllowEntry='true' List='1;2;3;4;5' > </Field>"

Enabling the Allow drop down entry option injects the "AllowEntry='true' " statement. AllowEntry can also be 'false', indicating that the list cannot be editable and you have to select from the drop down list.

If you do not add any variables, the application selected above will be used to receive the notification.

For example, you can attach a specific key such as customer or stock code to the message so that when selected, the system will pass the application a specific key to action (e.g. notify a user to change the credit limit value against a customer in the Customers)