Managing Web Store Performance Impact
When deploying a user event script, you can permit or prevent the deployment from being triggered by web store activity. You configure this behavior by specifying execution contexts on the Context Filtering tab of the script deployment record. Execution contexts let you control whether the deployment is triggered by particular events, such as UI actions or web store activity. For more information, see Execution Contexts.
The following execution contexts apply to web store activity:
-
Web Application
-
Web Store
Scripts can significantly slow web store performance. By preventing script deployments from being triggered by web store activity, you can improve web store response times.
You can set up execution context filtering when you deploy a user event script. You can also set up execution context filtering by editing a script deployment record for a user event script, as described in the following procedure.
To enable or disable web store triggers for a user event script deployment:
-
Open the script deployment record, for a user event script, for editing. For example, go to Customization > Scripting > Script Deployments. Locate the appropriate script deployment record and click the corresponding Edit link.
-
On the script deployment record, on the Context Filtering tab, specify the execution contexts for the script. If you select Web Application or Web Store, those contexts are enabled for your script. If you do not select them, they are disabled for your script.
-
Click Save.
Another option for optimizing web store performance is the Asynchronous afterSubmit Sales Order Processing feature. When you enable this feature, all afterSubmit user events and workflows triggered by web store checkout run asynchronously. For more information, see Commerce Features.