Product-oriented task tracking assigns unique task identifiers to products (groups of objects). This approach is suitable for small teams which have little crossover between products. In product-oriented tracking, all developers share the same task identifier when working on a particular product. Task IDs can be used to migrate the complete set of product changes.
Product-oriented task tracking requires less administration than Full Task-Oriented Tracking.
To use Task Tracking by Product you must follow the steps as described in Set Special Task ID.
For example, Task IDs such as *T00000A and *T00000B could be created for Product A and Product B, respectively. These special Task IDs will allow multiple developers to be authorized to the task. This approach assumes that there are no shared objects between Product A and Product B during the time that development work is being performed with these two tasks.
Using this scenario you should use the Keep Locks option when checking objects in to the iSeries Master repository from a Visual LANSA Slave. This will ensure that any new or modified objects will remain locked to the Task ID after they are checked into the LANSA for iSeries Master LANSA System and will be subject to status-based unlocking. (Refer to Unlock Objects in Task Tracking.)
If you use check-in unlocking, the object will be set to read-only on the workstation so that it is less likely that a developer can overwrite changes. They must check-out the object again before they can update it. However, if the object lock is released at check-in, it can now be used by a different task. You must be sure that the object is locked again so that it is included with the group of objects as part of the product.