Build better products with our product team
Description -While conducting our first real-life implementation case for data collection via the AEP Web SDK and the Edge Network, we wanted to rely on the out-of-the-box customer consent preferences:https://experienceleague.adobe.com/docs/experience-platform/edge/consent/supporting-consent.html?lang=en However, while experimenting with the different options available, we were facing major limitations with regards to the flexibility of handling the consent - in particular with the current consent object: consent: [{ standard: "Adobe", version: "2.0", value: { collect: { val: "y" }, metadata: { time: "2021-03-17T15:48:42-07:00" } } }] Mainly, I'm referring to these two limitations stated in the official documentation:#1 No granular consent handling:"Currently, the SDK supports only a single all or nothing purpose." #2 No overwriting of the collected consent:"After a user has opted out, the SDK will not allow you to set the users collect consent to y." Why is this feature important to you -RE#1: Modern consent management solutions such as OneTrust offer great flexibility and granularity for the user to decide which type of cookies and tracking solutions he/she is opting-in or not (e.g., first- vs. third-party). However, this can't be reflected with the current AEP consent object as it only takes binary inputs. This can result in fewer opt-in rates and/or data coverage because few users decide to go "all-in" and respectively the consent object has to be set to "n" which prevents any tracking to happen. Since data is key to the measurement of all kinds of marketing activities, the amount of data points captured is key, less coverage means less meaningful insights which ultimately can make client-side tracking solutions redundant. RE#2: As the user can opt-out this value of "n" will be irreversible written onto the AMCV, meaning in reality, for this particular user we will never ever be able to track any kind of data (unless they empty the browser's cache, switch devices etc.). This is even more severe as it drastically limits the potentially tracked users and can even have a disastrous impact when for instance, the value has been set to "n" by mistake. How would you like the feature to work -RE#1: Instead of just offering "y" or "n", give the flexibility to set different tracking categories within the consent object which correspond to different cookies/technologies (e.g., functional, first-party, third-party): consent: [{ standard: "Adobe", version: "2.0", value: { collect: { functional: "y", tracking: "y", marketing: "y" }, metadata: { time: "2021-03-17T15:48:42-07:00" } } }] RE #2: Just add the capability to either reset and/or update the value that has been previously submitted as the consent object would tremendously help in overcoming the initially described limitation. Current Behaviour -As explained above.
Description - The new "Boards" column in reporting displays a "Show" button that must be clicked to show the data. Why I gotta click Show? Seriously, if a have a list of 200 tasks, why do I have to click "Show" 200 times? I'm curious about the thought process regarding this "feature".Why is this feature important to you - I don't want to have to click show over and over to find what I'm looking for.How would you like the feature to work? - Just show the data!!Current Behaviour - User must click "Show" to see the data.
Description - wouldn't it be great to have workfront actively inform you if a resource is over allocated at the task level? Why is this feature important to you - resource leveling works great, but is on a seprate screen, and when using shared resources the resource's hours changes as other PM's book projects. it would be great to see at the task level that a resource assigned to that task is over allocated so you can adjust on the fly. How would you like the feature to work - at the task level, pull in the current user(s) hours for the duration of the task's assigned to them with the same behavior as resource manager, highlighting that a user is over or under allocated. Current Behavior - Currently there is no way to know a user is over allocated unless you actively check the resource manager. if a task is late there is no telling how that task pushed is going to effect the resources timeline without actively going to another window to check.
Self service flow step does not send Munchkin ID in its header. This prevents identifying the instance and providing the correct logic in return.Request you to please send Munchkin ID in the header, so we are able to identify the instance and provide appropriate logic. Thanks,Arvind
Description -Set the Month of Year dimension to be configured to each report suite's calendar type. Why is this feature important to you -We use the 4-5-4 for our report suites and this dimension is based on calendar year for the order. Other metrics like day of week adjust based on the calendar format set for the report suite. How would you like the feature to work -Set your date range to last year (according to NRF 4-5-4 Calendar). Rows for Month of year would be 1. February2. March3. April4. May5. June6. July7. August8. September9. October10. November11. December12. January Current Behavior -Set your date range to last year (according to NRF 4-5-4 Calendar). Rows for month of year would be 1. January2. February3. March4. April5. May6. June7. July8. August9. September10. October11. November12. December Link to my previous post with comments from Adobe team mentioning their thoughts on this recommendation (see comments): https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-questions/request-update-month-of-year-dimension-order-based-on-report/m-p/635868
Request for Feature Enhancement (RFE) Summary :Currently, Card view in AEM Assets is staggered. Metadata displayed on the card as well as the asset's format can push assets below it down, and the rows are not even. The staggered view is hard on the eyes, when trying to pick the right asset. When we scroll down to view more images, the pages redraws and assets keep moving around. This has been very frustrating to our users and this is the most common enhancement request from our users. Our request is to make the Card view grid-like, where all rectangles in a row are aligned. Use-case:Search results and browsing assetsCurrent/Experienced Behavior:Currently, Card view in AEM Assets is staggered.Improved/Expected Behavior:Card view is grid-like, where all rectangles in a row are aligned.Environment Details (AEM version/service pack, any other specifics if applicable):AEM Assets 6.5.6Customer-name/Organization name:Wakefern Food CorpScreenshot (if applicable):............................Code package (if applicable): ............................
Product - Customer Journey Analytics (CJA) Description - Date and Time Filter in Segmentation (Reporting Segmentation)Why is this feature important to you - To segment data from date & time dimensionHow would you like the feature to work - seamlessly Current Behaviour - Currently we are unable to filter a date range in with a segment given a date/time is in dimension ex - transaction date. To make matters more complicated this transaction date is present in profile dataset. For such cases it would nice to have segmentation for date range like we have in the data view to filter such as "before" or after a particular date. I have attached screen shots currently in data view and segments as a reference RegardsShrikar
There is an abundance of issue/task/project data available in the 'Updates Collections'. Currently, the data in these collections can only be displayed, as is. The Updates Collection data can not be manipulated with expressions (eg: specifying an expression to retrieve only a specific update type), as with other Collections. This was confirmed with Technical Support. It would be very helpful to be able to use expressions with the Updates collection, to aid in reporting. Thanks
Currently, using calculated fields, you can calculate the total duration of an object - project, task, issue - approval. However, if the approval has multiple stages, it is not possible to see the duration of each stage, to determine bottlenecks or roadblocks. You can only calculate total duration.
Description - To be able to have an upload field related to a topic in a custom form, it would be helpful to have an upload field as a custom field type. Why is this feature important to you - We have several briefing forms, which require to be able to upload documents related to different fields included in the form. How would you like the feature to work - Being able to add an upload field at any position in a custom field. Perfect would be, to be able to define a target folder individually for each upload field. Current Behaviour - We only have a single upload field at above or after a custom form. If the requestor has to upload different documents, he/she has to remember, all those to do it after / before filling the form completely.
Description - I would love to have access to a new field type to select a period of time (from - to)Why is this feature important to you - To be able define a periodHow would you like the feature to work - classical "Date Range Picker": 1st click: calendar popup, 2nd click: set start date, 3rd click: set end date, 4th click: applyCurrent Behaviour - Currently two date fields have to be added where we do not have any kind of verification if the date selected in the second field is after the first one. RegardsLars
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.