cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
udayanramesh
Nintex Newbie

Nintex For O365 API vs NW 2010 API

Jump to solution

We are migrating over our SharePoint on premise instance to the O365 and as a result our Nintex 2010 to Nintext For O365 version. A lot of our custom web applications (non SharePoint) were hooked up to Nintex 2010 workflows API to support the ability to 

- Start/stop workflows

- Respond to approvals tasks

- Fetch workflow tasks 

I'm not able to find any documentation (for Nintex For O365) to support any of the above mentioned functionalities. Are these no longer supported? 

Reply
3 Replies
fhunth
Nintex Newbie

Re: Nintex For O365 API vs NW 2010 API

Jump to solution

Currently those operations do not exist on the O365 API.

View solution in original post

0 Kudos
Reply
udayanramesh
Nintex Newbie

Re: Nintex For O365 API vs NW 2010 API

Jump to solution

Thanks. Unfortunately not a good news for us, as we will have to make significant changes to remove the integration points and redesign to keep the functionality.

0 Kudos
Reply
Nintex Employee
Nintex Employee

Re: Nintex For O365 API vs NW 2010 API

Jump to solution

Hi Ram,

From what source are you making these API requests currently?

- Start/stop workflowsYou are able to start instances of a workflow via the new Component Workflow feature - you can start a workflow with input variables from another workflow or via an API request. Additionally you can receive values back from the workflow at the end.

- Fetch workflow tasks - Tasks in O365 are just SharePoint list items, this could be achieved by using the SPO API to retrieve tasks assigned to a user in the Task List

- Respond to approvals tasks - We don't have this functionality (though again you could potentially respond to the Task item in the list using the SPO API), what is the use case you need an API for here? We have quite a few ways that users can complete a task (via SPO Form, Nintex Task Form, Lazy Approval, Actionable Email), I am curious how your users are responding/prefer to respond to tasks.

Thanks,


Callum

0 Kudos
Reply