Uploaded image for project: 'Service Packs and Hot Fixes'
  1. Service Packs and Hot Fixes
  2. MNT-16277

CLONE 5.0.N - This sync should be completely cleaned up, and no invalid synchronizations should appear in the cloud sync manager (step 2 - clean invalid synchronizations already created)

    Details

      Description

      This sync should be completely cleaned up, and no invalid synchronizations should appear in the cloud sync manager. (To clarify: the sync node is modified to remove the on-premise location, but stays around. This state is not a valid sync state. The sync node has no association both on-premise and in the cloud. We expect that the action should completely clean up the sync by removing the sync node on both on-premise and in the cloud.)

      We need to allow the customer to clean up old invalid synchronizations.

      ---------------------------------------
      Merge r126884 from 4.2.N, and make sure to add the startDelayMinutes property to the job (similar to other jobs), in sync-service-context.xml.

        Attachments

          Issue Links

            Structure

              Activity

                People

                • Assignee:
                  closedbugs Closed Bugs
                  Reporter:
                  cturlica Cristian Turlica
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  6 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Time Tracking

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - 0 minutes
                    0m
                    Logged:
                    Time Spent - 1 day, 2 hours, 30 minutes
                    1d 2h 30m

                      Structure Helper Panel