Maintaining projects with common objects

Unknown

Maintaining projects with common objects

Unknown

[color=rgb(20, 20, 20)][font=\"Open Sans\

Unknown

[color=rgb(34, 34, 34)][font=Arial, Helvetica, sans-serif]In this case, youll want to create a new project that houses all of your common components.[/font][/color]
[color=rgb(34, 34, 34)][font=Arial, Helvetica, sans-serif]
[/font][/color]
[color=rgb(34, 34, 34)][font=Arial, Helvetica, sans-serif]For example, you have 3 projects: Common Project, Project 1, and Project 2.[/font][/color]
[color=rgb(34, 34, 34)][font=Arial, Helvetica, sans-serif][ul][li]Any items associated with Project 1 will not be a dependency found in Project 2.
[/li][li]Any shared components (such as subflows, rules, etc.) that you want to include in both projects will be associated with your " Common Project " project.
[/li][li]For this scenario, if you ever need to import/export items between different instances, youll want to import "Common Project" first before you import Project 1 & 2 into the server.[/li][/ul][/font][/color]