versaSRS Knowledge Base

 

 

Updating Custom Scripts

Article ID: Q731519

Category: FAQ - Knowledge Base

The information in this article applies to:

  • versaSRS v7.1.0
  • Customisation

From version 7.1.0 of versaSRS the Custom Scripts listed below no longer need the additional functions that were originally included.

  • custom_main.js (Main Screen)
  • custom_manage_action.js (Manage Task)
  • custom_manage_call.js (Manage Call)
  • custom_manage_changerequest.js (Manage Change Request)
  • custom_manage_contact.js (Manage Contact)
  • custom_manage_contract.js (Manage Contract)
  • custom_manage_organization.js (Manage Organisation)
  • custom_manage_problem.js (Manage Problem)
  • custom_update_action.js (Update Task)
  • custom_update_call.js (Update Call)
  • custom-update_changerequest.js (Update Change Request)
  • custom_update_problem.js (Update Problem)

We recommend that the existing content of these files, default location C:\Program Files (x86)\VersaDev\versaSRS\versaSRS\Scripts, be replaced with the following code in each file:
NOTE: If you have already made customisations to the Custom Scripts be sure to include those customisations in the updated files.

$( document ).ready(function() {

});

Any custom functions you create can then be called from within the document.ready function. Alternatively, you can download the CustomScripts.zip file and replace the custom scripts in your versaSRS, this will allow you to start from fresh with any customisations.

NOTE: When making changes to Script files browser cache must be cleared for changes to be reflected in the application.

247 Signature Not Applied Correctly

370 Updating Custom Stored Procedures (versaSRS Version 7)

387 Enable Custom Scripts

Did the information in this article help answer your question?

Yes
No
Did not apply

Last Reviewed: 11/10/2024
Powered By VersaDev Pty Ltd Copyright 2022
Last Reviewed:
11/10/2024

Provided by
VersaDev Support Services

Supporting Documents