When created from the Workplace, the move request is associated to a Service Request. The Service Request follows the Move Request evolution. It opens the possibility to embed steps (notifications, satisfaction survey...) in the process.

When is created from any else place (e.g. Web Central), it is not associated. The ARCHIBUS behavior is then not similar depending of the origin of the request. It is not consistent.

The reason why is it interesting to associate the Service Request process, it to have the possibility to define notifications, approvals or other steps on a better and easier way.

The Move Management process as standard does not give any flexibility to manage the notifications without going in the JAVA code. It is real limitation.