create new tag
, view all tags
In some cases it is useful to restrict the change of certain fields in a TWikiForm. This could be accomplished by adding TWikiAccessControl to a form field. In other words, a form field can optionally be protected by a TWiki group, e.g. we would get an ACL with the granularity of a form field.

A form is currently defined by a table with columns: Name, Type, Size, Values and Tooltip message. We could add a "Change permission" column, which could be set to the TWikiAdminGroup for example.

Feedback, other ideas?

-- PeterThoeny - 09 Sep 2003

or we could seperate the tracking topic fomr the discussion topic, and implement PoorMansWorkFlow. the discussion topic sould %INCLUDE% the tracking topic, (possibly through METADATA) and at different stages of the WorkFlow different restrictions of conditional rendering could be done.

is there anyone in the core team that currently uses the TWiki for WorkFlow? If not, there are a number of us who have already done so (I've been running my company wide BugTrackingTWiki for over 2 years now).

-- SvenDowideit - 09 Sep 2003

wouldn't it be a good idea to handle tables (and what could be a table) in one single place (module) ? I believe other people have come to the same idea in the past. I am not able to show anything yet( See TabxPluginDev ) but as the same functionalities are being implemented in different places I just want to let you know that I am trying to handle tables in 1 single place. Ideas are welcome.

-- MarcelTrap - 09 Sep 2003

Similar issues have been mentioned about table editing in EditTablePlugin, but at present forms and table are totally independent. Form already support a settings columns in their definition. At present this is only used to make field that provide settings (note that this isn't used at TWiki.org at present). It would seem reasonable to extend this to cover permissions e.g. ALLOW=<group&rt;

FormFieldsPlugin can already change forms when editing, so some early testing could be done there. This particular implementation would mean that controls could be bypassed by turning off JavaScript, but the Plugin hooks don't require this.

If the new WebForm on Codev takes off, then there might be some sense in only certain people being able to set AssignedToCore, although I'm not sure it matter much.

Oh and yes, we do use forms for workflow at work. I have been playing a bit with hooks to make this more powerful, but so far haven't got beyond FormFieldsPlugin.

-- JohnTalintyre - 10 Sep 2003

excellent, I'm extremely glad that you use WebForms for workflow at work too. That means that our dissagreements can come to a usefull and common conclusion. I'm not sure that I can support my arguments yet, I need to think about (and probably discuss) this issues a bit more. But it is useful to note that our implementations are currently very different..

-- SvenDowideit - 10 Sep 2003

Looking forward to more informatino Sven. I should add that my ideas of how one should best do workflow in TWiki are still at an early stage.

-- JohnTalintyre - 10 Sep 2003

Edit | Attach | Watch | Print version | History: r6 < r5 < r4 < r3 < r2 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r6 - 2003-09-10 - JohnTalintyre
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.