Options for field level security in the framework package.

Our packing is maintained and provided by a 3rd party vendor.
Currently the 3rd party states that their application does not support security at the 'data level'.

Our 3rd party vendor gave us the following options:
If the desire is to implement this type of security in FrameWork Manager, one of two options are available.
Firstly, you could build your own custom package(s) to support this security request and discontinue the package provided to you. Secondly, you could create another package that is updated after or from the provided package.

Is there any other way?  Ideas?

Thanks,
Jen



------------------------------
Jenifer Broughton
------------------------------

#CognosAnalyticswithWatson

A few ideas come to mind, but some questions first. 

Are you doing this to support ad-hoc querying or allowing the end users to build their own reports?
How often does the vendor update the package?
How does the vendor supply the updated package?

What I'm thinking is you could build a linked model with the vendor's as a base. When they supply an updated package you would just open and republish yours.

------------------------------
Paul Mendelson
------------------------------

Original Message:
Sent: Tue February 11, 2020 11:48 AM
From: Jenifer Broughton
Subject: Field Level Security when using 3rd party (fiserv)

Options for field level security in the framework package.

Our packing is maintained and provided by a 3rd party vendor.
Currently the 3rd party states that their application does not support security at the 'data level'.

Our 3rd party vendor gave us the following options:
If the desire is to implement this type of security in FrameWork Manager, one of two options are available.
Firstly, you could build your own custom package(s) to support this security request and discontinue the package provided to you. Secondly, you could create another package that is updated after or from the provided package.

Is there any other way?  Ideas?

Thanks,
Jen



------------------------------
Jenifer Broughton
------------------------------

#CognosAnalyticswithWatson

@Paul Mendelson  - Hi Paul.  Thanks for the reply. We are allowing select group of users to create their own reports.  Currently, we use the 3rd party tool to create filtered 'views'​​.  Then the users have to go in to create their reports and within the reports they are doing a lot of joins between the views they have access to.  I find it's a lot of unnecessary work on the users part.  Also, we are creating ALOT of views!  The users aren't even using the Framework Package because we are not able to have the 3rd party lock it down based on field level security.

The package gets 'synced' 3 times a day.   The vendor supplies the package thru the cognos portal. 

Thanks for your input on this.

------------------------------
Jenifer Broughton
------------------------------

Original Message:
Sent: Wed February 19, 2020 02:27 PM
From: Paul Mendelson
Subject: Field Level Security when using 3rd party (fiserv)

A few ideas come to mind, but some questions first. 

Are you doing this to support ad-hoc querying or allowing the end users to build their own reports?
How often does the vendor update the package?
How does the vendor supply the updated package?

What I'm thinking is you could build a linked model with the vendor's as a base. When they supply an updated package you would just open and republish yours.

------------------------------
Paul Mendelson

Original Message:
Sent: Tue February 11, 2020 11:48 AM
From: Jenifer Broughton
Subject: Field Level Security when using 3rd party (fiserv)

Options for field level security in the framework package.

Our packing is maintained and provided by a 3rd party vendor.
Currently the 3rd party states that their application does not support security at the 'data level'.

Our 3rd party vendor gave us the following options:
If the desire is to implement this type of security in FrameWork Manager, one of two options are available.
Firstly, you could build your own custom package(s) to support this security request and discontinue the package provided to you. Secondly, you could create another package that is updated after or from the provided package.

Is there any other way?  Ideas?

Thanks,
Jen



------------------------------
Jenifer Broughton
------------------------------

#CognosAnalyticswithWatson