I would like to develop a workflow script or action capable of creating a new Package and have that script add workflows, configurations and actions that i specify into that package. I've got a multi-developer project that will have multiple 'packages' each with a large number of workflows, actions and configurations that may change often. Managing a package manually seems like it would be prone to human error and automation seems the best approach here.
I've learned how to utilize scripts to enumerate thru workflow categories (ie, folders) to grab all workflows associated with a project. But i cannot seem to locate any possible way to create a new package and add items to it. the new package() constructor can be called, and name assigned but no package is actually created in vRO, and there's no .save() method documented.
I've found there are a huge number of undocumented ways to access information while inside a workflow script, and i was hoping someone had a way to do this. If it's not possible via script, is it possible via a plugin? i haven't learned plugin development yet but would be willing to if it's required for interacting with packages.
Thanks for any help anyone can provide.
Currently, there is no out of the box REST or scripting API to create/modify packages, except for importing a package. There is a feature request to add REST API for package operations so I guess the next vRO release (7.1) will provide such API.
It is possible to implement a plug-in and expose such package operations as scripting objects/methods, but the plug-in code will need to access the internal/private vRO API. Certainly doable, but access to these internal API is not officially supported and there is no guarantee these API won't change in future releases.
Currently, there is no out of the box REST or scripting API to create/modify packages, except for importing a package. There is a feature request to add REST API for package operations so I guess the next vRO release (7.1) will provide such API.
It is possible to implement a plug-in and expose such package operations as scripting objects/methods, but the plug-in code will need to access the internal/private vRO API. Certainly doable, but access to these internal API is not officially supported and there is no guarantee these API won't change in future releases.