We have now extended this concept to ILF link files.
(An ILF file is like a shortcut, which doesn't contain any real data. Instead it instructs Omniscope to open a file from a URL written inside the ILF file. You would use ILF files typically if you want to force Omniscope to open an IOK file directly from the IOK file's URL, rather than allow a web browser upon click to download the IOK file to a temporary folder first. This would allow you to use domain locking, for example.)
Use the new Server Edition XML action "Create Link File" to create ILF files which customise DataManager parameters. As with command-line parameters from the above linked post, you can specify the name of DataManager parameters and the value to use, which overrides the current value in the file. Using this method, you can override an unlimited number of parameters.
For example, the attached two ILF files instruct Omniscope to open the IOK file attachment from the above linked post. - The first overrides the parameters to show the first 5 "abbey" tickers. - The second overrides the parameters to show the first 3 "hbos" tickers.
A further question I have – is there/ could there be a way to set up an MS Access file name and path or a SQL database as a parameter. This would then work in the database block, so that a database from which data is drawn could be specified when calling Omniscope?
Thanks Steve - I have also addressed the question/ request to Thomas. We need this to be able to call Omniscope from inside our application and have it look at the correct data.
This functionality - parameterising the Access file path, and also the table name - has been implemented in 2.8, available in the next few weeks to alpha partners.
It's in a state of flux due to ongoing major changes to support cross-region / time zone-independent publishing - but as soon as we can, we'll release it to alpha partners.