Merge pull request #207 from electric-cloud/FLOWPLUGIN-8319

Rebranding from "CloudBees Flow" to "CloudBees CD".
electric-cloud · Jun 1, 2020 · f7a7a96 · f7a7a96
2 parents 8d2e471 + d1f71fa
commit f7a7a96
Show file tree

Hide file tree

Showing 61 changed files with 149 additions and 139 deletions.
diff --git a/README.md b/README.md
@@ -1,7 +1,7 @@
 EC-WebLogic
 ============
 
-The CloudBees Flow WebLogic integration
+The CloudBees CD WebLogic integration
 
 ## Compile ##
 

diff --git a/build.gradle b/build.gradle
@@ -28,7 +28,7 @@ repositories {
 
 group = "com.electriccloud"
 description = "Plugins : EC-WebLogic"
-version = "3.5.0"
+version = "3.5.1"
 
 apply plugin: 'flow-gradle-plugin'
 apply plugin: 'license'

diff --git a/help/changelog.yaml b/help/changelog.yaml
@@ -1,3 +1,5 @@
+3.5.1:
+  - Rebranding from "CloudBees Flow" to "CloudBees CD".
 3.5.0:
   - Add checking connection while creating a configuration.
   - Jobs for the successful "CreateConfiguration" and "EditConfiguration" run is now preserved.

diff --git a/help/overview.md b/help/overview.md
@@ -14,7 +14,7 @@ applications and secure.
 
 For more information about WebLogic, go to <a href="http://www.oracle.com/technetwork/middleware/weblogic/overview/index.html" target="_blank">WebLogic home page</a>.
 
-## CloudBees Flow Integration to WebLogic
+## CloudBees CD Integration to WebLogic
 
 Use this plugin to interact with the Oracle WebLogic server for application
 and server management, interacting or editing existing applications, and deploying new applications.

diff --git a/help/procedures/AddServerToCluster/postface.md b/help/procedures/AddServerToCluster/postface.md
@@ -1,9 +1,9 @@
-<p>After the job runs, you can view the results on the Job Details page in CloudBees Flow. The status of the page was checked successfully.</p>
+<p>After the job runs, you can view the results on the Job Details page in CloudBees CD. The status of the page was checked successfully.</p>
 
 <img src="../../plugins/EC-WebLogic/images/AddServerToCluster/EC-WLSAddServerToClusterStatus3.png" />
 <p>In the <b>AddServerToCluster</b> step, click the Log button to see the diagnostic information:</p>
 <br />
 <img src="../../plugins/EC-WebLogic/images/AddServerToCluster/EC-WLSAddServerToClusterStatus4.png" />
 <p>
-    <b>Note:</b> In the URL, the protocol is http. For this procedure,CloudBees Flow uses an internal method to test the status of the page URLs with the original http protocol used in the web browsers.
+    <b>Note:</b> In the URL, the protocol is http. For this procedure,CloudBees CD uses an internal method to test the status of the page URLs with the original http protocol used in the web browsers.
 </p>
diff --git a/help/procedures/AddUserToGroup/postface.md b/help/procedures/AddUserToGroup/postface.md
@@ -3,9 +3,9 @@
 
 
 <h3>Output</h3>
-<p>After the job runs, you can view the results on the Job Details page in CloudBees Flow. The status of the page was checked successfully.</p>
+<p>After the job runs, you can view the results on the Job Details page in CloudBees CD. The status of the page was checked successfully.</p>
 <img src="../../plugins/EC-WebLogic/images/AddUserToGroup/EC-WLSAddUserToGroupStatus3.png" />
 <p>In the <b>AddUserToGroup</b> step, click the Log button to see the diagnostic information:</p>
 <br />
 <img src="../../plugins/EC-WebLogic/images/AddUserToGroup/EC-WLSAddUserToGroupStatus4.png" />
-<p><b>Note:</b> In the URL, the protocol is http. For this procedure, CloudBees Flow uses an internal method to test the status of the page URLs with the original http protocol used in the web browsers.</p>
+<p><b>Note:</b> In the URL, the protocol is http. For this procedure, CloudBees CD uses an internal method to test the status of the page URLs with the original http protocol used in the web browsers.</p>
diff --git a/help/procedures/ChangeUserPassword/postface.md b/help/procedures/ChangeUserPassword/postface.md
@@ -1,9 +1,9 @@
 <img src="../../plugins/EC-WebLogic/images/ChangeUserPassword/EC-WLSChangeUserPasswordStatus2.png" />
 
 <h3>Output</h3>
-<p>After the job runs, you can view the results on the Job Details page in CloudBees Flow. The status of the page was checked successfully.</p>
+<p>After the job runs, you can view the results on the Job Details page in CloudBees CD. The status of the page was checked successfully.</p>
 <img src="../../plugins/EC-WebLogic/images/ChangeUserPassword/EC-WLSChangeUserPasswordStatus3.png" />
 <p>In the <b>ChangeUserPassword</b> step, click the Log button to see the diagnostic information:</p>
 <br />
 <img src="../../plugins/EC-WebLogic/images/ChangeUserPassword/EC-WLSChangeUserPasswordStatus4.png" />
-<p><b>Note:</b> In the URL, the protocol is http. For this procedure, CloudBees Flow uses an internal method to test the status of the page URLs with the original http protocol used in the web browsers.</p>
+<p><b>Note:</b> In the URL, the protocol is http. For this procedure, CloudBees CD uses an internal method to test the status of the page URLs with the original http protocol used in the web browsers.</p>
diff --git a/help/procedures/CheckClusterStatus/postface.md b/help/procedures/CheckClusterStatus/postface.md
@@ -1,7 +1,7 @@
 <img src="../../plugins/EC-WebLogic/images/CheckClusterStatus/EC-WLSCheckClusterStatus2.png" />
 
 <h3>Output</h3>
-<p>After the job runs, you can view the results on the Job Details page in CloudBees Flow. The status of the cluster was checked successfully.</p>
+<p>After the job runs, you can view the results on the Job Details page in CloudBees CD. The status of the cluster was checked successfully.</p>
 <img src="../../plugins/EC-WebLogic/images/CheckClusterStatus/EC-WLSCheckClusterStatus3.png" />
 <p>In the <b>CheckClusterStatus</b> step, click the Log button to see the diagnostic information:
 <br />

diff --git a/help/procedures/CheckPageStatus/postface.md b/help/procedures/CheckPageStatus/postface.md
@@ -1,10 +1,10 @@
 <img src="../../plugins/EC-WebLogic/images/CheckPageStatus/WLSCheckPageStatus2.png" />
 
-After the job runs, you can view the results on the Job Details page in CloudBees Flow. The status of the page was checked successfully.
+After the job runs, you can view the results on the Job Details page in CloudBees CD. The status of the page was checked successfully.
 
 <img src="../../plugins/EC-WebLogic/images/CheckPageStatus/EC-WLSCheckPageStatus3.png" />
 
 In the *CheckPageStatus* step, click the Log button to see the diagnostic information:
 
 <img src="../../plugins/EC-WebLogic/images/CheckPageStatus/EC-WLSCheckPageStatus4.png" />
-<p><b>Note:</b> In the URL, the protocol is http. For this procedure, CloudBees Flow uses an internal method to test the status of the page URLs with the original http protocol used in the web browsers.</p>
+<p><b>Note:</b> In the URL, the protocol is http. For this procedure, CloudBees CD uses an internal method to test the status of the page URLs with the original http protocol used in the web browsers.</p>
diff --git a/help/procedures/CheckServerStatus/postface.md b/help/procedures/CheckServerStatus/postface.md
@@ -1,7 +1,7 @@
 <img src="../../plugins/EC-WebLogic/images/CheckServerStatus/EC-WLSCheckServerStatus2.png" />
 
 <h3>Output</h3>
-<p>After the job runs, you can view the results on the Job Details page in CloudBees Flow. The status of the server was checked successfully.</p>
+<p>After the job runs, you can view the results on the Job Details page in CloudBees CD. The status of the server was checked successfully.</p>
 <img src="../../plugins/EC-WebLogic/images/CheckServerStatus/EC-WLSCheckServerStatus3.png" />
 <p>In the <b>CheckServerStatus</b> step, click the Log button to see the diagnostic information:
 <br />

diff --git a/help/procedures/ConfigureUserLockoutManager/postface.md b/help/procedures/ConfigureUserLockoutManager/postface.md
@@ -2,7 +2,7 @@
 <img src="../../plugins/EC-WebLogic/images/ConfigureUserLockoutManager/EC-WLSConfigureUserLockoutManagerStatus2.png" />
 
 <h3>Output</h3>
-<p>After the job runs, you can view the results on the Job Details page in CloudBees Flow. The status of the server was checked successfully.</p>
+<p>After the job runs, you can view the results on the Job Details page in CloudBees CD. The status of the server was checked successfully.</p>
 <img src="../../plugins/EC-WebLogic/images/ConfigureUserLockoutManager/EC-WLSConfigureUserLockoutManagerStatus3.png" />
 <p>In the <b>ConfigureUserLockoutManager</b> step, click the Log button to see the diagnostic information:
 <br />

diff --git a/help/procedures/CreateCluster/postface.md b/help/procedures/CreateCluster/postface.md
@@ -2,7 +2,7 @@
 <img src="../../plugins/EC-WebLogic/images/CreateCluster/EC-WLSCreateClusterStatus2.png" />
 
 <h3>Output</h3>
-<p>After the job runs, you can view the results on the Job Details page in CloudBees Flow. The status of the server was checked successfully.</p>
+<p>After the job runs, you can view the results on the Job Details page in CloudBees CD. The status of the server was checked successfully.</p>
 <img src="../../plugins/EC-WebLogic/images/CreateCluster/EC-WLSCreateClusterStatus3.png" />
 <p>In the <b>CreateCluster</b> step, click the Log button to see the diagnostic information:
 <br />

diff --git a/help/procedures/CreateConfiguration/preface.md b/help/procedures/CreateConfiguration/preface.md
@@ -1,4 +1,4 @@
-**After you perform the setup below it is important to make sure that the CloudBees Flow agent machine on which WebLogic runs is registered as a resource that can be pinged.**
+**After you perform the setup below it is important to make sure that the CloudBees CD agent machine on which WebLogic runs is registered as a resource that can be pinged.**
 
 <img src="../../plugins/EC-WebLogic/images/Config/EC-WLSConfig.png" />
 

diff --git a/help/procedures/CreateDatasource/postface.md b/help/procedures/CreateDatasource/postface.md
@@ -2,7 +2,7 @@
 <img src="../../plugins/EC-WebLogic/images/CreateDataSource/CreateDataSource2.png" />
 
 <h3>Output</h3>
-<p>After the job runs, you can view the results on the Job Details page in CloudBees Flow. The database was created successfully.</p>
+<p>After the job runs, you can view the results on the Job Details page in CloudBees CD. The database was created successfully.</p>
 <img src="../../plugins/EC-WebLogic/images/CreateDataSource/CreateDataSource3.png" />
 <p>In the <b>CreateDatasource</b> step, click the Log button to see the diagnostic information:
 <br />

diff --git a/help/procedures/CreateDomain/postface.md b/help/procedures/CreateDomain/postface.md
@@ -2,7 +2,7 @@
 <img src="../../plugins/EC-WebLogic/images/CreateDomain/EC-WLSCreateDomainStatus2.png" />
 
 <h3>Output</h3>
-<p>After the job runs, you can view the results on the Job Details page in CloudBees Flow. The database was created successfully.</p>
+<p>After the job runs, you can view the results on the Job Details page in CloudBees CD. The database was created successfully.</p>
 <img src="../../plugins/EC-WebLogic/images/CreateDomain/EC-WLSCreateDomainStatus3.png" />
 <p>In the <b>CreateDomain</b> step, click the Log button to see the diagnostic information:
 <br />

diff --git a/help/procedures/CreateGroup/postface.md b/help/procedures/CreateGroup/postface.md
@@ -2,7 +2,7 @@
 <img src="../../plugins/EC-WebLogic/images/CreateGroup/EC-WLSCreateGroupStatus2.png" />
 
 <h3>Output</h3>
-<p>After the job runs, you can view the results on the Job Details page in CloudBees Flow. The database was created successfully.</p>
+<p>After the job runs, you can view the results on the Job Details page in CloudBees CD. The database was created successfully.</p>
 <img src="../../plugins/EC-WebLogic/images/CreateGroup/EC-WLSCreateGroupStatus3.png" />
 <p>In the <b>CreateGroup</b> step, click the Log button to see the diagnostic information:
 <br />

diff --git a/help/procedures/CreateManagedServer/postface.md b/help/procedures/CreateManagedServer/postface.md
@@ -3,7 +3,7 @@
 
 ## Output
 
-After the job runs, you can view the results on the Job Details page in CloudBees Flow. The Managed Server was created successfully.
+After the job runs, you can view the results on the Job Details page in CloudBees CD. The Managed Server was created successfully.
 <img src="../../plugins/EC-WebLogic/images/CreateManagedServer/EC-WLSCreateManagedServer3.png" />
 
 In the <b>CreateManagedServer</b> step, click the Log button to see the diagnostic information:

diff --git a/help/procedures/CreateOrUpdateConnectionFactory/postface.md b/help/procedures/CreateOrUpdateConnectionFactory/postface.md
@@ -2,7 +2,7 @@
 
 ## Output
 
-After the job runs, you can view the results on the Job Details page in CloudBees Flow. The Connection Factory was created successfully.
+After the job runs, you can view the results on the Job Details page in CloudBees CD. The Connection Factory was created successfully.
 
 <img src="../../plugins/EC-WebLogic/images/CreateOrUpdateConnectionFactory/Summary.png" />
 

diff --git a/help/procedures/CreateOrUpdateDatasource/postface.md b/help/procedures/CreateOrUpdateDatasource/postface.md
@@ -2,7 +2,7 @@
 
 ## Output
 
-After the job runs, you can view the results on the Job Details page in CloudBees Flow. The Datasource was created successfully.
+After the job runs, you can view the results on the Job Details page in CloudBees CD. The Datasource was created successfully.
 
 <img src="../../plugins/EC-WebLogic/images/CreateOrUpdateDatasource/Summary.png" />
 

diff --git a/help/procedures/CreateOrUpdateJMSModule/postface.md b/help/procedures/CreateOrUpdateJMSModule/postface.md
@@ -2,7 +2,7 @@
 
 ## Output
 
-After the job runs, you can view the results on the Job Details page in CloudBees Flow. The JMS Module was created successfully.
+After the job runs, you can view the results on the Job Details page in CloudBees CD. The JMS Module was created successfully.
 
 <img src="../../plugins/EC-WebLogic/images/CreateOrUpdateJMSModule/Summary.png" />
 

diff --git a/help/procedures/CreateOrUpdateJMSModuleSubdeployment/postface.md b/help/procedures/CreateOrUpdateJMSModuleSubdeployment/postface.md
@@ -2,7 +2,7 @@
 
 ## Output
 
-After the job runs, you can view the results on the Job Details page in CloudBees Flow. The JMS Module Subdeployment was created successfully.
+After the job runs, you can view the results on the Job Details page in CloudBees CD. The JMS Module Subdeployment was created successfully.
 
 <img src="../../plugins/EC-WebLogic/images/CreateOrUpdateSubdeployment/Summary.png" />
 

diff --git a/help/procedures/CreateOrUpdateJMSQueue/postface.md b/help/procedures/CreateOrUpdateJMSQueue/postface.md
@@ -2,7 +2,7 @@
 
 ## Output
 
-After the job runs, you can view the results on the Job Details page in CloudBees Flow. The JMS Queue was created successfully.
+After the job runs, you can view the results on the Job Details page in CloudBees CD. The JMS Queue was created successfully.
 
 <img src="../../plugins/EC-WebLogic/images/CreateOrUpdateJMSQueue/Summary.png" />
 

diff --git a/help/procedures/CreateOrUpdateJMSServer/postface.md b/help/procedures/CreateOrUpdateJMSServer/postface.md
@@ -2,7 +2,7 @@
 
 ## Output
 
-After the job runs, you can view the results on the Job Details page in CloudBees Flow. The JMS Server was created successfully.
+After the job runs, you can view the results on the Job Details page in CloudBees CD. The JMS Server was created successfully.
 
 <img src="../../plugins/EC-WebLogic/images/CreateJMSServer/Summary.png" />
 

diff --git a/help/procedures/CreateOrUpdateJMSTopic/postface.md b/help/procedures/CreateOrUpdateJMSTopic/postface.md
@@ -2,7 +2,7 @@
 
 ## Output
 
-After the job runs, you can view the results on the Job Details page in CloudBees Flow. The JMS Topic was created successfully.
+After the job runs, you can view the results on the Job Details page in CloudBees CD. The JMS Topic was created successfully.
 
 <img src="../../plugins/EC-WebLogic/images/CreateOrUpdateJMSTopic/Summary.png" />
 

diff --git a/help/procedures/CreateTemplate/postface.md b/help/procedures/CreateTemplate/postface.md
@@ -2,7 +2,7 @@
 <img src="../../plugins/EC-WebLogic/images/CreateTemplate/EC-WLSCreateTemplateStatus2.png" />
 
 <h3>Output</h3>
-<p>After the job runs, you can view the results on the Job Details page in CloudBees Flow. The database was created successfully.</p>
+<p>After the job runs, you can view the results on the Job Details page in CloudBees CD. The database was created successfully.</p>
 <img src="../../plugins/EC-WebLogic/images/CreateTemplate/EC-WLSCreateTemplateStatus3.png" />
 <p>In the <b>CreateTemplate</b> step, click the Log button to see the diagnostic information:
 <br />

diff --git a/help/procedures/CreateUser/postface.md b/help/procedures/CreateUser/postface.md
@@ -2,7 +2,7 @@
 <img src="../../plugins/EC-WebLogic/images/CreateUser/EC-WLSCreateUserStatus2.png" />
 
 <h3>Output</h3>
-<p>After the job runs, you can view the results on the Job Details page in CloudBees Flow. The database was created successfully.</p>
+<p>After the job runs, you can view the results on the Job Details page in CloudBees CD. The database was created successfully.</p>
 <img src="../../plugins/EC-WebLogic/images/CreateUser/EC-WLSCreateUserStatus3.png" />
 <p>In the <b>CreateUser</b> step, click the Log button to see the diagnostic information:
 <br />

diff --git a/help/procedures/DeleteCluster/postface.md b/help/procedures/DeleteCluster/postface.md
@@ -2,7 +2,7 @@
 <img src="../../plugins/EC-WebLogic/images/DeleteCluster/EC-WLSDeleteClusterStatus2.png" />
 
 <h3>Output</h3>
-<p>After the job runs, you can view the results on the Job Details page in CloudBees Flow. The status of the server was checked successfully.</p>
+<p>After the job runs, you can view the results on the Job Details page in CloudBees CD. The status of the server was checked successfully.</p>
 <img src="../../plugins/EC-WebLogic/images/DeleteCluster/EC-WLSDeleteClusterStatus3.png" />
 <p>In the <b>DeleteCluster</b> step, click the Log button to see the diagnostic information:
 <br />

diff --git a/help/procedures/DeleteConnectionFactory/postface.md b/help/procedures/DeleteConnectionFactory/postface.md
@@ -3,7 +3,7 @@
 
 ## Output
 
-After the job runs, you can view the results on the Job Details page in CloudBees Flow. The Connection Factory was deleted.
+After the job runs, you can view the results on the Job Details page in CloudBees CD. The Connection Factory was deleted.
 
 <img src="../../plugins/EC-WebLogic/images/DeleteConnectionFactory/Summary.png" />
 

diff --git a/help/procedures/DeleteDatasource/postface.md b/help/procedures/DeleteDatasource/postface.md
@@ -1,7 +1,7 @@
 <img src="../../plugins/EC-WebLogic/images/DeleteDataSource/DeleteDataSource2.png" />
 
 <h3>Output</h3>
-<p>After the job runs, you can view the results on the Job Details page in CloudBees Flow. The database was deleted successfully.</p>
+<p>After the job runs, you can view the results on the Job Details page in CloudBees CD. The database was deleted successfully.</p>
 <img src="../../plugins/EC-WebLogic/images/DeleteDataSource/DeleteDataSource3.png" />
 <p>In the <b>DeleteDatasource</b> step, click the Log button to see the diagnostic information:
 <br />

diff --git a/help/procedures/DeleteGroup/postface.md b/help/procedures/DeleteGroup/postface.md
@@ -2,7 +2,7 @@
 <img src="../../plugins/EC-WebLogic/images/DeleteGroup/EC-WLSDeleteGroupStatus2.png" />
 
 <h3>Output</h3>
-<p>After the job runs, you can view the results on the Job Details page in CloudBees Flow. The database was created successfully.</p>
+<p>After the job runs, you can view the results on the Job Details page in CloudBees CD. The database was created successfully.</p>
 <img src="../../plugins/EC-WebLogic/images/DeleteGroup/EC-WLSDeleteGroupStatus3.png" />
 <p>In the <b>DeleteGroup</b> step, click the Log button to see the diagnostic information:
 <br />

diff --git a/help/procedures/DeleteJMSModule/postface.md b/help/procedures/DeleteJMSModule/postface.md
@@ -3,7 +3,7 @@
 
 ## Output
 
-After the job runs, you can view the results on the Job Details page in CloudBees Flow. The JMS Module was deleted.
+After the job runs, you can view the results on the Job Details page in CloudBees CD. The JMS Module was deleted.
 
 <img src="../../plugins/EC-WebLogic/images/DeleteJMSModule/Summary.png" />
 

diff --git a/help/procedures/DeleteJMSModuleSubdeployment/postface.md b/help/procedures/DeleteJMSModuleSubdeployment/postface.md
@@ -2,7 +2,7 @@
 
 ## Output
 
-After the job runs, you can view the results on the Job Details page in CloudBees Flow. The JMS Subdeployment was deleted.
+After the job runs, you can view the results on the Job Details page in CloudBees CD. The JMS Subdeployment was deleted.
 
 <img src="../../plugins/EC-WebLogic/images/DeleteSubdeployment/Summary.png" />
 

diff --git a/help/procedures/DeleteJMSQueue/postface.md b/help/procedures/DeleteJMSQueue/postface.md
@@ -2,7 +2,7 @@
 
 ## Output
 
-After the job runs, you can view the results on the Job Details page in CloudBees Flow. The JMS Queue was deleted.
+After the job runs, you can view the results on the Job Details page in CloudBees CD. The JMS Queue was deleted.
 
 <img src="../../plugins/EC-WebLogic/images/DeleteJMSQueue/Summary.png" />
 

diff --git a/help/procedures/DeleteJMSServer/postface.md b/help/procedures/DeleteJMSServer/postface.md
@@ -2,7 +2,7 @@
 
 ## Output
 
-After the job runs, you can view the results on the Job Details page in CloudBees Flow. The JMS Server was deleted.
+After the job runs, you can view the results on the Job Details page in CloudBees CD. The JMS Server was deleted.
 
 <img src="../../plugins/EC-WebLogic/images/DeleteJMSServer/Summary.png" />
 

diff --git a/help/procedures/DeleteJMSTopic/postface.md b/help/procedures/DeleteJMSTopic/postface.md
@@ -2,7 +2,7 @@
 
 ## Output
 
-After the job runs, you can view the results on the Job Details page in CloudBees Flow. The JMS Queue was deleted.
+After the job runs, you can view the results on the Job Details page in CloudBees CD. The JMS Queue was deleted.
 
 <img src="../../plugins/EC-WebLogic/images/DeleteJMSTopic/Summary.png" />
 

diff --git a/help/procedures/DeleteManagedServer/postface.md b/help/procedures/DeleteManagedServer/postface.md
@@ -2,7 +2,7 @@
 <img src="../../plugins/EC-WebLogic/images/DeleteMangedServer/EC-WLSDeleteManagedServer2.png" />
 
 <h3>Output</h3>
-<p>After the job runs, you can view the results on the Job Details page in CloudBees Flow. The Managed Server was deleted successfully.</p>
+<p>After the job runs, you can view the results on the Job Details page in CloudBees CD. The Managed Server was deleted successfully.</p>
 <img src="../../plugins/EC-WebLogic/images/DeleteMangedServer/EC-WLSDeleteManagedServer3.png" />
 <p>In the <b>DeleteManagedServer</b> step, click the Log button to see the diagnostic information:
 <br />

diff --git a/help/procedures/DeleteUser/postface.md b/help/procedures/DeleteUser/postface.md
@@ -2,7 +2,7 @@
 <img src="../../plugins/EC-WebLogic/images/DeleteUser/EC-WLSDeleteUserStatus2.png" />
 
 <h3>Output</h3>
-<p>After the job runs, you can view the results on the Job Details page in CloudBees Flow. The database was created successfully.</p>
+<p>After the job runs, you can view the results on the Job Details page in CloudBees CD. The database was created successfully.</p>
 <img src="../../plugins/EC-WebLogic/images/DeleteUser/EC-WLSDeleteUserStatus3.png" />
 <p>In the <b>DeleteUser</b> step, click the Log button to see the diagnostic information:
 <br />

diff --git a/help/procedures/DeployApp/postface.md b/help/procedures/DeployApp/postface.md
@@ -2,7 +2,7 @@
 <img src="../../plugins/EC-WebLogic/images/DeployApp/EC-WLSDeployApp2.png" />
 
 <h3>Output</h3>
-<p>After the job runs, you can view the results on the Job Details page in CloudBees Flow.
+<p>After the job runs, you can view the results on the Job Details page in CloudBees CD.
 The application was deployed successfully.</p>
 <img src="../../plugins/EC-WebLogic/images/DeployApp/EC-WLSDeployApp3.png" />
 <p>In the <b>DeployApp</b> step, click the Log button to see the diagnostic information:</p>