Build better products with our product team
Add a column with a True/False for Hidden to easily identify which fields in an export are hidden.
To fully utilize the mark up feature in proof, we would like to be able to generate and mark up a proof prior to submitting an issue to the request queue. Currently, one can upload a doc to a submitted request and then convert it to a proof. Depending on the speed of project conversion, the issue could become a project before the requestor has the opportunity to mark comments, leading to confusion and communication break down between the project converter and the requestor. Allowing Proof Generation in Issue would provide an opportunity prior to submission for the requestor to make all of their notes in the proof before triggering next steps.
Hi,Activities create variables with the shared array vars.* and change the output schemaFor example:- Input example: A Loading data (file) configured with "specified in the transition" is in fact using "calculated: vars.filename", so any change to vars.filename before the data loading will corrupt it- Output example: After a delivery, the transition contains the broadLog schema where vars.recCount is the total number of broadLogs- Output example: A post-processing delivery workflow contains the delivery id via vars.deliveryIdCan we get documentation on all of this? It would be better than reverse-engineering and guessing the codebase..ThanksRegards
In the documentation, a bad practice for developper is unwantedly suggested:https://experienceleague.adobe.com/docs/campaign-classic/using/configuring-campaign-classic/api/data-oriented-apis.html?lang=enTo limit the number of records returned by the query to 100:<queryDef schema="nms:recipient" operation="select" lineCount="100">...To retrieve the next 100 records, run the same query again, adding the startLine attribute.<queryDef schema="nms:recipient" operation="select" lineCount="100" startLine="100">...In fact, a dev should never use the startLine attribute as it contribute to a loss of performance:exemple with a SQL translation of the 1rst example:select top 100 from nmsRecipientYou'll get the 1rst 100 records... No issue about that Now is the SQL translation of the 2nd querydef:select top 200 from nmsRecipient=> as the startLine begin at 100, the "top" will start at 100 and add the line count attributes (100) ... Then the JS engine will keep the last 100 recordsThis doc is used by developper to create code in order to loop over all the records of a table as queryDef are limited to 10000 records usually:Imagine a loop with a lineCount of 10K... If you want to use a queryDef in order to operate on a 100K table: it will creates 10 sql queries, retrieving each time 10k more results leading to retrieve 550K results instead of 100K and each requests to be more greedy on performance (10+20+30+40+50+60+70+80+90+100). The good practice should be then to use an Id (directly the id of the schema or a rowId from a wkf work table if possible) in the where clause in order to replace this "startLine" attribute:<queryDef schema="nms:recipient" operation="select" lineCount="100"><where> <condition expr="[@id] > " var.lastProcessedId /></where></queryDef>I observed in the past some workflow JS activity with the "startLine" implementation that were optimized from 4h down to 2 min. Placing a warning in the documentation in order to inform that they should never use startIndex as a way to loop over a schema would be really helpfull, specially for beginners. Ps: TY @cedricrey for this tip months ago
It would be great to have the ability to change the font size, style (bold / standard), and color (maybe) in the titles of panels and visualizations.A crude illustration:Source image file 21787 not availableThis would make it more feasible to do some degree of grouping of views of the metrics, as well as to draw the user's eyes to the key visualizations.
「メールを開く」トリガーにある追加フィルターの「最小回数」について、実際には設定ができない(機能していない)ものの表示されているとサポートより伺いました。システムの仕様上、全てのトリガーやフィルターに追加フィルターとして「アクティビティ日」「最小回数」の設定が表示されているものの、「メールを開く」トリガーでは「最小回数」の追加フィルター機能はない為、最小回数の設定に関わらず最初の1回でトリガーが発火する仕様となっているようです。 フィルターで共通デザインとなっているためかと思いますが、誤解を招くのでこのようなフィルターを非表示として欲しいです。
Rather than create additional smart campaigns/flows to accomodate this, it would be really useful if system tokens (or even a local token) can be used as the default value for a form field - often times these are hidden fields. For example, when someone opts-in to receive future email communications from us, we need to date-stamp an "optin date" field with the time/date that this took place. To be able to use the {{system.dateTime}} token as the default value would be very convenient.
When an anonymous leads is crated during a visit to our website, we set values in ithe newly created record's 'Initial Online Source' field and other fields that tell us the source of their initial visit to our site. Later, if a known record for the same lead is created by Sales, we don't set the Initial Online Source field and leave it blank. Then when we send an email to the lead and the lead clicks the tracked link, Marketo merges the anonymous lead record with the known lead record. However, the resulting merged record's Initial Online Source field is empty.This is unexpected as the 'Merging Leads: Behind the Scenes' help article (community.marketo.com/MarketoArticle?id=kA050000000KyszCAC) states that, "When merging a lead with an empty field with another who has a value for that field, the merged lead will have a value in that field."Paradoxically, Marketo does clear set a standard field's value to empty when automatically merging an anonymous record with a field value and a known record that has no field value.My suggestion is that when Marketo authomatically merges an anonymous and a known lead record, any field with a value should be preserved if the other recrod's field is empty.
Description - When there is an error with an activity, provide users with the opportunity to see the details of where the error lies in order to fix it.Why is this feature important to you - It would allow for tremendous time saving when building activities as well as allow for an easier learning curve. How would you like the feature to work - When you see the error in the UI, you also see specific details of the error location. EX: Sync failed for XXX at path: XXX Status: XXXCurrent Behaviour - If you come across a sync error or the like, you have to contact Adobe Client Care, where they have the access to detailed logs and can tell you exactly where the error lies.
Most companies rely on many solutions across different departments, divisions and tech stacks. For a multitude of reasons, it is not always possible to host all Forms within the Marketo instance.As we capture information and learn more about our customers and prospective customers, Pre-fill is an important capability that companies rely on. Pre-fill is a key part of a Progressive Profiling strategy, and will become more and more important as new Privacy / Transparency in Communication Compliance laws are put in place.It would be a tremendous asset if Marketo Forms supported Pre-fill capabilities when embedded into other landing page solutions such as LaunchPoint partners (InstaPage, etc). This would enable marketing automation teams to develop a lead/data capture strategy and roll it out across multiple departments/divisions solutions with a consistent user experience and results.#marketoform #prefill form #non-marketo landing pages
Description - I worked in a Tech Ops team where I was the only Windows user, my colleagues where all Linux users, and during knowledge sharing sessions we had to look for Windows emulators that could be installed on their Mac machines to no avail, most crashed on certain operations. And the question still lies, why has Adobe not developed a client for other operating systems?Why is this feature important to you - Important to the whole industry.How would you like the feature to work - Allow ACC client for other non-windows Operating Systems.Current Behaviour - only windows
Description - File resources currently has limitations and issues around trying to re-upload files with updated code, annoyingly enough, the only way around is to change the file name and re-upload a new file which fills up file resources folder with a lot of junk. Furthermore, while deleting the file from the file resources folders gives the impression of file deletion, this is not the case, it still lives in the server, even after I run a shell file deletion script which literally removes the file from the server, the file still is accessible from online, as if it was cached by cloudfront perhaps?How would you like the feature to work -Enhance the file resources form provide an actual file manager which allows advance file handling and search functionality.Upon uploading new file, allow file replace so that users don't end up uploading dozens of variants of the same file which fills up file resources folder. (particularly annoying while working with css and js file, where changes are done frequently and require alot of code refresh)Allow acc to call cloudfront, or whatever caching module is being used as to force expiry of cached assets to allow us to test in real time uploaded files.Allow file upload whitelisting control filters from file resources, currently this is configured from within serverfile, perhaps creating an admin control zone that allows these filters to be controlled from within the client will be easier to manage.Current Behaviour - lacking features, bugs, limitations
It would be helpful to be able to arrange the icons on the left of the document summary panel to be more efficient for my teams use case. They are finding it difficult to scroll through all of the information the y do not care about and it is not very easy to read through to find the section needed
Please make it possible to remove the deactivated Workfront users from the Proof "Users" tab without deleting their Workfront accounts.If that cannot be achieved, then can you please add sort or filter functionality to the Proof Users area so that we can hide those deactivated users, or at least group them together.We're getting overwhelmed by all the deactivated users mixed in with active ones and having visibility on who has which permissions.
Description - Enhance native webapp error validation to be in line with modern web standardsWhy is this feature important to you - modern web developmentHow would you like the feature to work - to be more inline with bootstrap, currently, an ugly error pops up on the top left hand corner, and error validation is only done after the user submits the form, perhaps this could be enhanced to perform validation on pre-submission, I've had to completely supress native error validation by using bootstrap and a lot of custom code. furthermore, enhance the error box to be displayed under the field rather than top window, this is bad usability experience.Current Behaviour - errors displayed on top-left corner of webapp Suggested behaviour, below, is my bootstrap validation which is what AC webapps validation should be providing natively.
Description - Allow Custom Target Mapping access to subscription servicesWhy is this feature important to you - Multiple client's requestsHow would you like the feature to work - If I create a custom recipient target mapping, they should be able to be registered against subscription servicesCurrent Behaviour - Custom target mappings cannot access subscription services
Description - Current connector does not allow ACC to fetch data from ms dynamics viewsWhy is this feature important to you - Should be a standard feature which is not working on current connectorHow would you like the feature to work - Allows ACC to fetch data from ms dynamics viewsCurrent Behaviour - Can only pull data from tables/buckets but not views.
We use data feeds to send Post Processing events from our app and web report suites through to S3 each hour, where we use that data to combine with other streams. Unfortunately Data Feeds sends the data with the timestamps from each hour collected, rather than the data collected during that hour. This means that where we use offline data collection in our apps, and the data is stored to be sent to Adobe later, the hourly data feed doesn't pick this data up. This can result in our data being up to 10% out of what we see in Adobe Analytics Workspace.This impacts our ability to use digital data to drive machine learning models or to understand performance and opportunities.Data Feed sends data collected in that hour/day/time period selected in the config.Currently Data Feed sends data for actions performed in that hour/day/time period.
Pretty self-explanatory. I have a batch smart campaign that I need to run every hour on a daily basis with no end date. Since "hour" is not a frequency option, I had to create 24 recurring batch smart campaigns to achieve this result. I'd much prefer to manage this through on smart campaign, as opposed to 24!
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.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK