The following best practices are related to scripting.
-
Avoid scripting. Always use existing functionality and contact Hyland Software if a feature that requires scripting is reoccurring. Do not script what OnBase can already do. OnBase has rich native functionality. Prior to writing a script, ensure that existing functionality cannot already accomplish the task.
-
When running scripts on form load, ensure they are tuned for optimal performance. Limit the amount of work performed by a script executing at load time. A complex script that needs to run every time a user selects a document can be seen as slow performance by a user. If a script is loading a significant amount of information or performing a number of validations, consider allowing the user to request the information rather than load it every time. For instance, if using a multi-tabbed E-Form, consider populating the data on the non-active tabs only when the tab becomes active. This saves time when loading the form.
-
Off load a script to the Workflow Server if the script is performing resource intensive functions. If a script is performing processing-intensive operations, consider off loading the script to run behind a timer on the Workflow Server. This releases the process-initiating machine to continue processing the work it was designed to handle.
-
If a script is not updating keywords, use the “Run Script Without Document” action. If the configured script does not update keywords on the document there is no need to reload the keywords from the database after script execution.
-
It is a best practice to always use the Refresh document after script has executed option in the Run Unity Script action and rule if altering keyword data via a script and using any subsequent actions/rules within the same task list that may need to use the most recent keyword data.