The challenge of end users is always selective access - It adds a massive amount of complexity of what can and can't be copied. Not saying we'd never do it, but not likely for the initial release
And yes, the action would be editable as per any other action once created - In fact for this to work with ALM, you would have to be able to edit the source and target members because if the list was a production list, the members in PROD are very likely to be different to DEV
One question for you both, and the wider audience. the original request for this was because it negated the need to be in the UI. But I'm hearing from others that publishing to a dashboard would also be very useful.
So, if phase 1 was just an action, is that still useful, of do we need to be able to publish the action as well?
As part of Initial release if it is just an action it can be still can be automated thru APIs - that being the major diff between this new feature and Native Bulk Copy feature. Anaplan can then think of updating it further releases. Long Story short yes, it still will be a great feature in initial release.
we are restricting the action to structural lists only, including an error message if you do try and set a list as production that is already used in a previously defined action - There is adding complexity in the UI to allow configuration of the action in deployed mode, and it keeps the deliverable in scope for the February release
The action will be able to be published to a dashboard, but only run by Workspace Admins
We will plan to add production lists in time as part of future development