By using the LANSA's ability to Transfer Object Locks, it is possible to combine some (but not all) of the task tracking approaches.
Full Task-Oriented Tracking can be combined with Tracking By Developer. In this scenario, a task is created for managing a unit of work. This is the task that will also be used to export objects when the unit of work is complete. A developer can use their own task to lock and work on the required objects, and then transfer these objects to the full task-oriented Task ID. This combined approach simplifies task tracking for each developer while still having manageable units of work for exporting changes. It requires some additional administration for the assignment of objects to developers and checking that objects are properly transferred once work is completed.
Tracking by Product can be combined with Tracking By Developer. In this scenario, a task is created for working on a product. This is the task that will also be used to export objects when the project is complete. A developer can use their own Task ID to lock and work on the required objects, and then transfer these objects to the product-oriented Task ID. This combined approach allows simple tracking by developers while still having project level tasks for exporting changes. It requires some additional administration for the assignment of objects to developers and checking that objects are properly transferred once work is completed.
Minimum Tracking should not be combined with other task tracking approaches.
These are just a few examples of task tracking approaches. You may design an approach that meets your specific site needs.
Also See
