Forum

Welcome to ProjeQtOr new Forum. We migrated old forum to the new website.
You will find all your posts here, with your usual account.
Just one point : you’ll have to reinitialize your password. Use “Lost password” feature.

Custom Fields appea...
 
Notifications
Clear all

Custom Fields appearing too soon

8 Posts
2 Users
0 Reactions
4,563 Views
 BILA
(@lsigroup)
Posts: 304
Contributor
Topic starter
 
[#6210]

Hi,

I manage in customization screen plugin a field that is supposed to appear by changing statuts in REPONDU (ticket screen as attachment). it works but too soon creating confusion.
Indeed, it appears blanck and without any label when i click on Status DDL but not committing transaction yet.

Why this new screen does not appear only when clicking on SAVE button ?


 
Posted : 23 Aug 2019 22H16
babynus
(@babynus)
Posts: 14966
Main Contributor Admin
 

It is same behavior for hide/visible, readonly and required fields : fields attribributes are dynamically set "as soon as possible".
For instance, for mandatory fields, it is important to see field is required before saving.
Also for fields appearing from a status, it means user should be able to entef data before saving.


 
Posted : 23 Aug 2019 23H30
 BILA
(@lsigroup)
Posts: 304
Contributor
Topic starter
 

Ok, understood, but why only the field appears but not its label. It creates confusion.


 
Posted : 27 Aug 2019 10H29
 BILA
(@lsigroup)
Posts: 304
Contributor
Topic starter
 

And also not at the final location (field appearing on the left)


 
Posted : 27 Aug 2019 10H49
babynus
(@babynus)
Posts: 14966
Main Contributor Admin
 

I don,t' understand last 2 remarks
Please explain.


 
Posted : 29 Aug 2019 18H10
 BILA
(@lsigroup)
Posts: 304
Contributor
Topic starter
 

When we are "between" the 2 status, the field is appearing (blank field) but not its name


 
Posted : 30 Aug 2019 12H24
 BILA
(@lsigroup)
Posts: 304
Contributor
Topic starter
 

Any news please?


 
Posted : 05 Sep 2019 20H37
babynus
(@babynus)
Posts: 14966
Main Contributor Admin
 

This issue has been recorded as Ticket #4182.
Fix will be included in V8.1.6


 
Posted : 05 Sep 2019 21H04
Share:

Scroll to Top