Yes, Oasis Workflow will work well with Visual Composer plugin.
If your team is using Visual Composer for editing the pages using their “FrontEnd Editor”, OR “Backend Editor” and you are also looking to review those changes before it’s published, then Oasis Workflow can help. Check out this article for more information – https://www.oasisworkflow.com/documentation/working-with-workflows/visual-composer-and-oasis-workflow-compatibility
In most cases, you may not require to update Oasis Workflow Pro manually. The automatic update should do the trick.
However, if your WordPress installation is behind a firewall OR your site is not able to communicate with our site, automatic update link may not appear. In such cases, you might want to update the plugin manually.
Refer to this documentation page to update the plugin manually – https://www.oasisworkflow.com/documentation/getting-started/how-to-update-oasis-workflow-pro-manually-to-the-latest-version
Yes, both “Free” and “Pro” versions support custom posts types and hierarchical posts.
With the “Pro” version you can even selectively add/remove the post types which you want the workflow to support.
The Custom Post Types are shown in the settings page and you can selectively allow/disallow a given post type to be part of the workflow.
Yes. All products including the add-ons are multi-site compatible.
Each site in a multisite setup will require a separate license key. You can selectively turn on/off workflows on specific sites in a multi-site setup.
For example, out of 10 sites in a multi-site setup, you want editorial workflows to be active on 8 sites. On the other 2 sites, you want to continue using out of the box WordPress publishing process. With Oasis Workflow multisite setup, you can activate workflows only for certain sites and create site specific editorial review process.
Yes. We recommend using Members plugin (http://wordpress.org/extend/plugins/members/) for managing roles and capability.