Kwizcom Forms is a SharePoint-native solution enhancing list forms with advanced features like dynamic field constraints, permissions, and context-sensitive forms, requiring no technical skills for end-users. With easy implementation, it integrates fully with SharePoint workflows and offers customizable mobile solutions for various user roles. The product enables efficient form management and supports diverse functionalities, catering to over 5000 global customers since its founding in 2005.

1. KWizCom Forms
True SharePoint-Native
Forms & Mobile Solution

2. KWizCom Corporation
• Founded in 2005
• Headquartered in Toronto
• Global vendor of SharePoint Add-Ons
• 5000+ customers worldwide

3. 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 ($)

4. Quick & easy
implementation
Support for various
field types
Fully integrated with
workflow, alerts and
search
You can easily add new parts
(such as 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
 More flexible form layout
 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 for custom columns
 Print
 File upload
 Separate design from SharePoint
 Full integration with SharePoint alerts, workflows,
search
 Requires Power-user skills

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

9. KWizCom Forms
Get all advanced form features
End-user tool, no technical skills required
Your forms already exist, just enhance
them!
100% SharePoint-Native
(Custom columns, themes, workflow)

10. Product Features
Let’s show you the features 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 rules
In 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 rule1
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”

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

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
Dynamic default values:
1. Different default values for different
people
2. Automatically update document Title to
be equal to the file’s name

54. Demo
Different default values for different
people

55. Customer
For a customer,
“Employee” field’s default
value should be equal to [Me]
(Although it’s invisible)

56. Helpdesk
Engineer
For Helpdesk engineers,
The “Employee” field’s default
value should be empty

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

58. 1

59. 2

60. We have configured 2
Default value rules

61. 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
Helpdesk
Engineer

62. Demo
Automatically update a document’s Title
(This has nothing to do with our Helpdesk example,
but still it’s an annoying issue…)

63. Click the “Library”
ribbon

64. Then click the
“List Extensions Settings”
menu

65. Select the field for
which you want to
setup a default value

66. Define your dynamic
default value
And click to add this
rule

67. Rule added

68. Click “OK” to save
the settings

69. Let’s add now a new
document

72. Demo
Field Constraints:
1. Dynamic: Conditionally-mandatory fields
2. Custom: Validate custom pattern using
regular expressions

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

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

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

76. 1

77. 2

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

79. We’ve configured 3 field
validation rules

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

81. Helpdesk engineer
edits a Support
Request item
Helpdesk
Engineer

82. Change Issue status
to “Closed”
Helpdesk
Engineer

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

84. Helpdesk
Engineer
Validation errors, as
configured

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

86. 1
2

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

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

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

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

91. Helpdesk
Engineer
Helpdesk engineer
sees the 2 tabs

92. Helpdesk
Engineer

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

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

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

96. Data Model
Expenses
Expense Details
1
∞

97. (1) Create your Expense Details list

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

100. Connect to the
details list

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

102. Configure summary
fields for
numeric/currency fields

103. Configure amount
of displayed rows
Preview result

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

105. Let’s create a new
expense report

106. Added expenses
and clicking
“Save”…

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

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

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

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

111.  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

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

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

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

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

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

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

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

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

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

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

122.  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

123. KWizCom Mobile
Improving efficiency of the mobile workforce

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

125. KWizCom Mobile

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

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

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

129. Optimized display
for mobile devices

130. All KWizCom Forms
features work in mobile
Custom Actions
Design once for both web and mobile!

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

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

137. The result:

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

139. KWizCom Forms
True SharePoint-Native
Forms & Mobile Solution

140. 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/
142

141. Thank you!
Nimrod Geva
Product Group Manager, KWizCom
nimrod@kwizcom.com