Product ideas | Community
Skip to main content

Ideas

Filter by idea status

10000+ Ideas

mtwinkleAdobe Employee

AEM Assets: Dynamic Concurrent Upload Throttling Based on File SizeNew

Summary A customer uploading 20 video files totaling 45GB (~1.8GB each) is experiencing Chrome out-of-memory crashes (Err Code 5). Potential root cause is that AEM browser-based asset upload functionality currently supports up to 7 concurrent uploads regardless of file size leading to browser memory exhaustion when uploading large files, particularly video assets.We are requesting an enhancement to dynamically adjust the concurrent upload count based on total active file size in memory.Fixed concurrency of 7 does not account for file size, leading to excessive browser memory consumption with large files Chrome does not gracefully handle memory exhaustion in this scenario — it crashes with Err 5 rather than exiting cleanlyProposed Solution Implement a dynamic concurrency model that uses total active upload file size as the throttling mechanism, rather than a fixed concurrent file count. The browser experience should be smart enough to do 7 for smaller files, or adjust down for larger ones.A simple limit like 2GB total active file size would make it more robust:calculate total file size of the active concurrent uploads If total current files in progress is less than 2GB add another If it's above 2GB, wait for the current ones to finish before adding another up to 7 concurrent.This approach would allow smaller files to upload in parallel at full concurrency, while automatically serializing large file uploads to prevent memory exhaustion — without requiring any user intervention.

tyreseLevel 3

Adobe Tags / Event Forwarding Library - Enhancement RequestNew

Enhancement SummaryRequesting a product enhancement in Adobe Tags to support the ability to transfer, copy, or promote selected components from one library into another library within the same property. This capability would allow users to move changes such as data elements, rules, extensions, and related configurations between libraries without manually recreating or porting them.Current StateAdobe Tags currently allows teams to create and manage libraries as part of the publishing workflow. However, when changes are created in one library, there does not appear to be a native way to push or transfer those changes into another existing library.As a result, teams are required to manually recreate or port data elements, rules, and other configuration changes from one library to another. Business ProblemThe current manual process introduces unnecessary operational risk and inefficiency.Manual porting between libraries can result in:Missed data elements or rules Inconsistent configuration between libraries Human error during recreation Increased validation and QA effort Delays in release timelines Higher risk of production defects Difficulty managing parallel workstreams across multiple librariesThis is especially impactful for teams managing complex tagging implementations, where multiple rules, data elements, and environment-specific changes may need to be coordinated across libraries.Requested EnhancementAdd native functionality in Adobe Tags that allows users to transfer, copy, or promote changes from one library into another library.Ideally, the enhancement would support:Selecting one or more rules from an existing library and copying them into another librarySelecting one or more data elements from an existing library and copying them into another libraryIncluding related dependencies automatically, such as referenced data elements or extension configurationsProviding a comparison view before transfer Identifying conflicts when the target library already contains a different version of the same component Allowing users to choose whether to overwrite, skip, or create a duplicate Preserving change history or audit visibility where possible Supporting role-based access controls consistent with existing Adobe Tags permissionsExample Use CaseA team creates and validates several new rules and data elements in Library 1. Later, the team determines that those same changes are also needed in Library 2, which contains a separate release package.Today, the team must manually recreate those rules and data elements in Library 2. This creates risk that the copied configuration may not match the original implementation.With the requested enhancement, the team could select the approved changes from Library 1 and transfer them directly into Library 2, reducing manual effort and ensuring consistency and also supports multi- user model in Adobe Tags If this is already available, can someone please point me in the right direction on how to solve for this - that would be perfect! Thanks,Ty

Eメールデザイナーテスト配信機能の改善New

NEW Eメールデザイナーのテスト配信機能について、旧メールエディタに比べ機能が悪化している点があるため、改善いただきたいです。 1.テスト配信先の指定をメールアドレスで一括指定できるようにしてほしい以前まで改行などで一括でテスト配信先を指定できていたが、一つずつ入力する必要がある 2.トークンや動的コンテンツを含まない場合は、シミュレート名でユーザーをしなくてもテスト送信ができるようにしてほしいNEW Eメールデザイナーでテスト配信をする際は、すべてのメールにおいてシミュレート名にリードを指定する必要があると思います。テストリードをMarketoに登録し、そのリードを各アカウントでプロフィールに登録すれば問題はないのですが、誤って本番用の顧客データをプロフィールに登録してテスト送信した場合、実際の顧客にはメールが送信されないものの、メール件名にその顧客のEメールがそのまま記載されてしまいます。例)TEST (To: xxx@xxx.xxx) | 件名自社内のみでMarketoを運用している場合は大きな問題にはなりませんが、協力会社が作業をしている場合などは、保有している個人情報がテスト送信で他社に共有されてしまうリスクが高いと考えています。※プロフィールの登録自体は、複数アカウントで共有されず各marketoアカウントでそれぞれ設定が必要という仕様であるため、誤って設定してしまう可能性も上がると考えています。 また、仮に個人情報を見れない権限で他社へのmarketo運用支援をしている場合、デザインスタジオなどでメールを作成する場合も、誰かしらのプロフィールを登録しなければならないと考えています。NEW Eメールデザイナーで作業をする場合はそのような支援自体が難しくなるため、仕様について見直していただきたいです。