Task Tracking Recommendations
Following are some general recommendations when using task tracking:
- Remember, task tracking is required in Visual LANSA as one of the Logon Parameters if you are using an IBM i Master Repository. You should plan your task tracking strategy before you begin LANSA development.
- Train your developers about task tracking. All developers must understand how you are using task tracking at your site. You must explain the development procedures relating to your task tracking strategy.
- Task tracking is just one part of you change management strategy. It is not the complete solution. To use task tracking effectively, you need properly defined standards and procedures in place. For example, you need procedures for creating Task IDs and assigning the Task IDs to developers, as well as procedures for updating current task lists.
- Create site naming standards for your Task IDs. Naming standards are very important and can help to simplify task tracking. These naming standards may need to consider Set Special Task ID.
- If you are using multiple LANSA Systems, you must create a task tracking strategy that properly manages Task IDs across the LANSA Systems. For example, if you create an identifier, TASK001, it should have the exactly the same definition on all LANSA Systems to allow objects to be migrated using Task IDs.
- If you have a large, complex, development environment, you should consider using 6.1.5 Third Party Packages to assist in implementing your change management strategy.
- Keep it simple. Choose a task tracking strategy that allows developers to be productive without excessive administration.
Remember, you should have an overall change management strategy with properly defined standards and procedures for your application development environment. (Refer to 6.1 Change Management Concepts.)
Also See
Task Tracking in Master/Slave Systems
Task Tracking on Independent Systems
6.2.2 Approaches for using Task Tracking
