Following is an example of a typical development cycle that might be used with Full Task-Oriented Tracking with a LANSA for i Master System:
1. Create a Task ID on the IBM i following site naming conventions.
2. Use System Initialization or propagation to make the new Task ID available in Visual LANSA.
3. Check out the required objects for update, as required, using the Task ID or start creating objects using this Task ID.
4. Maintain the Objects (Create, Edit, Compile).
5. Check in the objects to the IBM i Master System and Compile (and test if required).
6. Close the Task ID on the IBM i once the project is completed.
7. Use System Initialization or propagation so that the Task ID status is updated in Visual LANSA.
8. Create or maintain IBM i Export lists using the Task ID as required.
It is recommended that you create an export list for that specific task and the addition of that task to the export for the next release.
9. Create or maintain a Deployment Package in Visual LANSA using Task ID.
It is recommended that you create a package for that specific task and the addition of that task to the package for the next release.
10. Export the Task specific export list and import to your test partition on IBM i.
a. Update any test scripts to include new capabilities.
b. Test the changes delivered in that task.
c. Update documentation with new capabilities.
11. Deploy the Task specific package to your test partition on Windows.
a. Update any test scripts to include new capabilities.
b. Test the changes delivered in that task.
c. Update documentation with new capabilities.
12. Deploy the Task specific package to your test partition on Linux.
a. Update any test scripts to include new capabilities.
b. Test the changes delivered in that task.
c. Update documentation with new capabilities.
13. If issues exist:
a. Change the status of the task on the IBM i back to 'WRK'.
b. Use System Initialization or propagation so that the Task ID status is updated in Visual LANSA.
c. Go to step 3.
14. Change Task ID to 'FIN' status.
a. Refresh the Windows Development Server (Releases Objects from Task ID).
b. Use System Initialization or propagation so that the Task ID status is updated in Visual LANSA.
