# Writing Sample #3

**Note:** I intentionally reduced the screen captures since the content is proprietary.

### How to Deploy an Application with Dependencies in OnTime <a href="#writingsample-3-howtodeployanapplicationwithdependenciesinontime" id="writingsample-3-howtodeployanapplicationwithdependenciesinontime"></a>

The OnTime admin console provides tools for staging software applications, monitoring their performance, and managing permissions.&#x20;

When you are ready to stage an application, OnTime performs an automated dependency analysis across environments. The analysis ensures that staging will not impact the applications already running on the destination environment.&#x20;

To deploy an application that depends on other applications to work correctly, you must deploy *all* the applications in the *same* environment. If there are conflicts between applications, OnTime helps you quickly resolve them. This scenario demonstrates how to resolve a conflict between applications within the OnTime console.&#x20;

In this scenario, the **Customer Portal** application will be deployed to the **Quality Assurance** application for testing. However, the Customer Portal application depends on the **Cases** and **CRM Services** applications, also deployed on **Quality Assurance**.

#### Develop and Deploy Cases and CRM Services <a href="#writingsample-3-developanddeploycasesandcrmservices" id="writingsample-3-developanddeploycasesandcrmservices"></a>

The Customer Portal application reuses business logic from the Cases and CRM Services applications. To ensure the stability of all applications, first, deploy the Cases and CRM Services to Quality Assurance for testing.

![001](https://phillipcwilkerson.files.wordpress.com/2021/06/001.png?w=1100)

#### Deploy Customer Portal <a href="#writingsample-3-deploycustomerportal" id="writingsample-3-deploycustomerportal"></a>

After completing a development milestone, you can deploy the Customer Portal application to the Quality Assurance application for testing. Enhancements to the CRM Services application include new business logic that complements reuse by Customer Portal.

In this scenario, however, when you validate the plan for deploying Customer Portal to Quality Assurance, OnTime detects that Customer Portal cannot be deployed without *also* deploying the latest version of the CRM Services application. The result is that both applications become red, and continuing the deployment is not possible.

![002](https://phillipcwilkerson.files.wordpress.com/2021/06/002.png?w=1100)

#### Understand the Dependencies <a href="#writingsample-3-understandthedependencies" id="writingsample-3-understandthedependencies"></a>

Click the red error message near Customer Portal to understand and resolve the dependencies conflict.&#x20;

![003](https://phillipcwilkerson.files.wordpress.com/2021/06/003.png?w=1100)

The warning means that deploying the **0.3+** version of Customer Portal will make the application unstable in the Quality Assurance application. This happens because Customer Portal is incompatible with the CRM Services application currently deployed on Quality Assurance.

Click the Show Details link for more details about why Customer Portal is incompatible.&#x20;

Review the details, then click the red **Error** icon. The Customer Portal module depends on the Customers module from the CRM Services Application. Specifically, Customer Portal depends on the **Customer\_Details** action, which is unavailable on the version of CRM Services currently deployed on Quality Assurance.&#x20;

#### Resolve the Dependencies <a href="#writingsample-3-resolvethedependencies" id="writingsample-3-resolvethedependencies"></a>

The latest version of CRM Services exposes the **Customer\_Details** action as public. The solution is deploying the new CRM Services version to Quality Assurance. To reset the deployment option for CRM Services, follow these steps:&#x20;

1. Select and click **Tag & Deploy 1.4** on the CRM Services application.

![004](https://phillipcwilkerson.files.wordpress.com/2021/06/004.png?w=1100)

1. Click

**Validate Now** to validate the dependencies again.&#x20;

1. the dependency conflict is resolved this time, so the deployment button changes to green.&#x20;
2. Click

**Continue** to review the deployment plan.

#### Deploy to Quality Assurance  <a href="#writingsample-3-deploytoqualityassurance" id="writingsample-3-deploytoqualityassurance"></a>

Since Cases, Mobile Sales, and Sales depend on the applications you are deploying to Quality Assurance, OnTime verifies them to be re-deployed.&#x20;

![005](https://phillipcwilkerson.files.wordpress.com/2021/06/005.png?w=1100)

No changes are made to these applications. They have just been recompiled and deployed to use the new CRM Services and Customer Portal versions. &#x20;

You can uncheck the applications listed on the right so they are not redeployed. This makes the deployment faster, but those applications will continue using outdated references and may cause unexpected behaviors.

Review the deployment plan, add some notes, and click **Deploy Now**.

| ℹ️   You can redeploy only those applications to which you have permission. |
| --------------------------------------------------------------------------- |

The latest version of Customer Portal and CRM Services are deployed to Quality Assurance. The Cases, Mobile Sales, and Sales applications are redeployed in Quality Assurance, ensuring all applications work correctly.&#x20;

***


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://suntracer2030.gitbook.io/phillip-wilkerson-technical-writing-portfolio/writing-sample-3.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
