Reusable Components Approach

1)Local File Storage -Store the reusable components in the Source Control System. Sync files in shared location. Add the network path to the Library in Studio.(RECOMMENDED)
PROS: ✓ Easiest to implement ✓ Most secure
CONS: :black_small_square: In case a reusable needs to be changed, manual re-publishing and redeploying are required
2)Shared File Storage -use a file share location to store the reusable components and invoke them remotely.

PROS: ✓ Easy to implement ✓ Calling by reference

CONS: :black_small_square: In case of network failure, the robots are not able to run :black_small_square: The robots can run more slowly due to network latency (or even trigger exceptions) :black_small_square: Security risk (access to shared folder)

3)Shared Components Package

Create one package containing shared components and distribute it using the Orchestrator embedded provisioning mechanism.

PROS: ✓ Calling by reference ✓ Version control

CONS: :black_small_square: Harder to implement :black_small_square: Project path needs configuration

4)Custom Packaging Method
Use a third party solution to create packages that also provision the reusable components

PROS: An alternative to the Shared Components approach

CONS: :black_small_square: The most complex approach and the hardest to implement and maintain :black_small_square: Dependent on third party component

hope it will be helpful. consider whenever you think about Reusable Components.

Happy Automation