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

Add support for task variables on nuxeo-dropzone

    Details

    • Tags:
    • Impact type:
      API change
    • Upgrade notes:
      Hide

      The following changes on nuxeo-dropzone API occured:

      1. Usage of document and xpath properties was dropped and from now on the value property should be used;
      2. blobList property is now called multiple;
      3. A new property called valueKey was added and it represents the key used on the JSON object to store each entry, when using multiple mode.
        Examples:
        The file schema uses files:files to store blobs, each blob being stored in file key.
        On the other hand, when using the blobList ** type defined in Studio, each blob would be stored in item key.
      4. updateDocument property was removed which means that the nuxeo-dropzone element won't automatically update the document. From now it, the element using nuxeo-dropzone is responsible to trigger an update call if needed. The unique default case (nuxeo-document-attachments) was already covered and can be seen as an example of what can be done.

      Related to these changes, some refactoring was done.
      Due to that the S3 Upload functionality may need to be further tested in order to understand if no regressions were introduced (see NXP-24979, ELEMENTS-845, NXP-26242);
      The WOPI addon was also considered and should be working properly accordingly to NXP-26242;

      Show
      The following changes on  nuxeo-dropzone API occured: Usage of  document and  xpath properties was dropped and from now on the  value property should be used; blobList  property is now called  multiple ; A new property called  valueKey was added and it represents the key used on the JSON object to store each entry, when using multiple mode. Examples: The file schema uses  files:files to store blobs, each blob being stored in  file key. On the other hand, when using the  blobList **  type defined in Studio, each blob would be stored in  item key. updateDocument property was removed which means that the  nuxeo-dropzone element won't automatically update the document. From now it, the element using  nuxeo-dropzone is responsible to trigger an update call if needed. The unique default case ( nuxeo-document-attachments ) was already covered and can be seen as an example of what can be done. Related to these changes, some refactoring was done. Due to that the  S3 Upload functionality may need to be further tested in order to understand if no regressions were introduced (see NXP-24979 , ELEMENTS-845 , NXP-26242 ); The  WOPI addon was also considered and should be working properly accordingly to  NXP-26242 ;
    • Team:
      GANG
    • Sprint:
      nxGang Sprint 11.1.20
    • Story Points:
      5

      Description

      Workflows have a different approach then plain documents and current nuxeo-dropzone does not support task variables.

      Improve nuxeo-dropzone to be usable on workflow tasks layouts for uploading blobs to variables.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 0 minutes
                  0m
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 4 days, 45 minutes
                  4d 45m

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.