Oliver - Omniscope Batch Publishing blocks are controlled by a separate IOK Batch Configuration File (BCF), which allows you to specify all commands relating to properties of files/links to be output and delivered to individual recipients. This includes the ability to set column filters to remove fields that each recipient is not permitted to see.

Server Edition automation applies all these changes to the master Template IOK and refreshes/populates a personalised version, then delivers the personalised versions following the instructions in the BCF IOK file. In version 2.9, you can use one row of the BCF to define the unique filename/path to save to (a subfolder of the Mobile IOK web hosting folder) and personalised data filters to be applied. You can also specify the email to be sent with the (web-safe) link text matching the unique filename naming convention you will use for each email/web view recipient.

Each recipient just clicks on their email link and sees the web browser version of the IOK file personalised for them.

In DataManager 2.0/Version 3.0 there are yet more refinements to this to automate administration for large groups of link/file recipients. This Batch publishing approach is also independent of the LDAP group authorisation settings which may be used to further secure access to the web-hosted links.

Hi,

Thanks for the suggestion. I think this would work well if we had a small number of users that needed access to different data sets, but for the numbers of different combinations that we are talking about this would become unmanageable.

In the proposed solution we would need to keep multiple copies of each iok, and have separate liferay pages for each copy configured to point to the different iok locations, as well as maintaining each users access to the specific pages they should be able to see.

I was thinking that there could be a way of passing a parameter into Omni Mobile when the user opens the file, to say what the filters should be set at. I know that this possibly isn't functionality that already exists, but we do have a reasonably long time to get a solution to the client.

Oliver - I have reclassified this as an Idea. There is some thought to passing parameters in URLs that the viewing device could use to screen out/filter out columns and rows that are not to be seen by the recipient of the link...but this is easy to hack if done too obviously.