Uploaded image for project: '[Read Only] - Hippo Repository'
  1. [Read Only] - Hippo Repository
  2. REPO-1440

Groovy Updater - Add NodeUpdateVisitorContext#isDryRun()

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Normal
    • Resolution: Fixed
    • None
    • 4.0.0
    • None
    • Platform sprint 130

    Description

      If there's an invocation on workflow APIs in groovy updater scripts, the "Dry run" option doesn't work properly because some workflow operations are all committed already.
      I know it's kind of inevitable to have a separate dedicated jcr session used in the workflow operations.
      So, as a workaround solution to support "Dry run", if a groovy script can know if it is in dry run mode through NodeUpdaterVisitorContext#isDryRun(), then an advanced groovy scripter may implement it not to surprise administrator executing the script somehow (e.g, skipping workflow operations on dry run mode).
      I'm sure I have to make sure the script working fine locally without dry run option. That's something that I can endure with than being surprised afterward.

      Attachments

        Activity

          People

            uhommes Unico Hommes (Inactive)
            wko Woonsan Ko (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: