Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-22912

Allow for the document to not be saved in the Add/Remove Facet operations

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 8.10-HF12, 9.3-SNAPSHOT
    • Fix Version/s: 9.3
    • Component/s: Automation
    • Release Notes Description:
      Hide

      A new parameter has been added: save. When true, the document is saved, else it is not (other operations in the chain should then save it).
      Notice: Default value is true, the document is saved by default to maintain compatibility.

      Show
      A new parameter has been added: save . When true , the document is saved, else it is not (other operations in the chain should then save it). Notice: Default value is true , the document is saved by default to maintain compatibility.
    • Impact type:
      API change
    • Upgrade notes:
      Hide

      A new parameter has bee added: save. When true, the document is saved, else it is not (other operations in the chain should then save it).

      Notice: Default value is true, the document is saved by default to maintain compatibility.

      Show
      A new parameter has bee added: save . When true , the document is saved, else it is not (other operations in the chain should then save it). Notice: Default value is true , the document is saved by default to maintain compatibility.

      Description

      Both Document.AddFacet and Document.RemoveFacet automatically save the document, which makes it unusable in some events Before Document Modification for example).

      Add a paraleter allowing to not save the document.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: