WorkflowCommander - access the AE using Powershell!

Discussion created by joel_wiesmann_automic on Dec 12, 2016
Latest reply on Jan 16, 2017 by joel_wiesmann_automic
Hi fellows

Below is an example how I connect to two clients (non-verbose & verbose). Then I start a search on client 2000, export the result and import it on client 3000 with a simple Powershell one-liner. The object-path information are kept - missing folder structures are created on destination / existing objects are moved to new location if necessary.

I have several more cmdlets ready that integrate with each other. In example you can do a search on client A and use the search-result to check whether the same objects are deployed on client B. Or pipe it into search-aeStatistic to see when the last run happened. 

Also it's a no-brainer to pick the input from a database or file instead of a search-aeObject output.

Did I raise any interest? I'm looking for some serious feedback & people that are interested in testing. I plan to migrate my WorkflowVision ( as well as CSV2VARA ( solutions onto it. 

Works with AE10 /11/12 + Powershell v3+.


Btw, sorry for the German text. That's the Windows locale I guess :).