Build better products with our product team
Description - Currently, there is no way to manage the component curation of multiple Virtual Report Suites at a timeWhy is this feature important to you - If a company has multiple VRS for each geographical market, it is impossible to curate all the VRS in one go hence it is time consuming and cumbersome
Description -We want to have secondary identity to stitch multiple dataset.Exdata set 1 > identity 1, identity 2, identity 3data set 2 > identity 1data set 3 > identity 2use case - we want create segment in CJA where segment created with data set 3 applied in data set 2 should show results.we are looking to integrate data set 2 and data set 3 using dataset 1 as a pivot and get results. Why is this feature important to you -With wasting data engineering teams time we want to accomplish the stitching within the tool How would you like the feature to work -seamlessly Current Behaviour -One identity used to stitch the data
Description - Allow update of existing contact record with conditional criteria in Marketo via AEP segment rules. For example, we would like to apply the rule only for contacts in the US. Why is this feature important to you - It is important to the business because it allows direct synchronization of data between AEP and Marketo. How would you like the feature to work - I like it to work seamlessly and quickly without adding extra load to Marketo via API calls. Current Behaviour - The system only allow inserts without complex conditions or criteria.
When Marketo merge runs, the loser record is deleted. However, the "delete" activity is not registered anywhere. The Rest API endpoint cannot retrieve this "delete" activity.In general, Merge activity and Delete activities stored in different ways in Marketo and cannot be retrieved by one API endpoint. Delete - Rest API, Merge - Bulk activities export.This makes it very inconvenient to track these activities in case when we need to ensure our local database is properly updated.The suggestion is to have every "delete" to be recorded as part of the activity and be able to retrieve by single API even if delete occurred due to the Merge Thank you
Description - We would like to improve the error messages in Workfront when using Enhanced Connector !) Linking when user does not have permission in Author and DAM is not down: Current process: “Null” error is displayed to user.Future process: application will display a Failure message prompting this “You do not have DAM Author permissions to link an asset. Access Help document in the Training and Help folder for more information.” 2) Pushing when user does not have permission in Author and DAM is not down: Current process: “Null” error is displayed to user.Future process: application will display a Failure message prompting this” You do not have DAM Author permissions to push an asset. Access Help document in the Training and Help folder for more information.” 3) If System is down - server errorCurrent process: “Server Error” error is displayed to user.Future process: application will display a Failure message prompting this “Workfront connection to the DAM is currently down, please try again later or contact IT Support. Why is this feature important to you - this will permit for better experience to user and more info to troubleshoot in case of issues
Description - The system currently allows anyone with manage access to a project the ability to add a task directly to ANY open Iterations. There isn't any validation on whether the user has access to the Team. This also bypasses the backlog grooming/refining processes for Scrum. The team should be the ones to decide what is added to an Iteration (Sprint)Why is this feature important to you -The current process does not validate if the user has access to the Team. This means anyone can directly add stories to an iteration. This bypasses the formal process of adding a story to a teams backlog and the team determining what stories are added to an Iteration (Sprint). How would you like the feature to work -Ideally, the system would not allow the direct add of stories to an Iteration from a Project view, or at minimum validate that the user has access to that Team and only show iterations for the teams the user has access to. Current Behavior -Currently, the system allows anyone with manage access to a project to add a task(story) to ANY open Iteration.https://experienceleague.adobe.com/docs/workfront/using/agile/scrum/iterations/add-stories-to-existing-iteration.html?lang=en"You can add any task or issue to any iteration if you have Manage access to the project."
If you add a space before a link in the link URL field, it turns out Marketo will just leave it there. This can happen accidentally when pasting a link from another source. The resulting code inside the email looks like <a href=" examplelink.com"> with a space between the opening quote and https. If you click the image either in the preview or when the email is sent, it actually works just fine. But when preparing the email for send, Marketo doesn't recognize the link as a link, and therefore doesn't create a tracking link. The effect is the same as if you had included the entire link, http and all, inside a token: the link is functional, but you lose all tracking on it. This ends up being a mistake that's easy to make and hard to catch. The simple solution would be to add a function - like you see in many other input boxes - to automatically remove any leading spaces in that field. This would be a nice little failsafe that would prevent a mistake you would likely only catch when higher-ups are demanding a report from you.
Description - New object type 'Audit log' need to introduce in reporting to make reports on Audit log dataWhy is this feature important to you - Management team is required to know how user's were using Workfront. It helps them to forecast and they will invest in WorkfrontHow would you like the feature to work - New object type 'Audit log' need to introduce in reporting to make reports on Audit log dataCurrent Behaviour - There is no way to create reporting on Audit log data. Only Export is available but it is not useful.
Description - Add 'not equal to' operator in a Audit Log Typeahead field or including options similar to a report filter or Export Audit log more than 50,000 recordsWhy is this feature important to you - Audit logs plays major role in Workfront. It helps to get more valuable to clients.How would you like the feature to work - Like other objects type, if we able to create reports on audit log it will be more useful.Current Behaviour - Only export is available.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.