Product Communities

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 num

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

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

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

Implement feature to rollback to previous revisions/changes for workflows and templates.It gives the user the option to switch between historical revisions and also drafts(that is changes not being saved)A good example can be seen in WordPress, Jira, Confluence, whereby users can rollback changes made to pages and even compare changes between revisions.

Hi guys,I  think we should have version control for Transnational  Messaging templates .Because when X creates  a template and Y working on the same .Y makes some changes which X is not aware .If something goes wrong during production stages we cant roll back or have name of person or version number  in the changed document.So its better we have version control system in adobe campaign.

It would be great to have the ability to preview delivery templates that use targetData using seeds where the targetData has been configured for the seeds without having to create a workflow.

Its good to have a locking feature by default on the campaigns/workflows/web-apps or any other such activities on the platform which are already in editing mode by an user.

It would be nice to get update for jquery library currently we have 1.9.1 which has some security vulnerabilities and we cannot choose not to load the library in our web app.

Using or trying to use successfully emojis in the mail object and Adobe Campaign classic (v6/v7) is a pain at the moment.In most cases, it doesn't work correctly, even by typing such sequence of chars:=?UTF-8?Q?=F0=9F=8F=A2?=By chance, if some people succede to use it (probably due to different contexts (version of AC or charset used by the AC environment), it often breaks with a mix of special characters to use.Please find a way to ease typing emojis in the mail object field.And don't limit such improvment to Adobe Campaign standard version, it must apply to AC v6/v7RegardsJ-Serge Biron

Installing Adobe Campaign Classic seems to be only possible with a GUI. For automatic deployment it is better is the choices can be also defined by parameters. And thus allow a silent install of the application that can be distributed to multiple of users.Note: the configuration of the application it self must be done by the users. i.e. what server to connect to etc.

When viewing the "hot click" report for a campaign, you can see the creative with the % of clicks overlaid. I would like to be able to export this "hot click map" (aka heat map" into a JPEG or PDF so I can share it with others, paste into a PPT, etc. The only way I can do so now is if I print my screen, but that often cuts off most of the heat map image in the current ACS view. This makes heat maps not very helpful, despite all email marketers wanting to see and leverage them.

The Creative email designer has been released (beta tests at the moment) but only for ACS (Adobe Campaign Standard version).Please make it available for Adobe Campaign classic version (at least v7, and possibly v6).