About Order Extensions and Inheritance

During order creation, you can base new orders on the functionality of an existing order by using the extend feature. When you extend an order, the extended order inherits all of the data, tasks, rules, and behaviors of the parent order. For example, if you have multiple order types that all require the same subset of processes and tasks, you can create a base order that contains this data, then extend from this order to create as many new orders as necessary. You can add new data and behaviors to each of the new orders to create unique order templates and behavior functionality. To implement changes to the inherited data, you edit the data in the parent order and Oracle Communications Design Studio automatically implements those changes among all of the extended orders.

You cannot edit order data inherited from a parent order. For example, if you are working in an order that includes data inherited from a parent order, you cannot remove, rename, or reposition data elements inherited from the parent order, make changes to inherited behaviors, and so forth.

The child order does not inherit any configuration details specified in the parent order Details, Amendable, Notifications, Permissions, Jeopardies, Events, or Composite Data View tabs. You must manually set these configuration details for each child order.

Note:

Design Studio does not permit cyclic referencing. For example, if order O2 extends from order O1, and order O3 extends from order O2, then you cannot extend order O1 from order O3.