The fundamental objective of change management is to be able to identify and control how changes are made as applications are developed or maintained. The concept of task tracking is to create a Task Identifier that is used to control and record changes to individual objects in the LANSA development environment. Once a developer logs on with an assigned Task ID, the Task ID can be used to check authority to access objects, lock objects, log activity on objects, and so on. Specific Task Identifier Rules are defined to implement site standards.
Change management strategies might use task tracking in one of the following ways:
- To define units of work. A Task ID can be created to lock a group of objects for a specific application change.
- To a control changes to a product.
- To monitor or control the work done by individual developers. In this case each developer may be assigned their own Task ID to create a record of the work performed.
LANSA's task tracking is very flexible. For example, it allows you to define how object locking should be performed when task tracking is used. Refer to Unlock Objects in Task Tracking.
Task tracking is an optional feature. The LANSA development environment provides a variety of settings to control how Task IDs are used. For more details, refer to 6.2.2 Approaches for using Task Tracking.