Creating condition on a whole fragment - on the fragment it self - Status changed to: Investigating

[#1]

We would like to have the possibility to put conditions on a whole e-mail fragment, on the fragment it self. Meaning when creating a Fragment it would be nice to be able to create conditions on how the fragment should behave when been used. It could be conditions like, who should be able to see this Fragment and not bases on attributes. This can be done today but with coding it directly in the Fragment code. A interface to do this would be very helpful and create a new dimension to the use of Fragments. 

Yes this can be done inside the template when dragging the fragment in, and setting the condition on the container - but it we do this in the fragment itself this is then pre defined for all user that used this fragment - and is working directly out of the box when dropping the fragment into a template. This is really helpful if you are creating a library with pre defined Fragments with pre defined logic on the fragment. Then the end user can just use them without setting the right settings every time the fragment is been used.  

[#2]

Would Customisable Fragment help? https://experienceleague.adobe.com/en/docs/journey-optimizer/using/content-management/fragments/cust... 

If not, could you provide some concrete example to discuss further 

[#3]

See attached image showing a fragment where you can download a app. Our use case is that this fragment in total would be hidden if the profile data is telling us that you have been logging into the app in the last 365 days. 

To be able to get this result shown above we needed to create a code that "comes" before the actual fragment code, so that all styling etc is been hidden and there is no trace of anything between the fragment over and under the app-fragment. That code we created is like this: {%#if profile._xxxx.lastLoginxxxx occurs >= 365 days before now %}

This line of code we manually need to code/create inside the fragment in the HTML view, without any GUI. It there has been a attribute and event selector here to create that line of code, in the same why that we create audiences, it would be a really powerful tool to create conditions around a whole fragment, and not just conditional content inside a fragment.