What is the recommended strategy for disabling workflows before starting asset migration on AEMaaCS?

Question

Options

• AUse the ACS Commons Fast Action Manager.
• BDisable launchers for all workflows.
• CDisable launchers for the DAM Update Asset workflow.
• DSchedule activities to run on off-hours.

• A
  4% (2)
• B
  16% (8)
• C
  70% (35)
• D
  10% (5)

Explanation

Disabling launchers specifically for the DAM Update Asset workflow is the recommended approach because this workflow triggers automatically on every asset upload, and during bulk migration it would generate massive processing overhead - slowing ingestion and potentially crashing the system. Option A (ACS Commons Fast Action Manager) is a useful tool for bulk workflow processing, but it's not the recommended pre-migration disable strategy and is less relevant in AEMaaCS cloud environments. Option B (disabling launchers for all workflows) is overly aggressive and risks disrupting other critical system processes that should remain active during migration. Option D (off-hours scheduling) can complement migration efforts but does nothing to prevent the workflow from firing on each asset - the volume problem persists regardless of timing. Memory tip: Think "DAM = Danger During Migration" - the DAM Update Asset workflow is the one workflow that will fire on every single asset, so it's the one you must disable first before any bulk upload.

No community discussion yet for this question.