- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
Thanks Amit,
If you have an instance which is both control and execution and deploy the new archiving workflow from within the deployment wizard as explained in the installation document it will create a mcSync_local archiving workflow with the extAccountId of local
However, if you create the archiving workflow from withing the external account execution instance it will create the archiving workflow and append the extAccountId by default.
I tested both archiving workflow and only the mcSync_local fails.
So what determines a instance that is both control and execution? is it a single instance running all services (Standalone Deployment) with a message centre deployed locally? or even a Standard deployment would have the control and execution for message centre.
Views
Replies
Total Likes