Effects Of Custom Scripting
Meridian Enterprise client performance can be affected by vault configuration options and custom scripting. However, the PowerWeb is must less sensitive than the PowerUser client.
Following are some areas in scripting and configuration that can directly affect the user experience.
-
Property events
These script events occur when a lookup list is generated or when a value has changed, for example. Extensive scripting of these events can result in slowness while editing properties. Avoid heavy actions like table queries on these events.
-
Custom command/page/action visibility events
These events calculate whether items should be available in the user interface. They can make switching documents and showing menus slow.
-
Before/After events
These events occur in the same transaction so the client is suspended during the operation. Be careful how much customization you do in these events because it can make an operation very slow.
-
Settings versus scripting versus tables
The Vault.Option property for retrieving custom settings that are stored in the vault configuration is faster than using a table query for constant values and is more flexible compared to scripting.
-
Security validation
Evaluating security privileges in scripting can be very slow. The User.HasPrivilege and User.HasRole properties can slow down events or operations.
-
CAD link property events
These occur for specific events like workflow changes. In most cases, scripting delays during these events are not critical unless they wait for a result.
-
Special cases
Some events, for example, related to creating a project copy or assembly, may not be supported in PowerWeb. This is because of the performance delays that they may cause because PowerWeb is not a fully interactive client.
To help with optimizing scripting and configuration, consider using script logging as described in Debugging VBScript.