Embed Size (px)
Citation preview
Create Xtensions in Nintex for Office 365 and Nintex workflow cloud
David FitzpatrickProduct Manager
Rick De MarcoProduct Manager
Mike LewisDirector, Product Marketing
What is Nintex Xtensions?
How is it being used today?
What are the technology foundations?
Examples: NWC & Nintex for Office365
Capabilities, today and tomorrow
Agenda
What is Nintex Xtensions™?Nintex’s extensibility framework
Allows ISVs, customers and partners to interact, extend and integrate with the Nintex workflow platform
Leverages open standards and protocols to simplify the integration of APIs into workflow applications
Connects you to services and applications that are not yet available on our platform
How Nintex uses Xtensions
Recently released Nintex workflow cloud connectors that were built as Xtension components:• SharePoint online connector• Azure Active Directory connector• ServiceNow connector (coming soon)
Began as a way for Nintex to quickly add new connectors
Wanted to empower ISVs and our partners to do the same
6
How our partners use Xtensions• A Nintex partner and provider
of enterprise collaboration and communication software
• Creates intelligent workplaces on top of Office365 and SharePoint
• What Beezy uses Nintex workflow cloud and Nintex Xtensions to do include:• Create virtual workplace teams when a Salesforce
opportunity approaches high win probability• Create actionable cards for leave requests
Beezy video
Define your custom
connector
>
Import it into the
Xtensions
Repository
>
Specify your
security template
and add a custom
icon
>
Use your custom
Xtension connector
in the Nintex
Workflow designer!
Nintex XtensionsNeed a custom workflow component – write it!
Technology foundations of XtensionsUsing open standards to underpin the platform
Xtensionexamples
10
Example for Nintex Workflow CloudEmployee onboarding with Xtension actions
• Azure Active Directory – a Nintex out of the box connector• Add new employee details to an organization’s Active
Directory. • Get the new employee’s manager’s details.
• Asana - A custom connector• Create a task in Asana requesting provisioning of IT
equipment
• Lifx – An IoT system for controlling lighting• Turn on a light in the provisioning room to let the team
know a request has come in.
Xtensions for Nintex Office 365Reuse & Extend
Provide a way to easily reuse logic through Component
workflows
Extend the platform to meet your needs – you don’t have
to wait for us!
Obtain the benefits of our platform investments
Xtensions 365Demo
13
Nintex Xtensions capabilitiesAvailable today
• Create custom actions in Nintex workflow cloud
• Support for files in Nintex workflow cloud
Coming soon• Create custom actions in Nintex for Office365
• Create custom start events in Nintex workflow cloud and Nintex for Office365
• Out of the box SharePoint driven form choice controls for Nintex workflow cloud forms
• Create form choice controls from custom data sources
14
Get Started – Some useful resources• The Nintex Xtensions SDK
• https://help.nintex.com/sdk
• The Swagger.io editor• http://editor.swagger.io/
• Studio.Restlet• https://studio.restlet.com/
• David Fitzpatrick• [email protected]
Questions?
16
Stay informed of the continuous innovation delivered by Nintex
Offers a view of what’s coming in the near-term to cloud and on-premises
Focuses on new and updated features and capabilities*
Publicly available through the Nintex Connect technical community
roadmap.nintex.com
*Not a comprehensive view of all planned changes
17
nintex.uservoice.com
community.nintex.com
We want your feedback
From the xchange mobile app, select “Survey” from the sessions that you attend
Complete the short evaluation
Click “Submit”
Appendix
Technology foundations of XtensionsUsing open standards to underpin the platform
Anatomy of an OpenAPI specificationOperations• Method• Path• ID
Info Object• Metadata about the API• Endpoints• Base URL• Security
Responses• Status code• Headers• Body
Request • Headers• Query parameters• Body
Anatomy of an OpenAPI specThe trick to programming is to close as many brackets as you open
Anatomy of an OpenAPI specThe OpenAPI specification version is identified by its former name “Swagger”
Nintex Xtensions supports version 2.0
Anatomy of an OpenAPI specAdd metadata about the API
Title will become the name of the action category
Anatomy of an OpenAPI specAdd connection information–how will we connect to the API
Anatomy of an OpenAPI specDeclare that we are going to be exchanging data in JSON format
Anatomy of an OpenAPI specDefine Operations• Path to access the operation or resource on the host• HTTP method to use (e.g., get, put, post, or delete)
Anatomy of an OpenAPI specDefine Operation parameters (information required by the API in order to complete the operation)
Anatomy of an OpenAPI specDefine responses
