KWizCom Forms
True SharePoint-Native
Forms & Mobile Solution
Shai Petel
VP R&D, MVP
@shaibs
shai@kwizcom.com
KWizCom Corporation
• Founded in 2005
• Headquartered in Toronto
• Global vendor of SharePoint Add-Ons
• 5000+ customers w...
Implementing forms in SharePoint
SharePoint list forms
Power-user tool
End-user tool
InfoPath or other
proprietary form to...
Quick & easy
implementation
Support for various
field types
Fully integrated with
workflow, alerts and
search
You can easi...
What’s missing in SharePoint forms?
 Context and logic
 Dynamic field constraints
 Tabs, group fields
 More flexible f...
External Form Tools
Feature-rich form designer
Enhanced form capabilities
External Form Tools
But…you lose your SharePoint freedom:
 Support custom columns?
 Support file upload?
 Separate desi...
KWizCom Forms
Turn your existing
SharePoint list forms into
Smart, Context-Sensitive Forms
KWizCom Forms
 Get all advanced form features
 End-user tool, no technical skills required
 Enhance existing SharePoint...
Product Features
Let’s show you how the product works
by implementing an IT Helpdesk
solution, step-by-step
CustomerHelpde...
Demo
Static Field permissions:
Allowing different users see different fields
Customer
Helpdesk
Engineer
This is the
Support Request
form
Some fields should be
visible to customers
Other fields should...
Hide marked fields
from everyone
1
Show these fields only
to Helpdesk engineers
2
Helpdesk
Engineer
Let’s configure KWizCom Forms to hide
these fields
1
1
2
1
Select fields that you wish to
show/hide/disable
2
Select permission type
3
Type users/groups for which this
permission rule should apply
4
Select the list forms where
you want to apply the field
permission rule
5
Click to add static
permission rulesIn run-time, these rules
are processed one by one
according to their order.
Let’s save the settings and see which fields
users see now when creating a new
Support Ticket.
Customer
In New/Edit forms users
see only these fields, as
configured
In View form users see
all fields, as configured
Customer
Helpdesk
Engineer
Now let’s make these fields
visible to Helpdesk engineers
1
Select fields that
you wish to show
2
Select “Show”
permission type
3 Type users/groups for which
this permission rule s...
New rules added, showing
the selected fields to
Helpdesk engineers.
5
Customer
Customers still see only part
of the fields, as configured
Helpdesk
Engineer
While Helpdesk
engineers see all fields,
as configured.
Demo
Context-sensitive forms:
Dynamically hiding/disabling fields
according to business logic
Customer
Selecting a category should
show and hide the relevant
fields
Customer
When selecting
“Hardware”
Customer
When selecting
“Software”
Let’s configure KWizCom Forms to
dynamically show these fields
1
1
2
Hide the
“Hardware type”
field, and add rule
1
2
3
Show the
“Hardware type” field
if Category=“Hardware”
1
2
3
4
These 2 rules make the
“Hardware type” become visible
only when Category field equals
“Hardware”
Yes, alternatively you ca...
These 2 rules make the
“Hardware type” become
visible only when Category
field equals “Hardware”
Let’s click “OK” to
save ...
Customer
Customer
Customer
Customer
Simply do the same for software…
Helpdesk
Engineer
These 2 fields should be
displayed only when Issue
status field equals “Closed”
Let’s configure KWizCom Forms to
dynamically show these fields
1
1
2
These 2 dynamic rules display
the Issue closing date and
Resolution fields only if Issue
status equals “Closed”
Let’s clic...
Helpdesk
Engineer
Helpdesk
Engineer
Let’s close this Support
Request..
Helpdesk
Engineer
Relevant fields appear
when Issue status is
“Closed”
Demo
Field Constraints:
Dynamic: Conditionally-mandatory fields
Helpdesk
Engineer
These 2 fields should be
mandatory only when Issue
status field equals “Closed”
Let’s configure the Resolution and Issue
closing date fields to be mandatory only if
Issue status equals “Closed”.
1
2
1
Select the field that
you wish to validate
3
Define conditions (when to
validate the field’s value)
4
Click to add this ...
We’ve configured 3 field
validation rules
Resolution mandatory
Issue closing date mandatory
and not in the future
Helpdesk engineer edits
a Support Request item
Helpdesk
Engineer
Change Issue status
to “Closed”
Helpdesk
Engineer
Try to save without
updating Resolution and
Issue closing date fields
Helpdesk
Engineer
Helpdesk
Engineer
Customized validation
errors appear
Demo
Field Grouping:
Lets divide a long form to multiple tabs, each
visible to relevant audience
1
2
1
Create field
groups
2
Decide which fields appear
in each groups
3
Define who can see this
field-group
4
Configure group
...
Customer
This is the group (tab) used to
create support requests
And this one is for Helpdesk
engineers to update case resolution
details.
Helpdesk engineer
Customer
Customer sees only one tab, because he
has no permissions to see any of the
fields in the other tab.
Helpdesk
Engineer
Helpdesk engineer sees the
2 tabs
Helpdesk
Engineer
Summary – KWizCom Forms
 Field-level permissions
 View-level permissions
 Dynamic field constraints
 Dynamic default v...
Professional
KWizCom Forms Professional
 Field-level permissions
 View-level permissions
 Dynamic field constraints
 D...
Demo
Multi-row forms:
Managing employee expense reports
Data Model
Expenses
Expense Details
1
∞
(1) Create your Expense Details list
(2) In your Expenses list create a Repeating
Rows column that connects to the Expense
Details list
Connect to the details list
Select the columns to be
displayed in the
Repeating Rows field
Configure each
column’s width
Configure summary fields for
numeric/currency fields
Configure default
number of rows
Preview result
Let’s save the settings and see the result
end-user experience
Let’s create a new
expense report
Added expenses and
clicking “Save”…
All configured form
features work within the
Repeating Rows field
Form summary field
available as list column
Hover over the Repeating Rows
column to quickly view the details
Professional
KWizCom Forms Enterprise
 Field-level permissions
 View-level permissions
 Dynamic field constraints
 Dyn...
SharePoint Custom Action
Context-sensitive menus for productive business users
 Display customized menus, to
match user scenarios & use-cases
 Auto-update fields, minimize
human errors
 Trigger work...
Demo
Custom menus for a more
convenient IT Helpdesk UX
Demo
This is my
helpdesk workspace
I see an unassigned
issue that I wish to
assign to myself
Demo
I clicked the support
ticket to see it in
View mode
Since the issue is
unassigned, I see a single
custom action calle...
Demo
I am clicking the custom menu
to gain ownership over this
support ticket
Demo
Now the issue appears under
“My Support Tickets” web part
(which means it is assigned to me)
Demo
By looking at the Support Tickets list,
you can see that the custom action has
updated the “Assigned To” and “Issue
S...
Demo
Now I see 2 different custom menus,
which are relevant to me as the
support engineer to whom this issue is
assigned
V...
Demo
Now I see 2 different custom
menus, which are relevant to me
as the support engineer to whom
this issue is assigned
I...
Demo
I am redirected to the issue’s edit
form, That includes only the
relevant fields
(other fields are automatically upda...
Demo
Once I save my updates, I can see that
some additional fields were auto updated
(Issue Status, Issue Closing Date)
 Display customized menus, to
match user scenarios & use-
cases
 Have less fields to update,
less page refreshes
 Easil...
KWizCom Mobile
Improving efficiency of the mobile workforce
KWizCom Mobile
Smart, focused interface for productive mobile users
KWizCom Mobile
KWizCom Mobile
Smart, focused interface for productive mobile users
Server solution
Demo
Go Mobile:
1. All KWizCom Form features work in
mobile devices.
2. Create your custom mobile pages
Let’s click
“Go to mobile view”
Optimized display
for mobile devices
All KWizCom Forms features
automatically modified to
work in mobile
Custom Actions
Design once for both web and mobile!
Agenda viewApprove
Upload files &
attachments
Demo
Let’s design a more convenient mobile
workspace for IT Helpdesk engineers
1st, create mobile
pages
A page includes
“page parts”
The result:
KWizCom Mobile
Easily configure a custom mobile solutions
Easy-to-use mobile solutions
Exactly the pages & menus
that your...
Resources
• Product web page:
http://www.kwizcom.com/sharepoint-add-ons/sharepoint-list-forms-
extensions-feature/overview...
Questions?
Shai Petel
VP R&D, MVP
@shaibs
shai@kwizcom.com
http://kwizcom.blogspot.com
KWizCom Forms
KWizCom Forms
KWizCom Forms
KWizCom Forms
KWizCom Forms
Upcoming SlideShare
Loading in …5
×

KWizCom Forms

882 views

Published on

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

Published in: Software
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
882
On SlideShare
0
From Embeds
0
Number of Embeds
31
Actions
Shares
0
Downloads
12
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • 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
  • KWizCom Forms

    1. 1. KWizCom Forms True SharePoint-Native Forms & Mobile Solution Shai Petel VP R&D, MVP @shaibs shai@kwizcom.com
    2. 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. 3. Implementing forms in SharePoint SharePoint list forms Power-user tool End-user tool InfoPath or other proprietary form tools Workflows with forms
    4. 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. 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. 6. External Form Tools Feature-rich form designer Enhanced form capabilities
    7. 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. 8. KWizCom Forms Turn your existing SharePoint list forms into Smart, Context-Sensitive Forms
    9. 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. 10. Product Features Let’s show you how the product works by implementing an IT Helpdesk solution, step-by-step CustomerHelpdesk engineer
    11. 11. Demo Static Field permissions: Allowing different users see different fields
    12. 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. 13. Hide marked fields from everyone 1 Show these fields only to Helpdesk engineers 2 Helpdesk Engineer
    14. 14. Let’s configure KWizCom Forms to hide these fields
    15. 15. 1
    16. 16. 1 2
    17. 17. 1 Select fields that you wish to show/hide/disable
    18. 18. 2 Select permission type
    19. 19. 3 Type users/groups for which this permission rule should apply
    20. 20. 4 Select the list forms where you want to apply the field permission rule
    21. 21. 5 Click to add static permission rulesIn run-time, these rules are processed one by one according to their order.
    22. 22. Let’s save the settings and see which fields users see now when creating a new Support Ticket.
    23. 23. Customer In New/Edit forms users see only these fields, as configured
    24. 24. In View form users see all fields, as configured Customer
    25. 25. Helpdesk Engineer Now let’s make these fields visible to Helpdesk engineers
    26. 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. 27. New rules added, showing the selected fields to Helpdesk engineers. 5
    28. 28. Customer Customers still see only part of the fields, as configured
    29. 29. Helpdesk Engineer While Helpdesk engineers see all fields, as configured.
    30. 30. Demo Context-sensitive forms: Dynamically hiding/disabling fields according to business logic
    31. 31. Customer Selecting a category should show and hide the relevant fields
    32. 32. Customer When selecting “Hardware”
    33. 33. Customer When selecting “Software”
    34. 34. Let’s configure KWizCom Forms to dynamically show these fields
    35. 35. 1
    36. 36. 1 2
    37. 37. Hide the “Hardware type” field, and add rule 1 2 3
    38. 38. Show the “Hardware type” field if Category=“Hardware” 1 2 3 4
    39. 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. 40. These 2 rules make the “Hardware type” become visible only when Category field equals “Hardware” Let’s click “OK” to save settings
    41. 41. Customer
    42. 42. Customer
    43. 43. Customer
    44. 44. Customer Simply do the same for software…
    45. 45. Helpdesk Engineer These 2 fields should be displayed only when Issue status field equals “Closed”
    46. 46. Let’s configure KWizCom Forms to dynamically show these fields
    47. 47. 1
    48. 48. 1 2
    49. 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. 50. Helpdesk Engineer
    51. 51. Helpdesk Engineer Let’s close this Support Request..
    52. 52. Helpdesk Engineer Relevant fields appear when Issue status is “Closed”
    53. 53. Demo Field Constraints: Dynamic: Conditionally-mandatory fields
    54. 54. Helpdesk Engineer These 2 fields should be mandatory only when Issue status field equals “Closed”
    55. 55. Let’s configure the Resolution and Issue closing date fields to be mandatory only if Issue status equals “Closed”.
    56. 56. 1
    57. 57. 2
    58. 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. 59. We’ve configured 3 field validation rules
    60. 60. Resolution mandatory Issue closing date mandatory and not in the future
    61. 61. Helpdesk engineer edits a Support Request item Helpdesk Engineer
    62. 62. Change Issue status to “Closed” Helpdesk Engineer
    63. 63. Try to save without updating Resolution and Issue closing date fields Helpdesk Engineer
    64. 64. Helpdesk Engineer Customized validation errors appear
    65. 65. Demo Field Grouping: Lets divide a long form to multiple tabs, each visible to relevant audience
    66. 66. 1 2
    67. 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. 68. Customer This is the group (tab) used to create support requests
    69. 69. And this one is for Helpdesk engineers to update case resolution details. Helpdesk engineer
    70. 70. Customer Customer sees only one tab, because he has no permissions to see any of the fields in the other tab.
    71. 71. Helpdesk Engineer Helpdesk engineer sees the 2 tabs
    72. 72. Helpdesk Engineer
    73. 73. Summary – KWizCom Forms  Field-level permissions  View-level permissions  Dynamic field constraints  Dynamic default values  Field-grouping (Tabs) Standard
    74. 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. 75. Demo Multi-row forms: Managing employee expense reports
    76. 76. Data Model Expenses Expense Details 1 ∞
    77. 77. (1) Create your Expense Details list
    78. 78. (2) In your Expenses list create a Repeating Rows column that connects to the Expense Details list
    79. 79. Connect to the details list
    80. 80. Select the columns to be displayed in the Repeating Rows field Configure each column’s width
    81. 81. Configure summary fields for numeric/currency fields
    82. 82. Configure default number of rows Preview result
    83. 83. Let’s save the settings and see the result end-user experience
    84. 84. Let’s create a new expense report
    85. 85. Added expenses and clicking “Save”…
    86. 86. All configured form features work within the Repeating Rows field
    87. 87. Form summary field available as list column Hover over the Repeating Rows column to quickly view the details
    88. 88. 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
    89. 89. SharePoint Custom Action Context-sensitive menus for productive business users
    90. 90.  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
    91. 91. Demo Custom menus for a more convenient IT Helpdesk UX
    92. 92. Demo This is my helpdesk workspace I see an unassigned issue that I wish to assign to myself
    93. 93. 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”
    94. 94. Demo I am clicking the custom menu to gain ownership over this support ticket
    95. 95. Demo Now the issue appears under “My Support Tickets” web part (which means it is assigned to me)
    96. 96. 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!
    97. 97. 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…
    98. 98. 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.
    99. 99. Demo I am redirected to the issue’s edit form, That includes only the relevant fields (other fields are automatically updated)
    100. 100. Demo Once I save my updates, I can see that some additional fields were auto updated (Issue Status, Issue Closing Date)
    101. 101.  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
    102. 102. KWizCom Mobile Improving efficiency of the mobile workforce
    103. 103. KWizCom Mobile Smart, focused interface for productive mobile users
    104. 104. KWizCom Mobile
    105. 105. KWizCom Mobile Smart, focused interface for productive mobile users Server solution
    106. 106. Demo Go Mobile: 1. All KWizCom Form features work in mobile devices. 2. Create your custom mobile pages
    107. 107. Let’s click “Go to mobile view”
    108. 108. Optimized display for mobile devices
    109. 109. All KWizCom Forms features automatically modified to work in mobile Custom Actions Design once for both web and mobile!
    110. 110. Agenda viewApprove Upload files & attachments
    111. 111. Demo Let’s design a more convenient mobile workspace for IT Helpdesk engineers
    112. 112. 1st, create mobile pages A page includes “page parts”
    113. 113. The result:
    114. 114. 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
    115. 115. 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
    116. 116. Questions? Shai Petel VP R&D, MVP @shaibs shai@kwizcom.com http://kwizcom.blogspot.com

    ×