Difference between revisions of "Intelligent Capture Designer"

From Hornbill
Jump to navigation Jump to search
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
This document can now be found at its new location in the [https://docs.hornbill.com/servicemanager-config/customize/intelligent-capture-designer/ Hornbill Document Library].
 +
 +
[[file:hornbill-document-library.png|Intelligent Capture Designer|link=https://docs.hornbill.com/servicemanager-config/customize/intelligent-capture-designer/]]
 +
<!--
 +
 
{{DISPLAYTITLE:Intelligent Capture Designer}}
 
{{DISPLAYTITLE:Intelligent Capture Designer}}
 
{{breadcrumb|[[Main Page|Home]] > [[Configuration]] > Intelligent Capture Designer|Configuration}}
 
{{breadcrumb|[[Main Page|Home]] > [[Configuration]] > Intelligent Capture Designer|Configuration}}
Line 6: Line 11:
 
|
 
|
 
{{rightBox|Related Articles|
 
{{rightBox|Related Articles|
:* [[Progressive Capture Designer Validation, Error, and Information Messages|Capture Design Validation and Errors]]
+
:* [[Intelligent Capture Design Validation and Errors]]
 
:* [[Progressive Capture Workflow|Service Manager Intelligent Capture]]
 
:* [[Progressive Capture Workflow|Service Manager Intelligent Capture]]
 
:* [[Project_Manager_Progressive_Capture|Project Manager Intelligent Capture]]
 
:* [[Project_Manager_Progressive_Capture|Project Manager Intelligent Capture]]
Line 62: Line 67:
  
 
* When switching processes the UI for the analyst is  smooth as you are linking one process to another not replacing one with another
 
* When switching processes the UI for the analyst is  smooth as you are linking one process to another not replacing one with another
* The ability to return / revisit the forms in the initial process capture flow, once you have switched or linked to a second process capture flow in order to change values / choices or even change which progressive capture to switch / link too.
+
* The ability to return / revisit the forms in the initial process capture flow, once you have switched or linked to a second process capture flow in order to change values / choices or even change which pcapture to switch / link too.
* You don't need to include the same forms in both Progressive Captures, for example the Customer Search form could just be used in the initial progressive capture, and removed from the catalog item progressive capture (obviously if it already exists it will simply be ignored).
+
* You don't need to include the same forms in both captures, for example, the Customer Search form could just be used in the initial capture, and removed from the catalog item capture (obviously if it already exists it will simply be ignored).
  
 
'''Example'''  [[File:SwitchProcessConfig.png|right|thumb]]
 
'''Example'''  [[File:SwitchProcessConfig.png|right|thumb]]
Line 71: Line 76:
 
* 2.  Using another Custom Expression perform the same check but set this to '''Is Not Set''' (a Service rather than a request catalog item has been selected) and build your logic accordingly, equally you could define multiple other outcomes from this branch node to reflect the different service choices and paths you wish to take.
 
* 2.  Using another Custom Expression perform the same check but set this to '''Is Not Set''' (a Service rather than a request catalog item has been selected) and build your logic accordingly, equally you could define multiple other outcomes from this branch node to reflect the different service choices and paths you wish to take.
  
On the Switch Capture node, you can configure this to link to a specific new process, or use a '''Variable''' to link to the progressive capture linked to the request catalog item which has been chosen.  In this example, this is what we will do and the Variable to use would be '''Service details -> catalogProgressiveCaptureId'''
+
On the Switch Capture node, you can configure this to link to a specific new process, or use a '''Variable''' to link to the capture linked to the request catalog item which has been chosen.  In this example, this is what we will do and the Variable to use would be '''Service details -> catalogProgressiveCaptureId'''
 
 
* '''Note:''' with the introduction of the Switch Capture option, the behaviour will alter slightly on the '''Services Details''' form, is as much as the user will now have to select the '''Next''' button if they are selecting either the Service or the Request Catalog Item in order to progress the progressive capture.  Previously if a Request Catalog Item was chosen the progressive capture would immediately progress without the need to click '''Next'''.
 
 
 
== [[Default Form Configuration]] ==
 
  
Whilst default forms have a set purpose, it is also possible to configure aspects of these forms.
+
* '''Note:''' with the introduction of the Switch Capture option, the behaviour will alter slightly on the '''Services Details''' form, is as much as the user will now have to select the '''Next''' button if they are selecting either the Service or the Request Catalog Item in order to progress the capture workflow. Previously if a Request Catalog Item was chosen the capture would immediately progress without the need to click '''Next'''.
 
 
::[[Default Form Configuration|Read more...]]
 
  
 
== [[Customised Forms]] ==
 
== [[Customised Forms]] ==
  
As well as standard forms, Hornbill also provide the ability to create your own custom forms. With custom forms, you can create multiple questions of different field types for analysts and customers to answer during progressive capture.  
+
As well as standard forms, Hornbill also provide the ability to create your own custom forms. With custom forms, you can create multiple questions of different field types for analysts and customers to answer during capture.  
: '''New''' - A Never Skip configuration option has been added, which can be set to '''True''', this will ensure that this form is never bypassed in your progressive capture flow, even if custom questions have default values set, and the questions are not set to mandatory.  This will ensure the user will always be presented with the form to at least validate the default choices, or change them if required.
+
: '''New''' - A Never Skip configuration option has been added, which can be set to '''True''', this will ensure that this form is never bypassed in your capture workflow, even if custom questions have default values set, and the questions are not set to mandatory.  This will ensure the user will always be presented with the form to at least validate the default choices, or change them if required.
  
 
::[[Customised Forms|Read more...]]
 
::[[Customised Forms|Read more...]]
Line 92: Line 91:
 
When creating customised forms, and custom questions the default behaviour is for the question and answer to be visible on the request form in a '''Questions''' collapsable section.  It is also possible to map the answer from a custom question to one of the default fields on a request.
 
When creating customised forms, and custom questions the default behaviour is for the question and answer to be visible on the request form in a '''Questions''' collapsable section.  It is also possible to map the answer from a custom question to one of the default fields on a request.
  
::[[Mapping Fields from Customised Forms|Read more...]]
+
::[https://docs.hornbill.com/servicemanager-config/customize/mapping-fields-from-customized-forms/ Read more...]
  
 
==Sharing and Visibility==
 
==Sharing and Visibility==
  
Progressive capture owners will be able to view their own captures, and captures which have been shared with them from the Progressive Capture  List.   
+
Intelligent capture owners will be able to view their own captures, and captures which have been shared with them from the capture workflow list.   
  
 
When creating or editing a capture it is possible via the '''Manage Process Settings''' and '''Grant Access To''' option to share your process with:
 
When creating or editing a capture it is possible via the '''Manage Process Settings''' and '''Grant Access To''' option to share your process with:
Line 104: Line 103:
 
* Groups - Configured via the Organisational group structure
 
* Groups - Configured via the Organisational group structure
  
It is possible to share captures with multiple users, roles and groups.  Once a capture has been shared, the user will be able to view the capture from the '''Progressive Capture''' list.  
+
It is possible to share captures with multiple users, roles and groups.  Once a capture has been shared, the user will be able to view the capture from the '''Intelligent Capture''' list.  
  
 
To remove visibility to a specific User, Role or Group simply select the '''Trash Can''' icon next to the item you wish to stop sharing the capture with.
 
To remove visibility to a specific User, Role or Group simply select the '''Trash Can''' icon next to the item you wish to stop sharing the capture with.
Line 111: Line 110:
 
* Home > System > Settings > Advanced
 
* Home > System > Settings > Advanced
  
== Progressive Capture Options ==
+
== Intelligent Capture Options ==
  
Each Progressive Capture script has a number of configuration options
+
Each capture workflow has a number of configuration options
  
 
:* '''Download'''
 
:* '''Download'''
:: Download the definition file - downloads to a .txt file, a copy of the current progressive capture script
+
:: Download the definition file - downloads to a .txt file, a copy of the current capture workflow
 
:* '''Upload'''
 
:* '''Upload'''
:: Upload a pcf.txt file to the Progressive capture - this will replace the current progressive capture script content
+
:: Upload a pcf.txt file to the capture workflow - this will replace the current capture workflow content
 
:* '''Print'''
 
:* '''Print'''
:: Print out a document that provides a graphical representation of the the Progressive Capture script
+
:: Print out a document that provides a graphical representation of the capture workflow
 
:* '''Save''' (Validate, Activate, De-activate)
 
:* '''Save''' (Validate, Activate, De-activate)
:: After the creation or editing of a Progressive Capture script, your script needs to be saved and then activated to make if available for use.  Any Progressive Capture that you wish to keep but not have it available for use can be de-activated.
+
:: After the creation or editing of a capture workflow, your workflow needs to be saved and then activated to make it available for use.  Any capture workflow that you wish to keep but do not have available for use can be deactivated.
 
+
-->
== Versions ==
 
 
 
== Experimental Features ==
 
 
 
Hornbill may introduce new features in an experimental state, customers can choose to enable, use and provide feedback on these features. These features are subject to change and or removal.
 
 
 
== Displaying Conditional Fields ==
 
{{#ev:youtube|1dkfPvoKiZY|400|right}}
 
 
 
This feature allows for the showing or hiding of fields on custom progressive capture forms based on the answers to other questions on either the same custom progressive capture form, or answers to questions on previous progressive capture forms (conditions).
 
 
 
* Add a new form field to a progressive capture form and untick the '''This field will be visible on the form''' option under the '''Default Flags''' tab
 
* A new '''Override flags''' tab will be visible next to the '''Default Flags''', navigate here and select '''Add new condition'''
 
* Give the condition a name and choose options such as '''This field will be visible on the form'''
 
* Using the '''If the following is true''' option to add conditions under which this field will be shown / hidden, this can be based on a combination of values (answers) to other questions (fields) on the same or previous progressive capture forms.  Select apply Settings when finished.
 
* It is possible to set multiple sets of '''Conditions''' under which a field may be shown.  Simply add more conditions under the '''Override Flags''' tab using the '''Add new condition''' option
 
* Where multiple conditions are listed, these will be evaluated from the top down until a match is found, the evaluation will stop here and no further conditions will be checked).
 
* Complete the '''Field Type Settings''' options to define the attributes of the conditional field.
 
 
    
 
    
[[Category:Administration]][[Category:Videos]]
+
[[Category:HDOC]]

Latest revision as of 19:57, 11 April 2024

This document can now be found at its new location in the Hornbill Document Library.

Intelligent Capture Designer