We've consolidated all threads related to setting default options into this thread, including:All settings: https://forums.adobe.com/ideas/10122Report suite: https://forums.adobe.com/ideas/10194Default metrics: https://forums.adobe.com/ideas/10528Freeform settings: https://forums.adobe.com/ideas/9151Color palette: https://forums.adobe.com/ideas/10666Anomaly detection on/off: the start of this thread___Original ask for Anomaly detection on/off:It's fantastic to have gotten anomaly detection in Workspace in today's release. One point of feedback however would be that the function should be off by default when adding a new metric, with an option to turn it on.The reason we believe this is, workspace is used by a variety of end users throughout our organization (from technical to non-technical). For some of the non-technical users seeing an exclamation mark or anomaly has the potential to cause confusion and spurious concern. We therefore believe that having the default as off, would allow the anomaly detection to be more appropriately managed and used within our organization.Thanks in advance,Rory
Trivial quality-of-life request: currently, when editing a form field's label in HTML inside the Forms 2.0 editor, the focus in the form editor goes back to the field in question after updating the label. This behavior does not occur if the user is editing visibility rules; rather, once an update has been made, focus returns to the very top of the form. Could this please be updated to act the same way as label changes? This can be rather annoying on longer and more complex forms.
We recently upgraded from at.js 1.8.0 to at.js 2.2 - the newest library does not support QA links for AP activities. From support: "at.js 2.x does not currently support AP QA links"...previous library versions did and WE NEED THIS for our stakeholders, brand, and legal review of AP activities we create. Please upvote to get this functionality back in at.js 2.2 and beyond.
Need to be able to exclude from the Workload Balancer views projects with the status of Cancelled, On Hold or status equates to Dead, Hold, etc. I'm looking at a colleague with 72-hr, 22-hr, 12-hr, 12-hr, and 12-hr days (all in the same week) and the culprit seems to be Cancelled (=Dead) and On Hold (=Hold) projects. Am a system admin using Workfront New Experience 21.4 release Workload Balancer: Search All Fields. When I select Search All Fields, then use its search bar for status, pick either Project Status or Project Status Equates With (same result either way) the drop down box to pick the criteria for that field is immediately blank and if I click into it, it shows "no matches found". If I type into it it continues to show "no matches found". It also doesn't seem able to handle "Ors" as the 'grayed out' heading states "Include if all are true". A project wouldn't have more than one status assigned to it so even if this field worked it seems to me I'd only be able to exclude one status or equates with at a time.
I'd like to be able to hover over display logic codes to see what field the icon is matched to. The color matching is useless with longer forms.
Currently you have to open a custom form to find the option to deactivate. If you have any broken logic, you cannot save the form until you resolve broken links. For lengthy forms, this is insanely difficult. There should be a button to mark a custom form as inactive without having to open the custom form.
To produce a POAP, rather having the tasks / milestones in a tabular view on the left, can you please able to show the task name next to the milestone. Thanks
"As a user of processing rules, I want to be able to read more of a variable name, so that I can read a rule set easier; and not have to click on each one to read the entire variable name. This feature would reduce both my own propensity to commit innocent errors, and, reduce the propensity of those I manage to make errors." Concretely: the current width of the drop down boxes, now set at approximately 20 characters, is too narrow for today's product manager on the go. Whereas I appreciate the constraint of the fat left navigation, we do set very descriptive, girthy names for our variables. Thank you!
We are currently using WF across several agencies in different countries and are using Groups for our department structure as well as our various global agencies.It would be great if like all of the other ways to customize various settings by Group, if we could customize expenses by Group. Certain expense types aren't relevant for certain agencies.
I need to access Report Summary View on reports with calculated views. Often times I create advanced reports using text mode but the data does not aggregate on Summary view.
Issue: Extracting from the mobile AEP SDK "Target.getTntId" is very slow & "Target.getSessionId" does not exist. Details: Albertsons team is looking for ways to extract `sessionId`, `tntId`, `ECID` from the mobile AEP SDK as quickly as possible (to forward to another API call to load Recs).Observations:1. Testing `Target.getTntId` with callback, noticed that this promise-function always resolves after Target response is back. (Just like documented.) This took about 0.4 seconds on Vadym's simulator device with high-speed Internet connection. This is really slow.2. Since `tntId` is cached in the app, in reality we could always read it from cache to eliminate waiting for `tntId` via callback. This surely would improve the performance, however, it is an unsupported method.3. There is no `Target.getSessionId` available in AEP SDK. (Vadym understands it was not designed to be available, but in current case, it must be retrieved from cache, which is an unsupported method.) `Target.getSessionId` could potentially sync visitors between an app and web if the same session ID are passed. Today, only ECID sync is available between the app and mobile web or browser web.Feature Request: Offer a more efficient way to extract `sessionId`, `tntId`, `ECID` from the mobile AEP SDK by doing the following:1. Adjust `Target.getTntId` to pull `tntId` from cache when available and if not available then fallback to Target response.2. Add `Target.getSessionId` that behaves similarly to #1 pulling `sessionId` from cache when available or fallback to Target response.
Recently, deactivated users can now be assigned to things. Why this would be helpful escapes me. Why this would be harmful is obvious.Let's say I accidentally assign a really important task to a deactivated user, guaranteeing it will be ignored… and late. A great way to anger a client.I cannot think of a single good reason to assign anything to someone who does not work here anymore and will absolutely, 100% not fulfill the request.
There should be a way to send sample emails to yourself or others on your team to order to test all your A/B test variations in an email program. It seems this feature is not available now and you can only send a sample of the "A" version.
Issue: In order for me to create an audience that looks for visors within a 100 mile radius I end up having to make an audience filled with zip codes or city names. Feature: Please create a feature that allows me to quickly build an audience form the UI where by I specific the zip code and then select the option to extend that audience to 10, 20, 50, 100 miles of that zip code.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.