Specific application is to have a list of server names in one place, then individual reports can use this list to open database connections. If server is ever changed then only one change in one file would be required.]]>
- Import bookmarks. This option allows you to import all the bookmarks saved in a bookmarks XML file. This file can be located on your own computer, on a network location or somewhere in the cloud. Any bookmarks that you import will be embedded in your local bookmark file, so any edits you make will be made locally and will not edit the bookmarks XML file.
- Link to bookmarks.This option allows you to link to a bookmark XML file. You can link to a file on your own computer, a file on a network or a file somewhere in the cloud. Linked bookmarks cannot be edited, and are updated every time you open DataManager. You can trigger a manual refresh by selecting the linked bookmark and clicking the "Refresh" button in the bookmarks toolbar. If the linked bookmarks file is deleted they will no longer appear in your bookmarks the next time the list is updated. Linking to bookmarks allows you or your company to create a central bookmarks file that can be managed by an administrator and linked-to by multiple Omniscope users. If, for example, a database password changes, only a single update is required to propagate that change to all users.
- Export all bookmarks/Export folder. These options allow you to export all your bookmarks or a selected folder to a bookmarks XML file. After exporting, other Omniscope users can either import or link to the bookmarks. You can choose to export bookmarks to your local computer, a network location or somewhere on the cloud. Any passwords defined in any of the sources or outputs that you export will be encrypted.
Please let us know if you have any questions or ideas for improving this feature.
]]>In addition to their current use cases, ILF files can now be used to distribute branding packs, organisational style presets and data source bookmarks.
You can now export settings fro a reference installation as ILF files you can distribute to others as e-mail attachments, via shared/synchronised folders, etc. When an installed Omniscope user double-clicks the ILF file, Omniscope will automatically install its contents in that installation, where it will affect all files managed on that installation.
Note: the ILF extension automatically associated with Omniscope when at install time.
Current use cases of ILF export/import files
- Shortcut to the original file - for example instructing Omniscope to open a file from a URL written inside the ILF file. This approach is typically used with the domain locking file security settings.
More information: http://www.visokio.com/domain-locking - To override the parameters in your Omniscope file.
More information: http://forums.visokio.com/discussion/1402/integration-ilf-link-files-with-parameter-overrides-2.8
New use cases of ILF export/import files
Branding
Distribute your branding pack to with others in a form of an ILF file which on double-click installs the branding pack on the user’s machine.
Currently you must have the branding pack you wish to distribute as ILF on your local machine
How to create: Settings > (Application-wide) Advanced > Tools > Create distributable branding pack…
More information: http://www.visokio.com/kb/rebrandingStyle
Distribute individual style with others by simply sending them an ILF which on double-click installs the Style on the user’s machine.
How to create: Style > Application styles > Edit… select the style you wish to distribute and at the top of the dialog click “Export”.
More information: http://www.visokio.com/kb/customising-installationsBookmarks
Distribute your saved bookmarks in DataManager with others in form of an ILF file. On double-clicking the ILF the bookmarks will be installed on the user's machine.
How to create: Settings > (Application-wide) Advanced > Tools > Create distributable bookmarks…
More information: http://www.visokio.com/kb/customising-installations
Thanks, Jamie]]>
i.e To enable bookmarks to be created then in the data block just to reference the name of the bookmark (and then the bookmark references the database)
Currently as far i am aware the only functionality of the bookmark is that you can drag the bookmark across and thus do not have to repeatedly set up frequently used databases.
The purpose is that it would enable me to change the database the bookmark references and not have to change the individual data blocks within each Omniscope if the DBs change the name/locations of the database/server.]]>
1.) Being able to bookmark an output so I do not have to reconfigure the FTP site every time
2.) Being able to bookmark a filter fields so I can use templates and all my outputs are the same if desired
3.) Having a bookmark repository so multiple users could share bookmarks. Ideally there would be some bookmarks that should be used across the enterprise and some that are personal in nature. I would suggest a "bookmarks" and a "my bookmarks" rather than just rolling them up to each user. The my bookmarks would work just like they do now. The "bookmarks" would refer to a centrally managed set of bookmarks and would be configurable.]]>