Issue 20166 - Q-PCD ConfigAdminDeploy-42
Summary: Q-PCD ConfigAdminDeploy-42
Status: CONFIRMED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 1.1
Hardware: All All
: P5 (lowest) Trivial (vote)
Target Milestone: AOO Later
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-09-26 11:31 UTC by Mathias_Bauer
Modified: 2017-05-20 11:29 UTC (History)
1 user (show)

See Also:
Issue Type: FEATURE
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description Mathias_Bauer 2003-09-26 11:31:56 UTC
Source
Goetz Wohlberg / Dirk Grobler

Category
Administration

Product Requirement 
It must be possible to prevent centrally configured settings against overwriting
by settings of users or settings stored inside a document.

Customer Need/Problem
An administrator should be able to enforce specific settings. In that case it
should not be possible to override the central configuration settings locally.

Comment
-

Eng Effort
-

Eng Owner
Mathias Bauer

Product Concept
Enforced settings fixed by an administrator can not be overruled by a
configuration setting stored in a document. In this case applications also
ignore settings stored with documents.

Functional Specification
-
Comment 1 lutz.hoeger 2003-10-23 07:45:40 UTC
added keyword Q-PCD
Comment 2 Mathias_Bauer 2004-01-07 11:34:02 UTC
.
Comment 3 Mathias_Bauer 2004-05-25 12:10:10 UTC
Dirk, we already implemented a lot of things to support "final" configuration
properties in code an UI.
As you are named as "source" of the issue: who will decide when it's "enough"?
The PCD item is not very clear about the necessary amount of support, OTOH it's
clear that we will not support *all* configuration items in "Q".

Comment 4 dirk.grobler 2004-05-27 13:01:54 UTC
Hi Mathias,

What is the current coverage? Can I find somewhere a list? 
The general approach was to say, a property should be finalized at the moment,
when it is relevant for administration. I have only a very general list for
defining the relevance:

 + settings which deal with security
 + settings which deal with lockdown
 + settings which reference resources, like hosts, ports, URLs, paths etc.
 + settings which are used to define the corporate identity, like fonts or colors

As I don't know, what new settings have been or will be introduced at this
stage, it is difficult to provide a definite answer. Mid/End July JB and Falko
will go over the newly added settings and will define, which settings are
relevant for admins. This should be then a final list. 

This process seems to be less than ideal. From my perspective the GUI should be
generic in that way, that every setting that is readonly, could be displayed as
such. This should be a goal for OOo 3.0.

- Dirk

Comment 5 Mathias_Bauer 2004-05-27 14:24:00 UTC
I agree that a list built from ground up should be a goal for the next version.
For "Q" the current state is accepted as it is.
Comment 6 Marcus 2017-05-20 11:29:38 UTC
Reset assigne to the default "issues@openoffice.apache.org".