Agreed, marketers shouldn’t have to navigate back to the audience portal, search for the name, and then return to the condition they’re using. Instead, provide a view with folders for easy selection

This would be helpful to have folders in fragments as well as for content templates. For now, we are classifying based on tags for each team.

The List function of the filter helps resolve our use case. Here are the details of the same.https://experienceleague.adobe.com/en/docs/journey-optimizer/using/orchestrate-journeys/building-advanced-conditions-journeys/main-functions-journey/list/functionfilter 

When I try to save a visual fragment with the dataset lookup function, it throws the below error but works fine in email templates.    {{datasetLookup datasetId="1234567890" id="101" result="store" required=false}} Product details: Name:{{store.productName}} Description:{{store.productDescription}...

In addition to other documents, AEP [Video-based] tutorials are helpful.  https://experienceleague.adobe.com/docs/platform-learn/tutorials/overview.html

This is a  cool feature for marketers; I've tried and tested it and recorded it here

For email field validation, use client-side validation with JavaScript. Embed your custom script in the Custom HTML block to validate the email field before submission. For dynamic content blocks, implement personalization using JavaScript. You can achieve this through URL parameters or by integrati...

There may be a gap between the launch and the lifecycle of fragments in existing sandboxes. Once a fragment is published, it cannot be edited. Instead, a new draft version must be created, modified, and then published. The updated version will apply to all campaigns using the fragment.

The purpose of this testing is to verify whether the profiles meet the defined rules and match the intended audience. I recommend conducting this testing in your DEV/QE sandbox using the following approach:Since the final launch journey relies on a batch audience, which requires a 24-hour evaluation...