Libraries are specialized projects that serve as reusable containers for resources that can be shared across multiple projects.
Unlike regular projects, which are intended for creating and managing specific workflows, libraries are designed to house common elements—like processes, enumerations, and media assets—that other projects may rely upon.
This makes libraries a cornerstone for establishing consistency and efficiency across various projects.
Resource Sharing:
Dependencies:
Versioning:
Creating a Library:
Managing Library Resources:
Adding Library Dependencies to Projects:
Libraries can be added as a dependency only to Work-In-Progress (WIP) project versions.
Centralized Resource Management:
Version-Controlled Dependency Management:
Streamlining Updates Across Projects:
Libraries thus play a crucial role in modularizing the development process, enabling reusable and maintainable components across different projects. This leads to improved project organization, reduced redundancy, and simplified resource management.
How do I add a library as a dependency to an project?
A: In the project workspace, navigate to the Dependencies section. Select the library you want to add, choose the specific build version, and confirm. Once added, the resources from that library will be available for use within the project.
What happens if a resource in a library is updated?
A: When a resource in a library is updated, dependent projects will not be affected unless the library build they reference is updated to a newer version. This allows projects to maintain stability by controlling when updates are adopted.
Can I use multiple libraries as dependencies for a single project?
A: Yes, a project can depend on multiple libraries. Each library can be referenced by selecting the desired build version. However, ensure that dependencies are managed carefully to avoid conflicts or redundancy.
What should I do if a newer library build is available?
A: Before switching to a newer library build, test it in a development or staging environment to ensure compatibility. If everything functions as expected, update the project’s dependency to the new build in the Dependencies section.
Libraries are specialized projects that serve as reusable containers for resources that can be shared across multiple projects.
Unlike regular projects, which are intended for creating and managing specific workflows, libraries are designed to house common elements—like processes, enumerations, and media assets—that other projects may rely upon.
This makes libraries a cornerstone for establishing consistency and efficiency across various projects.
Resource Sharing:
Dependencies:
Versioning:
Creating a Library:
Managing Library Resources:
Adding Library Dependencies to Projects:
Libraries can be added as a dependency only to Work-In-Progress (WIP) project versions.
Centralized Resource Management:
Version-Controlled Dependency Management:
Streamlining Updates Across Projects:
Libraries thus play a crucial role in modularizing the development process, enabling reusable and maintainable components across different projects. This leads to improved project organization, reduced redundancy, and simplified resource management.
How do I add a library as a dependency to an project?
A: In the project workspace, navigate to the Dependencies section. Select the library you want to add, choose the specific build version, and confirm. Once added, the resources from that library will be available for use within the project.
What happens if a resource in a library is updated?
A: When a resource in a library is updated, dependent projects will not be affected unless the library build they reference is updated to a newer version. This allows projects to maintain stability by controlling when updates are adopted.
Can I use multiple libraries as dependencies for a single project?
A: Yes, a project can depend on multiple libraries. Each library can be referenced by selecting the desired build version. However, ensure that dependencies are managed carefully to avoid conflicts or redundancy.
What should I do if a newer library build is available?
A: Before switching to a newer library build, test it in a development or staging environment to ensure compatibility. If everything functions as expected, update the project’s dependency to the new build in the Dependencies section.