Task Tracking can be used in order to manage and control development within LANSA. Task identifiers can be allocated to individual tasks, developers, or products (groups of objects). Tasks are defined at system level but lock objects and records changes at the partition level. (Refer to Task Identifier Rules.) Task Tracking will allow you to:
- Keep strict control of development within LANSA by controlled allocation of Task identifiers to individual development staff.
- Enforce locks on objects during development by allocating a specific Task identifier against an object.
- Review an audit/history log of all work performed on objects within the task.
- Create an export list of all objects changed for a particular maintenance item or enhancement using a specific Task identifier.
If Task Tracking is enabled for the selected partition, a developer must select a Task ID when logging on to Visual LANSA. (Refer to Logon Parameters.) Once logged on, a developer is only allowed to modify objects that have already been locked to the specified Task ID and PC Name, or objects that have not yet been assigned to a Task. The current Task ID is displayed on all the relevant LANSA windows. The developer may switch to a different Task ID if required. (Refer to Change Current Task.)
Generally, an object that is locked out by one task cannot be used by another task. (Refer to Tracked Objects.)
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. For further information, refer to 6.2.4 What Happens When Task Tracking Is Active?
If you are using a Visual LANSA Slave System with a LANSA for iSeries Master System, you will find a description of Task Tracking and how to set up your Task Identifiers in Task Tracking in