Application Merge

Expected Behaviour

• Applications can only be merged with another application from the UI.
• Unique users/activities of the destination app remain unchanged after the merge.
• Common users/activities and unique ones are combined.

Attributes impacted:

• Users
• App User Activities

All other attributes remain with the target application only.

Current Behaviour

• A managed application cannot be merged into another application.
• An application with any authorization state can be merged into a managed application.
• Applications with associated contracts/licenses/spend cannot be merged.
• Status change logs of applications are not merged.
• Audit logs of applications are not merged—source app audit logs are not accessible after merge.

Important Points

• Once a User/Application is merged, merged activities are not immediately visible in the UI.
  They appear after the standard SLA processing window of 24 hours.
• If app A1 (under parent P1) is merged into app A2 (under parent P2),
  • Activities from A1 and A2 merge under P2.
  • Activities from P1 are not merged.
• Zluri does not store child app sources, so merged activities cannot be rolled back.

Best Practices

• Use merging only for different versions/variants of the same application, not different apps entirely.
• Do not merge applications from different parent apps.

Example:

• ✅ Merge MS Word 2021 and MS Word 2023 into MS Word
• ❌ Do not merge MS Word and MS Excel

Checks in UI

• Direct Integrations → cannot be merged
• Applications with Contracts, Spends, or Licenses → cannot be merged
• Managed Applications → cannot be merged