Overview: Importing and Exporting Tasks
You can import or export tasks, including global screen handlers, in order to provide flexibilty and robustness to your projects. You can import or export tasks and global screen handlers from a project to any location in the file system.
By importing or exporting selected tasks and global screen handlers, you can:
- Work collaboratively; multiple host developers can all work on portions of a project, which will eventually be consolidated and deployed
- Develop your own work processes
- Support a version control system to manage the development of projects between developers
Using the Import and Export Feature to Work Collaboratively
In both these examples developers use the import and export function to work collaboratively to develop a project.
- Internal collaboration between two developers
- Developer 1 has to create a task against a certain mainframe application. He creates a very simple login task and logs the user into the system. From there he proceeds to create a complex task against the application itself.
- While Developer 1 is fine-tuning the task for the mainframe application, Developer 2 begins work on a more robust login task.
- Once Developer 2 has completed the login task, he uses the Export Task wizard to export only that task to a shared location on the network.
- After the login task has been exported, Developer 1 imports the task using the Import Task wizard. He overwrites the existing login task with the new one and imports all of the associated screens.
- Developer 1 completes the work on the mainframe application task and publishes the complete project to MCS.
- Collaboration between multiple developers and the use of a version control system
- Development of a complex project typically starts out with a basic login task to a host. Developer 1 creates the login task and then uses the Export Task wizard to export the task to a known location on the network.
- After exporting the login task, Developer 1 adds the task to the version control system where it can be accessed by other developers.
- Developers that are creating tasks for the host check out the latest version of the login task from the version control system and use the task as a starting point for the tasks they are creating.
- While other developers are creating their particular tasks, Developer 1 continues development on the login task. Each time the login task is updated, Developer 1 exports it and checks it into the version control system.
- The other developers can then check-out the latest version of the login task and import it into their projects.
- As each developer makes changes to their respective components, they export the tasks they have been working on and check them into the version control system. By checking in their tasks individually, developers can make simultaneous changes to what will become the whole project.
- After development on all of the tasks is complete and committed to the version control system, Developer 2 is responsible for putting all of the tasks together and deploying them to MCS.
- Developer 2 takes all of the exported tasks and imports them into one project using the Import Task wizard.
- After the tasks have been tested to verify that they work, the complete project is deployed to MCS.
Information, Warnings, and Errors
In the bottom left pane of the import or export wizard you will see different types of messages. These provide information about project incompatiblity and workflow issues. The messages are also listed in the Summary of Changes at the end of the import or export process.