DES/Current/Designer/AppStruc - Revision history

WikiSysop at 19:43, March 30, 2022

2022-03-30T19:43:07Z

Brian.marshall@genesys.com: Published

2021-06-22T19:37:41Z

Published

Ed.jamer@genesys.com: Text replacement - "{{#widget:Vimeo" to "{{Video"

2021-06-10T12:01:54Z

Text replacement - "{{#widget:Vimeo" to "{{Video"

Brian.marshall@genesys.com: Published

2021-05-18T17:55:02Z

Published

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

2021-04-21T13:57:37Z

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

Brian.marshall@genesys.com: Published

2021-03-19T14:48:16Z

Published

Brian.marshall@genesys.com: Published

2021-02-11T20:26:18Z

Published

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

2020-07-25T02:34:31Z

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

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

2020-07-15T11:45:41Z

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

Bgrenon: Published

2020-06-08T15:21:15Z

Published

New page

{{Article
|Standalone=No
|DisplayName=Application Workflow
|TocName=Application Workflow
|Context=Learn about the workflow Designer uses for developing applications.
|ComingSoon=No
|Platform=PureEngage
|Role=Administrator
|Application=Designer
|Prereq=
|Section={{Section
|sectionHeading=
|anchor=
|alignment=Vertical
|Media=
|image=
|structuredtext=Designer uses a stream-based workflow for developing applications. In this type of model, an application consists of multiple work {{Link-SomewhereInThisManual|topic=AppStruc|anchor=appStreams|display text=streams}}, each of which represents a different stage in the life cycle of the application (such as the development or quality assurance stage).

At various times, you can "freeze" the current state of the application code as a {{Link-SomewhereInThisManual|topic=AppStruc|anchor=appBuilds|display text=build}}, which you can then assign to the appropriate stream. The builds are promoted through the various streams until a build is approved for use in the live production environment.

One of the primary benefits to this type of workflow is that each stream runs a build of the application that is completely independent of the others. For example, the development team can be working on a build without impacting the build being tested by the quality assurance team or the build that is actively running in production.

This page provides more details about builds and streams. You can also watch this video to see an example of a workflow in action:

{{#widget:Vimeo|id=305589601|height=405|width=720}}
|structuredtextwide=
|FAQHeading=
|Status=No
}}{{Section
|sectionHeading=Application streams
|anchor=appStreams
|alignment=Vertical
|Media=
|image=
|structuredtext=You can view and manage the streams of an application from the {{Link-SomewhereInThisManual|topic=ApplicationsBar|anchor=appprops|display text=application properties}}:

[[File:Des app properties streams example 02.png]]

There are four application streams:
====DEV (Development)====
This stream is the only one that can run the latest published version of the application code. As such, it is also the only stream impacted by Designer upgrades.
====QA (Quality Assurance)====
This stream is for builds that require quality assurance testing.
====UAT (User Acceptance Testing)====
This stream is for builds that require beta-testing or some other variation of user-based trials.
====LIVE====
This stream is for builds that are actively running in the production environment.
====LIVE B====
This is an optional stream that can run a second application build in the live production environment. For more information, see {{Link-SomewhereInThisVersion|manual=Designer|topic=AppStruc|anchor=liveb|display text=LIVE B streams}}.

All streams are enabled by default. You can use the '''Status''' sliders to {{Link-SomewhereInThisVersion|manual=Designer|topic=ApplicationsBar|display text=enable or disable them|anchor=stream_status}}, as needed.
|structuredtextwide=
|FAQHeading=
|Status=No
}}{{Section
|sectionHeading=Application builds
|anchor=appBuilds
|alignment=Vertical
|Media=
|image=
|structuredtext=When you want to "freeze" a version of your application code, you can create a build. A build is basically a self-contained package of the application code. It has all of the resources it needs to run, so you can assign a build to a stream without worrying about impacts to the original resources or to the other builds.

You can create a build by clicking '''Build''' when the application is open in editing mode. Designer automatically increases the version number of the build, but you can add your own label and note:

[[file:des_generate_new_build.gif]]

You can manage the builds for an application by clicking {{Link-SomewhereInThisManual|topic=ApplicationsBar|anchor=manage_builds|display text=Manage Builds}} from the application properties.

{{NoteFormat|
* '''Once generated, a build cannot be changed.''' If you want to make changes, you must generate a new build. You can also choose to perform a rollback by selecting a previous build.
* '''There is a limit of 20 builds for each application.''' Therefore, it's recommended that you generate a build only when required. If you exceed 20 builds, the '''Build''' button becomes disabled. You can re-enable the button by deleting builds that are no longer needed.
}}
|structuredtextwide=
|FAQHeading=
|Status=No
}}{{Section
|sectionHeading=Parallel Test Environment (PTE)
|anchor=pte
|alignment=Vertical
|Media=
|image=
|structuredtext=The Parallel Test Environment enables you to use test resources instead of production ones when running an application build in a non-production stream. You can {{Link-SomewhereInThisVersion|manual=Designer|topic=ApplicationsBar|anchor=pte|display text=enable this option}} on the '''Misc''' tab in the application settings. When enabled, you can create copies of certain resources and add a special ''test_'' prefix to the resource name.

Streams that are running non-production builds (DEV, QA, and UAT) will reference the PTE versions of the resources (test_''<resource name>'') instead of the ones being used in production. The LIVE build continues to reference the original production resources.

PTE is supported for Business Controls resources ('''Business Hours''', '''Emergency Flags''', '''Special Days''', and '''Data Tables''') and certain configuration resources ('''Virtual Queues''', '''Agents''', '''Agent Groups''', and '''Skills''').
|structuredtextwide=
|FAQHeading=
|Status=No
}}{{Section
|sectionHeading=LIVE B streams
|anchor=liveb
|alignment=Vertical
|Media=
|image=
|structuredtext=You can run an optional LIVE B stream in addition to the existing LIVE stream. This allows you to run a second application in LIVE production mode, which gives you greater flexibility in how you can introduce new application builds into your production environment.

For example, each LIVE stream can have different contact points assigned to it, so one way you could use the LIVE and LIVE B streams is to allocate interactions coming from a certain region to a particular stream, or use the streams to balance (or gradually introduce) the number of interactions being handled by a new production build. In this way, you can implement a form of A/B testing.

Let's say you wanted to split or balance the number of interactions being handled between the LIVE and LIVE B builds. Typically, you would gradually introduce more interactions from LIVE to LIVE B, which could be done as follows:

*Assign '''Build X''' to the LIVE stream.
*Use the '''Manage''' button to assign phone numbers to the LIVE stream. At this point, 100% of the interaction load will be handled by '''Build X''' on the LIVE stream.
*Now, assign '''Build X+1''' to the LIVE B stream.
*Assign some of the phone numbers to the LIVE B stream so that 70% of the interaction load is handled by LIVE and 30% by LIVE B.
*:{{NoteFormat|The {{Link-SomewhereInThisVersion|manual=Designer|topic=ApplicationsBar|anchor=transfer|display text=Transfer from Others}} button is a great way to easily and quickly move several numbers from one stream to another.|2}}
*Check Designer Analytics to see if there are any issues.
*If there are no issues, we can then move more of the phone numbers from LIVE to LIVE B, so that 30% of the interaction load is being handled by LIVE and 70% load by LIVE B.
*Again, we continue to monitor Designer Analytics to see if there are any issues.
*If everything still looks ok, we can move the remaining phone numbers from LIVE to LIVE B, so that 100% of the interaction load is being handled by LIVE B.
*Assign '''Build X+2''' to the LIVE stream. This is a new build that we want to test in conjunction with '''Build X+1''' on LIVE B.
*Assign some phone numbers to the LIVE stream so that 30% of the interaction load is being handled by our new application build running on LIVE and 70% by LIVE B.
*Continue to check Designer Analytics for any issues, and adjust and balance the interaction load between the two builds as desired.
|structuredtextwide=
|FAQHeading=
|Status=No
}}
}}

@@ Line 71: / Line 71: @@
 *'''Rollbacks are permitted'''. To perform a rollback, simply assign a previous build to a stream.
 *'''Each application has a 20-build limit'''. Therefore, it's recommended to only generate builds when required. If you exceed this limit, the '''Build''' button becomes disabled. You can re-enable the button by deleting builds that are no longer needed.
 To manage the builds for an application, use the {{Link-SomewhereInThisManual|topic=ApplicationsBar|anchor=manage_builds|display text=Manage Builds}} option when viewing the {{Link-SomewhereInThisManual|topic=ApplicationsBar|anchor=appprops|display text=application properties}}.

@@ Line 9: / Line 9: @@
 |Application=Designer
 |Section={{Section
 |alignment=Vertical
-|structuredtext=Designer uses a stream-based workflow for developing applications. In this type of model, an application consists of multiple work '''streams''', each of which represents a different stage in the life cycle of the application:
+|structuredtext=Designer uses a stream-based workflow for developing applications. In this type of model, an application consists of multiple work {{Link-SomewhereInThisManual|topic=AppStruc|anchor=appStreams|display text=streams}}, each of which represents a different stage in the life cycle of the application:
 *DEV (Development)
@@ Line 17: / Line 19: @@
 *LIVE (Live Production)
-To learn more about streams, see {{Link-SomewhereInThisManual|topic=AppStruc|anchor=appStreams|display text=application streams}}.
+When you want to freeze the current state of the application code, you can generate an {{Link-SomewhereInThisManual|topic=AppStruc|anchor=appBuilds|display text=application build}} and assign it to a stream. The build can then be promoted to the QA and UAT streams until you are ready to assign the build to LIVE and run it in the production environment.
 This type of workflow enables you to have multiple builds of the application running in different streams, completely independent of the others. For example, a developer can work on a build without impacting the build that is assigned to quality assurance or the build that is actively running in production.
-Watch this video to see the workflow in action:
+This video shows the workflow in action:
-{{Video|id=305589601|height=405|width=720}}
+{{Video|id=305589601|height=405|width=720|Description=Working with application builds and streams}}
 |Status=No
 }}{{Section
@@ Line 35: / Line 33: @@
 |structuredtext=You can view and manage the streams of an application from the {{Link-SomewhereInThisManual|topic=ApplicationsBar|anchor=appprops|display text=application properties}}:
-[[File:Des app properties streams example 02.png]]
+[[File:Des_app_properties_streams_example_02.png]]
 There are four application streams:
@@ Line 49: / Line 47: @@
 This is an optional stream that can run a second application build in the live production environment. For more information, see {{Link-SomewhereInThisVersion|manual=Designer|topic=AppStruc|anchor=liveb|display text=LIVE B streams}}.
-All streams are enabled by default. You can use the '''Status''' sliders to {{Link-SomewhereInThisVersion|manual=Designer|topic=ApplicationsBar|display text=enable or disable them|anchor=stream_status}}, as needed.
+All streams are enabled by default. You can use the '''Status''' sliders to {{Link-SomewhereInThisVersion|manual=Designer|topic=ApplicationsBar|anchor=stream_status|display text=enable or disable them}} as needed.
 |Status=No
 }}{{Section

@@ Line 10: / Line 10: @@
 |Section={{Section
 |alignment=Vertical
-|structuredtext=Designer uses a stream-based workflow for developing applications. In this type of model, an application consists of multiple work streams, each of which represents a different stage in the life cycle of the application. There are four streams you can use: DEV (development), QA (Quality Assurance), UAT (User Accessibility Testing), and LIVE (production stream). For more information, see {{Link-SomewhereInThisManual|topic=AppStruc|anchor=appStreams|display text=application streams}}.
+|structuredtext=Designer uses a stream-based workflow for developing applications. In this type of model, an application consists of multiple work '''streams''', each of which represents a different stage in the life cycle of the application:
-When you want to freeze the current state of the application code, you can generate a build and assign it to a stream. The build can then be promoted to the QA and UAT streams until you are ready to assign the build to LIVE and run it in the production environment. For more information, see {{Link-SomewhereInThisManual|topic=AppStruc|anchor=appBuilds|display text=application builds}}.
+*DEV (Development)
-This workflow enables you to have multiple builds of the application running in different streams, completely independent of the others. For example, a developer can work on a build without impacting the build that is assigned to quality assurance or the build that is actively running in production.
+To learn more about streams, see {{Link-SomewhereInThisManual|topic=AppStruc|anchor=appStreams|display text=application streams}}.
-This video shows the workflow in action:
+When you want to freeze the current state of the application code, you can generate a '''build''' and assign it to a stream. The build can then be promoted to the QA and UAT streams until you are ready to assign the build to LIVE and run it in the production environment.
 {{#widget:Vimeo|id=305589601|height=405|width=720}}
@@ Line 54: / Line 63: @@
 [[File:des_create_build.png]]
-Designer automatically adds or increases the version number of the build. You must assign the build a '''Label''' and, if desired, you can also add a '''Note'''. When you are finished, click '''Build'''.
+Designer automatically adds or increments the '''version''' of the build. You must assign the build a '''Label''' and, if desired, you can use the '''Note''' field to provide any additional information about the build. When you are finished, click '''Build'''.
-[[File:des_create_build_2.png]]
+[[File:Des create build example.png]]
 Things to keep in mind when working with builds:

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

@@ Line 1: / Line 1: @@
 {{Article
 |Standalone=No
-|DisplayName=Application Workflow
+|DisplayName=Application workflow
 |TocName=Application workflow (builds and streams)
-|Context=Learn how the Designer application development workflow is managed with builds and streams.
+|Context=Learn how to use builds and streams to manage the Designer application development workflow.
 |ComingSoon=No
 |Platform=GenesysEngage-cloud
@@ Line 10: / Line 10: @@
 |Section={{Section
 |alignment=Vertical
-|structuredtext=Designer uses a stream-based workflow for developing applications. In this type of model, an application consists of multiple work {{Link-SomewhereInThisManual|topic=AppStruc|anchor=appStreams|display text=streams}}, each of which represents a different stage in the life cycle of the application (such as the development or quality assurance stage).
+|structuredtext=Designer uses a stream-based workflow for developing applications. In this type of model, an application consists of multiple work streams, each of which represents a different stage in the life cycle of the application. There are four streams you can use: DEV (development), QA (Quality Assurance), UAT (User Accessibility Testing), and LIVE (production stream). For more information, see {{Link-SomewhereInThisManual|topic=AppStruc|anchor=appStreams|display text=application streams}}.
-At various times, you can "freeze" the current state of the application code as a {{Link-SomewhereInThisManual|topic=AppStruc|anchor=appBuilds|display text=build}}, which you can then assign to the appropriate stream. The builds are promoted through the various streams until a build is approved for use in the live production environment.
+When you want to freeze the current state of the application code, you can generate a build and assign it to a stream. The build can then be promoted to the QA and UAT streams until you are ready to assign the build to LIVE and run it in the production environment. For more information, see {{Link-SomewhereInThisManual|topic=AppStruc|anchor=appBuilds|display text=application builds}}.
-One of the primary benefits to this type of workflow is that each stream runs a build of the application that is completely independent of the others. For example, the development team can be working on a build without impacting the build being tested by the quality assurance team or the build that is actively running in production.
+This workflow enables you to have multiple builds of the application running in different streams, completely independent of the others. For example, a developer can work on a build without impacting the build that is assigned to quality assurance or the build that is actively running in production.
-This page provides more details about builds and streams. You can also watch this video to see an example of a workflow in action:
+This video shows the workflow in action:
 {{#widget:Vimeo|id=305589601|height=405|width=720}}
@@ Line 30: / Line 30: @@
 There are four application streams:
 ====DEV (Development)====
-This stream always runs the latest published version of the application code. As such, it is also the only stream that can be affected by Designer upgrades.
+This stream always runs the latest published version of the application code. As such, it is the only stream affected by Designer upgrades.
 ====QA (Quality Assurance)====
-This stream is for builds that require quality assurance testing.
+For builds that require Quality Assurance testing.
 ====UAT (User Acceptance Testing)====
-This stream is for builds that require beta-testing or some other variation of user-based trials.
+For builds that require beta-testing or some other variation of user-based trials.
 ====LIVE====
-This stream is for builds that are actively running in the production environment.
+For builds that are actively running in the production environment.
 ====LIVE B====
 This is an optional stream that can run a second application build in the live production environment. For more information, see {{Link-SomewhereInThisVersion|manual=Designer|topic=AppStruc|anchor=liveb|display text=LIVE B streams}}.
@@ Line 46: / Line 46: @@
 |anchor=appBuilds
 |alignment=Vertical
-|structuredtext=When you want to "freeze" a version of your application code, you can create a build. A build is basically a self-contained package of the application code. It has all of the resources it needs to run, so you can assign a build to a stream without worrying about impacts to the original resources or to the other builds.
+|structuredtext=A build is basically a self-contained package of the application code. It has all of the resources it needs to run, so you can assign a build to a stream without worrying about impacts to the original resources or to the other builds.
-You can only create a build ''after'' the application has been published. If your application has not yet been published, the '''Build''' button remains disabled until the application has been published at least once. When generating a new build, Designer always uses the most recently ''published'' version of the application code. If you've made changes to an application that you want to capture in a new build, you must re-publish the application before generating the build.
+Builds can be created only ''after'' the application has been published. If your application has not yet been published, the '''Build''' button remains disabled until the application has been published at least once. When generating a new build, Designer always uses the most recently ''published'' version of the application code. If you've made changes to an application that you want to capture in a new build, you must re-publish the application before generating the build.
 To create a build, open the application in editing mode and click '''Build:'''
@@ Line 63: / Line 63: @@
 *'''Builds are immutable.''' Once generated, a build cannot be changed.
 *'''Rollbacks are permitted'''. To perform a rollback, simply assign a previous build to a stream.
-*'''Each applications has a 20-build limit'''. Therefore, it's recommended to only generate builds when required. If you exceed this limit, the '''Build''' button becomes disabled. You can re-enable the button by deleting builds that are no longer needed.
+*'''Each application has a 20-build limit'''. Therefore, it's recommended to only generate builds when required. If you exceed this limit, the '''Build''' button becomes disabled. You can re-enable the button by deleting builds that are no longer needed.
 To manage the builds for an application, use the {{Link-SomewhereInThisManual|topic=ApplicationsBar|anchor=manage_builds|display text=Manage Builds}} option when viewing the {{Link-SomewhereInThisManual|topic=ApplicationsBar|anchor=appprops|display text=application properties}}.
@@ Line 71: / Line 71: @@
 |anchor=pte
 |alignment=Vertical
-|structuredtext=The Parallel Test Environment enables you to use test resources instead of production ones when running an application build in a non-production stream. You can {{Link-SomewhereInThisVersion|manual=Designer|topic=ApplicationSettings|anchor=pte|display text=enable this option}} on the '''Misc''' tab in the application settings. When enabled, you can create copies of certain resources and add a special ''test_'' prefix to the resource name.
+|structuredtext=The Parallel Test Environment enables you to use test resources instead of production ones when running an application build in a non-production stream.
 Streams that are running non-production builds (DEV, QA, and UAT) will reference the PTE versions of the resources (test_''<resource name>'') instead of the ones being used in production. The LIVE build continues to reference the original production resources.
@@ Line 85: / Line 87: @@
 For example, each LIVE stream can have different contact points assigned to it, so one way you could use the LIVE and LIVE B streams is to allocate interactions coming from a certain region to a particular stream, or use the streams to balance (or gradually introduce) the number of interactions being handled by a new production build. In this way, you can implement a form of A/B testing.
 Let's say you wanted to split or balance the number of interactions being handled between the LIVE and LIVE B builds. Typically, you would gradually introduce more interactions from LIVE to LIVE B, which could be done as follows:
-*Assign '''Build X''' to the LIVE stream.
+#Assign '''Build X''' to the LIVE stream.
-*Use the '''Manage''' button to assign phone numbers to the LIVE stream. At this point, 100% of the interaction load will be handled by '''Build X''' on the LIVE stream.
+#Use the '''Manage''' button to assign phone numbers to the LIVE stream. At this point, 100% of the interaction load will be handled by '''Build X''' on the LIVE stream.
-*Now, assign '''Build X+1''' to the LIVE B stream.
+#Next, assign '''Build X+1''' to the LIVE B stream.
-*Assign some of the  phone numbers to the LIVE B stream so that 70% of the interaction load is handled by LIVE and 30% by LIVE B.
+#Assign some of the  phone numbers to the LIVE B stream so that 70% of the interaction load is handled by LIVE and 30% by LIVE B.
-*:{{NoteFormat|The {{Link-SomewhereInThisVersion|manual=Designer|topic=ApplicationsBar|anchor=transfer|display text=Transfer from Others}} button is a great way to easily and quickly move several numbers from one stream to another.|2}}
+#:{{NoteFormat|The {{Link-SomewhereInThisVersion|manual=Designer|topic=ApplicationsBar|anchor=transfer|display text=Transfer from Others}} button is a great way to easily and quickly move several numbers from one stream to another.|2}}
-*Check Designer Analytics to see if there are any issues.
+#Check Designer Analytics to see if there are any issues. If there are no issues, we can move more of the phone numbers from LIVE to LIVE B so that 30% of the interaction load is being handled by LIVE and 70% load by LIVE B.
-*If there are no issues, we can then move more of the phone numbers from LIVE to LIVE B, so that 30% of the interaction load is being handled by LIVE and 70% load by LIVE B.
+#Continue to monitor Designer Analytics for any issues. If everything still looks ok, we can move the remaining phone numbers from LIVE to LIVE B so that 100% of the interaction load is being handled by LIVE B.
-*Again, we continue to monitor Designer Analytics to see if there are any issues.
+#Assign '''Build X+2''' to the LIVE stream. This is a new build that we want to test in conjunction with '''Build X+1''' on LIVE B.
-*If everything still looks ok, we can move the remaining phone numbers from LIVE to LIVE B, so that 100% of the interaction load is being handled by LIVE B.
+#Assign some phone numbers to the LIVE stream so that 30% of the interaction load is being handled by our new application build running on LIVE and 70% by LIVE B.
-*Assign '''Build X+2''' to the LIVE stream. This is a new build that we want to test in conjunction with '''Build X+1''' on LIVE B.
+#Continue to check Designer Analytics for any issues, and adjust and balance the interaction load between the two builds as desired.
 |Status=No
 }}
 }}

@@ Line 5: / Line 5: @@
 |Context=Learn about the workflow Designer uses for developing applications.
 |ComingSoon=No
-|Platform=GenesysEngage-onpremises
+|Platform=GenesysEngage-cloud
 |Role=Administrator
 |Application=Designer

DES/Current/Designer/AppStruc - Revision history

WikiSysop at 19:43, March 30, 2022

Brian.marshall@genesys.com: Published

Ed.jamer@genesys.com: Text replacement - "{{#widget:Vimeo" to "{{Video"

Brian.marshall@genesys.com: Published

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

Brian.marshall@genesys.com: Published

Brian.marshall@genesys.com: Published

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"