nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Unable to load JavaScript in profile

medini_1059113299

Hello,

I'm hoping someone can help. I have a series of scripts that I reuse for different projects, and rather than have them hiding within the profiling mechanism I would like them to be held in the model browser and then referenced from the derived property under the relevant element in profiling.

For example, I have a script under a b

I have a blank package called "scripts".

I have file, "information_script.js", with a function, "get_info" specified.

In the profile, under "Failures" for FMEA I have a derived property, which has the following:

load("information_script.js");

get_info();

But when I run this, I receive an error in the FMEA worksheet column for this new derived property, stating:

Failed to execute Java Script: Wrapped java.ioFileNotFoundException: information_script.js (The system cannot find the file specified) (unknown#1)

I have already enabled scripting support within the preferences window.

Any help would be great!

Thanks, J

Find more posts tagged with

medini

medini legacy

Accepted answers

medini_1059007410

Hi Jamie,

Welcome to the forum!

My guess is that you created a normal package in the model browser, which you have given the name "scripts", right? This is not the same as the actual "scripts" folder, which is representing the path /config/scripts within the project in the workspace (accessible also via the view "Navigator (Deprecated)").

I addition to enable script development for the workspace via Preferences, you need to "enable script development" for the individual project (via right-click on the project itself). See in the help: medini™ analyze Scripting and API Documentation > About this documentation > Quick Start > Point 2.

Does it work then?

Also have a check of Introduction to Scripting here in the forum.

Happy scripting!

Cheers,

Nils

All comments

medini_1059007410

Hi Jamie,

Welcome to the forum!

Does it work then?

Also have a check of Introduction to Scripting here in the forum.

Happy scripting!

Cheers,

Nils

medini_1023909254

Hi Jamie,

did you create the folder scripts manually in the model browser? Note, this need to be s dedicated system folder that is shon only as a virtaul folder in the model browser.

Please check the medini analyze Scripting and API Documentation from the help menu of medini:

Scripts can be written using arbitrary development tools or just plain text editors, as long as they can be saved as a file and published (copied) into the project later. However, the tool comes with built-in support to develop scripting using Java Script. By default, all scripting development capabilities are disabled at the user interface. To enable them, the user has to edit the "Scripting" preferences and check the relevant options. Note that the execution of scripts is an independent feature and always enabled. The preferences page is just about script development. Having it enabled the developer has rich Java Script editing capabilities including a Java Script editor with auto completion, syntax highlighting and refactoring support.

The easiest way to get started as a script developer is to use the "Enable Script Development" action that is available at any project node in the model browser. Once executed, the project is prepared automatically. Refresh the project once and you will see an additional virtual folder "scripts" in your project that contains an initial sample script to get started. Note that the "scripts" folder is created inside the project file structure but not inside any project model. More precisely: the project is changed and prepared on file system level but not changed at model level, even though the folder is virtually visible in the model browser. Note again that the "Enable Script Development" action is nice to have for writing scripts but not necessarily required to execute them.

Any script file that is found in the "scripts" folder is visible in the model browser now. New files can be easily dropped from the outside into the folder or created using the "Navigator" view, or duplicated using Ctrl-C / Ctrl-V. Scripts can be opened and edited by double-click with the Java Script Development Toolkit (JSDT) or directly executed using the context menu.

Best regards,

Eckhardt

medini_1059113299

Hi Nils, Eckhardt,

Thanks for the speedy replies, you are both correct. I had added a standard model package...my mistake. I've followed your instructions and it's all working as expected.

Thanks again, Jamie