Seeking Clarification: Unexpected Package Dependencies and Circular Risks

Hello Everyone,

I am currently developing a new application called "Ticket Management" (mygTicketManagement). Ticket Management depend only on the Customer 360 package (UsrCrtCustomer360App) to access Account and Contact data.

However, after checking the Package Dependencies, I found an unexpected hierarchy (as shown in the attached screenshots):

1. The Issue: My mygTicketManagement package is being depended on by UsrCrtLeadOppMgmtApp.
2. The Confusion: I am not sure how this relationship was established.

My specific questions are:

• Trigger: Does adding a Data Source (Object) from another package within the Freedom UI Designer automatically prompt or create these package dependencies?
• Validation: Is it a best practice to have a linear dependency (e.g., Customer360 -> LeadOpp -> Ticket)? I am concerned about accidentally creating a Circular Dependency which might block future deployments or compilations.

• Cleanup: If I realized a dependency was added by mistake (e.g., Ticket depending on LeadOpp), what is the safest way to remove it without breaking the UI pages that might have "peeked" at those objects?

  Current Environment: Creatio 8.3.3 (Freedom UI)

  Any guidance on how to maintain a clean package structure and prevent "spaghetti dependencies" during UI configuration would be greatly appreciated!

  Thank you!