Set Up Development Stages with Divisions

Studio development stages allow you to set up a series stages that correspond to your organization's script development lifecycle. Script developers promote scripts through the stages during their development workflow.

This help page provides information about setting up development stages for CXone Mpower systems that use divisions Separate data securely between lines of business. Data can only be accessed from within the division it's part of.. If your system is not configured for divisions, set up the stages for organizations. You can learn about the differences between using divisions and organizations with Studio.

Divisions Page

When you click Development Workflows in Studio, the Divisions page loads. It shows a list of all divisions that have been set up in the Admin application. Divisions are displayed with nested hierarchy structure. This allows you to see the relationship between divisions so you can understand which scripts users of each division will be able to see.

This page lists the status of the divisions' configuration for development stages in Studio. Possible statuses are: 

• Not Configured: Nothing has been configured for this division.
• Configured: The script folder and at least two development stages have been configured.

• Partially Configured:  The script folder has been configured, but no stages have been set up.

• Status not Found: Status data is unavailable.

The Divisions page also shows the configured top-level script folder for each division. If a division has been configured to sync to a GitHub repository, the Repository column contains a link to it.

You can search for divisions using the search bar at the top of the page. You can use wildcard characters in your search. Search results only show divisions you have permission to view.

You cannot create divisions on this page. Divisions can only be created in the Admin application by a user with the appropriate permissions.

Root and Nested Divisions

Divisions are shown in a nested hierarchy. Click the greater-than symbol to expand the list. You can see: 

• Root Division: This is the level one (L1) division. This division contains all other divisions. The Root Division can be renamed, so the name you see in Studio may be different. You can create development stages in the Root Division and assign a GitHub repository to it, if you're using that option.

• Custom Divisions: Under the Root Division are all the custom divisions that your company has set up. Custom divisions can be nested and have levels two and three (L2 and L3). You can create development stages in the each custom division and assign unique GitHub repositories to them, if you're using that option.

Set Up Development Stages for a Division

Required Permission: ACD > Studio > Organizations & Stages >Create/Edit 

Development stages are unique to each division Separate data securely between lines of business. Data can only be accessed from within the division it's part of.. Studio allows you to enable between two and four development stages for each division. After enabling a development stage, it cannot be deleted and scripts must be promoted through that stage.

Studio has default names for each of the four possible development stages. These names do not appear in the Studio UI for script developers. Instead, script developers see the name of the folder you assign to each stage. Name the folders appropriately to correspond to each division's development workflow lifecycle terminology.

Each development stage has its own folder located in its division's top-level folder. You can name the division's top-level folder and the development stage folders. The names cannot be modified after saving.

1. In CXone Mpower, click the app selector and select Studio.
2. Click Development Workflow.
3. Click the organization you want to work with. If you cannot find a division that was just created in Admin, log out and back in again to refresh the list in Studio.
4. On the General tab, enter the name of Script Folder want this division's development stage folders to be stored in.
5. On the Workflow tab, select the checkbox next to each development stage you want this division to use.
6. For each stage, enter the name of the Stage Folder you want all scripts in that stage to be stored in.
   
7. Click Save.
8. Create the corresponding folders in Studio. For each folder you named in the preceding steps, including the division's Script Folder named on the General tab: 
   1. Create a new script.
   2. In Location, select the parent division folder where you want the folder to be created. If the parent division does not have a named folder, choose the root division's folder or the Studio root folder. You can check a division's script folder name in the Folder column on the Studio Divisions page.
   3. In Location, click Create New folder and then scroll to the top of the list.
   4. Enter the folder name exactly as you typed it in the preceding steps. Press Enter after typing the name.
   5. Ensure the new folder is selected, then click Create New folder again and enter the name of the stage. Type it exactly as you entered it when defining the stage. Press Enter after typing the name.
   6. Ensure the second new folder is selected and click Create New folder again. Enter the name of the branch folder. If you're creating folders for the development stage, this must be main. If you're creating folders for other stages, you can use any name you want. Press Enter after typing the name.
   7. Select the branch folder you created and press Enter.
   8. Ensure the new branch folder is selected in Location and then click Create.

Add or Change the Repository Assigned to Division

Required Permission: ACD > Studio > Organizations & Stages >Create/Edit 

Studio can commit script changes to a GitHub repository. You can assign a different repository to each division. Repositories are not required, so you only need to assign one to the divisions that use it. Before completing the following tasks: 

• Set up the repository in GitHub.
• Create an access token in GitHub. You may be prompted to provide your access token during these steps.

1. In CXone Mpower, click the app selector and select Studio.
2. Click Development Workflow.
3. Click the division you want to work with.
4. On the Repository tab, select the Repository Provider. Currently, the only option is GitHub.
5. Enter the Repository URL for the repository you want to associate with this organization. The URL must be a valid GitHub repository URL.
6. Click Save.

Assign Permissions to Studio Users

The ability to interact with development stage folders is controlled by permissions. Assign Studio permissions for development stages to roles for CXone Mpower users who need to access and interact with scripts.