Build better products with our product team
Description -In scheduled reports not able to see annotations summary description fully, looking to see in future complete description.Why is this feature important to you - its very important to see the complete description in pdf, if not we do not know what exactly we are looking.How would you like the feature to work - need to see complete DescriptionCurrent Behaviour - not able to see complete description fully in scheduled pdf to team
Description - We can now see where segments and calculated metrics are used. Suggest we should be able to see the same for eVars, props, and metrics in AA/CJA.Why is this feature important to you - At times some components may be obsolete or no longer used. It would be nice to be able to see if & where these components are used. When used, it'd make it easier to update with new versions of components as needed.How would you like the feature to work - Similar to Used In column for Segments & Calculated Metrics search. Clickable links for admins in setup screen, or perhaps data dictionary.Current Behaviour - Without using complex API queries or 3rd party tools, there's no easy way to determine where components are used.
In the most recent Workfront 22.1 release, they added the ability to display projects on the Workload Balancer by color. Each project is randomly assigned a color to make it easier to distinguish it from the other projects on the balancer. However, I would LOVE it if we could customize the assigned color in some way on the back end. For context, how my organization would utilize this is marking some projects (like meetings, time blocks, misc assignments) a different than projects that are for actual assigned work for our clients. Or color coding projects for clients in one division different from another. I would ideally want this setting to be able to be set up on the template level so that every project scheduled with that template carries that same color automatically. But one could change the color too once the project is in flight. Thanks!Lindsey
I've seen many customers have a security review that comes back flagging the use of GET on the API and putting client id and secret on the URL. Apparently people are somehow convinced that that's "in public". https://developers.marketo.com/rest-api/authentication/#using_an_access_token developers.marketo.com/rest-api/endpoint-reference/authentication-endpoint-reference/#!/Identity/identityUsingGET I've explained to people that it doesn't put it in cleartext to the public exactly (which is what people seem to think), as all connections are HTTPS. There is an abstract risk related to logging or something like proxy intercepting - if they log full URLs somewhere then that would be logged in a file somewhere and then that file and who can see it is important. Regardless, it's not how OAuth 2.0 is supposed to work and there is risk associated with GET, which is why it's not allowed in the OAuth 2.0 spec. Would it be possible to update these pages to show that you can use a POST? i.e. both of these work perfectly well: curl --location --request GET '123-ABC-456.mktorest.com/identity/oauth/token?grant_type=client_credentials&client_id=<client id>&client_secret=<client secret>' curl --location --request POST '123-ABC-456.mktorest.com/identity/oauth/token' \ --header 'Content-Type: application/x-www-form-urlencoded' \ --data-urlencode 'grant_type=client_credentials' \ --data-urlencode 'client_id=<client id>' \ --data-urlencode 'client_secret=<client secret>'I'm not sure if the POST is officially supported at Marketo, but it absolutely should be, and if it is, I think the documentation should have that as the default, not the GET, and maybe even deprecate the GET, up to you.Security is more and more on people's minds and this has been flagged in numerous companies. I tried the POST like 2 years ago, and saw that it worked, and have told people they can use that instead - I just told someone else today and I think it might be best to just support this and change the documentation.Thanks for the consideration.
With large 100+ task projects involving large teams, the Updates section on a project can become overwhelming and hard to navigate. For ease of use and improvement to pace of work, please add an option to filter updates that are directed to, or posted by, the user. As a workaround, I've advised users to just ctrl/cmd+f and search for their name on the page, but there could be pages and pages of updates to wade through in which you'll need to repeat the process.
When viewing images in the updates section, the "view image" option does not work well for full-screen images. The content of the image is hard to see. This option is fine for square images, but not for rectangular ones, leading us to download the image and view. A feature that allows full-screen viewing is needed.See image pop-up window:
If an image is added to a project comment/update, to reference it again, you would have to search for it in the updates section or in the main menu- documents.It would be ideal if the added image would auto populate in the project documents folder for easy access/reference.
It would be great to identify subteams within a parent team. For instance, our team of photographers and our team of stylists are both part of a larger "Studio Team". There are many subteams for the studio. When I add new people and choose "Photographer Team" for instance, they would automatically be included in the parent team as well.
When assigning users to tasks, it would be helpful to be able to see in the same view that person's availability (like in the WLB but without having to toggle). OR like it will alert you when you try to assign a task to someone while they have time off, if there could be an alert icon if you try to assign a task to someone that is overbooked for that time.This would result in more proactive project and resource management.
Hi, I think it will be extremely helpful if we can tag programs with custom tags and then run a smart campaign to change the value of this or that field if the lead was added to a program with this or that tag. In that way we won't have to keep adding every new program we're building to the flow that changes the value of the field.
Description - We often use "Category Name" in project/task/issue reports as a quick link from a dashboard report for users to fill in information on the related custom form. This helps when we are on a task report and want the user to fill in details on the project-level (because inline editing isn't possible then) or if their are too many fields that need to be filled for inline editing / if we want to show the conditional logic of the form.With that, the current pop-up window/module that appears is small and cuts off fields in the form; it's a minor ask but it would be ideal for the size of the module to be increased to enhance the user experience.Current Behaviour - The pop-up is small and cuts off text.
Box plots are an ideal way to visualize distribution of a population. It could be used to visualize metrics like:visits per visitororder value distributionjourney completions per visitorIt would be especially powerful if we could click into specific areas of the box plot (including outliers), and identify/further analyze those data points.
As an analyst I'd like to be able to create "calculated" dimensions. I see this working in 3 ways:Simple manipulation of a value - for example like the LEFT/RIGHT/MID functions you have in Excel so I can snip out the relevant bit from a dimension value that I need in my workspace report.Ability to combine two (or more dimension) to create a new oneThe functionality to use a CASE statement (or similar) to change the dimension value.I appreciate something like 3 could be done by classification but the ability to do #1 and #2 at report run-time by the analyst building the report would be great!
Description - Ability to add multiple level dimension in Flow chartsWhy is this feature important to you - Helps us to add more conditions and pathing direction we want to seeHow would you like the feature to work - We can place multiple level dimension to form a desired chartCurrent Behaviour - Only one dimension can be placed in flow charts
Description - Integrated/OOTB Bot detection tool in Adobe AnalyticsWhy is this feature important to you - There are lot of BOT attacks that happen which might elevate the data and cause problems in generating right insightsHow would you like the feature to work - There should be an inbuilt tool to identify BOTs in the customer traffic data.Current Behaviour - I understand that Adobe Analytics tool provides provision to exclude identified BOTs from the data, but we do have a need to have built in tool which might help us identify BOTs based on the traffic/user behaviour.
The Workfront experience for Document->Custom Integrations lacks several critical pieces of functionality that have resulted in extended downtime on our systems. For example, we have had instances where the Adobe Enhanced Connector will stop processing project properly. However there is no indication in Workfront that there is any problem. In the case of a failure is with the Workfront functionality, Workfront will stop sending data to the connector if it detects too many failures when sending data. Although detecting failures and halting communication to avoid complication has merit, the implementation within Workfront is deeply flawed. The communication from Workfront to the Enhanced Connector happens through the Custom Integration system in Workfront (Setup -> Documents -> Custom Integration).The Custom Integration Feature uses an API key that must match between AEM and Workfront. Generally, this works acceptably.The Custom Integration Feature, however, is flawed in significant ways:There is no way to remove old integrations. We have 27 integration configurations in the system, but only 4 are needed.When a custom integration is marked “frozen” or “disabled” in Workfront, there is no indication in the UI.When a custom integration is marked “frozen” or “disabled” there is no notification to alert admins.There is no UI to un-freeze or re-enable a custom integration.There are no logs that we can view that show the state of the custom integration.The authorization token for the interface is not visible, but if it is not the same between systems, the interface will fail.Multiple custom integrations can share the same name and same destination. This can (and has) resulted in confusion regarding which custom integration should be made active.If a new integration is set up, its auth token will be different, and existing project communications will fail. Recently, we had to revert the auth token value to a previous state using methods described below.There is an API call we can use to access the event subscriptions, which are the message identifiers for current integrations:The API results do not show the name of the integration. Only the GUID is shown for the specific event subscription in the API. The GUID is not visible in the UI, so alignment is difficult.The API returns 160,383 results currently, so it can be a fishing expedition to locate the relevant records to determine current state.Even if we locate the record that tells us whether the custom integration is frozen or disabled, we cannot fix the state with this API. It has some benefit for identification.The authorization token is visible in the API results, but to verify it against AEM requires hashing the token (using asystem/console/crypto interface in AEM) to compare to the existing configuration. In addition to not being visible, most of this is not documented and requires getting to the Workfront engineering team to restore our connection communication to resolve the issue. We cannot simply create a new connection, because a new connection would disable all existing communication between the systems and would break all existing projects. So we need to restore the existing connection. Because of the above complications, when we encounter a connector issue, we face hours, and sometimes days, of downtime while we explain to initial support team the issue. We need to repeatedly escalate to resolve. What would we like changed: We would like to be able to remove outdated custom integrations.We would like to be able to see the current status of any custom integration.We would like to ability to unfreeze and re-enable any custom integration.We would like a UI to allow us to match the auth token between the two systems. This ideally would happen automatically.We would like to be able to review logs to understand the current state of the integration without requiring assistance from Adobe.We would like the custom integration process to be documented to ensure both ourselves and Adobe support understand and can resolve the problem quickly.
Description - With GDPR regulation and other government compliance requirements, the ability to store data in different Adobe data centers across the world is a very valuable feature with Adobe Analytics. Unfortunately, Adobe Analytics Workspace Reports (projects) cannot be copied across markets (data centers). I'm requesting that Adobe add the ability to copy Adobe Analytics Workspace Reports (projects) to any markets Why is this feature important to you -Having the ability to work on a Workspace Report in one market and then copy to another market would reduce many hours of duplicate labor in re-building the reports in the other markets. Additionally, this would cut-down on errors, make the reports the same for each market, and free up time to build better reports. How would you like the feature to work -On the Workspace tab, select report that you want to copy.Add a "copy" button click on "copy" buttonChoose market to add copied report Current Behaviour -Does not exist.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.