Re: Locked attributes and edit records, posted by Stefan Ritt on Tue May 15 10:29:26 2012
|
| UlfO wrote: |
|
But it says locked on "websubmission" in the instructions for the command "Locked attributes".
Doesnt it mean that for instance a logged in admin should be able to change a value of a submitted locked attribute.
I am looking for a possibility to have have certain attributes locked on submission but for instance admin should be able to change the data in them after they has been submitted.
|
No it does not mean that the admin should be able to change it afterwards. The only way is like I described it (change the config file temporarily). |
|
Re: Locked attributes and edit records, posted by UlfO on Tue May 15 12:42:15 2012
|
| Stefan Ritt wrote: |
|
| UlfO wrote: |
|
But it says locked on "websubmission" in the instructions for the command "Locked attributes".
Doesnt it mean that for instance a logged in admin should be able to change a value of a submitted locked attribute.
I am looking for a possibility to have have certain attributes locked on submission but for instance admin should be able to change the data in them after they has been submitted.
|
No it does not mean that the admin should be able to change it afterwards. The only way is like I described it (change the config file temporarily).
|
OK!
Thank you for a fast response!
Do you plan to implement this feature in later releases?
|
|
Re: Locked attributes and edit records, posted by Stefan Ritt on Tue May 15 12:49:54 2012
|
| UlfO wrote: |
|
| Stefan Ritt wrote: |
|
| UlfO wrote: |
|
But it says locked on "websubmission" in the instructions for the command "Locked attributes".
Doesnt it mean that for instance a logged in admin should be able to change a value of a submitted locked attribute.
I am looking for a possibility to have have certain attributes locked on submission but for instance admin should be able to change the data in them after they has been submitted.
|
No it does not mean that the admin should be able to change it afterwards. The only way is like I described it (change the config file temporarily).
|
OK!
Thank you for a fast response!
Do you plan to implement this feature in later releases?
|
No. |
|
Re: Locked attributes and edit records, posted by UlfO on Tue May 15 14:05:03 2012
|
| Stefan Ritt wrote: |
|
| UlfO wrote: |
|
| Stefan Ritt wrote: |
|
| UlfO wrote: |
|
But it says locked on "websubmission" in the instructions for the command "Locked attributes".
Doesnt it mean that for instance a logged in admin should be able to change a value of a submitted locked attribute.
I am looking for a possibility to have have certain attributes locked on submission but for instance admin should be able to change the data in them after they has been submitted.
|
No it does not mean that the admin should be able to change it afterwards. The only way is like I described it (change the config file temporarily).
|
OK!
Thank you for a fast response!
Do you plan to implement this feature in later releases?
|
No.
|
Is it possible in some other way to make certain attributes preset but readonly for normal user at submission but afterwards changed by admin user? |
|
Re: Locked attributes and edit records, posted by Stefan Ritt on Tue May 15 14:14:35 2012
|
| UlfO wrote: |
|
| Stefan Ritt wrote: |
|
| UlfO wrote: |
|
| Stefan Ritt wrote: |
|
| UlfO wrote: |
|
But it says locked on "websubmission" in the instructions for the command "Locked attributes".
Doesnt it mean that for instance a logged in admin should be able to change a value of a submitted locked attribute.
I am looking for a possibility to have have certain attributes locked on submission but for instance admin should be able to change the data in them after they has been submitted.
|
No it does not mean that the admin should be able to change it afterwards. The only way is like I described it (change the config file temporarily).
|
OK!
Thank you for a fast response!
Do you plan to implement this feature in later releases?
|
No.
|
Is it possible in some other way to make certain attributes preset but readonly for normal user at submission but afterwards changed by admin user?
|
No. |
|
Re: Load attribute options from attributes in another logbook, posted by Andreas Luedeke on Tue May 5 10:54:54 2015
|
> Hi again,
> Hope I'm not draining to much time from you guys !
>
> here is the scenario (fake one just to understand the logic..):
> My main logbook as a Option attribute Called "Electrician availables"
> My second logbook is a list of workers and there capacities Moptions : "Electrician", "Plumber", "Genius"
>
> So my question is:
>
> Is it possible to load my main logbook attribute "Electrician availables" Options based on all the "Electrician" found under my second logbook ?
>
> Thanks :)
I think that this is neither possible nor reasonable. Of course everything is possible with shell- and java-scripting, but that would be a software
package on top of ELOG.
Keep in mind we are talking about an electronic logbook here, not about a relational database.
Cheers
Andreas |
|
Re: Literal comma in elogd.conf entries where "," is an item separator?, posted by Stefan Ritt on Mon Jul 25 20:25:26 2005
|
| Chris Green wrote: | | Could you tell me if there is a way to escape characters in elogd.conf? Particularly, I want to have a drop-down "Keyword" attribute where one of the options is "Spelling, grammar and typos.". This invariably gets split into "Spelling" and "grammar and typos". I've tried "\,", ",,", "%," and "%27", to no avail. |
Just put it in quotations, like
Options Keyword = "Spelling, grammar and typos", Other
that will do the job. |
|
Re: Literal comma in elogd.conf entries where "," is an item separator?, posted by Chris Green on Mon Jul 25 21:41:00 2005
|
Sorry for being dense. Thanks for this,
Chris. |