1.11 Task Tracking
In order to keep track of development within LANSA, task tracking is used. Task identifiers can be allocated to individual tasks, developers, or products (groups of objects) at partition level.
A developer chooses the task to work on when logging on to LANSA and the Task ID is displayed on all the relevant LANSA windows.
An object that is locked out by one task cannot be used by another task. "Objects" include:
- Fields
- Visual LANSA components
- Files
- Functions
- Processes
- Application templates
- System variables
- Multilingual variables.
You can review a history of all work performed on an object using the Task Identifier and you can use the task identifier to export all objects worked on for a task.
Task tracking can, and should be, tailored to your site's specific needs. You can decide how much control you want to have over the development effort, how much administration overhead you are willing to bear, how big is your team and whether development needs to be controlled by individual developer, by product or by both.
You must use Task Tracking when developing with Visual LANSA. This means that before you start your Visual LANSA development, you must first set up your Task Tracking requirements using LANSA on IBM i. When developing with Visual LANSA, in addition to locking by task, Task Tracking will also lock objects by PC Name on IBM i.
You will find a description of task tracking and how to set up your Task Identifiers in Task Tracking in