Product ideas | Community
Skip to main content

Filter by idea status

10000 Ideas

Andrew_Wathen_
Andrew_Wathen_New Participant

Virtual Report Suite Curation: Impact on user created components prevents useNew

My organisation has been trying to move to using curated Virtual Report Suites.  However, we have had to abandon these plans because of the following 2 main problems:1) Segments can either be shared to everyone or no one2) Users who create segments metrics are unable to see what they createDetails of the issues encountered...There are now 3 administrative capabilities relating to segments:User admin control over creation of segmentsSharing of segments (e.g. clicking “share”)Customization of Virtual Report Suite Components (VRS Curation)Unfortunately, they interact with each other in bizarre and contradictory ways.  However, all the problems seem to stem from the “Customization of Virtual Report Suite Components” capability.Issues observed:The sharing of segments becomes all or nothing.          This is because:Any segment that has been included in VRS curation become visible to all users of that virtual report suite (even if the segment is not “shared”)Shared segments that are not included in VRS curation cannot be seen by any usersThis means:Either everyone gets a segment, or no one gets a segmentThe segment “share” functionality in analytics becomes completely redundantUsers who have been granted access to create segments suffer a poor/degraded experienceWhen a user creates a segment it is not a curated segment within the virtual report suite and is therefore blocked from appearing in the left-hand rail.This break a well establish workflow leading to much confusion as segments do not appear where users expect them.(Note: users aren't actually blocked from using segments they've created as they still have the capability within the panels to create segments in the project.)

estelito
estelitoNew Participant

Ability to download PDF with annotations annotated in the Document Cloud PDF viewerInvestigating

Request for Feature Enhancement (RFE) Summary: Using the features provided by Document Cloud PDF Viewer as outlined in this link: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/assets/manage/manage-pdf-documents.html?lang=en#multi-page, we can annotate on PDFs (and other document formats converted to PDF).However, the annotations can only be viewed by someone who has access to AEM. In the case that someone who doesn't have access to AEM needs to get a summary of the annotations to a particular document, it is currently not possible to download the annotated PDF as displayed by the Document Cloud PDF Viewer. There is no download/print/export button available, and even the "Print" button on the main toolbar for an asset won't print the pdf in full (that one only prints the first page rendition of the asset). Use-case: Users without access to AEM needs to get a copy of the asset (PDF or converted to PDF) with the annotations that was added in AEM. Current/Experienced Behavior: Cannot download the PDF with annotations. Improved/Expected Behavior: Provide or enable a "Download" / "Print" / "Export" function in order to get a copy of the PDF with the annotations Environment Details (AEM version/service pack, any other specifics if applicable): AEM Cloud, latest version Customer-name/Organization name: <redacted> Screenshot (if applicable): the document cloud pdf viewer with annotations that we want to get a download/copy of.the output of clicking on the "Print" button in an asset's toolbar     Code package (if applicable):  

Casey_Grimes2
Casey_Grimes2New Participant

Correct validation for SVG files uploaded into Marketo EngageNew

As someone working within Marketo's Design Studio section, I often find myself leaning on a tool called Adobe Illustrator to design SVG images.   You may have heard of it.   Unfortunately, when validation rules were set up to check SVG files in Marketo Engage's Images and Files section, a mistake seems to have been made. When you use the default SVG Export Plugin, which Illustrator very much points you towards, the output contains xlink code. This is most commonly noted in the opening tags (xmlns:xlink, xml:space), but it also rejects any code within the SVG that is intentionally using xlink! For example, I have had to replace <clipPath id="SVGID_2_"> <use xlink:href="#SVGID_1_" style="overflow:visible;"/> </clipPath>  with alternate options—effectively making me redraw the entire graphic. While the community has offered some stopgap ways to address this (spoof a different MIME type, use one very specific form of SVG output), this is really counter-intuitive from a company that owns both products.    I also want to emphasize that, from an infosec point of view, I completely understand why xlink has been treated this way; however, a better experience would involve accepting the SVG upload, then sanitizing the output before it's stored in Marketo. There are plenty of SVG options for doing this. This makes especially little sense when the xlink is not leaving the SVG document itself.

HachidoriNew Participant

Request for system setting to allow option to increase the number of Custom Forms allowed per ObjectNew

Description - Background: There is a large project that personnel had added 10 custom forms to, on templates that were previously set-up (I'm sure personnel at the time didn't realize there was a limit to custom forms allowed per project). There is an 11th custom form I need to add, that is added to every project because it has calculated fields that auto-add to reports, for delivery managers and leaders to see unique project information in the most efficient view they require for planning purposes. Issue:Due to the hard system setting that limits the number of Custom Forms allowed per Object to only 10, and due to all 10 forms currently being utilized on this particular project, I am unable to add the 11th custom form required for reports (I can't delete any of the other forms, as they are all being utilized for the project). Why is this feature important to you - As stated above, the 11th custom form I need to add is admin-only, and is required to be added to every project because it has calculated fields that auto-add to reports (for delivery managers and leaders to see unique project information in the most efficient view they require for planning purposes). Due to the 11th custom form and associated fields are admin-only, I'd prefer to not have to add the fields to other forms as a workaround; however, I understand that may be my only option for now, to add fields within a Section set for privacy, admin-only on a form already on the project. Current Behaviour -The main issue is that I am unable to add to this required admin-only custom form to the project due to all of the other 10 forms are being utilized on the project; I'm unable to delete any other forms to add the 11th required one. Any work-arounds would be inefficient time-wise and communication-wise; it would be easiest to be able to increase the number of forms allowed to '11' in the systems settings. I called Workfront Support, and was told that the feature to update the number of Custom Forms allowed per object, in the System Set-Up, is not an option at this time. How would you like the feature to work - I am requesting for system setting to allow the option to increase the number of Custom Forms allowed per Object (in this particular case, to '11'.  

Lyndsy-Denk
Lyndsy-DenkNew Participant

Document and flag effects of Timeline Calculations settingNew

Description - In Setup > Project Preferences > Projects there are two fields under Timeline Calculations. If you change these fields, it adjusts all existing project and template Planned Durations and Planned Hours. I learned this the hard way when trying to configure our system to support more specific resource planning. The only way to bring your Planned Durations and Planned Hours back to neat numbers it to manually update, which is prohibitively inefficient. I wish this fact had be more obvious.Why is this feature important to you - With better understanding of the consequences of this setting, I would think more carefully about if and when I changed the setting. If opting to change the setting, I could plan work to bring our Planned Durations and Planned Hours back into more friendly alignment without bothering users too much.How would you like the feature to work - Update the Experience League documentation to clarify what these fields do by providing examples. Additionally, add a quick tip/info flag next to the field name in Setup so that when we hover over it, there is a description of the consequences; something along the lines of, "Changing these numbers affect your existing project and template Planned Durations and Planned Hours."Current Behaviour - The Experience League documentation (https://experienceleague.adobe.com/docs/workfront/using/administration-and-setup/set-up-wf/configure-system-defaults/set-project-preferences.html?lang=en#:~:text=a%20schedule.-,Timeline%20Calculations,-Typical%20hours%20per) nor the field in Setup identify the consequences to changing the setting.