Product Communities

Description - Increase the maximum number of custom forms that can be added to an object. Why is this feature important to you - As we've redesigned a request process, we've been severely limited by the maximum of 10 custom forms. Our process collects request at the program level, which will always result in multiple projects - and 10 forms is not enough. We have had to create over-complicated forms as a workaround, which is not user-friendly from a configuration perspective OR from an end user perspective. How would you like the feature to work - The maximum form limit should be increased to a number higher than most will need (for example, 500 field limit on a form - most people don't put that many fields on a form - we'd like to have more options than we would ever need to add forms). Current Behaviour - System does not allow you to add more than 10 forms to any object.

I have clients who would like the ability to edit the exported custom forms before they are downloaded. It would be great if this was something you could templatize, so that no one has to go in each time and make those edits. It would help out our client with guest facing visibility.

Description -Currently in the journey expression editor, batch instance ID is not available in properties. It would be ideal to have batch instance ID and use it for reporting purposes. Why is this feature important to you -Not every customer would rely on Data Distiller query to fetch batch instance id from journey step events dataset. Batch Instance ID is helpful to identify different cohorts in a recurring batch audience triggered journeys. How would you like the feature to work -Provide ${journeyBatchInstanceId} property in the journey expression editor. Current Behaviour -${journeyBatchInstanceId} is not available.

When creating emails in the email designer it is possible to lock parts of the email for editing. It is imported for me as i user to be able to lock content for other, if I act as a administrator for the templates, but they should be able for others with my role to edit and publish. Todays feature with content locking is a little to narrow when it comes to use cases. It should be possible to lock on you user for personal editing, but there should be a "admin" user group the can overrun this, and it should be possible for a admin user group to lock content so ordinary users cant change critical content. More role, and user group possibilities to admin the lock feature is needed. 

 Description Currently, the profile attributes are not allowed to configure URL tracking parameters at channel level. This would help to add tracking parameters from profile level attributes. Why is this feature important to you?This would allow you to track and collect additional parameters at the tracking logs. How would you like the feature to work?Allow profile attributes to configure URL tracking parameters at channel level. Current Behaviour - Currently, the profile attributes are not allowed to configure URL tracking parameters at channel level. 

We have started to use variables in Fragments in a advanced way to control links on head logo, language differences, design possibilities like background color, choice between CTA txt link or a button etc. This variables can be set in each Fragment when dragging them into the email. To optimize we she that is would be nice if this can be done for the whole email from the  email "preview" window where you define the subject. If we here could reflect the defined variables that is possible to use, they could be set in this page as a default when you start editing. And you could change the variable setting locally in one fragment if you want to afterwards. You could f ex choose to enable or disable the variables you need in this unique email. The variables with name and value possibilities might be stored in a own page - or you as a admin can add this so it fits the logic that is build into each fragment.   

This is a suggestion from the Summit Technical Support Booth, on behalf of Questrade. Batch deliveries should have a final deduplication step similarly to what is done in Campaign to safeguard profiles from receiving more than one email.  Questrade is using a non-stitch merge policy which is resulting in multiple emails to the same address, due to multiple profiles with the same email address.  Caleb Hill AJO T3 Americas 

Description - Currently, our platform only supports single-page forms, limiting our ability to create comprehensive, multi-step feedback or survey wizards.Marketing forms are scattered across various third-party Content Management Systems (CMS), complicating data ingestion into Adobe Experience Platform (AEP).  Why is this feature important to you - Streamlines the process of collecting detailed feedback and survey data.Eliminates the need for external CMS platforms for marketing forms, simplifying data ingestion into AEP.Enhances marketing personalization capabilities by providing a centralized data source.Improves user experience by creating a more intuitive and structured form submission process.  How would you like the feature to work -  Implement a multi-page form wizard feature. This would allow users to create forms that span multiple pages, capturing detailed feedback data step-by-step.Enable seamless data storage within AEP from these mu

Currently, AJO does not include audience id in the Send Logs of the AJO Message Feedback dataset. This makes it difficult to analyze which specific audience groups are associated with a given campaign, track the effectiveness of messaging per audience segment, and integrate campaign performance data seamlessly with other Adobe Experience Platform (AEP) datasets. Why is this feature important to you?•Helps in measuring campaign success across different audience segments.•Enhances reporting and analytics by allowing segmentation-based performance tracking. Current Behavior•The AJO Message Feedback dataset provides logs for sent, delivered, opened, and clicked messages but does not contain audience segmentation details.

Description - We have a need to show and enforce a word limit at the custom form level on text fields. The use case for this is an automation we are building to send a content fragment (e.g., a paragraph) to another system (e.g., Seismic) for input into a piece of content (e.g., a PowerPoint) Why is this feature important to you - This will enable the automations we are building between Workfront and other systems to assemble pieces of content with limited manual input. Without a word limit, users who are unaware of the limit will have to spend time rewriting content, which hinders the efficiency we are trying to create. How would you like the feature to work - As stated in description. Current Behaviour - No word limit is shown or enforced anywhere in Workfront to my understanding.

If the numbers for a send de- or increase in the process...i want to know this. Idea is a form where i can add that i want to be informed, at which level of  change (5 percent, 10 percent or more, and to which email or telephon or account thiis information should go! The same process should happen if an error occurs du to the process.

Description - The only way we have found to preview the confirmation text for an unsubscribe page is through "preview/test" the problem is we need to click the button "confirm" to see the confirmation text. When doing this the selected test profile gets unsubscribed and cannot be used to send proof. Seems like a hassle to get them re-subscribed as we need to use API's which isn't ideal when it's users testing and they should then be able to either revert the unsubscribe OR test the confirmation page some other way.Why is this feature important to you - We want to preview everything that is exposed to our customers, sometimes multiple times and still send proofs normally with same test-profiles.How would you like the feature to work - Separate preview from test. So if we click "preview" the profile doesn't get unsubscribed but we can still see the look of the unsubscribe page as well as the confirmation page. The second mode for TEST would then be used to test if unsubscribe as a featur