To send change requests to the CCB database, you can either:
OR
Once a parent change request is created in the CCB database, the CCB creates one or many child change requests associated with that parent, and sets the Work in database field for each child change request to correspond to the satellite development database in which action is taken on that child.
All development work takes place in the satellite development databases. Thus, all tasks and associated configuration items reside in the appropriate development databases. When a child change request is completed or rejected, email is sent to the CCB. You can send notification email using an email trigger. The email message instructs the CCB to review the status and progress of the parent change request. The CCB cannot complete a parent change request until all the child change requests are in a terminal state (such as concluded).
Typically, only change requests are replicated back to the CCB database. The CCB does not typically need to see the breakdown of each child change request into its tasks, or view the breakdown of tasks to configuration items. Users can obtain such details from the relevant development databases.