Siebel Business Process Framework: Task UI Guide > Building a Task UI >
Roadmap for Developing a Task UI
To develop a task UI, perform the following processes and tasks:
- Process of Building a Task UI
- Process of Deploying a Task UI
- Process of Testing a Task UI
- Migrating a Task UI
- Administering a Task UI
Note that these processes do not include analysis and design work. For more information, see:
This topic provides a procedural overview for developing a Siebel Task UI. For examples that detail these procedures and the phases of a task UI implementation project, see Examples of Developing a Task UI.
Figure 15 illustrates the planning and development lifecycle of a task UI.
Figure 15. Planning and Development Lifecycle of a Task UI
The following steps are performed to develop a task UI:
- Analyze. Analyze your business requirements and the job tasks that must be supported.
- Design. Model the job task to be supported, then define a visual layout for the task UI.
- Build. Build the task UI by defining objects in Siebel Tools. Example objects include the object definition of the task UI and task steps.
- Deploy. Deploy your task UI by validating the logic of the task, publishing the object definitions of the task from the repository tables to the run-time tables, then activating the task for use in the Siebel client.
- Test. Test, verify, and troubleshoot your task UI to make sure the objects and logic you defined meet the business requirements.
- Migrate. Migrate the deployed task UI to the production environment. You can use a utility, such as ADM, REPIMEXP, or Import/Export.
- Administer. Administer the migrated task UI in the production environment.
Note that while the lifecycle illustrated is a linear flow, the typical development cycle is iterative.