Connectivity to SharePoint (O365 and or On-Prem) lists and Libraries

Hi John Ackery‌,

Thank you for sharing our excitement in getting Nintex Workflow Cloud to General Availability!

Regarding connectivity to SharePoint lists and libraries, that work has begun but we do not yet have a delivery date on when that will be available. However, you may be able to leverage the "external start" functionality in the interim if you'd like to test some of the possible interoperability with our other workflow platforms.

Here's a blog post about it in case you haven't seen it. Internally we were able to trigger a Nintex Workflow Cloud workflow by adding an item to a SharePoint list, which kicked off a SharePoint workflow, which then called a Nintex Workflow Cloud workflow.

Are there specific scenarios you are hoping to accomplish with O365 and SharePoint connectivity?

Thanks,
Renai

Hi Frank,

Thanks for the note. Does this technique allow the passing of SharePoint list data as variables to a NWC workflow?

Is it possible with the current release of NWC to write Workflow values into SharePoint?

Yours Sincerely,

John Ackery Director

<http://www.devworkz.net/SitePages/DigitalWorkplacesEbookDesigners.aspx>

Website www.devworkz.net<http://www.devworkz.net/> Administration: admin@devworkz.net<mailto:admin@devworkz.net> Events: events@devworkz.net<mailto:events@devworkz.net> Support: service@devworkz.net<mailto:service@devworkz.net>

Hi John,

You can currently configure a Nintex Workflow for SharePoint call web service action to start a Nintex Workflow Cloud external start workflow. For a more seamless experience, I can share with you that in the next release of Nintex Workflow for SharePoint later this month, will feature a dedicated "Start workflow in Nintex Workflow Cloud" action. Both these options will allow you to pass SharePoint list data into an NWC workflow.

Additionally, as Renai mentioned earlier, there is a Nintex Workflow Cloud SharePoint connector actively being worked on. In terms of the current release of Nintex Workflow Cloud, without the SharePoint connector there is no way of writing workflow values back into SharePoint.

Are you able to share details of the scenario you are building out?

Regards,
David

Hi Frank,

Is it possible with the current release of NWC to write Workflow values back into SharePoint ?

Can we use the external start on SQL data tables, is there a BLOG post on this?

Thanks and Best Regards John Ackery

Hi John,

Currently, it's not possible to write workflow values back into SharePoint, and we don't yet support external starts via SQL data tables. These items are both on our roadmap so keep an eye out for them in the future!

Thanks,
Renai

Hi Renai,

Thanks for this update. It looks like the current release of NWC is very much targeted at, and limited to, at the NetSuite to SalesForce domain.

All other system interpretability is nonexistent or requires some bespoke coding.

Regards JA

Hi John,

Thanks for your comments in the thread.

Nintex Workflow Cloud is not intended to be a replacement product with a uniform feature set to our Nintex Workflow for SharePoint offerings. Instead, it is intended to be an extension to our existing product suite so our customers can leverage the strength of each of our platforms to automate their business scenarios and processes.

Our subscription pricing model provides the flexibility to automate a given business scenario on the platform that best suits the need, whether it’s Nintex Workflow for SharePoint or Nintex Workflow Cloud. This is driving why we are releasing features that allow interoperability between our platforms, enabling you to use the best tool we offer for a given job. As mentioned previously, the latest release of Nintex Workflow for SharePoint features a 'Start workflow in Nintex Workflow Cloud' action.

Additionally, we will be releasing a connector extensibility framework in early 2017, which will enable customers, partners, and SaaS providers to build their own connectors. This will also include a Nintex Workflow Cloud SharePoint connector, which is already in development. When released, this will allow you to pass data from SharePoint to Nintex Workflow Cloud and back to SharePoint.

Please don't hesitate to contact us with more questions, we would welcome a phone discussion to continue the conversation.

Thanks,

Nintex Community Team

Hi Renai,

Thank you for update. Its fantastic to get simple accurate information.

Please keep up the good work.

Are u based in AU or US. Will u be in InspireX New Orleans?

JA

Sent from my iPhone

Hi John,

Thanks for the feedback! I'm based in our US office but other members of our product and engineering team are in our AU office as well as Malaysia.

The entire product team for Nintex Workflow Cloud will be in New Orleans for InspireX; hopefully we'll see you there!

Thanks,

Renai

Hello all! Just wanted to check back in on the status here, see if there are any updates to be had? We have a use case for a publicly accessible form that we'd like to use to get data into SharePoint Online (we're a fully online shop, no on-prem stuff). If there's another/a better way to accomplish this, I'm all ears!

Hi Courtney,

Can you clarify if you are using Nintex Workflow for Office365 or Nintex Workflow Cloud?

Thanks,

David

Hey David,

We currently have Nintex Workflow and Forms for Office 365. We have a possible use case for Nintex Workflow Cloud in that we need a publicly accessible form that does not require credentials to be used. We'd like to point the data gathered from this into SharePoint if possible.

The exact use case is really a ticketing system for our Facilities manager. We own a building that houses other corporate tenants as well as individual people tenants and all of these users need to be able to submit work requests. We were hoping to use Nintex Workflow Cloud for this. But, I spoke with  and it seems like the customizability of the forms portion of this is pretty minimal at this point. After talking to him, the business of course mentioned that they'd like cascading drop downs, which I'm not so sure the current Form implementation on Nintex Workflow Cloud could handle.