Uploaded image for project: 'Hippo CMS'
  1. Hippo CMS
  2. CMS-7746

Prefer handle based copy workflow within translationworkflow

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Normal
    • Resolution: Fixed
    • 2.26.00
    • 2.26.00
    • None
    • Sprint 74

    Description

      The TranslationWorkflow uses a nested copy workflow (category "translation-copy") to copy documents and assets.
      With the new DocumentWorkflow, which is configured on the handle, this should be preferred to the now deprecated FullReviewedActionsWorkflow.
      However for assets still the DefaultWorkflow is/needs to be used which is configured on the document itself.
      The TranslationWorkflow(Impl) therefore should first try to find a matching copy workflow defined on the handle, but use as fallback the lookup on the document itself, as before.

      Attachments

        Activity

          People

            abanck Arent-Jan Banck
            adouma Ate Douma
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: