Build better products with our product team
i would like to have the ability to add a notice bar at the top of a specific Workfront tab/section like Home/My Work or the Requests tab. Use case: I'd like to provide updates to requesters regarding our teams turn around time to get something done, for example tell them it'll take 3 weeks instead of 2 weeks to turn something around. This would help improve communication so we don't have to send an email out. This could be updated when needed and also taken down/turned off when not needed.
As a system admin with many project templates that have similar request queues, I would like to be able to set up routing rules at the system level and then apply them to the necessary queue topics so that i can more easily manage changes to routing assignments without having to go into every template and active project.
In the Calendar on ToutApp extension, we have the dates in the following format. Here are a few times that work for me: Wed Apr 17, 12:00 PM-12:30 PM CEST Thu Apr 18, 12:00 PM-12:30 PM CEST Fri Apr 19, 12:00 PM-12:30 PM CEST Our Salespeople are all working in different languages and we've been wondering whether it's possible to have the availability dates and times in local languages (e.g., Italian, German, Spanish, etc). Changing Gmail language in the settings didn't help. Would be great if this feature can be implemented!
It would be helpful to have a secondary chart come up when you drill into a section of a pie chart, so you can see further breakdown or categorization of data. For example. if you were looking at a pie chart showing $$ spent per department, if you clicked on a singular department, another pie chart could show where those specific department dollars went by project.
While there's a lot of use from the mktoActive and mktoAddByDefault attributes when defining modules for email templates, there's a more common problem that hasn't been addressed with template attributes: requiring a module to be on all emails within a template. Sometimes, it doesn't make sense to include a header/footer/etc. outside of .mktoContainer, so Marketo users may be stuck with trusting that other users will keep modules within an email for compliance reasons--think a module that has boilerplate legal text or subscription information. In a case like that, you'd want that module to always be in the email, so the ability to do something like mktoRequired="true" in conjunction with mktoAddByDefault would address this problem. This gets even more powerful if order is respected, so, if you have a header module, middle module, and footer module all set to be required, you could allow content to go between header and middle or middle and footer to force brand guidelines.
In order to keep my list of evars and props in a sensible numeric order, it would be really great if you could rearrange the list. Or let us sort the list by number.
List Vars (s.list1, s.list2 and s.list3) are common enough variables (moreso than Hierarchy, I suspect) but right now we have to move to custom code to set them. I understand it gets trickier because of the list-y nature of them, but in most cases my Data Element is making the properly-delimited list I want, and I just need a way to reference it in my rules. Also, it's odd to have Transaction ID in the interface, but not purchaseID- they're very similar, and it would be nice to be able to set them side by side and not in custom code.
It would be great if the order of these 3 elements would be natural, even if you add a lower number later on it should be shown in the correct order as it was in DTM. As an example I had the following eVarseVar1eVar9 Then I added eVar5 so the order when I open the Global Vars of the extension configuration or in a rule in the Set Variable element the next time should be the following and nto eVar5 at the end.eVar1eVar5eVar9
The users of my instance find the new feature to re-name files to the name of the new version confusing. Assuming this functionality will not be reversed, this feature request is to show a notification when the file is renamed from a new version of the document.
Would love the ability to assign permissions at the extension level so specific users, or groups of users, could only make changes to extensions they had access to. This would reduce internal governance efforts by minimizing users' abilities to poke around where they shouldn't. It would be especially useful for enterprise level organizations and those with strict security or legal protocols (i.e. GDPR/COPPA).
Currently, if there is no library assigned to a dev or staging environment, it 404s. This can (reasonably) bother developers and break analytics testing on dev/staging/QA servers.Ideally, if an environment does NOT have a library currently on it, it would just use whatever is currently upstream in prod.
When SSO is enabled the system will not send out a notification to the user that they have been setup. A nice welcome email would be GREAT to alert users they have been setup in the system, this would make user setup more efficient and cut down manual workarounds to let users know they are in the system. Currently the functionality you have is only for NON SSO customers where system sends an email to user asking user to setup a password. The functionality I am requesting is just for the system to send an email without asking for an action to take, but more of an alert - hey you are in!Thank you.
It would be of valuable use to some large organizations which are split into many Exp Cloud login companies to have an option to share WorkSpace projects and templates across Login Companies. An example of this would be as follows. 1. User A create a complex project in WorkSpace in login company A (Top level ORG)2. User A would like to share this project with User B in login company B (Same top level ORG, but different login company)3. User A now have to recreate the complex project in login company B, generating more work in Analytics. If anyone else thinks this would be of great value please vote up this Idea or comment on your use case below.
Good afternoon, Was discussing a current limitation of Adobe Audience Manager with our Adobe consultant, and she suggested raising a feature request with you (to then pass on to the product / engineering teams). Context:NOW TV is a digital TV streaming service (part of the Comcast family). Our users can pick and choose from a variety of content passes: CINEMA / ENTERTAINMENT / REALITY TV / KIDS / SPORTS – and are not tied to any contract. They can select monthly subscriptions and cancel them whenever they like.To make data processing and compute as efficient as possible, we store every user action within our service into our data lake as an event (with corresponding event timestamp) Challenge: Since we operate as a subscription business, a lot of things we do require us to use dates, e.g to know when a subscription expires, to calculate our customer lifetime value, tenure, etc.However, unlike Adobe Campaign, Audience Manager does not understand the concept of a date (or a timestamp). The impact for us is that we then have to create very complex logics to make the data work specifically for Audience Manager e.g instead of using the date a pass expires, every single day we have to calculate the number of days until a pass expires.We have more than 11.5 Millions of accounts in the UK alone, and this example is only one attribute out of dozens of customer attributes that we use that do require such date calculations. (We also operate across 6 EU countries)Adding support for date values would be extremely beneficial for us and speed up our release cycles. Ask: Could we add support for date values in Audience Manager as a roadmap candidate? (would benefit all subscription businesses, independent of vertical) Cheers, Robin
Hello, Could you please feed back to the engineer team that limiting the analysis for traits ( minimum population is 28,000 during the last two weeks)segments (minimum population is 70,000 during the last two weeks) is doing a deservice to the platform from a usability perspective by limiting the commercial scope of the functionality. We don’t need statistical significance to calculate the overlap between two populations and should be left to the user to decide what’s viable for them. I do appreciate a minimum for building a lookalike, where statistical models are being applied but not on overlapping. We have a large volume of niche websites and removing the overlap limitation would help tremendously monetise those websites better. Let me know if there is any way you can remove the minimums for both segments and traits. Thank youAdriana
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