The following has been released to the Test environments on Oct 28th, but will not be released to production next week. We will let this feature sit in Test for a while before enabling it in Production, since it affects how you work with activities in Data Manager/Activity Manager
General improvement
Show all activities in Data Manager. All activities are now visible in Data Manager, even if they are sent to Activity Manager for scheduling or have been scheduled.
The reason behind this is simple. You should always have the full picture of all activities, regardless of where they are in the process.
So what has changed?
In simple terms, it is no longer a "sending" that takes place, only a status change.
When sending activities to AM, it will receive a new status in DM called "Ready for scheduling". This means it will also be visible in AM with the status "Not scheduled". Once an activity has been scheduled, it will get the status "Scheduled" both in AM and DM.
When an activity is "Ready for scheduling" (and visible in AM), it can still be changed in DM like normal. The changes are of course reflected in AM, since they are the same activities.
When autoscheduling, and an activity fails to schedule, it will receive the "Failed" status both in AM and DM. Failure messages will be also be visible in DM
When activities are in "Ready for scheduling", they can be "sent back" to DM, either from the Activity series view in AM, or in DM, by selecting them and clicking "Send back to DM". The activities will then get the status they had before
We are also changing the behaviour on which activities that can be sent back and forth between DM and AM. We have previously included all activities for each primary object when sending, but now a single Activity Series can be set to "Ready for scheduling" without it affecting other series for the same primary object.
What's coming soon?
We are going to change the way we manage statuses in Data Manager, to make it clearer what is actually happening. This will be released to Test environments in good time before releasing the whole feature to production.
These actions will become status transitions instead. More info will come when it is released to Test environments