This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Locking of Scripts in Designer

Hi All,

 

Can you explain me what is the use of locking the script in Designer. What will be the efect if the script is in locked status which is being used in any process task.

 

Thanks

  • If a script is locked, it will not be compiled during the database compilation. As the scripts can only be compiled all-at-once a compilation error in one script would lead to a non working script library.

    For that reason, the database compiler ask you to lock a script when it contains compilation errors.
  • Hi Markus,

    Thanks for the reply. If we are using the locked script in any Process will there be any issue or it will execute normally.
  • You cannot use a script that is locked as it is not compiled. So, the next time, someone will compile the database, your processes will run into an error that rely on locked scripts.
  • Hi Markus,

    In my case i have locked a script which was already being used in a process and then compiled the DB again and triggered the process from Object browser and noticed that the process has executed without any errors. Can you please advise me on this?

    Thanks
  • How did you use the script in the process? In a generating condition or in a process step running a script component?
  • I have used it in a process step which is running this script component
  • You will not get an error during the generation of the process chain in the object browser, as the script name parameter is just a string. You are not trying to execute the script at this point in time.

    But you will get an error during the execution of the process step as the script component will not be able to execute the script as it is not part of the compiled script assembly.
  • You can think of a locked script as a script which doesn't exist from an execution point of view - so, as Markus said, when the time comes to execute the process step which runs the script it won't find the script and complain. The feature is useful say if you are writing a script but don't want it to be compiled as part of the DB since the script might not be ready for compilation.
  • Thanks for the reply one last thing can i know how to test the lock functionality
  • I believe you already have a process which calls a script. Lock that script, commit, compile and execute the process - it will fail by complaining the script couldn't be found (or something to that effect). Now,Unlock the script, commit to DB, compile and execute the process again, it will work (barring any errors generated during script execution or other process errors itself).