Build better products with our product team
Please use the parameter label instead of the name.We have a large library of custom fields that follows a naming convention that would not make sense to most of our users.The naming convention is required to keep control and avoid duplicates.We also avoid changing the name to prevent reports/views/groupings/filters from breaking.When building reports, we would prefer the chart pulls the 'label' vs. 'name'.
Description -In Analysis Workspace, users may want to define constant values (like a yearly sales goal or revenue-per-order threshold) and use them in multiple places, like multiple projects, segments, or calculated metrics. However, the only current way to achieve this is through calculated metrics, which come with a bunch of disadvantages:They can't be used in segmentsIf they are used in other calculated metrics, they are copied instead of referenced. Therefore, changes to the original metric will not be reflected in other metrics where the original has been usedThis makes this approach unmanageable for values that might change in the future, which can be especially true for sales goals.Why is this feature important to you -Avoid inconsistency in reporting and extreme maintenance overhead when working with goals or other, widely used metrics.How would you like the feature to work -In addition to the already available component types, introduce a "Constant" type of element. We should be able to create, edit, and delete them from within workspace, and also share them with users, groups, or the whole company. The interface for creating and editing them should be very simple and just allow us to input a number and a name. The constants would then show up in a list and be available in workspace and the editors for segments and calculated metrics. Any changes to the constant should then be reflected everywhere it has been used.Current Behaviour -😩
Description -Creating segments and calculated metrics in Analytics/Analysis Workspace is, naturally, a lot of work for complex ideas. Here is the summary I recently created for my post about the Linearity Indicator:As both a user of Analysis Workspace and content creator, I would like to make it as easy as possible for me and others to confidently replicate or adapt the segments and metrics I've invested a lot of time in. Ideally, we would have the same "summary" view for segments too and be able to click into the field, then edit or copy/paste the content (a bit like formulas in Excel).Why is this feature important to you -Drive user adoption through easier workflows for complex scenarios. Increase maturity through more advanced use cases.How would you like the feature to work - Bring the Summary view from Calculated Metrics over to SegmentsWhen a user clicks into the Summary, turn it into an editable text field that allows to copy or edit/replace the content. Once the user clicks out of the field, change the metric/segment definition below, according to the changes, or return an error if there is one, preferably with a hint towards what is wrong.Current Behaviour - 😩
In Analysis workspace reports we are seeing low traffic data but the customer does not want to see these data in reports.We are seeing low traffic for Evar 26.Can you change the threshold limits for Low traffic to include all data? Basically, we want to remove the threshold.
Description - Make permissions related to virtual report suite (VRS) management (create, edit, delete) be consistent with those for standard report suites.Why is this feature important to you - To be able to create/edit/delete VRS, you need to be a (Product Profile?) Administrator. But that is a very powerful role that some organisations may be hesitant to assign to the users just to be able to manage VRS (e.g. an analytics agency/vendor user). On the other hand, you can have the necessary permissions to create/edit/delete any report suite settings and yet still be unable to manage VRS. (Just take a moment to appreciate the breadth of that discrepancy…)How would you like the feature to work - VRS permissions are consistent with standard report suite permissions, i.e. create/edit/delete permissions, especially without the need to be a (Product Profile?) Administrator.Current Behaviour - An Analytics user can have permissions to create/edit/delete report suite settings, including props/eVars/success events/Marketing Channels, yet be unable to create/edit/delete VRS without being added as a (Product Profile?) Administrator. (I repeat, just take a moment to appreciate the breadth of that discrepancy…)
Enhance the Data Insertion API that it supports the use of Supplemental Data ID (SDID) We are promoting our server-side interfaces diligently. But if the tracking with AA is taking place on the server side and the Data Insertion API for Target does not support SDID our customers are not able to use A4T.
Currently, screen size data is pre-determined by the device's user agent to populate mobile reports, and as such it's currently impossible to obtain screen resolution without additional implementation as this help page details - https://helpx.adobe.com/analytics/kb/comparing-iphone-device-versions.htmlThis means that all iPhone screen sizes are reported as 320x480As such, the accuracy of this report is largely brought into question, especially when Apple mobile products contribute to such a large portion of mobile traffic.The data capture method for this report should be looked at to improve the accuracy of the data being captured without the need to implement additional eVars to capture screen sizes for specific devices.
When cloning an email blast program, the only thing that does not automatically update but should be considered an internal program reference is the selection of which program the reports should refer to. With a Default program, the cloned version does have the settings of the reports changed over correctly, but for an email blast program this needs to be swapped manually. Can this be updated to the cloned program as well?
Days marked as Time-Off should not be allowed for inputting hours, to be shown in-active/grey-out in TimeSheets. This gives the valid hours-input to the WF system and helps for effective resource management.
Clicking into an email notification from Workfront doesn't link the system. Does this have to do with SAML authentication or SSO? Update From Workfront Support: Workfront reports these are one of the drawbacks using SSO. If a user is not previously authenticated to Workfront (before the timeout), the system doesn't know if it is an internal, or external user, so it redirects them to the SSO system for authentication. This is really no way for the system to distinguish of the usr should be an SSO user for or outside user until they type in credentials. Again, they've suggested for this to be included as an enhancement request from our end.
<b>There is no Velocity in Language dropdown. Just because of that HTML/XML language was chosen here</b> <br><br> <b>Following links will work correct from Velocity:</b> <br><br> <a href="https://www.veeam.com" target="_blank">Example of static link to veeam.com</a> <br><br> #set ( $myLink01 = "www.veeam.com/how-to-videos.html" ) <a href="https://${myLink01}" target="_blank">Example of static link from variable to veeam.com/how-to-videos.html</a> <br> <br><br> ## --- Links with problem -- inside of the Array - s ## <b>Example of the problem: </b> <br> <br> if we generate links inside of the array -- when we are sending ecard to Test we will have the same links to Page with Title for <b>Veeam Basics (Americas)</b>: <br> But links should be different ones<br> It means that in test for All links we have link for the last item in array: <b>Veeam Basics (Americas)</b><br><br> #set( $arr_database = {} ) #set( $arr_database.array_0 = { "name": "Fundamentals of Data Protection (APJ)", "lp": "www.veeam.com/product-demo/fundamentals-data-protection-apj-live-product-demo-4487.html" }) #set( $arr_database.array_1 = { "name": "Veeam Backup for Microsoft Office 365 – Best Practices (EMEA)", "lp": "www.veeam.com/product-demo/backup-microsoft-office-365-best-practices-emea-live-product-demo-4331.html" }) #set( $arr_database.array_2 = { "name": "Veeam Basics (Americas)", "lp": "www.veeam.com/product-demo/basics-americas-live-product-demo-4238.html" }) #set( $arr_database = [ $arr_database.array_0, $arr_database.array_1, $arr_database.array_2 ]) #foreach ($arr_item in $arr_database ) #set( $webinar_lp = $arr_item.lp ) $arr_item.name <br> <a style="color: #00b336; text-decoration: none;" href="https://${webinar_lp}" target="_blank"> </a><br><br> link to landing page (works properly at Email Preview, doesn't work properly when email received: links should be different in this block) #end ## --- Links with problem -- inside of the Array - e ## Description - Velocity can't 'by design' produce multiples (different) links in a loop that will end up with their distinctive token if tracked Why is this feature important to you - it's extremely important for business users to track customer activity in order to nurture and score them. How would you like the feature to work - Velocity script-made links produce multiple links by array and all of them are different from each other with "Include mkt_tok" enabled as it shows on email preview. Current Behaviour - Velocity script-made links looks good (valid) on email preview (one different link per event), but become identical with "Include mkt_tok" enabled when email is sent. Velocity script can't 'by design' produce multiples links that will end up with their disctincive token if tracked. The idea is to fix this design feature.
One unfortunate discovery after transitioning our setup to take advantage of Subgroups, is that a Subgroup cannot have its own custom statuses. In the same way that Groups inherit the System-wide statuses and can have additional custom statuses; Sub-groups should inherit their parent Group's statuses, and have the ability for their own additional statuses. When we have a small team that is part of a large group that needs custom statuses, we have to choose to either make them a separate group (which introduces other challenges), or make their collection of custom statuses available to the larger group, which gets very messy and introduces confusion.
When @-tagging only first/last name appears. Suggest adding another distinguisher (email address or roll-over profile info.?) so that it is easier to distinguish the correct "John Smith" from all the "John Smiths". This may be especially helpful to groups like ours using SSO because we cannot provide distinguishing names in the user profile that will survive the next login when SSO is re-authenticated.
Please add URL in the Condition Types of the Core Extension. Scenario: fire a rule on https://my.website.com/pageThe current version requires to build a list of conditions:for protocolfor subdomainfor pathIf there was a URL condition available, it would would require only a single condition. The creation will be faster and easier. This is how the current version looks: Obviously, there is a workaround with using a custom code, but let's make the tag manager more convenient for the Launch developers. Thumbs up 👍 if you agree. Best wishes,Andrey Osadchuk | Inspect Launch Implementation, Automate Classifications & Data Sources, Essential Bookmarks
As part of depreciation of legacy resourcing tool, 'Project: budgeted hours' field no longer displays data for budgeted hours. Pulling this field into a project view displays '0', even if budgeted hours are set up in the new resourcing planner. This means project managers cannot see their allocated 'bucket of hours' against their planned and actual hours within their Workfront plans, forcing them to look at three different places at once (WF plan + resourcing planner + utilization tool) and therefore adding in unnecessary additional clicks and time. This also prevents us adding a calculated custom field to each project plan which gives an at-a-glance running total of budgeted hours remaining as planned hours are added.As we begin moving all our resourcing efforts into the platform, this would be an essential element to enable project managers to understand their allocation and plan their hours accordingly.
We often use the "star" feature to sort out projects that are most urgent so that these schedules are at PM's finger tips. Would it be possible to set up a status report that shows these starred projects at a glance?
My business area uses Projects that need unique names, as each Project is tied to a specific product. For us, when the same Product project is imported via Kickstart into our workflow it doesn't break anything - if we catch it we remove the extra and only one will go through the workflow. However, at the end of the season we then have a lot of open product projects that we need to circle back and see if they are duplicates or are truly missed. Right now, I just run reports of the projects and group by project name and investigate any of the groupings with more than (1). Having a "is/is not Unique" option when searching by project name (a text field) would be incredible as then I can search for just the offenders, similar to is/is not Blank.
Request for Feature Enhancement (RFE) Summary: Add the same functionality to AEM Designer for adding a Tool Tip, Custom Text, etc. as there is for editing a default value in a fillable field. Use-case: When creating 508 compliant documents/forms where the Tool Tip or Custom Text needs to be entered. Current/Experienced Behavior: AEM Designer provides a very small window for entering and editing text. Some tool tips have extensive text or have more text than the current box shows Improved/Expected Behavior: Create the same feature in AEM Designer that is available for a default value in a fillable object (i.e. Text Field). At least the window would be big enough or bigger to allow for easier tool tip or custom text creation and editing. Environment Details (AEM version/service pack, any other specifics if applicable): AEM Designer 6.5 Customer-name/Organization name: Rick Kuhlmann/DT Professional Services Screenshot (if applicable): Code package (if applicable):
One of the most irritating issues in Workfront over the years that I have used it is the default display rows are set to 100. Very often you start analyzing data in either a project task list or a report and much later realizes that you are not looking at ALL the data. Could the default displayed rows become a feature where each customer can decided how to set the amount or can you at least make the default displayed rows more than 100? If the latter, I would at least suggest 1000 rows.
When I use the portfolio/program or project filter on the Workload balancer without a user specific filter, all the users in the system are shown, not just the users that are associated with that portfolio/program/projects in that portfolio. This not intuitive and not what a user is expecting when they use this filter.
Currently, when viewing a webhook you cannot see what headers you have set in the "Details" panel. It would be good to show which headers you have applied in the details panel.
Description - Provide option for creating segments/calculated metrics at project-level when creating them inside a project Why is this feature important to you - Having a lot of segments/calculated metrics at a user-level can make it difficult to manage them. Worse, when the user leaves the organisation, the user who gets these components transferred to will have even more segments/calculated metrics to deal with. How would you like the feature to work - In the segment/calculated metric builder, include a checkbox to allow the created component to be at the project-level. Current Behaviour - When creating a segment or calculated metric, the default behaviour is to create it at the user's level.
For some reason, I cannot seem to reset the smart campaign limit for an individual batch campaign back to the Default (admin) value once I have set it to a custom value at the smart campaign level. With needs for recurring smart campaigns changing over time as an instance develops, it would be great to be able to revert to Default.
The "Open Summary" capability is a valuable time-saver when working on tasks within a task list within a project. We recommend adding that capability to dashboards with "Task" reports so that tasks can be worked on right from a dashboard instead of clicking on the dashboard task and then working from within the project.
It would be extremely useful to see the impact of editing an issue, task or project approval process before we make the edits. For example, when editing an issue approval process, I would like to see if that process is associated with any queue topics in the system. Similarly, if I am editing a task approval process, I would like to see if this process is currently attached to any template tasks.This would help us update approval processes more quickly and maintain a clean list of approval processes in the system.
Already have an account? Login
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.
Sorry, our virus scanner detected that this file isn't safe to download.
