This document outlines an agenda for a presentation on building SharePoint Online workflows and customizing forms using Nintex for Office 365. It introduces Nintex as a leading tool for SharePoint and Project Server workflows. It then discusses Nintex for Office 365, including Nintex Forms and Nintex Workflows for Office 365. It provides information on designing forms and workflows using these products, including demos of list workflows, site workflows, sequential workflows, and state machine workflows. The agenda concludes with time for questions and answers.
2. • Introduction to Nintex
• Nintex for Office 365
• Nintex Forms for Office 365
• Demo
• Nintex Workflows for Office 365
• Demo
• Q & A
Agenda
3. • Leading tool for SharePoint and Project Server Workflows
• With browser-based, drag-and-drop designers.
• So many awards including
• “Most Business Value for a SharePoint Add-in” for Nintex Workflow for
Office 365.
• “Best User Interface for a SharePoint Add-in” for Nintex Forms for Office
365.
Introduction to Nintex
4. • 50 million workflows
• Fastest growing Nintex product ever
• SharePoint hosted Add-ins
• Consists of two products
• Nintex Forms for Office 365
• Nintex Workflows for Office 365
Nintex for Office 365
5. • Design forms quickly and easily
• Generate forms for browsers, including tablet and mobile
• Publish to Office 365 with one click
• Dynamic fields, data validations, conditional display areas
and custom formatting available
• Nintex Forms combines with Nintex Workflow for Office
365, to deliver complete Workflow and Content Automation
solutions
Nintex Forms for Office 365
7. • Design powerful workflows using clicks
• Nintex connecters help to interconnect Nintex Workflow for
Office 365 with leading cloud services and apps
• Workflow Types
• List workflow
• Site workflow
• Not Available – Reusable Workflows (Last updated: June 5, 2017)
Nintex Workflows for Office 365
8. • List workflows can be associated with document libraries
and lists.
• Collect feedback on documents or list items
• Can be started whenever a document or item is added or
edited.
• We can also manually start these workflows or start them
from other workflows.
List Workflow
9. • Site workflows operate across the site, independent of
specific documents or list items.
• We can manually start these workflows or start them from
other workflows.
Site Workflow
11. • A sequential workflow is one that follows a specific path.
• The default behavior is sequential workflow when you start
to create a workflow.
Sequential Workflow
12. • State machine workflow do not typically follow a specific
path of execution. Rather, they consist of two or more
states.
• Think of each state as a smaller workflow that contains
multiple workflow activities.
State Machine Workflow