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
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
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
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
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
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
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
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
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
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
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
Here we have a support request form.
The form has some fields that should be visible and updatable by end users (customer), and some – by Helpdesk engineers..
Let’s hide the marked fields from everyone, and then show them only to the Helpdesk engineers group
By clicking the “Add field-level permission rule” we have added 4 rules for the 4 selected fields.
These rules are processed in run-time when a user opens any of the list forms.
These rules are called “Static rules” because we did not use any conditions, we skipped over the “Conditions” sections.
Last thing to do is click “Apply” to save the settings.
Let’s see the results…
Users cannot see those fields that we have hidden in New/Edit forms (Including administrator).
In the View form these fields are visible (as configured).
Now, let’s enable ONLY helpdesk engineers to view and update these fields.
Let’s click “Apply” to save the settings and see the results…
As a customer I still see the same fields, and do not see the fields that were configured as hidden
As a helpdesk engineer I can see all fields, as configured
So, we saw how we can hide fields from specific user/group. We call it ”Static” field permissions because these permission rules apply always, depending only on who you are (Customer or Helpdesk engineer in our example).
In this demo we’ll see “Dynamic” field permissions; these are permission rules that can be conditionally applied, depending on the current situation (and not only on who is the current user).
When reporting an issue, the end-user has to select the issue category. Depending on the selected value, different fields should appear, which are relevant to the selected category.
If user selects the “Hardware” category…
If user selects the “Software” category…
2 rules were added:
First one hides the “Hardware type” field always, from everyone and the second rule shows the field only if Category field equals “Hardware”.
Let’s repeat the same way and configure “Which software?” field be visible only when Category field equals “Software”
Let’s save the settings and check the results…
As a result, a new “Hardware type” choice fields appears.
And if I choose the “Software” category, the relevant field appears.
The Resolution and Issue closing date also need to be displayed in a dynamic way: only if Issue status field equals “Closed”.
Let’s configure the appropriate dynamic permission rules.
Let’s save the settings and check the results…
Remember these 2 fields (Resolution and Issue closing date)?
We’ve already configured them to appear to Helpdesk engineers only when Issue status field is set to “Closed”.
Now, we want these fields to be mandatory, only if Issue status equals “Closed”. So, what we want is these fields to be conditionally-mandatory. This is a dynamic constraint.
So, we’ve configured 3 field validation rules:
So, we’ve configured 3 field validation rules:
According to rules 1 and 2, Issue closing date field is mandatory and also cannot be a future date (later than today) if Issue status equals “Closed”.
According to rule 3, Resolution field is mandatory if Issue status equals “Closed”.
Let’s see how this works…
Tabs transform into groups, most features behave identically to the web or provide similar functionality modified to better suite the mobile.
Upload supports android, iOS, WindowsRT and Windows Phone 8.1