Build better products with our product team
I need to be able to run a trigger when someone is created through a DynamiChat dialog. Can we get a constraint for DynamicChat added?
In the new Workfront experience, when a document with a very long file name is uploaded, the entire filename is not displayed even though there is plenty of room to show more characters.Why is this feature important to you:Often, the remainder of the document name contains important information that we need at a glance. Having to click on the document and then navigate to the details tab to see the full name is inefficient. Users have also noted that the truncation of the project portfolio and name causes similar issues.How would you like the feature to work:Ideally, the full file name should be displayed within the available space in a standard-size browser window. Additionally, the project portfolio and name should be fully visible without truncation, utilizing any available space at the top of the interface.Current Behaviour:Currently, long file names and project details are truncated, requiring users to click on the document and navigate to the details tab to see the full information. This is not efficient and is a frequent complaint among users.
Would love the ability to copy documents from one project to another so you dont have to download from one and upload to another.
We are experience that maintenance of Tags is hard do to access rights, especially deleting Tags. It must be easier to change the name and/or to delete a Tag that is not wanted or not just any more. It the Tag feature shall work and be trusted by the users the Tag must be spelled right be generic and have some sort of structure. This is work that is always going on - and the need of change and maintenance will always be there. We see misspelled words, not generic enough and the list includes many tests. This is hard to change and make the tool full of "bad data" - and the user experience will drop over time. During the development of AJO there has come better features regarding deleting audiences. When deleting a audience it will be checked it this audience is connected to another audience and/or a journey. If so you get a error message and info about that connections there is regarding the audience you want to delete. We see the need of the same mindset here regarding Tags. All user should be able to change or delete a Tag, but when deleting there should be a check if the Tags is been used somewhere before it is deleted. Changing name should be able as is since this is dynamic data. Is should be able to delete Tags without disable the Tag first. Use of Tags and the need of using Tags is growing along with the extend use of AJO. And if Tags should be used Tags must also be able to be maintained fast and easy, like other features in the tool. With the possibility to also have a folder stricture it would even be more easy and more relevant to use. Today we can create but in a real working environment we cant change and maintain the Tags easy - and will therefor not been used. I see that a good Tag strategy can help us working better with audiences etc where the Tags is part of how we find and target customer.
Currently even Offers with a Ranking score of 0 will be sent back as a response. It should be possible to avoid sending back Offers to the customer based on the value of the Ranking formula (e.g. if the value is 0).Some conditions need to be generally applied without having the risk that someone forgets to apply them. Therefore these conditions are not put into the Offer eligibilities (recurring risk to forget them) but they are put in the ranking formulas so that they are automatically generally applied.
I would like to be able to see all dependences that a audience has at all time. Audiences is the beating heart ot the solution and I therefor need to see where these is used to have good control. Today when trying to delete a audience we get a error message it it is in use somewhere. I would like to have more information regarding this. Like showing exactly where it is used, in other audiences, in offers, in Campaigns and in Journeys. This is an extended version of todays error report when trying to delete a used audience. I would also like to be able to manually run this check on every audience just to se it here is any dependencies to this audience.
Description - device information (user Agent) in the tracking dataset Why is this feature important to you - It will give us ability to track if users are more on Mobile or Desktop. Also help to debug in case of clicks not reaching landing pages if the failures are related to mobile or web browser. It will also help to ghost opens (Apple Mail Privacy) from real openers How would you like the feature to work - Getting the details into tracking dataset. Add a report on a breakdown of open and clicks per operating systems, devices and browsers will be a plus Current Behaviour - None Thanks, David
Description -In the context of reporting, the control group holds significant importance. Why is this feature important to you -It is an important marketing KPI in reportingHow would you like the feature to work -We want to compare the same target group/audience who fulfill the same criteria. Then we will compare the contacted vs not contacted customers by sales Kpi. That not contacted customers will be flagged and frozen in the control group. Current Behaviour -It is not available at all for Journeys. I've come across several posts where Adobe has mentioned that this feature is currently unavailable.
In the customer profile UI there is currently no possibility to quickly check Offer eligibilities (for all active Offers). It should be possible in the customer profile UI to check the eligibility of Offers.Operational efficiency when performing testing or investigation tasks required for a customer inquiry.
Currently there is only one fall-back Offer per decision, even if in the decision there are multiple Placements involved. It should be possible to indicate a fall-back Offer per Placements.If there is more than 1 Placement involved in a decision but there is only 1 fall-back Offer per decision, it means that some Placements will not be used as a potetial promotion. This can be sub-optimal in the communication strategy towards the customers.
Currently context parameters can already be used in Offer eligibility rules but only via the API and not via the UI. It should be possible to also use them via the UI.Full use of the UI potential in daily operations, without having to create ourselves an API interface fur daily operational tasks.
I discovered an interesting issue with the Email Performance Report that I will assume less than 10% of Marketo users are aware of. This issue is detailed below in a note at the bottom of this help doc: "Multiple sends from the same campaign to the same person are counted only once." Email Performance Report Help Doc So does that issue mean? For those of us who use tokens all across our Marketo instances and use them particularly to swap in/out content via those tokens for scalability and efficiency, (maybe in an automated nurture) this is a BIG problem. When a person is sent an email from the same campaign multiple times over any timeframe, the Email Performance Report only records a single email send Example Notice the three email sends below. Two of the sends are via the same campaigns. The below report only displays 2 emails were sent - and this is our issue Solution To me, every email send in the activity log should appear on this report. I am unsure what the use case is for the current methodology, where email sends from the same campaign to the same person are grouped together. I would think most customers would just want to report on all email sends and what the outcome of those sends were (bounce,open,click) over the course of time. Two versions of the Email Performance Report would also suffice. For now - it looks like the only solution to this is via API exports of your email activity. For fun, feel free to include in your comments if you were aware of this! Best, Mike
Description - the Journey Optimizer > Browse UI has fixed column widths. This causes problems to quickly assessing information of the Journeys on this UI. Having the ability to resize column widths to my preference will enable agility in navigation and speed to workWhy is this feature important to you - Our naming convention is complex due to a lack of folder structure in the Browse UI, and thus the ability to navigate quickly to our Journeys is limited because the title of the Journeys are cut off. In addition, other columns, such as "last Updated By", or "Published by", get cut off because of how the UI resizes column widths to account for window widthsHow would you like the feature to work - I'd to "drag and drop" the column width to my likingCurrent Behaviour - column widths are not modifiable. They do resize to account for window width, but this does not provide me the agility I would like.
Request for Feature Enhancement (RFE) Summary: On multifield component dialog: add sufficient space between the validation alert and the up/down arrows so each can be individually selected. This is a bug fix. Use-case: When a user makes an error in the list component, eg by not filling a mandatory field, they cannot view the validation message that would tell them what to fix, because when they click it, they click into the field to drag items up and down. It is impossible to select the validation alert. Current/Experienced Behavior: As above - user cannot select or read validation alert to know what to fix. Improved/Expected Behavior: Sufficient space between the validation alert and the up/down errors so their selection field does not overlap. Then a user can click and read the validation message and / or click and move items up and down. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 Customer-name/Organization name: University of Sydney Screenshot (if applicable): Added as attachment Code package (if applicable):
When viewing tasks assigned to multiple people in the workload balancer a green checkmark will only appear if all assignees completed their work. It would make things a little easier/faster from a resourcing standpoint if we could see these green checkmarks when an assignee marked their part as complete instead of having to wait for all assignees to complete. I know this can be solved by just creating individual tasks but that's a process issue that would take longer to resolve. THANKS!
When assigning multiple projects, make it more user friendly. Ability to search by program and not just project. It would also be helpful if we could check mark the projects instead of having to add the search in each time. When assigning out a program of work there are sometimes 8-15 projects with the same role assignment and while the bulk assignment is good, it could be more efficient then adding each project in the search individually. Even if we could filter by Project Group AND Project Status to pull up the assignments it would be easier.
Description - We'd highly appreciate an option to restore key objects in the product. At the moment majority of users would like to have ability to modify objects like Decisions/Offers/Journeys etc., however there's no way to restore changes applied to them or even to lookup previous version/status of those objects. Why is this feature important to you - since high volume of users has ability to modify all others objects (mentioned above), and there's no ownership of those objects it's very easy for someone to break others objects, either by accident or because of similarities in naming convention. We need to have this ability to restore to previous version, ability to protect them from others (sharing options) would also be useful. How would you like the feature to work - many options: 1. simple - API endpoint with lookup to previous versions of the object, and ability to append JSON response into another call to update that object to previous version 2. complex - restore button in UI (with a separate permission for Product profile or Role) 3. Optional remedy: - ownership of the object, only creator can modify unless shared with other's (individuals or user groups) - email to object owner (if feature available) about changes to that object in the Production sandbox, with option to subscribe and unsubscribe from Alert/notification Current Behaviour - you can only see current status of above objects even when using API, there's no way to lookup previous versions of the object. Objects are owned by everyone there's no sharing option so easy to break someone else's offers, decisions, journeys etc. There's currently only change log available, which is not very helpful other than finding a person to blame
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK