Work area handling on DCM receive

When DCM receives a project that is not in the receiving database, it creates a 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 can happen if the work area path does not exist or is invalid at the receiving database. Additionally, an exception occurs if the database is on the same LAN. The database might attempt to use the same work area path used by the project in the source database, which results in failure. Instead, if the receiving project has work area maintenance enabled, it is given a new default work area path based on the default work area path template used by the user.

If a work area cannot be created for a new received project, DCM automatically disables work area maintenance for the project. DCM also attempts to create the project without a maintained work area. DCM includes a warning that it has done so in the DCM Event Log and any DCM receive email 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