Best way to include and distribute custom files in OMI ViewApp

Hi Rooz, I'm guessing that what you are looking for is a way to include custom files in your deploy, to be able to dynamically reference them in script or animations?

Equivalent of putting a file in the InTouch application directory and thus having it distributed with the deploy of the application to a client.

And enabling dynamic reference in s script such as InfoInTouchAppDir()+"\MyCustomFile.xml";

I'm not aware of a method for doing the same in OMI, and the solution might be to use another mechanism of distributing the files.

Perhaps some script logic on the Platform could ensure filecopy for you.

As RAINER CARLTON DSOUZA mention, using a network file share might be one solution, but then you are dependent of the availability of that node sharing the folder, but if you do not have network access you might have other issues as well.

InfoInTouchAppDir() does not seem to work in OMI Scripting (it only returns a "." )

Perhaps someone else knows a solution for this to have it part of the package in a deploy of OMI.

Hi Rooz, I'm guessing that what you are looking for is a way to include custom files in your deploy, to be able to dynamically reference them in script or animations?

Equivalent of putting a file in the InTouch application directory and thus having it distributed with the deploy of the application to a client.

And enabling dynamic reference in s script such as InfoInTouchAppDir()+"\MyCustomFile.xml";

I'm not aware of a method for doing the same in OMI, and the solution might be to use another mechanism of distributing the files.

Perhaps some script logic on the Platform could ensure filecopy for you.

As RAINER CARLTON DSOUZA mention, using a network file share might be one solution, but then you are dependent of the availability of that node sharing the folder, but if you do not have network access you might have other issues as well.

InfoInTouchAppDir() does not seem to work in OMI Scripting (it only returns a "." )

Perhaps someone else knows a solution for this to have it part of the package in a deploy of OMI.