Uploaded image for project: 'Fuse/AMQ Documentation'
  1. Fuse/AMQ Documentation
  2. FUSEDOC-4853

Document Data Mapper CSV support requires editing step

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • fuse-7.11
    • fuse-7.11
    • Fuse Online
    • None
    • integration-doc-2022-02-07, integration-doc-2022-02-28, integration-doc-2022-03-21, integration-doc-2022-04-11, integration-doc-2022-05-02, integration-doc-2022-05-23, integration-doc-2022-06-13

      From Zoran's comment in the related ENTESB Jira:

      Check to see if there are other UI updates that impact the doc as a result of
      "With PR#9902 we are upgrading to AtlasMap 2.3.13 which brings in the changes to the Parameters dialog discussed here and on the upstream issue mentioned here. With that the issues with persisting and passing the correct data shape parameters (used only for CSV currently) should be resolved."

      In addition to that a new warning has been added to the mapping step, similar to the warning we already had for the data shape mismatch – the one encouraging users to add a mapping step, this one encouraging users to edit the mapping step. This warning covers four cases:

      one of the source steps has changed it's output
      the target step's input is not compatible with the mapper's output
      one of the source steps has gone missing
      the target step has gone missing

      For any documentation changes. Perhaps in the section 4.3 step 7 here in addition to suggesting to add a mapping step we could also suggest to edit the mapping step (if the warning is on the mapping step that is); and here in the section 7.2

            abelgaon@redhat.com Arati Ajit Belgaonkar
            mflinn@redhat.com Melissa Flinn
            Matej Kralik Matej Kralik
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: