Forum

Notifications
Retirer tout

Hidde fields

8 Posts
3 Utilisateurs
0 Reactions
19.4 {numéro}K Vu
(@ndusch)
Posts: 80
Active Member
Début du sujet
 
[#1487]

Hello
we plan to introduce Projeqtor apps. So the software is very complete we think in a first step to reduce the number of features.
The acces right on forms helps to reduce the access to funtions.
It is also possible to hide fileds in the forms which users have access?

Thank you for your reply.
Nicolas


 
Posté : 22 Nov AM 01:1111
(@babynus)
Posts: 14952
Membre Admin
 

It is also possible to hide fileds in the forms which users have access?

It is possible, but not with parametering.
You must update code of the class in /model directory.
Complete the array $_fieldsAttributes to add "theDesiredField"=>"hidden".
The field "theDisiredField" will then automatically be hidden.


 
Posté : 22 Nov AM 02:1111
(@ndusch)
Posts: 80
Active Member
Début du sujet
 

Hello
It works. Great.
What about with update of Projeqtor with a future version.
Bye


 
Posté : 22 Nov PM 12:1111
(@babynus)
Posts: 14952
Membre Admin
 

What about with update of Projeqtor with a future version.

You'll have to report your changes on every new depoyment 🙁


 
Posté : 22 Nov PM 12:1111
(@ford)
Posts: 4
Active Member
 

Dear Babynus,

First, bravo on developing/managing the creation of open software that is fantastic.

I am interested in creating a system that is an overlay to the standard ProjecQtOr development releases. It could be a plugin or a side project.

It would allow you simply hide unused fields (i.e. hide all software related items ... Target Version, Contexts, etc.).

I know the development release must be the foundation and the database will always need to be uniform from version to version.

Let me know if you are interested in having me work on this.

Best Wishes,
Stafford Shealy


 
Posté : 9 Jan PM 21:011
(@babynus)
Posts: 14952
Membre Admin
 

Hi,

There is already some kind of improvement in V4 that allows you to hide some fields, or change other attributes.
It is not very flexible, but works fine :
you just have to copy the class from /model to /model/custom and change $_fieldsAttributes (or any other thing) in /model/custom class.
New releases will never erase what is in /model/custom, and classes in that folder will preceed /model ones.
Disadvantage is that you then won't benefit from changes from new releases on this class.

Of course, if you can you on more flexible solution, like some plugin, please do.
I'd be happy to integrate in future release any changes that will benfit to comminuty and improve the product.

Thanks in advance.


 
Posté : 10 Jan AM 01:011
(@ford)
Posts: 4
Active Member
 

Thank you. I will look at your recommendation.


 
Posté : 10 Jan AM 01:011
(@ndusch)
Posts: 80
Active Member
Début du sujet
 

Hello Stafford

It would be a great improvement.
The application is terrible and very rich of funtionnalities.
When user starts to work with the level of assimilation of all functionnalities is to high. The possibility to hidde fields would decrease the level of complexity.
And all fields are not used.

Regards,
Nicolas


 
Posté : 22 Jan AM 11:011
Share:
Retour en haut