Currently, there are project level templates that can be attached to an existing project, but this requires higher access to the project to leverage. In order to limit access, assignees only have permissions within their owned tasks. However, they cannot leverage templates because of this without exposing the rest of the projects and potentially users attaching templates to the wrong tasks.The request is to add an option at the task level to attach a template of tasks under the current task as the default parent. This way, task owners who have permission to create tasks can do so using a template without worry of attaching the template tasks to the wrong parent task. Attaching a template at the task level would obviously ignore any of the template setup for projects. Only the tasks and the associated details would be copied from the template per the options.
Currently, once a task is created it cannot be edited and changed to a recurring task. In some instances, with our more complex processes we end up having to change a task to recurring task so we would like the ability to change a task to a recurring task.
There are various regulations governing the handling of Personal Identifiable Information (PII). Based on the definition of PII, if you can see a user's profile in Workfront, you can see their contact info and manager, and that is already PII. Workfront currently allows 4 controls allowing admins to restrict profile visibility using Access Levels:1) Access Level > Users > View - leave "View Contact Info" unchecked2) Additional Restriction: Users could View only companies, groups & teams they belong to3) Additional Restriction: People in other companies should only view users from...Their Company4) Additional Restriction: People in other companies should only view users from...Primary CompanyWhat is not offered is the ability to restrict People in other companies so they can only view user profiles from groups or teams at other companies with which they're explicitly working. There is an unfortunate limitation for us with current functionality, because if you can't see a person (in Search Bar typeahead) due to restrictions because they're at another company, you also cannot tag them in Update threads. Our organization relies on teams from various companies to collaborate with one another on Work Items. The visibility restriction makes it so we cannot allow users from different companies to tag one another (to get their attention thru notifications) when there is an update because it means they can see EVERYONE at the other company. We're pretty seriously hampered because we have to disallow people in Company A from tagging people from Company B if it means the personally identifiable info of everyone at Company B is exposed to Company A. PROPOSED IDEA: add another level of granularity so that users from one company can at least tag users from diffferent companies, as long they are all in the same team or group, while still preventing them from seeing ALL users from any other company. Plugging up this hole should allow maximum availability of the Updates tagging feature without exposing Workfront customers to liability of sharing PII unnecessarily.
Please align the features in the Workload Balancer to what is available in the Scheduler. We know drag and drop resource assignments are on the way, but it will be critical that we can identify project tasks by color. Simply, if I am looking at task assignments in the Workload Balancer, I can quickly identify other tasks in the same project by locating the same color. At a glance, this will help identify resource assignments.
It would be so nice if there was an easy way to export all products form a Catalog or Collection. BrendanJaffary
Currently the workload balancer does not permit issue hours to be modified per user/per day - the same way task hours can be edited. This is needed for Agile functionality so backlog work can be assigned - with specific hours per day during the iteration period. Currently the planned hours can only be rearranged - This doesn't permit true resource utilization data.
Description - Allow the copy and paste of mulitple recipients in the workspace share dialog windowWhy is this feature important to you - When adding multiple recipients to many workspace reports it would save time in the case where admin access is not granted for me and admin resources will not prioritize the use of publishing lists or groupsHow would you like the feature to work - Simple copy and paste of multiple email addresses would be added through a lookup to verify the members instead of one by one verifcation by typing each individualCurrent Behaviour - Must type each individual and select the intended recipient with a mouse click
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.
Currently, there is no ability to track if a user opens a project, issue, request, or task. It would be helpful if there were an activity log that would track what a user does in Workfront such as opening a project. This activity log will be used by system admins and exportable to leadership.
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.
「メールを開く」トリガーにある追加フィルターの「最小回数」について、実際には設定ができない(機能していない)ものの表示されているとサポートより伺いました。システムの仕様上、全てのトリガーやフィルターに追加フィルターとして「アクティビティ日」「最小回数」の設定が表示されているものの、「メールを開く」トリガーでは「最小回数」の追加フィルター機能はない為、最小回数の設定に関わらず最初の１回でトリガーが発火する仕様となっているようです。 フィルターで共通デザインとなっているためかと思いますが、誤解を招くのでこのようなフィルターを非表示として欲しいです。
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.
We are able to copy an entire custom form but I would like to be able to create a new custom form and drag and drop only specific fields from an existing custom form to the new custom form.
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
Rich text formatting on an update does not show up in reports. We have reports and dashboards with each project as a line item but we don't get any of the formatting on the report, which makes it harder to read.
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.
When using the auto provisioning process, data for attribute fields are passed for new user accounts and existing user accounts. Our goal is to create a process for auto-registration. If a person does not have an account and attempts to access Workfront, a basic "request access level" user is created. However, the "home group" field is required. I would like to have the "home group" field only updated for new users. Since we attempted to use a default value for the home group for new users, applying it to existing users can break reports and structures throughout the system. This functionality is preventing us from using the auto provisioning process.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
