Asset should NOT be allowed to publish without mandatory properties

[#1]

Request for Feature Enhancement (RFE) Summary:	AEM Assets metadata schema allows client to configure metadata schema with mandatory properties. Once this schema is applied to folder, then assets inside that that folder is highlighted with banner as REQUIRED METADATA MISSING. Also will NOT be allowed to save metadata without putting mandatory properties. But asset are allowed to publish without mandatory properties. AEM should restrict publishing asset without mandatory property.
Use-case:	AEM Assets metadata schema allows client to configure metadata schema with mandatory properties. Once this schema is applied to folder, then assets inside that that folder is highlighted with banner as REQUIRED METADATA MISSING. Also will NOT be allowed to save metadata without putting mandatory properties. But asset are allowed to publish without mandatory properties. AEM should restrict publishing asset without mandatory property.
Current/Experienced Behavior:	Asset are allowed to publish without mandatory properties.
Improved/Expected Behavior:	As mandatory properties are missing, asset should not be allowed to publish (similar to how metadata save is not allowed without adding mandatory properties).
Environment Details (AEM version/service pack, any other specifics if applicable):	AEM as cloud service (AEMaaCS)
Customer-name/Organization name:	Lenovo
Screenshot (if applicable):
Code package (if applicable):

[#2]

Agreed, this is a better implementation of required metadata fields than the current approach.

It is often the case that users will not have all the required metadata field information at various points in the process. The current implementation prevents saving *any* metadata information until all required fields are completed.  Which puts users in a bind of having to not update metadata at all OR update with bad metadata on some required fields in order to make the update for values that are known. As a result, our best practice for implementation is never to use required metadata fields because the product implementation actually encourages less accurate metadata.

Our workaround has always been to create a publishing gate that prevents distribution of assets before certain fields are completed as requested in this feature. But this would be better as a product feature than a custom implementation.

[#3]

Hello @abulqasimkp 

I apologize for the delay of this answer. 

Have you contacted AEM Support about this request prior to open it? 
It looks to me more like a bug than a feature enhancement. 

[#4]

Hi @Cedric_Latimier_ ,

Yes, Support team asked to put the request here. 

[#5]

Hi @abulqasimkp @Cedric_Latimier_ what is the update on this one? Right now, Adobe cloud service allows author to publish page, xf and CF and asset without filling mandatory field in component/cf. Is it something Adobe already working on to handle?

[#6]

@aem_2718 As mentioned in the previous comment, the request seems more appropriate to a potential bug than a feature enhancement. I would route this to Support. 

[#7]

@kautuk_sahni Has the bug been fixed? In what release?

[#8]

@HerveAntoine I kindly suggest checking with the Support team as I don't have direct access to verify this. The Ideas section is intended for feature suggestions. For any bugs, you can create a question in the community where fellow members can provide advice. However, the Support channel would be the best route for you to confirm whether the bug has been addressed or not.