This article documents the process of testing the following:
When a customer has a tasks created, will the task fall away when (1) the customer code changes, and when (2) the customer is merged into another customer.
A new customer is created called Duplicated Customer (HB_NC1) and as the name states, the code for this customer is HB_NC1_.
A task is created at this customer, and is assigned to Berno.
Changing the customer code
The customer code is now changed. Firstly, it is attempted to give the customer the same code as the customer that we will eventually merge this one into. Since the customer code is a unique identifier, Skynamo doesn't allow the code to be NC1.
The customer code is therefore changed to NC1a, as can be seen in the following screenshot.
We then check to see if the task has not fallen away, after the customer code has changed. The tasks has not fallen away, and it is still assigned to Berno, at the original customer, even though this customer has a new code.
Merging the customers
It will now be tested if the customers are merged, does the created task at this customer fall away. The two customers that will be merged is shown in the screenshot below.
The NC1 customer is the Target, and the NC1a customer is the Source.
The merge is done. The tasks is still on the instance. The only change is that the customer has changed to the Target customer - Bothaville Beef.
Summary and findings
From this test, the following is found:
(1) If a task is created at a customer, and the customer code is changed, then the tasks will not be removed. It will still be on the calendar for the user it was originally created for at the same customer.
(2) If a task is created at a customer that will be merged into another, the task will still be created, however, it will now be created for the Target customer.