PH20834: ENVIRONMENT TEMPLATE NOT APPLYING ENVIRONMENT "TYPE" WHEN CREATED DIRECTLY FROM "CREATE ENVIRONMENT" DIALOGUE

APAR status

• Closed as program error.

Error description

• Steps to reproduce :
  
  Step 1. Select Create Application
  Step 2. Select Application Template
  Step 3. Allow Application Template to add all Environment
  Templates associated with it.(Select PROD environment template
  in that team that also does not have environment execution
  access)
  Step 4. Application is created with all selected Environments in
  that are of Production Environment Type have the correct
  permissions â “ NO EXECUTE for Team Members due to correct type
  propagated from template.This is expected behavior.
  
  All these above steps are working fine. Only problem is below
  step.
  
  Step 6: After all the 5 steps done (After application created)
  then go to that created application and go to environments
  create new environment with using same PROD environment template
  that time you can see by default all types of team added
  automatically (production type, Dev type standard type.) because
  of that we are getting the execution access on newly created
  environment. This is the issue because when you select
  environment template , it should propagate its teams and "Types"
  to environment.
  

Local fix

• Remove the not required types and create environment with needed
  ones.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All end users on all supported browsers.                     *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Steps to reproduce :                                         *
  *                                                              *
  * Step 1. Select Create Application                            *
  * Step 2. Select Application Template                          *
  * Step 3. Allow Application Template to add all Environment    *
  * Templates associated with it.(Select PROD environment        *
  * template                                                     *
  * in that team that also does not have environment execution   *
  * access)                                                      *
  * Step 4. Application is created with all selected             *
  * Environments in                                              *
  * that are of Production Environment Type have the correct     *
  * permissions ⠓ NO EXECUTE for Team Members due to correct *
  * type                                                         *
  * propagated from template.This is expected behavior.          *
  *                                                              *
  * All these above steps are working fine. Only problem is      *
  * below                                                        *
  * step.                                                        *
  *                                                              *
  * Step 6: After all the 5 steps done (After application        *
  * created)                                                     *
  * then go to that created application and go to environments   *
  * create new environment with using same PROD environment      *
  * template                                                     *
  * that time you can see by default all types of team added     *
  * automatically (production type, Dev type standard type.)     *
  * because                                                      *
  * of that we are getting the execution access on newly created *
  * environment. This is the issue because when you select       *
  * environment template , it should propagate its teams and     *
  * "Types"                                                      *
  * to environment.                                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Fixed in version 7.1.1.1                                     *
  ****************************************************************
  

Problem conclusion

• Fix is provided in IBM UrbanCode Deploy 7.1.1.1
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  UC DEPLOY

• Fixed component ID

  5725M5400

Applicable component levels