Table of Contents

Search

  1. Preface
  2. Understanding the Repository
  3. Using the Repository Manager
  4. Folders
  5. Managing Object Permissions
  6. Local and Global Shortcuts
  7. Team-Based Development with Versioned Objects
  8. Labels
  9. Object Queries
  10. Team-Based Development with Deployment Groups
  11. Copying Folders and Deployment Groups
  12. Exporting and Importing Objects
  13. Exchanging Metadata
  14. Copying Objects
  15. Metadata Extensions
  16. Appendix A: MX Views Reference

Repository Guide

Repository Guide

Dependent Objects

Dependent Objects

A dependent object is an object used by another object. For example, a source definition referenced by a mapping is a dependent object of that mapping. You can perform the following tasks on dependent objects:
  • Copy.
    You can copy dependent objects with the Copy Wizard in the Workflow Manager, Designer, and Repository Manager. When you copy an object, the Copy Wizard also copies all dependent objects.
  • Deploy.
    You can add dependent objects to a static deployment group. You use a deployment group to copy objects to another folder or repository.
  • View.
    You can view dependent objects before modifying or deleting parent objects in the Repository Manager, Designer, and Workflow Manager.
  • Modify or validate.
    When you modify a dependent object, you may cause the parent object to become invalid. For example, if you modify a mapping by updating a port datatype to an incompatible dataype, the session may become invalid.
  • Import or export.
    You can choose to import or export a parent object with or without its dependent child objects. You might want to export and import an object without its dependent objects if you change a workflow property, such as a workflow variable, but you did not change any task in the workflow.

0 COMMENTS

We’d like to hear from you!