Work area handling on DCM receive

When DCM receives a project that does not currently exist in the receiving database, by default it creates the project with the same work area properties as in the source database. An exception to this is that the work area path is not replicated. This is because that work area path might not exist or be valid at the receiving database, or if the database is on the same LAN, it might attempt to use the same work area path as used by same project in the source database, which would always fail. Instead, if the project being received has work area maintenance enabled, it is given a new default work area path based on the current user's default work area path template.

If a work area cannot be created for a new received project, DCM automatically disables work area maintenance for the project and attempt to create the project without a maintained work area. DCM also includes a warning that it has done so in the DCM Event Log and any DCM receive e-mail that is sent. The reason for such action is that it allows the DCM receive to proceed and to populate the project with its members, after which a user can correct the work area problem without having to run a failed DCM receive again.

The default behavior can sometimes give unwanted results:


Feedback