Understanding Object Transfer Activity Rules

You must configure object transfer activity rules for each object type used in a project that you want to perform an action on.

For each object type you want to perform an action on, you must define this information:

• Project statuses at which users can check in, check out, and get objects ("getting" an object means copying its specifications to your work area without checking it out)

• At which status change you would like objects to be transferred

• Project statuses at which object tokens are released

These object location tasks must be performed when setting up object transfer activity rules:

• Define FROM and TO transfer locations for each object type at each project status transition-for example, when project status 21 (development) changes to project status 26 (prototype). In this example, objects are transferred from DV810 to PY810.

• Define checkout and get locations for Object Librarian object types.

• Define checkin locations for Object Librarian objects.

  Note: Transfer activity rules can occur in any order. For example, you might have one status change that will require more than one object transfer. If you expect an object to transfer from DV810 to PY810 and then to PD810, you will want to set up rules to transfer the object from DV810 to PY810 and from DV810 to PD810 because the object could be retrieved in any order.