Skip to main content

Filter by idea status

10000+ Ideas

KatherineLaNew Participant

Boards Enhancements - Intake Column AdditionsNew

Description - Within the existing Board design, the Intake column does not display the Due date of the Task or Issue on the face of the card until it is brought into a main column. Nor is that column sortable by any of the same options supported for the rest of the columns that have been created, even as a partial solution. This makes it a barrier to user adoption, as they have no way to understand what is being asked of them first without opening each card in the Intake column to find the information. Why is this feature important to you - For any team or individual trying to manage their workflow on a Board, the ability to quickly understand 'what is being asked for first'? is critical to the usability of the Boards. Without that easy visibility, teams may prioritize discussions about items that are not as time sensitive as something later in the list. For any team or individual with more than a handful of work requests, this is simply unrealistic to expect and they are switching back to old task and issue reports to manage their work.How would you like the feature to work - The 'Planned Due Date' field should display on the face of the Intake column cards exactly as it does in every other column. Clicking 'Sort By' should affect the Intake column exactly as it does every other column. Current Behavior - Field is not displayed, and Sort functionality does not affect the Intake column at all.

Perrin_Ennen
Perrin_EnnenNew Participant

Modification of the prehiding logic for websdk for redirects offersNeed info

What is the current situation? I currently have the problem that redirectOffers are running in Activities on a page with the WebSDK (asynchronously via Adobe Launch / Data Collection). The preHiding snippet is also used. Yes, at the first alloy sendEvent the style with the id alloy-prehiding is removed accordingly. But this is unfavorable for redirect offers because the page may be displayed before the redirect takes place.   To fix this, I have currently built this workaround. I make an alloy sendEvent in Launch. I also pass the desired data to AT. What is new now - is that I additionally check in the promise with .then whether has_schema(data, “personalization/redirect-item”) contains. If this is the case, I know that this is a redirect offer and insert an additional hiding. In this case, not the default document.body.style = “opacity: 0;” - but that I only use the cmp-container and page-wrapper style classes in my setup here. I also do not insert the id alloy-prehiding here. As this is a redirect - I am not adding a timeout here either (you can of course extend this accordingly).     What should the feature do? My idea is - that I don't have to do this myself, but that the WebSDK itself checks whether a redirect-item is contained in the first alloy sendEvent call. Or at least the option that a checkbox with a field for custom CSS is available here, for example.   Note: I am aware here that with a very slow connection - the problem is that the normal prehiding snippet is removed after 3 seconds anyway - before Launch has been executed if necessary.   Example code how my current workaround is: var data = { '__adobe' : { 'target' : { … } } } alloy("sendEvent", { "data": data, "renderDecisions": true, "xdm": { … } } }).then((data) => { const is_redirect = has_schema(data, "personalization/redirect-item") if(is_redirect) { const style = document.createElement("style"); style.innerText = '.cmp-container, .page-wrapper { opacity: 0 !important; }'; document.head.appendChild(style); } })

JillClNew Participant

Proof Download & Print Functionality - Format of CommentsNew

ISSUE: PROOF DOWNLOAD/PRINT FUNCTIONALITY – FORMAT OF COMMENTSAgency Project Managers are the gate keepers of the feedback, ensure all feedback is in and actionable, then download to share with the creative and strategy teams for next stepsThe issue is that neither version available for download using the “print” function are ideal for feedback review – and we end up pulling both versions down and our creative & strategy teams manually toggle between both to transcribe feedback back into the source document. Below are the issues with the different formats:Proof > Print > Print as PDF: Challenging to read. Lengthy comments stack on top and it is hard to see final direction. Comment thread numbers are referenced in comments, but not visible in this view. When comments are not tagged to a specific spot they float. This version takes a significant amount of time to arrive in Outlook inbox and often causes delay.Proof > Print > Standard print (Green Button): Challenging to read. View of document is very small, hard to tell where the comment is tagged. Comments are grouped by thread numbers, but out of order of where they occur within the document.Impact: High impact for all projects, high risk for errors, additional work for project management and creative and strategyIdeal solve: documents uploaded as a proof would remain in their native source file format and could be downloaded and shared as such and comments are then in a live, actionable document format and not a locked PDF file format