Import script function libraries

You can enhance an object’s functionality by attaching a script to it. Some scripts include functions that depend on external files called script function libraries. Scripts are included in the object import operation, but you must import the script function libraries separately.

Note: Libraries, Client Controls, and OMI Apps compiled with any version of .NET Core (including .NET 5, 6, 7, or 8) are not supported in System Platform. While the system may indicate a successful import, these components will not appear in the IDE or be usable in design time or at runtime.

Some .NET Standard libraries may work, but compatibility is not assured. For the best results, we recommend only using libraries compiled with .NET Framework 4.8.1.

To import a script function library

1. From the ribbon, select Galaxy, then Import, then Scripts.

2. Browse to the directory that contains the script function library you want to import.

3. Select the script function library to be imported, and then select Open to start importing the selected library. Acceptable file types and file name extensions for script function libraries are:

   • Script Library Files (.aaSLIB file extension)

   • .NET or .COM files (.dll, .tlb, .olb, or .exe file extensions)

   • InTouch Script Extension Files (.wdf file extensions)

     An information window opens when the import successfully completes.

4. Validate any graphics that use the custom script functions contained in the imported library. See Validate objects for additional information.

5. Redeploy any InTouchViewApp instances containing graphics that use the script functions in the imported library.

   Note: When you import a new version of an existing script library into a Galaxy, you must stop and restart the engine that hosts the script's owning object. The new script version does not replace the old version until after the hosting engine has restarted and you have redeployed the object.

If you import an object whose script references a script function library that is not resident in the Galaxy, the imported object is set to Bad state and cannot be deployed. To correct this, import the script function library and validate the object. For more information about scripts, see the Application Server Scripting Guide. For more information about validating scripts, see Validate objects.

If you import a script function library that is a different version than the current library, a message is displayed to notify you that there are dependent objects. The message indicates how many objects will need to be redeployed if you continue with the import. If you continue with the import, the dependent objects are marked for redeployment.

Script function libraries that are COM libraries developed using Visual Studio 6 or earlier are not automatically deployed. To place this COM library on the target platform, you can either:

• Install it directly on the target platform and register it.

• Import it to the Galaxy, and then export it as an aaSLIB. Modify the aaSLIB xml to designate that the library is to be registered as a COM object. Reimport the aaSLIB so that it is automatically deployed and registered.