Script Development Lifecycle

Content on this page is for a product or feature in controlled release (CR). If you are not part of the CR group and would like more information, contact your Account Representative.

This page is for Studio script writers. If you're a Studio administrator, see the Development Lifecycle Management help page.

Studio supports a development lifecycle for scripts. It allows your organization more control over scripts, such as limiting who can put a script into production. The lifecycle allows you to promote scripts from one stage to another. You can also copy a script from a higher stage down to a lower stage, such as when a change must be made.

Development workflows, script promotion, and using a version control system with Studio must be enabled and configured by a Studio administrator.

In software engineering, many organizations follow methodologies that use a multi-stage approach to development. In these methodologies, the software development lifecycle (SDLC) consists of stages for planning, designing, developing, testing, and deploying software changes. Following a multistage SDLC methodology helps improve the quality of the end product and streamline the development process.

Script Stages, Promotion, and Copy-Down

There are up to four development stages that a Studio administrator can enable. Each stage is associated with a folder in Studio. If you have the appropriate permissions, you can promote a script from one stage to the next. When a script is promoted, it's copied into the next stage's folder. You can also copy a script down from a higher stage to a lower one. For example, if a script is in the testing stage and you find a defect, you can copy it down to the development stage to fix it.

The default names of the stages are: 

  • Development
  • Testing
  • Pre-deployment 
  • Production

However, the names that appear in the Studio UI may be different. This is because Studio displays the name of the top-level folder assigned to each stage. If your Studio administrator calls the folder for the testing stage "test," you'll see test when you promote or copy a script down to that stage.

The ability to view, create and edit, and promote scripts to each development workflow stage is controlled by permissions. Contact your CXone Mpower or Studio administrator if you have questions about your Studio permissions.

Version Control

If your organization uses a third-party version control system with Studio, script promotion is committed to that system. You must have access to the repository to commit changes to it. If you don't have access, talk to the repository owner in your organization.

The first time you commit a change to the repository, you are prompted to enter an access token from the version control system. You can generate a token in the version control system's platform. Currently, GitHub is the only supported provider.