DES/Current/Designer/Segmentation - Revision history

Brian.marshall@genesys.com: Published

2021-04-21T15:36:43Z

Published

Ed.jamer@genesys.com: Ed.jamer@genesys.com moved page PEC-ROU/Current/Designer/Segmentation to DES/Current/Designer/Segmentation: Text replacement - "PEC-ROU/Current/Designer/" to "DES/Current/Designer/"

2021-04-21T13:57:34Z

Ed.jamer@genesys.com moved page PEC-ROU/Current/Designer/Segmentation to DES/Current/Designer/Segmentation: Text replacement - "PEC-ROU/Current/Designer/" to "DES/Current/Designer/"

WikiSysop: Text replacement - "\|Platform=([^\|])GenesysEngage-onpremises([\|])" to "|Platform=$1GenesysEngage-cloud$2"

2020-07-25T02:31:13Z

Text replacement - "\|Platform=([^\|]*)GenesysEngage-onpremises([\|]*)" to "|Platform=$1GenesysEngage-cloud$2"

WikiSysop: Text replacement - "\|Platforms?=([^\|])PureEngage([\|])" to "|Platform=$1GenesysEngage-onpremises$2"

2020-07-15T11:46:31Z

Text replacement - "\|Platforms?=([^\|]*)PureEngage([\|]*)" to "|Platform=$1GenesysEngage-onpremises$2"

Bgrenon: Published

2020-06-08T15:16:47Z

Published

New page

{{Article
|Standalone=No
|DisplayName=Segmentation Block
|TocName=Segmentation Block
|Context=This block enables an application to take a different path when certain conditions are met.
|ComingSoon=No
|Platform=PureEngage
|Role=Administrator
|Application=Designer
|Prereq=
|Section={{Section
|sectionHeading=
|anchor=
|alignment=Vertical
|Media=
|image=
|structuredtext=You can use a '''Segmentation''' block to take a different path depending on the specific values of application variables. A valid ECMAScript expression containing application variables, ECMAScript operators, and Designer functions can be used to define a Segmentation Option. If this condition is evaluated to a ''true'' (Boolean) value while the application executes, the application flow takes the path of that Segmentation Option.

You can define multiple Segmentation Options, each with their own conditions. For example, the condition can be a variable with a Boolean value, a call to a function that returns a Boolean, or a combination of variables with logic operators that evaluates to a Boolean.

The first condition that evaluates successfully is selected as the segmentation path, and any blocks under that Segmentation Option are executed. If no condition expression evaluates successfully, none of the Segmentation Options execute, and the application executes the block that follows the '''Segmentation''' block.

Application variable values can be set based on logic in the application, by querying external data sources from blocks (such as the {{Link-SomewhereInThisManual|topic=HTTPREST|anchor=top|display text=HTTP REST block}}), or by collecting input from a caller in the {{Link-SomewhereInThisManual|topic=UserInput|anchor=top|display text=User Input block}}.

Conditions are ordered and exclusive, which means:

*Condition expressions are evaluated in the order they are defined.
*If one condition evaluates to true and the corresponding path is selected, then the following condition expressions are not tested. After executing this segment path, the application executes the block that follows the '''Segmentation''' block.

{{NoteFormat|If the same logic needs to be executed in multiple segmentation paths, Genesys recommends that you keep the paths for each option independent and avoid using '''GoTo''' blocks to jump between paths. The common logic can be moved into a {{Link-SomewhereInThisManual|topic=SharedModulesBar|anchor=top|display text=Shared Module}}, which can then be called from multiple paths. This improves the structure and reliability of your application.|2}}

The '''Segmentation''' block selects the first segment whose condition is a valid ECMAScript expression that evaluates to ''true'' (Boolean). If none of the conditions evaluate to ''true'', no segment is executed, and processing moves on to the next sibling of the '''Segmentation''' block.

{{NoteFormat|You must use condition expressions that evaluate to a Boolean value. Expressions that evaluate to a different data type can result in errors.|3}}

The following are valid expressions:

*Using a variable whose value is ''true'' or ''false'' and comparing it to a Boolean value, such as the variable used to hold the result of a '''Special Days''' block:
*:<pre>isSpecialDayVar == true</pre>
*:or:
*:<pre>isSpecialDayVar == false</pre>
*Using a Boolean property of an object stored in a variable, such as the '''Route Call''' block outcome variable:
*:<pre>routeCallOutcomeVar.success == true</pre>
*An expression using Boolean variables and logical operators:
*:<pre>var1 == false || (var2 == true && var3 == true))</pre>
*An expression using comparison operators:
*:<pre>var1.length > 3 || var2 === 'stop'</pre>
|structuredtextwide=
|FAQHeading=
|Status=No
}}{{Section
|sectionHeading=Conditions tab
|anchor=Conditionstab
|alignment=Vertical
|Media=
|image=
|structuredtext=Click '''Add Condition''' and type the condition to evaluate in the '''Condition Expression''' field. The value can be a simple Boolean value, a variable with some Boolean content, or any valid JavaScript expression that evaluates to a Boolean. The condition expression can refer to other variables.

You can edit the '''Segment Label''' field to give a meaningful label to your segment. The child segment block will be named accordingly.

To remove a condition, click the trash icon for that condition in the '''Segmentation''' block or click the trash icon on the related child block.

{{NoteFormat|Always make sure the condition evaluates to a Boolean value at runtime.}}

[[File:des_segmentation.png]]
|structuredtextwide=
|FAQHeading=
|Status=No
}}{{Section
|sectionHeading=Milestone tab
|anchor=Milestonetab
|alignment=Vertical
|Media=
|image=
|structuredtext=Add a Milestone to mark this key moment while the application is running, similar to within the {{Link-SomewhereInThisVersion|manual=Designer|topic=Milestone}}.
|structuredtextwide=
|FAQHeading=
|Status=No
}}
}}

@@ Line 8: / Line 8: @@
 |Role=Administrator
 |Application=Designer
 |Section={{Section
 |alignment=Vertical
 |structuredtext=You can use a '''Segmentation''' block to take a different path depending on the specific values of application variables. A valid ECMAScript expression containing application variables, ECMAScript operators, and Designer functions can be used to define a Segmentation Option. If this condition is evaluated to a ''true'' (Boolean) value while the application executes, the application flow takes the path of that Segmentation Option.
@@ Line 46: / Line 41: @@
 *An expression using comparison operators:
 *:<pre>var1.length > 3 || var2 === 'stop'</pre>
 |Status=No
 }}{{Section
@@ Line 53: / Line 46: @@
 |anchor=Conditionstab
 |alignment=Vertical
-|Media=
+|structuredtext=Click '''Add Condition.''' The '''Condition Expression''' field is pre-populated with a sample expression that you can edit by typing a condition to evaluate.
-|image=
-|structuredtext=Click '''Add Condition''' and type the condition to evaluate in the '''Condition Expression''' field. The value can be a simple Boolean value, a variable with some Boolean content, or any valid JavaScript expression that evaluates to a Boolean. The condition expression can refer to other variables.
+[[File:des_segmentation_add_condition.png]]
 You can edit the '''Segment Label''' field to give a meaningful label to your segment. The child segment block will be named accordingly.
@@ Line 64: / Line 59: @@
 [[File:des_segmentation.png]]
 |Status=No
 }}{{Section
@@ Line 71: / Line 64: @@
 |anchor=Milestonetab
 |alignment=Vertical
 |structuredtext=Add a Milestone to mark this key moment while the application is running, similar to within the {{Link-SomewhereInThisVersion|manual=Designer|topic=Milestone}}.
 |Status=No
 }}
 }}

← Older revision	Revision as of 13:57, April 21, 2021
(No difference)

@@ Line 5: / Line 5: @@
 |Context=This block enables an application to take a different path when certain conditions are met.
 |ComingSoon=No
-|Platform=GenesysEngage-onpremises
+|Platform=GenesysEngage-cloud
 |Role=Administrator
 |Application=Designer

DES/Current/Designer/Segmentation - Revision history

Brian.marshall@genesys.com: Published

Ed.jamer@genesys.com: Ed.jamer@genesys.com moved page PEC-ROU/Current/Designer/Segmentation to DES/Current/Designer/Segmentation: Text replacement - "PEC-ROU/Current/Designer/" to "DES/Current/Designer/"

WikiSysop: Text replacement - "\|Platform=([^\|]*)GenesysEngage-onpremises([\|]*)" to "|Platform=$1GenesysEngage-cloud$2"

WikiSysop: Text replacement - "\|Platforms?=([^\|]*)PureEngage([\|]*)" to "|Platform=$1GenesysEngage-onpremises$2"

Bgrenon: Published

WikiSysop: Text replacement - "\|Platform=([^\|])GenesysEngage-onpremises([\|])" to "|Platform=$1GenesysEngage-cloud$2"

WikiSysop: Text replacement - "\|Platforms?=([^\|])PureEngage([\|])" to "|Platform=$1GenesysEngage-onpremises$2"