Creating a Cartridge for Orders That Use Processes

The procedure below outlines the basic steps to create an OSM cartridge configuration in Design Studio.

After you create a cartridge project, you can model the process flow first or define your data first (see "Modeling Data" for information about defining data). The steps required to create the cartridge configuration are the same; only the starting points differ. For example, if you elect to model your process first, you start by creating a new cartridge project, then model the process in the Process editor. If you want to define data first, you can open the Data Schema editor to define as much data as necessary.

The following procedure demonstrates how to create an OSM cartridge, modeling the process first.

To create a cartridge for orders that use processes:

1. Create an OSM cartridge project.

   The OSM cartridge project is your working area for the OSM configuration. When you create a new cartridge project, Design Studio displays the new cartridge project in the Studio Projects view of the Design perspective. In addition to the newly-generated Project entity, the project contains entities for an order and for the Data Dictionary. See "Creating New Cartridge Projects" for more information.

2. Model the process.

   A process is a sequence of tasks that executes either consecutively or concurrently to fulfill an order or part of an order. Using the Process editor as a white board, you can create, sequence, and link the tasks that are required to implement the process flow. See "Working with Processes" for more information.

3. Model the roles.

   You can permit specific roles access to a standard set of functions in the Task web client. See "Working with Roles" for more information.

4. Model tasks and task data.

   A task is one step in a process. The data that you model for the task includes all of the data that the task requires to complete.

   You can define different types of tasks (manual or automation), create the task data, assign task states and statuses, add behaviors, and define other parameters as needed. You can associate the task with an existing OSM order or model a new order (and order template) for the task. See "Working with Tasks" for more information.

5. Model the order.

   You model the data for the order and add behaviors that affect the manner in which the data appears in the Task web client or Order Management web client. You can associate a default process, a creation task, and a life-cycle policy with the order, associate rules with the order, and permit specific roles access to the order. See "Working with Orders" for more information.

6. Refine the process.

   After reviewing your configuration, you may need to make changes, such as removing tasks from the process flow, renaming tasks, changing the data required at a task, updating the Data Dictionary, or adding additional states and statuses.

7. Package the cartridge.

   Packaging enables you to control which entities, libraries, and resources will be included in the cartridge when you deploy the cartridge to the OSM run-time environment. See "Packaging and Deploying OSM Cartridges" for more information.

8. Deploy and undeploy to and from development environments.

   You create an Environment project to contain the information required to connect to your run-time environment. You can deploy all of the data in your cartridge, or when possible, deploy only the changes to your cartridge project (using the Optimize Deploy feature). See "Packaging and Deploying OSM Cartridges" and "Deploying Cartridge Projects with Optimize Deploy" for more information.