Explore product-specific spaces to ask questions, share insights, and learn best practices.
Recently active
Show the number of selected tasks. Will help make sure you do not have multiple tasks selected when deleting or moving within large tasks / workbook.
Description -Implement a hashing solution to the Adobe Launch script to avoid security issues such as an attacker tricking a user into downloading content with altered scripts from the compromised serverWhy is this feature important to you -It would ensure secured delivery of the scriptHow would you like the feature to work -Provide an out of the box solution to hash the Launch script for added protectionCurrent Behaviour -No built in tool currently exists in Launch
I am looking for a way to make issues (requests) read only for a group of free users. View permission still allows for posting updates, however, we want to restrict these users from posting updates in the historical requests they have submitted. A true READ ONLY level of permissions would be very helpful
It would be preferable if Workfront could implement the following enhanced features within the timesheets in Workfront:Ability to distribute a set number of logged hours against several projects and/or tasks on timesheet in one entryEffortlessly filter timesheet line items by searching keywords, job codes, etc. Capability to custom freeze columns and rows and view the entire month, not just week, in one screen on timesheets
We would like to see an update in the update feed along with a link in the header of the project and request when requests are converted to projects. I have added screenshot examples below:
Currently, Marketo offers some "Bulk Export" functionality for situations where latency can be higher and many records need to be exported. This is marketed as an alternative to real time calls. However, transitioning from real-time calls to the bulk export feature is not straight forward because the data offered by the real-time call exceeds what is offered in the bulk export call. This specifically affects the data in the "Attributes" property that is offered by both API calls. The real-time call returns more data in that field than the bulk export call. For consistency and to avoid additional API calls when transitioning from real-time to the bulk export API, it should offer the exact same data points in the "Attributes" property as the real-time call.
you should not have to be an admin in order to create or change a workflow. maybe the admin could just give permission to a person to change proofing workflows
Allow Administrators to monitor Email Notifications. Administrators can not tell if Notifications have gone to update a user work was assigned to them. Even if there is just a log for review by the Administrator so we can verify what has gone out.
Allow users to effectively use formatting options like bold, underline and italics within ProofHQ comments. Our business has specific formatting requirements that need to be met for various regulations within creative being reviewed, and without the option to use formatting, the requirements are often missed or misinterpreted between rounds of review.
It would be nice to be able to clear logs and events from one place and/or have the option to not persist between reloads. Why is this feature important to you -It is annoying to have to clear logs and events in different tabs every time I reload.How would you like the feature to work -Under settings you could have a clear all data button and a persist data check box. Current Behaviour -You have to clear logs and events from different tabs.
Training Assets Repository We generate training assets on a regular basis; video recordings of sessions, documents, PDFs, etc... We would like to set up a library within Workfront where users can quickly find what they're looking for across a range of subjects.
It would be great if we could target report emails to users the report applies to rather than it going to an entire group/team/user list.Example - a project report showing projects that are overdue by 10 days or more, sent weekly but only to the owners of those projects and their managers.The recipient section of the recurring email menu would allow you to either select user fields that appear in the report or to add parameters in the same way you build reports.
For agile teams it is difficult to show future capacity/workload and predict when we will need extra resource. Instead of a list for the unallocated resource, it would be useful to show if there is capacity within the team to get these task completed. So if everyone in the team was allocated work to be at max capacity, is there enough resource to cover what needs to be achieved.
The "idea" is to stop counting API users towards the number of licensed users. Assume you have 25 users as baseline and you add a couple of connections, you cut your users in half pretty quickly. In addition, there are separate limits (quota, rate, concurrency) that are shared across all the API users anyway , so it's kind of double-penalizing the usage. Would be nice if this would be changed, so people do not have to go for an API gateway approach (although that comes with different benefits of course).
Markto Outlookアドインのセールスメールについて、受信者がセールスメール開封時にアラートを出しております。 ただし、送信者が送信済みメールを開封しても「セールスメール開封」のアクティビティが付いてしまうため、送信済みメールを確認できるよう自己表示を防ぐ方法、あるいはシステム改良頂ければと思います。 以下設定を組みましたが、結果自己表示は防げませんでした。 自己表示を防ぐ https://experienceleague.adobe.com/docs/marketo/using/product-docs/marketo-sales-connect/email/common-tracking-questions/preventing-self-views.html?lang=ja 送信済みのメールは確認する場合があるため、確認時の自己表示が防げるとアクティビティ精度が増すと思われます。 検討、ご対応の程お願いいたします。
We need the ability to use the Workload Balancer's features on Unassigned Work to placeholder-in allocations in order to judge what Workes might be the best fit.We use a pool system so sometimes we need to see how the allocations might work FIRST to find the best Worker fit.
Currently when viewing issue details, the overview details are automatically open and provide a lot of details that are not necessary for everyday users to view. Custom form details are typically more pertinent so it would be great if we had the ability to rearrange the order of the Issue details to put the Custom form details above the overview, or at the very least automatically collapse the Overview details so they arent expanded by default.
The idea is to separate the permissions between custom forms and custom fields, to allow people to create forms, but not create new fields.We hold the governance of new custom fields at a Global admin Level, which means we have to create all forms as well. This makes sure that our group admins in every agency and market in our global network do not end up creating 100s of duplicate fields (either in language or slightly different naming for the same data etc etc) in our single instance. As this would 1 make a mess of the system and 2 break global reporting. We need to be able to allow our group admins to only be able to create new custom forms, and not create new custom fields.
Description -When using Adobe Launch oob, you insert a script to your website that points to "assets.adobedtm.com".As it is possible to get CNAME from Adobe for Analytics and Target (which helps a lot with Cookie issues), Adobe should offer this for Launch, too.Why is this feature important to you -I think it is important, because many "browser privacy tools" may block the domain "assets.adobedtm.com", so the Tag Manager is not loaded for those visitors.I really appreciate that Launch offers a "self hosting" option, but it is struggle to get this done with internal IT (at least for me).How would you like the feature to work -Just like the CNAME program for Analytics/Target, it should work the same way (including a SSL certificate for the new CNAME).Current Behaviour -As I said above, the default Launch domain may be blocked as "browser privacy concerns" are rising. It would be a good alternative for "self hosting"
We recently ran into a issue where our salesforce instance was throwing in query errors when we try to add mkto leads to campaigns. The list size was over 500 leads. I tried syncing in 100 leads at a time and it went through no problem. I understand this to a salesforce issue and is a result of multiple processes/flows that are triggered during the sync. But, if only there was a way/option to send in leads in smaller batches within marketo. A way to automate this inside a flow maybe, let marketo know only to sync 100 at a time, then the next batch etc, till we resolve the issue with Salesforce?
A lot of our Users often use "Request More Access". When we click the Request Access name drop down, the box is so small it cuts off people's names. Any way to make the drop down box bigger so we see full names? Anyone else think this is a great idea? Thank you! Jay Schertzer
Currently, the only way to know that a project was copied from another project is that "Copy of xxx" appears in the Project Name. However, project names can easily (and will likely) be changed. It would be helpful for this piece of information to be written into another field or tracked in the project history.
機能強化リクエスト(RFE)のサマリー: Get logs more than one week from Cloud Manager ユースケース: When we receive Alert notification from Customer, We can retrace its past and survey it. 現在/過去のビヘイビアー: Within one week 改善済み/予想されるビヘイビアー: more than one week (for as long a time as possible) 環境の詳細(AEM バージョン/サービスパック、該当する場合はその他の詳細): AEM as a Cloud Service 顧客名/組織名: スクリーンショット(該当する場合): コードパッケージ(該当する場合):
Currently to change the condition of a task while making an update, the user must be assigned to that task OR they need a view on the task list that shows Condition so they can change it on the task list.A user not assigned to the task, needing to use a view on the task list to change the condition poses 2 issues.they risk changing the condition on the wrong task since they are not making the change within the task itselfour uses still need to make a comment on the task if they are changing the condition, so it's a multi-step process to make the comment on one page and change the condition on another page, likely also needing to switch the view of the task list so they see a Condition columnI can see some companies not wanting users who aren't assigned to the task to be able to change the condition, so ideally this would be able to be turned on/off in setup.
Collapsed view of tasks on Kanban board does not offer enough information. Only shows task name. Issue - If you have several Search Results Banner tasks to design you will see a bunch of tasks that say Search Results Banner with no other information. You can’t tell which task goes with which project unless you add a bunch of information to the task name which clutters up the actual task. If you expand the card, the width of the card blows out the column (BUG previously mentioned). Right now, we have to add tons of information to the task name as a work around.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.