[FRONTIFY-12] Allow to enable / disable Frontify fields Created: 16/Nov/22  Updated: 22/Feb/23  Resolved: 07/Feb/23

Status: Closed
Project: Frontify
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0.2

Type: Improvement Priority: Neutral
Reporter: Carlos Cantalapiedra Assignee: Riste Drangovski
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2023-02-13-16-38-58-132.png    
Issue Links:
Relates
relates to JSFIELD-29 Propagate the readonly flag to the JF... Resolved
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Currently is not possible to disable/enable a Frontify field through AvailaiblityRules or AccessDefinition. Would be nice to provide a way to succeed on this or at least some guidelines so the costumers who has this need can accomplish it.

For rest of Magnolia default fields (Vaadin ones) is it possible to succeed by simply creating a new field which extends the original and including an AccessDefinition attribute on its definition, that way when the field is created this attribute can be checked to compare the current user permissions and the one specified on the component definition.



 Comments   
Comment by Alberto Ramirez [ 29/Nov/22 ]

Hi Teresa,

Any scheduled plans to start this?

Thx!

Comment by Teresa Miyar [ 29/Nov/22 ]

Hi,

We haven't scheduled it yet, do you have a workaround you could use for now?

Comment by Alberto Ramirez [ 29/Nov/22 ]

Hi Teresa,

Saddly we dont have any workaround, and if the user hit the buttons of the field, the jcr is modified. The other fields of magnolia can be put in view mode and we dont have a problem with them.

Comment by Teresa Miyar [ 30/Nov/22 ]

Would it be a possibility to put this field inside a complex field and apply the availability rules on the complex field directly? It should affect all fields inside the complex field.

Comment by Alberto Ramirez [ 01/Dec/22 ]

Hi,

We tried to wrap it inside a compositeField but it didn't block the buttons.

 

Comment by Alberto Ramirez [ 13/Feb/23 ]

Hi, Riste

We have two concerns.

Firstly, we have noticed that there is no release 1.2.2 uploaded to nexus repository for 
magnolia-ui-framework-javascript; in fact, frontify-dam-connector still depends on version 1.2.2-SNAPSHOT.
 
Secondly, magnolia-ui-framework-javascript version 1.2.2-SNAPSHOT is not updated since a year.
 
So, ¿when wil frontify-dam-connector 1.0.2 be ready to be downloaded?
 
Thanks, regards
 
Alberto 

Comment by Teresa Miyar [ 13/Feb/23 ]

Hi,

We have just deployed the latest snapshot os the jsfield, we will be able to release both modules by the end of the week, meanwhile you can test with the updated snapshot if you want.

Comment by Alberto Ramirez [ 22/Feb/23 ]

Hi, everyone

A brief question: when is frontify-dam-connector 1.0.2 (not SNAPSHOT) planned to uploaded to nexus repository?

Thanks

Regards, Alberto

Comment by Teresa Miyar [ 22/Feb/23 ]

Hi, It's been released now.

Generated at Mon Feb 12 02:03:48 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.