Build better products with our product team
It would be great to have more flexibility on where a custom form appears in a request. This would include the ability to have custom forms listed appear at the top or sit between any selected "New Item Fields" that were enabled for the request queue.
Currently, when a document is uploaded to a task, that document is visible from the "Documents" tab on the project, but there is nothing to indicate which task that document is associated with.Ideally, there would be a small hyperlink with the task name next to / underneath the document, so anyone looking at it can quickly access the task it was uploaded to.This would be helpful with large projects with multiple documents uploaded. Sometimes we need to work on documents specific to certain tasks, and this change would help us navigate to that document quickly.
Updates threads on larger projects become cumbersome, and difficult to use. It would be great if the updates thread could be organized like an inbox on the project. Allowing users to select only topics or threads that they want to read!
In the "People" section of a project, there is the ability to "Update All". I would like to have similar functionality for task assignment - "Assign All on project". For some tasks, the entire *project* team is assigned. Currently , for large teams, it takes a long time to make all those assignments.
Working with Custom Forms can be very frustrating. The way data is displayed within Project Details, Business Case or the edit menu is a very bad experience, especially when working with fields such as Check-boxes. If labels are a bit longer, the text just gets wrapped around and the entire area looks messy. Also they are using only about a third of the width of the form, everything on the right is just blank space. I feel the text wouldn't wrap around, if we'd just allow the field to use the entire width of the form.Also, when working with multi-select fields I want to be able to reference to the label and the value. I don't want Workfront to randomly display the value or the label, depending on what I am looking at. When looking into the Portfolio Optimizer I see values, when looking in a standard column I see labels, when using text mode in most of the cases I am seeing the value (sometimes also the label).These are only a few examples, but in general I would like to see a better usability and display of this data.Thank you!
It could be helpful for key users to be able to "tag" profiles with one or more tags - arbitrary strings - that could then be used for building audiences and populating queries. This would enable those users to collect the audiences they need without having our IT group add more fields to the Profile resource.For instance, we might need to send a communication to "power users" of several applications on a periodic basis about upgrades or downtimes. There is no yes/no flag on our Profile resource corresponding to a power user. The profiles of these power users could be tagged as "Power User" without the need to add a database field or create a brand-new audience.This could operate similarly to how blog posts can be tagged with certain subjects then searched or filtered by those subjects... or how tags on these forum posts are used.
We have a request that whenever a message is sent using a particular template that a set of defined addresses will be automatically added to the recipients.The use case for this is when an e-mail goes out from our technology support group to end users, the members of the technology support staff should also receive that message so they are aware of its contents and can respond to incoming questions.It is possible to specify one audience for a delivery template but it does not appear to be possible to set multiple audiences, with one of them always included.I contacted Client Care and was told that there is no delivered feature to support this.I am therefore submitting this feature idea. Provide a method for enabling messages from a delivery template to always be sent to members of a second audience in addition to the audience chosen for the delivery.
There should be a way to filter the dimensions column in ACS reports, much like we can do in Analytics. Right now, our delivery report includes our proofs, and there is no way to filter them out.
Every ESP I have worked with has some mechanism for tracking how an email click converts on a client website into a sale, such as placing the ESP's pixel on an order confirmation webpage. For example, all retailers need to know how email campaigns drive conversion rate, orders, linked sales, average order value and revenue per email. Unfortunately, ACS does not have this pixel and has no means to include whether or not an email drove a sale in its dynamic reports. One must log into Adobe Analytics and look at "behavioral data" in that tool. This means 1) the email marketer cannot produce all campaign KPIs inside of ACS, 2) the email marketer must either learn a 2nd tool (AA) or ask their AA analyst for help, 3) time must be spent exporting campaign results from both ACS and AA for marketer's internal reports (so extra time consuming). I recommend Adobe pipe the sales conversion data (and view viewed conversion data if a brand needs that) from AA into ACS dynamic reports, or create an ACS pixel that will track sales orders and send results directly into ACS.
Currently we import a large number of stand alone lists into ACS and save these as an Audience (Type: List).When you go into each Audience, it has a number count, and a 'Count Date' listed. Unfortunately that 'Count' number doesn't automatically update - it's a static number that relates to the original number of a list. The count date seems to update each time that audience is used for a mailing, but by looking at it, it suggests that the count number, would relate to the count date, which is not true.Of course over time mailing lists deteriorate, so the list gets smaller unless we get sent an updated version, and often we get asked to report on how many people are on a particular list. To get that number we either have to count it via workflow, or scroll down, continually load ALL of the records until the number in the top right displays.It would be very useful if the Count number was dynamic and automatically updated, or had the option to allow us to easily recalculate the count number.
It would be very useful if when adding an email activity to a workflow you could select an existing draft email, rather than having to create an email from scratch every time. So for example when it brings up all the template options, it also has a tab for 'Drafts' and lists all emails in draft format to select from.We often create a draft email outside of a workflow, but then the original request changes and we have to re-create via a workflow.
We are developing a workflow in which some steps will only run if a custom option is set to True.When creating a custom option (Administration > Application Settings > Options), you can set the Data Type to Text, Integer, Floating Point, Date+Time, or Long Text. However, Boolean is not a possible Data Type for an Option.It would be helpful to have a Boolean as a possible Data Type for Options. This would allow for the definition of Yes/No or True/False options without needing to rely on a convention such as 1/0, Y/N, or T/F in a Text or Integer field. The option could then be used in queries inside workflows to act as an if/then condition.
It is possible to create new Dimensions for use in Dynamic Reporting by adding Profile fields to a Sending Logs Extension; these added fields will then appear in the Dimensions area. Here is an example in which we extended the sending logs with our custom fields "Is Employee" and "Is Student"; these then became available as Dimensions.However, the only Segments available in Dynamic Reporting are by Age, and there is no way to create more Segments.It would be beneficial to allow for the creation of custom segments for use in filtering report results. For example, we could create segments for various regions across the U.S. by grouping several states into each segment, or by distance from a certain location (i.e. under 50 miles, 50-99 miles, 100-200 miles, etc.), or even by age ranges other than those provided (such as splitting 18-25 into 18-20 and 21-25).Custom segments should not be specific to a single report. Like the custom Dimensions, they should be usable in any report.
When editing the Load File step of a workflow, if you turn on the "Detect structure from a new file" option, then upload a new file, all of the columns on the Column Definition are reset to the Text data type and lengths of 255 characters.This is inconvenient when the new file structure is similar to the old file structure, perhaps different only in the additional of a couple of columns. All of the previous changes to data types, lengths, value mappings, etc. have to be recreated.If Campaign detects that a column in the newly uploaded file has the same name and data type as an existing column definition, then it should not change the data type, length, value mapping, etc. This will reduce the rework needed when deriving the structure from a new file.
When defining the column definitions in a Load File step in a workflow, if you select Boolean for the Data Type, Campaign expects that the incoming data in the column will be either 1 or 0.If your source data uses a different convention for Boolean values, such as Y/N (yes/no) and T/F (true/false), then you must define these in Value Remapping. This can become cumbersome if you have many columns having the Boolean data type. It can also lead to errors since you have to many set these for each column; you might forget to set them or set them incorrectly.Do one of the following to alleviate this potential problem:1. Have Campaign automatically handle input values of "Y" and "T" as "1" and values of "N" and "F" as "0".2. When the user designates a column as Boolean, have the user select from several predefined sets of possible input values: 1/0, Y/N, T/F, etc.3. Allow users to define a Boolean value remapping elsewhere in Campaign then reference it in the Column Properties dialog. This would allow the user to reuse the same remapping definitions on multiple fields.
It would be helpful to be able to add text boxes to workflows to contain comments from the workflow author.As workflows get more complex, these text boxes could be used to mark a set of related steps, give more information than can fit in the label for a step, and to provide special instructions to the viewer, such as conditions that must be fulfilled before running the workflow.The text box should be able to support different fonts, text sizes, colors, borders, etc.
Hi,it would be very nice if the "Extract File" workflow task were enriched by an "add all attributes" functionality: by dropping a target into the fields definition area all the attributes of the entity coming from the previous step are added.Fabio
It would be great if in the help menu of Campaign Standard there was a place to submit ideas and also get easy access to the forum. Every time I am looking for either I find myself search for at least 5 minutes.
Requesting Adobe Campaign Standard Search be changed to non-exact match and non case specific. As is, an email address search is not useful if case does not match or an exact match is not found. Please add this feature and rollout as soon as possible. Thanks
If the profile is extended to store custom data like e.g. Interests or Structural assignments those are not available in the dynamic reports.Would be very helpful to have those, since the custom files often are the most interesting ones.
By sending workflow data as the test proof instead of the test profile would allow us to validate that the variables within the workflow are accurate and provide us a view of what the customers are receiving.
Hi Team,Please find the steps to replicate the issue.1. Open any delivery and drag and drop any column structure2. Drag and drop Image components3. Click on Adobe assets button. Result: Getting following error clicking in screenshot below
For example we may want to additional value like "Non Binary" to OOTB Gender field's enumeration.
Hi,It would be nice to be able to add comments on every page of the documentation, like on php.net, e.g. https://www.php.net/manual/en/class.pdo.phpIt gives:- real life examples- snippet sharing- provides fix and best/bad practicesetcRegards
It only matches attributes in the root element but will not search in any toggled down sub elements.As an example: in the delivery schema find the contact date. If you toggle down the Delivery scheduling element and search the phrase again it works
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.
