Uploaded image for project: 'OpenIDM'
  1. OpenIDM
  2. OPENIDM-14358

Mappings which have Queued Sync enabled should have implicit synchronisation executed in the order they are defined within sync.json

    Details

    • Target Version/s:
    • Verified Version/s:
    • Story Points:
      2
    • Sprint:
      2020.03 - IDM

      Description

      When executing implicit synchronisation, the sync engine first hands off the queued sync enabled mappings and then begins to execute the non-queued mappings from the top of the sync configuration down.

      However, there are use cases where a customer may not wish for a target configured for queued synchronisation to be handled until a non-queued synchronisation is completed, e.g.:

      • Synchronise to Target A,
      • If the synchronisation to Target A succeeds, launch queued synchronisation of the later targets
      • Else, do not synchronise other targets

      With the change requested in place, customers who wish to maintain the current functionality can simply define all their queued sync mappings first (top) in the sync.json file and non-queued later on.

        Attachments

          Activity

            People

            • Assignee:
              cgdrake Chris Drake
              Reporter:
              tom.wood Tom Wood
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: