KWizCom forms - introduction

141
KWizCom Forms True SharePoint-Native Forms & Mobile Solution

description

KWizCom Forms is a SharePoint add-on that turns your existing SharePoint list forms into rich, enhanced web & mobile forms. Easily create your custom forms by quickly enhancing existing list forms. No need to deploy and learn a new, external form tool. KWizCom Forms is 100% SharePoint-Native, which means there's no external designer and new proprietary forms technology.

Transcript of KWizCom forms - introduction

Page 1: KWizCom forms - introduction

KWizCom Forms

True SharePoint-NativeForms & Mobile Solution

Page 2: KWizCom forms - introduction

KWizCom Corporation

• Founded in 2005

• Headquartered in Toronto

• Global vendor of SharePoint Add-Ons

• 5000+ customers worldwide

Page 3: KWizCom forms - introduction

Implementing forms in SharePoint

SharePoint list forms Immediate & simple Works in all SharePoint editions LIMITED

Power-user tool

End-user tool

InfoPath & Other proprietary form tools Advanced, dynamic forms Requires technical InfoPath/other tool skills Not fully integrated with SharePoint Additional cost ($)

Page 4: KWizCom forms - introduction

Quick & easy implementation

Support for various field types

Fully integrated with workflow, alerts and

searchYou can easily add new parts (such as custom columns, Print,

Scan and more)

List Forms – the natural option

Page 5: KWizCom forms - introduction

What’s missing in SharePoint forms? Context and logic Dynamic field constraints Tabs More flexible form layout Cascaded fields Repeating sections Better mobile forms

Page 6: KWizCom forms - introduction

External Form Tools Feature-rich form designer Enhanced form capabilities

Page 7: KWizCom forms - introduction

External Form ToolsBut…you lose your SharePoint freedom: Support for custom columns Print File upload Separate design from SharePoint Full integration with SharePoint alerts, workflows,

search Requires Power-user skills

Page 8: KWizCom forms - introduction

KWizCom Forms

Turn your SharePoint list forms into

Smart, Context-Sensitive Forms

Page 9: KWizCom forms - introduction

KWizCom FormsGet all advanced form featuresEnd-user tool, no technical skills requiredYour forms already exist, just enhance

them!100% SharePoint-Native

(Custom columns, themes, workflow)

Page 10: KWizCom forms - introduction

Product Features

Let’s show you the features by implementing an IT Helpdesk solution,

step-by-step

CustomerHelpdesk engineer

Page 11: KWizCom forms - introduction

DemoStatic Field permissions:Allowing different users see different fields

Page 12: KWizCom forms - introduction

Customer

HelpdeskEngineer

This is the Support Request

form

Some fields should be visible

to customers

Other fields should be visible to

Helpdesk engineers

Page 13: KWizCom forms - introduction

Hide marked fields from everyone

1

Show these fields only to Helpdesk engineers

2

HelpdeskEngineer

Page 14: KWizCom forms - introduction

Let’s configure KWizCom Forms to hide these fields

Page 15: KWizCom forms - introduction

1

Page 16: KWizCom forms - introduction

1

2

Page 17: KWizCom forms - introduction

1Select fields that

you wish to show/hide/disable

Page 18: KWizCom forms - introduction

2

Select permission type

Page 19: KWizCom forms - introduction

3

Type users/groups for which this permission

rule should apply

Page 20: KWizCom forms - introduction

4

Select the list forms where you want to

apply the field permission rule

Page 21: KWizCom forms - introduction

5

Click to add static permission rules

In run-time, these rules are processed

one by one according to their order.

Page 22: KWizCom forms - introduction

Let’s save the settings and see which fields users see now when creating a new Support Ticket.

Page 23: KWizCom forms - introduction

Customer

In New/Edit forms users see only these fields, as configured

Page 24: KWizCom forms - introduction

In View form users see all fields, as

configured

Customer

Page 25: KWizCom forms - introduction

HelpdeskEngineer

Now let’s make these fields visible to

Helpdesk engineers

Page 26: KWizCom forms - introduction

1

Select fields that you wish to show

2

Select “Show” permission type

3 Type users/groups for which this permission

rule should apply

Click to add static permission rules

4

Page 27: KWizCom forms - introduction

New rules added, showing the selected

fields to Helpdesk engineers.

5

Page 28: KWizCom forms - introduction

Customer

Customers still see only part of the

fields, as configured

Page 29: KWizCom forms - introduction

HelpdeskEngineer

While Helpdesk engineers see all

fields, as configured.

Page 30: KWizCom forms - introduction

DemoContext-sensitive forms:Dynamically hiding/disabling fields according to business logic

Page 31: KWizCom forms - introduction

Customer

Selecting a category should show and hide

the relevant fields

Page 32: KWizCom forms - introduction

Customer

When selecting “Hardware”

Page 33: KWizCom forms - introduction

Customer

When selecting “Software”

Page 34: KWizCom forms - introduction

Let’s configure KWizCom Forms to dynamically show these fields

Page 35: KWizCom forms - introduction

1

Page 36: KWizCom forms - introduction

1

2

Page 37: KWizCom forms - introduction

Hide the “Hardware type” field,

and add rule1

2

3

Page 38: KWizCom forms - introduction

Show the “Hardware type” field

if Category=“Hardware”1

2

3

4

Page 39: KWizCom forms - introduction

These 2 rules make the “Hardware type” become

visible only when Category field equals “Hardware”

Page 40: KWizCom forms - introduction

These 2 rules make the “Hardware type” become

visible only when Category field equals “Hardware”

Let’s click “OK” to save settings

Page 41: KWizCom forms - introduction

Customer

Page 42: KWizCom forms - introduction

Customer

Page 43: KWizCom forms - introduction

Customer

Page 44: KWizCom forms - introduction

Customer

Page 45: KWizCom forms - introduction

HelpdeskEngineer

These 2 fields should be displayed only when Issue

status field equals “Closed”

Page 46: KWizCom forms - introduction

Let’s configure KWizCom Forms to dynamically show these fields

Page 47: KWizCom forms - introduction

1

Page 48: KWizCom forms - introduction

1

2

Page 49: KWizCom forms - introduction

These 2 dynamic rules display the Issue closing date and Resolution fields only if Issue status equals “Closed”

Let’s click “OK” to save settings

Page 50: KWizCom forms - introduction

HelpdeskEngineer

Page 51: KWizCom forms - introduction

HelpdeskEngineer

Let’s close this Support Request..

Page 52: KWizCom forms - introduction

HelpdeskEngineer

Relevant fields appear when Issue status is “Closed”

Page 53: KWizCom forms - introduction

DemoDynamic default values:

1. Different default values for different people2. Automatically update document Title to be

equal to the file’s name

Page 54: KWizCom forms - introduction

DemoDifferent default values for different people

Page 55: KWizCom forms - introduction

Customer

For a customer, “Employee” field’s default value should be equal to

[Me](Although it’s invisible)

Page 56: KWizCom forms - introduction

HelpdeskEngineer

For Helpdesk engineers,The “Employee” field’s default

value should be empty

Page 57: KWizCom forms - introduction

Let’s configure the “Employee” field’s default value to be equal to [Me] only for customers.

Page 58: KWizCom forms - introduction

1

Page 59: KWizCom forms - introduction

2

Page 60: KWizCom forms - introduction

We have configured 2 Default value rules

Page 61: KWizCom forms - introduction

1st rule: set the default value to [Me] for

everyone

Customer

2nd rule: set the “Employee” field’s default value to be empty only for

Helpdesk engineers

HelpdeskEngineer

Page 62: KWizCom forms - introduction

DemoAutomatically update a document’s Title

(This has nothing to do with our Helpdesk example, but still it’s an annoying issue…)

Page 63: KWizCom forms - introduction

Click the “Library” ribbon

Page 64: KWizCom forms - introduction

Then click the “List Extensions Settings”

menu

Page 65: KWizCom forms - introduction

Select the field for which you want to

setup a default value

Page 66: KWizCom forms - introduction

Define your dynamic default value

And click to add this rule

Page 67: KWizCom forms - introduction

Rule added

Page 68: KWizCom forms - introduction

Click “OK” to save the settings

Page 69: KWizCom forms - introduction

Let’s add now a new document

Page 70: KWizCom forms - introduction
Page 71: KWizCom forms - introduction
Page 72: KWizCom forms - introduction

DemoField Constraints:1. Dynamic: Conditionally-mandatory fields2. Custom: Validate custom pattern using

regular expressions

Page 73: KWizCom forms - introduction

DemoField Constraints:Dynamic: Conditionally-mandatory fields

Page 74: KWizCom forms - introduction

HelpdeskEngineer

These 2 fields should be mandatory only when Issue status field equals “Closed”

Page 75: KWizCom forms - introduction

Let’s configure the Resolution and Issue closing date fields to be mandatory only if Issue status equals “Closed”.

Page 76: KWizCom forms - introduction

1

Page 77: KWizCom forms - introduction

2

Page 78: KWizCom forms - introduction

1

Select the field that you wish to validate

3

Define conditions (when to validate the

field’s value)

4

Click to add this field validation rule

2

Define the validation rule

Page 79: KWizCom forms - introduction

We’ve configured 3 field validation rules

Page 80: KWizCom forms - introduction

Issue closing date mandatory and not in

the future

Resolution mandatory

Page 81: KWizCom forms - introduction

Helpdesk engineer edits a Support Request item

HelpdeskEngineer

Page 82: KWizCom forms - introduction

Change Issue status to “Closed”

HelpdeskEngineer

Page 83: KWizCom forms - introduction

Try to save without updating Resolution

and Issue closing date fields

HelpdeskEngineer

Page 84: KWizCom forms - introduction

HelpdeskEngineer

Validation errors, as configured

Page 85: KWizCom forms - introduction

DemoField Grouping:Lets divide a long form to multiple tabs, each visible to relevant audience

Page 86: KWizCom forms - introduction

1

2

Page 87: KWizCom forms - introduction

1

Create field groups

2

Decide which fields appear in each

groups

3

Define who can see this field-group

4

Configure group layout settings

Page 88: KWizCom forms - introduction

Customer

This is the group (tab) used to create

support requests

Page 89: KWizCom forms - introduction

And this one is for Helpdesk engineers to update case resolution

details.

Helpdesk engineer

Page 90: KWizCom forms - introduction

CustomerCustomer sees only one tab, because he has no

permissions to see any of the fields in the other tab.

Page 91: KWizCom forms - introduction

HelpdeskEngineer

Helpdesk engineer sees the 2 tabs

Page 92: KWizCom forms - introduction

HelpdeskEngineer

Page 93: KWizCom forms - introduction

Summary – KWizCom Forms Field-level permissions View-level permissions Dynamic field constraints Dynamic default values Field-grouping (Tabs)

Stan

dard

Page 94: KWizCom forms - introduction

Prof

essi

onal

KWizCom Forms Professional Field-level permissions View-level permissions Dynamic field constraints Dynamic default values Field-grouping (Tabs) Cascaded fields Repeating rows field

Stan

dard

Page 95: KWizCom forms - introduction

DemoMulti-row forms:Managing employee expense reports

Page 96: KWizCom forms - introduction

Data ModelExpenses

Expense Details1

Page 97: KWizCom forms - introduction

(1) Create your Expense Details list

Page 98: KWizCom forms - introduction

(2) In your Expenses list create a Repeating Rows column that connects to the Expense Details list

Page 99: KWizCom forms - introduction
Page 100: KWizCom forms - introduction

Connect to the details list

Page 101: KWizCom forms - introduction

Select the columns to be displayed in the

Repeating Rows field

Configure each column’s width

Page 102: KWizCom forms - introduction

Configure summary fields for

numeric/currency fields

Page 103: KWizCom forms - introduction

Configure amount of displayed rows

Preview result

Page 104: KWizCom forms - introduction

Let’s save the settings and see the result end-user experience

Page 105: KWizCom forms - introduction

Let’s create a new expense report

Page 106: KWizCom forms - introduction

Added expenses and clicking

“Save”…

Page 107: KWizCom forms - introduction

All configured form features work within the

Repeating Rows field

Page 108: KWizCom forms - introduction

Form summary field available as

list column

Hover over the Repeating Rows column

to quickly view the details

Page 109: KWizCom forms - introduction

Prof

essi

onal

KWizCom Forms Enterprise Field-level permissions View-level permissions Dynamic field constraints Dynamic default values Field-grouping (Tabs)

Cascaded fields Repeating rows field

File Upload fields Custom Actions KWizCom Mobile

Stan

dard

Ente

rpris

e

Page 110: KWizCom forms - introduction

SharePoint Custom ActionContext-sensitive menus for productive business users

Page 111: KWizCom forms - introduction

Display customized menus,

relevant to your business logic

Auto-update fields

Trigger workflows

Redirect to pages

Configure permissions for menus

Display selected Tabs

With Custom Actions you can

Page 112: KWizCom forms - introduction

DemoCustom menus for a more convenient IT Helpdesk UX

Page 113: KWizCom forms - introduction

Demo

This is my helpdesk workspace

I see an unassigned issue that I wish to

assign to myself

Page 114: KWizCom forms - introduction

Demo

I clicked the support ticket to

see it in View mode

Since the issue is unassigned, I see a single

custom action called “Assign to me”

Page 115: KWizCom forms - introduction

Demo

I am clicking the custom menu to gain ownership over this

support ticket

Page 116: KWizCom forms - introduction

Demo

Now the issue appears under “My Support Tickets” web part(which means it is assigned to me)

Page 117: KWizCom forms - introduction

Demo

By looking at the Support Tickets list, you can see that the custom action has updated the “Assigned To” and “Issue

Status” fields

Conclusion:You can use Custom Actions to auto-update item fields without having to edit the item!

Page 118: KWizCom forms - introduction

Demo

Now I see 2 different custom menus, which are relevant to me as the

support engineer to whom this issue is assigned

Viewing this support ticket

Page 119: KWizCom forms - introduction

Demo

Now I see 2 different custom menus, which are relevant to me as the support engineer to whom

this issue is assigned

If I now click this item

After resolving this issue, I am clicking the “Close Ticket”

custom menu to update the relevant ticket’s fields.

Page 120: KWizCom forms - introduction

Demo

I am redirected to the issue’s edit form, That includes only the

relevant fields (other fields are automatically updated)

Page 121: KWizCom forms - introduction

Demo

Once I save my updates, I can see that some additional fields were auto

updated(Issue Status, Issue Closing Date)

Page 122: KWizCom forms - introduction

Create customized menus,

relevant to your business logic

Have less fields to update,

less page refreshes

Easily integrate with workflows

Easier, user-friendly UX

Custom Actions enable you to

Page 123: KWizCom forms - introduction

KWizCom MobileImproving efficiency of the mobile workforce

Page 124: KWizCom forms - introduction

KWizCom MobileSmart, focused interface for productive mobile users

Page 125: KWizCom forms - introduction

KWizCom Mobile

Page 126: KWizCom forms - introduction

KWizCom MobileSmart, focused interface for productive mobile users

Server solution

Page 127: KWizCom forms - introduction

DemoGo Mobile:1. All KWizCom Form features work in

mobile devices.2. Create your custom mobile pages

Page 128: KWizCom forms - introduction

Let’s click“Go to mobile view”

Page 129: KWizCom forms - introduction

Optimized display for mobile devices

Page 130: KWizCom forms - introduction

All KWizCom Forms features work in mobile

Custom Actions

Design once for both web and mobile!

Page 131: KWizCom forms - introduction

DemoLet’s design a more convenient mobile workspace for IT Helpdesk engineers

Page 132: KWizCom forms - introduction
Page 133: KWizCom forms - introduction

1st, create mobile pages

A page includes “page parts”

Page 134: KWizCom forms - introduction
Page 135: KWizCom forms - introduction
Page 136: KWizCom forms - introduction
Page 137: KWizCom forms - introduction

The result:

Page 138: KWizCom forms - introduction

KWizCom MobileEasily configure a custom mobile solutions

Easy-to-use mobile solutions

Exactly the pages & menus that your business users need!

Less clicks, less page refreshes Work FASTER

Page 139: KWizCom forms - introduction

KWizCom Forms

True SharePoint-NativeForms & Mobile Solution

Page 140: KWizCom forms - introduction

142

Resources• Product web page:

http://www.kwizcom.com/sharepoint-add-ons/sharepoint-list-forms-extensions-feature/overview/

• FREE 30-day evaluation version (SP2007, 2010, 2013):http://www.kwizcom.com/sharepoint-add-ons/sharepoint-list-forms-extensions-feature/download/

• Admin guide:http://catalog.kwizcom.com/sites/pc/Product%20Documentation/KWizCom_SharePoint_List_Forms_Extensions_Feature_Admin_Guide.pdf

• Training videos:http://www.kwizcom.com/sharepoint-add-ons/sharepoint-list-forms-extensions-feature/training-videos/

Page 141: KWizCom forms - introduction

Thank you!

Nimrod GevaProduct Group Manager, [email protected]