Report writer limit capabilities

[wcgodfrey]

List:
Has any one found a way to limit the capabilities
of the report writer in one world so that by user it
is truly a report writer and has no update
capabilities?

I am uneasy about providing training in report
writer because of the extensive capabilities of the
package and would like to limit the exposure to
mistakes.

Conversely is it possible to limit access to
report writer to only specific environments. For
example only allow access in PY7333 so that if data is
corrupted it is only in prototype and not live. Any
feedback would be appreciated.

Are there any restrictions that anyone has run
into writing reports via Terminal server?



Bill Godfrey

B7333 SP14.2

Data AS400

SQL 7 SP 6


_______________________________________________________

 

[Adrian_Chimirel]

Hello Bill,
Our way to accomplish something close to your requirement is to limit ... the Developer access to the DV & PY environments, only! Therefore mistakes are ... almost welcome, not only human
In regards with writing reports via Terminal Server, there were a couple of threads some time ago, the archives could help you.
Warm regards,
Adrian

LIVE: B732.1 SP12.2, Oracle 806, FormScape 2.1
SANDBOX: Xe SP15 & Update2, Oracle 8i
RS/6000, Citrix

 

[Larry_Jones]

Adrian / Bill,

You probably are already aware of this but for the benefit of others considering Adrian's approach ... be aware that you CAN set UBEs to run against the data of other environments. Adrian's approach helps protect against honest mistakes, but not snooping and maliciousness.

Regards,

Larry Jones
[email protected]
OneWorld XE, SP 15.1
HPUX 11, Oracle SE 8.1.6
Mfg, Distribution, Financials

 

[Adrian_Chimirel]

Larry is right ... as usually (I totally agree with Zoltan on this).
That is why the Security Workbench comes in handy, complementing the prior approach


LIVE: B732.1 SP12.2, Oracle 806, FormScape 2.1
SANDBOX: Xe SP15 & Update2, Oracle 8i
RS/6000, Citrix