A Share operation makes a component appear in another location, without removing it from its original location. This means that at first glance, sharing might appear indistinguishable from copying, but it is important to understand how sharing differs from copying.
When a component is copied, the copy represents a new data object. Initially it looks like the original, or source object, but it is independent. Any subsequent changes to the copy have no effect on the original, and vice-versa.
But when a component is shared, no new data object is created. The same data object is merely made to appear in two or more locations. For a component that is shared, although it appears in two or more locations, there is only one data object. Therefore, any subsequent change to that object is reflected automatically and instantaneously in every other shared location.
Examples
That consequence might be exactly what you desire. For example, maybe you have a Task that is a component in more than one duty area (Function). It is exactly the same task, taught in exactly the same way. And so you choose to share the Task; you position it in two locations in the hierarchy, under each of the two duty areas. Any subsequent changes to the Task are reflected in both of its locations.
On the other hand, supposing you wanted that Task to appear in another duty area, but with the intent of customizing the Taskāfor the new location only. In other words, you want the Task to appear in an additional location, but it's not going to be identical. Perhaps the wording of the Task statement is to be slightly different. Or perhaps it will have different conditions or standards. Or perhaps it will not include the same set of children. In that case, it would be better to copy that Task, rather than share it.
Children are Also Shared
Finally, remember that when you share a hierarchy component, its children are shared as well. So, for example, if you share a Task, not only will that Task appear in more than one location, but so will any Elements and Skill/Knowledges that are children of the Task. After all, since sharing results in the same Task appearing in multiple hierarchy locations, it follows that you are going to see the same children when you expand the view of that Task.
|