Know what there is to know about KWizCom Forms for SharePoint, including: Enhancing your SharePoint list forms Adding custom actions with specific forms + logic for your use cases Going mobile with SharePoint

1. KWizCom Forms
True SharePoint-Native
Forms & Mobile Solution
Shai Petel
VP R&D, MVP
@shaibs
shai@kwizcom.com

2. KWizCom Corporation
• Founded in 2005
• Headquartered in Toronto
• Global vendor of SharePoint Add-Ons
• 5000+ customers worldwide
• 50+ products & add-ons for SharePoint

3. Implementing forms in SharePoint
SharePoint list forms
Power-user tool
End-user tool
InfoPath or other
proprietary form tools
Workflows with forms

4. Quick & easy
implementation
Support for various
field types
Fully integrated with
workflow, alerts and
search
You can easily extend functionality
Custom columns, Print, Scan and more
List Forms – the natural option

5. What’s missing in SharePoint forms?
 Context and logic
 Dynamic field constraints
 Tabs, group fields
 More flexible form layouts
 Cascaded fields
 Repeating sections
 Better mobile forms

6. External Form Tools
Feature-rich form designer
Enhanced form capabilities

7. External Form Tools
But…you lose your SharePoint freedom:
 Support custom columns?
 Support file upload?
 Separate design from SharePoint
 Need to create all your forms from scratch
 Partial integration with SharePoint
(alerts, workflows, search)
 Requires trained power-user/development skills

8. KWizCom Forms
Turn your existing
SharePoint list forms into
Smart, Context-Sensitive Forms

9. KWizCom Forms
 Get all advanced form features
 End-user tool, no technical skills required
 Enhance existing SharePoint forms with
advanced features
 Design once for web and mobile
 100% SharePoint-Native
(Custom columns, themes, workflow)

10. Product Features
Let’s show you how the product works
by implementing an IT Helpdesk
solution, step-by-step
CustomerHelpdesk engineer

11. Demo
Static Field permissions:
Allowing different users see different fields

12. Customer
Helpdesk
Engineer
This is the
Support Request
form
Some fields should be
visible to customers
Other fields should be
visible to Helpdesk
engineers

13. Hide marked fields
from everyone
1
Show these fields only
to Helpdesk engineers
2
Helpdesk
Engineer

14. Let’s configure KWizCom Forms to hide
these fields

15. 1

16. 1
2

17. 1
Select fields that you wish to
show/hide/disable

18. 2
Select permission type

19. 3
Type users/groups for which this
permission rule should apply

20. 4
Select the list forms where
you want to apply the field
permission rule

21. 5
Click to add static
permission rulesIn run-time, these rules
are processed one by one
according to their order.

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

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

24. In View form users see
all fields, as configured
Customer

25. Helpdesk
Engineer
Now let’s make these fields
visible to Helpdesk engineers

26. 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

27. New rules added, showing
the selected fields to
Helpdesk engineers.
5

28. Customer
Customers still see only part
of the fields, as configured

29. Helpdesk
Engineer
While Helpdesk
engineers see all fields,
as configured.

30. Demo
Context-sensitive forms:
Dynamically hiding/disabling fields
according to business logic

31. Customer
Selecting a category should
show and hide the relevant
fields

32. Customer
When selecting
“Hardware”

33. Customer
When selecting
“Software”

34. Let’s configure KWizCom Forms to
dynamically show these fields

35. 1

36. 1
2

37. Hide the
“Hardware type”
field, and add rule
1
2
3

38. Show the
“Hardware type” field
if Category=“Hardware”
1
2
3
4

39. These 2 rules make the
“Hardware type” become visible
only when Category field equals
“Hardware”
Yes, alternatively you can create one rule
to hide hardware type if category does
not equal hardware.

40. These 2 rules make the
“Hardware type” become
visible only when Category
field equals “Hardware”
Let’s click “OK” to
save settings

41. Customer

42. Customer

43. Customer

44. Customer
Simply do the same for software…

45. Helpdesk
Engineer
These 2 fields should be
displayed only when Issue
status field equals “Closed”

46. Let’s configure KWizCom Forms to
dynamically show these fields

47. 1

48. 1
2

49. 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

50. Helpdesk
Engineer

51. Helpdesk
Engineer
Let’s close this Support
Request..

52. Helpdesk
Engineer
Relevant fields appear
when Issue status is
“Closed”

53. Demo
Field Constraints:
Dynamic: Conditionally-mandatory fields

54. Helpdesk
Engineer
These 2 fields should be
mandatory only when Issue
status field equals “Closed”

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

56. 1

57. 2

58. 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

59. We’ve configured 3 field
validation rules

60. Resolution mandatory
Issue closing date mandatory
and not in the future

61. Helpdesk engineer edits
a Support Request item
Helpdesk
Engineer

62. Change Issue status
to “Closed”
Helpdesk
Engineer

63. Try to save without
updating Resolution and
Issue closing date fields
Helpdesk
Engineer

64. Helpdesk
Engineer
Customized validation
errors appear

65. Demo
Field Grouping:
Lets divide a long form to multiple tabs, each
visible to relevant audience

66. 1
2

67. 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

68. Customer
This is the group (tab) used to
create support requests

69. And this one is for Helpdesk
engineers to update case resolution
details.
Helpdesk engineer

70. Customer
Customer sees only one tab, because he
has no permissions to see any of the
fields in the other tab.

71. Helpdesk
Engineer
Helpdesk engineer sees the
2 tabs

72. Helpdesk
Engineer

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

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

75. Demo
Multi-row forms:
Managing employee expense reports

76. Data Model
Expenses
Expense Details
1
∞

77. (1) Create your Expense Details list

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

80. Connect to the details list

81. Select the columns to be
displayed in the
Repeating Rows field
Configure each
column’s width

82. Configure summary fields for
numeric/currency fields

83. Configure default
number of rows
Preview result

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

85. Let’s create a new
expense report

86. Added expenses and
clicking “Save”…

87. All configured form
features work within the
Repeating Rows field

88. Form summary field
available as list column
Hover over the Repeating Rows
column to quickly view the details

89. Professional
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
Standard
Enterprise

90. SharePoint Custom Action
Context-sensitive menus for productive business users

91.  Display customized menus, to
match user scenarios & use-cases
 Auto-update fields, minimize
human errors
 Trigger workflows
 Redirect to pages
 Configure permissions for menus
 Display only relevant fields for this
use case
With Custom Actions you can

92. Demo
Custom menus for a more
convenient IT Helpdesk UX

93. Demo
This is my
helpdesk workspace
I see an unassigned
issue that I wish to
assign to myself

94. 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”

95. Demo
I am clicking the custom menu
to gain ownership over this
support ticket

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

97. 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!

98. 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 now…

99. 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.

100. Demo
I am redirected to the issue’s edit
form, That includes only the
relevant fields
(other fields are automatically updated)

101. Demo
Once I save my updates, I can see that
some additional fields were auto updated
(Issue Status, Issue Closing Date)

102.  Display customized menus, to
match user scenarios & use-
cases
 Have less fields to update,
less page refreshes
 Easily integrate with workflows,
but much more than
workflows!
 Easier, user-friendly UX
Custom Actions enable you to

103. KWizCom Mobile
Improving efficiency of the mobile workforce

104. KWizCom Mobile
Smart, focused interface for productive mobile users

105. KWizCom Mobile

106. KWizCom Mobile
Smart, focused interface for productive mobile users
Server solution

107. Demo
Go Mobile:
1. All KWizCom Form features work in
mobile devices.
2. Create your custom mobile pages

108. Let’s click
“Go to mobile view”

109. Optimized display
for mobile devices

110. All KWizCom Forms features
automatically modified to
work in mobile
Custom Actions
Design once for both web and mobile!

111. Agenda viewApprove
Upload files &
attachments

112. Demo
Let’s design a more convenient mobile
workspace for IT Helpdesk engineers

114. 1st, create mobile
pages
A page includes
“page parts”

118. The result:

119. KWizCom Mobile
Easily 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
HTML5, jQuery Mobile

120. 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/
121

121. Questions?
Shai Petel
VP R&D, MVP
@shaibs
shai@kwizcom.com
http://kwizcom.blogspot.com