Functional enhancements in Code Pipeline version 22.01
The following table describes the major functional changes added for Code Pipeline 22.01.
Feature | Description |
|---|---|
Length of Application | In Code Pipeline 18.02, the length of the Application name field was restricted to four characters, causing difficulties in adequately describing an application. Starting with Code Pipeline 22.01, we have increased the length of this field to eight characters to allow for more descriptive names. |
SubApplication | You can now define new SubApplications (SubAppl) under each Application. You can use this new eight-character field to further break down your applications. |
Types | Starting with Code Pipeline 22.01, we have increased the length of the Type field from four characters to eight characters to allow for more descriptive type names. |
Length of Deployment Domain | You can use Deployment Domains to split the software components for a single Deployment Type and Sub-Environment into different storage names. Starting with Code Pipeline 22.01, we have increased the length of the Deployment Domain field from four characters to eight characters. |
Length of WORK REQ | You can use the WORK REQ field for many purposes, such as an associated budget, change ticket number, and so on. Starting with Code Pipeline 22.01, we have increased the length of this field from eight characters to 24 characters. |
Using the new features
After you have installed Code Pipeline 22.01, you may want to use the following new features. These are further explained in the subsequent sections in this page.
Using the longer Application name
You can now use eight characters in Application names when you create the next Application. Thus, when you go to the M.AP and M.AD panels, you can now enter up to eight characters for an Application name.
To change an existing Application name to a new longer one, you need to clone the current application to the new Application with the longer name.
Using new SubApplications
SubApplications reside under an Application. They are distinct from other SubApplications. Post upgrade to Code Pipeline 22.01, existing applications will have one SubApplication by default with the same name as Application. This will not affect your work and you can continue as you have before. However, you may want to create SubApplications in certain cases, such as:
- when you run processing for several customers, the same software but different versions. Here, you can use SubApplication for each customer.
- when you put out distinct releases of your software. Here, you can create SubApplications for each version, then maintain them under the distinct version going forward.
The new SubApplication (SubAppl) field allows up to eight characters, giving you the opportunity to have greater granularity in your application definitions.
If you want more SubApplications, you need to add them in the M.AD and M.AP panels.
You can create a new SubApplication by cloning an existing SubApplication. For more information, see Application-Clone-Utility.
Using the longer Type field
Types define processing the type of component (for example, you can use them to direct which compiler to use). They also determine how Code Pipeline processes the specified component type (for example, whether it should be generated).
The enhanced Type field allows eight characters; for example, COBC can now be COBCICS.
Using the longer Deployment Domains field
Deployment Domains provide a way to split the software components for a single Deployment Type and Sub-Environment into different storage names. Deployment Domain has expanded from four characters to eight characters.
Benefiting from the longer WORK REQ field
In Code Pipeline 18.02, the WORK REQ field was limited to eight characters. Often Trouble Ticket or Accounting numbers were longer than eight characters. This forced the use of the longer Description field. To resolve this, we have expanded the WORK REQ field to a maximum of 24 characters in Code Pipeline 22.01. This higher character limit allows more scope for use in tracking issues and free up the Description field to enable you to enter meaningful notes. Thus, you can use WORK REQ for integrations.