--- title: "Digital Process - Deploy and Preview" slug: "digital-process-deploy-and-preview" updated: 2024-11-06T16:41:23Z published: 2024-11-06T16:41:23Z canonical: "kb.easysend.io/digital-process-deploy-and-preview" --- > ## Documentation Index > Fetch the complete documentation index at: https://kb.easysend.io/llms.txt > Use this file to discover all available pages before exploring further. # Digital Process - Deploy and Preview ## Article Overview The following article provides information about deploying your digital processes. It describes the differences between a development environment and a production environment in your Builder platform. ## What is a Digital Process Deployment? Deployment is a process of publishing a digital process into a selected environment. A deployment process can be done during different stages of building a digital process, for example, the Builder platform user needs to test it for QA purposes or it is time to share the digital process with the world. ## Deploying to Different Environments (See **Figure 1**) You will usually have two types of environments that you can use to deploy a digital process: - Development (dev) - an environment for testing, QA - Production (PROD) - an environment for live deployment ![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/digital-process---deploy-and-preview-image-d1j3rf1p.png) **Figure 1: Deployment Environments** While a digital process is being built, tested, or examined internally within your organization it is mandatory to deploy it only to a dev environment. Once all QA testing is done and you are ready to publish and share the process with your external customers then deploy it to a PROD environment. Deploying a digital process to a PROD environment while it is not done and ready, or if a previous version of it is already published, can damage it. In some cases, multiple deployments to a PROD environment can result in you being financially charged by EasySend (according to your agreement). ## How To Perform a Deployment (See **Figure 2** to **Figure 7**) To deploy and view a digital process, perform the following steps: ![Click the Deploy button.](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/digital-process---deploy-and-preview-image-kw36v9vc.png) **Figure 2: Deploy Button** 1. Click the **Deploy** button (1). *Result:* A list of available environments (dev and PROD) (2) appears: ![Click the desired environment from the list.](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/digital-process---deploy-and-preview-image-nm9dg40q.png) **Figure 3: Available Environments** 1. Click the desired environment from the list (2). **NOTE: When selecting to deploy to a PROD environment, the following message will appear:** ![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/digital-process---deploy-and-preview-image-l429py9o.png) **Figure 4: Deploy To Production** *Result:* A popup window appears for a few seconds and then the deployment indicator appears (3): ![Wait until the deployment indicator disappears.](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/digital-process---deploy-and-preview-image-3ytkj1gb.png) **Figure 5: Deployment Indicator** 1. Wait until the deployment indicator (3) disappears. *Result:* The deployment is finished, and the result indicator appears (4): ![The deployment is finished, and the result indicator appears.](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/digital-process---deploy-and-preview-image-ceycky8j.png) **Figure 6: Result Indicator** ![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/digital-process---deploy-and-preview-image-jjybdpak.png) **Figure 7: Preview Button** 1. Click the **Preview** button (5). *Result:* The digital process is viewed. ### ## How do I know if a Digital Process was Deployed to a PROD Environment? (See **Figure 8**) Under the Process Manager screen, select a desired Business Group (1) or locate your digital process by using the search bar (2). Once you locate your process, check its status under In Production (3). ![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/digital-process---deploy-and-preview-image-yooxgcl4.png) **Figure 8: Process Manager Screen** ### ## Dev Vs PROD - Additional differences There are a few more additional differences between a dev and a PROD environment: - Warnings and Errors - when a deployment process encounters problems it may display warnings or error messages. Warnings do not prevent you from publishing your digital process but errors do. In some cases, a warning message that appeared while deploying to a dev environment can appear as an error message while deploying to a PROD environment. For additional information, click [here](https://kb.easysend.io/v1/docs/deploying-and-viewing-a-digital-process). - Analytics - only processes that were deployed to a PROD environment are eligible for analytics data. For additional information, click [here](https://kb.easysend.io/docs/easysend-analytics). - Bulk Sender - only processes that were deployed to a PROD environment can be used by the Bulk Sender. For additional information, click [here](https://kb.easysend.io/docs/bulk-sender). - Journey Tracker - only processes that were deployed to a PROD environment can be tracked by the Journey Tracker. For additional information, click [here](https://kb.easysend.io/docs/journey-tracker). - Reports - only processes that were deployed to a PROD environment can appear in reports. For additional information, click [here](https://kb.easysend.io/docs/analytics-and-reports). ## Production Deployment - Required Steps Once a process is ready for production deployment, perform the following steps: 1. Add metadata tagging to the Journey Sender fields (for an example, click [here](https://kb.easysend.io/docs/journey-tracker#customer-name-tagging)) - Full name - Phone number - Email address 2. Check the process link in the DEV environment - check if everything works correctly: - The validations are displayed - The flow works properly - The emails/SMS are sent as required 3. Check if the email address/phone number fields in production recipients are correct 4. Verify that the servers both DEV and Prod are up to date - if yes, continue to **step 5**. If no, perform the following: 1. Contact your EasySend rep to update the DEV environment 2. Run a second check on the DEV environment (as described in **step 2**) 3. If the process was already deployed to PROD, run a check on the PROD environment 4. Contact your EasySend rep to update the PROD environment 5. If the process or your other processes were already deployed to PROD, run a check on the PROD environment without deploying the processes 5. Start deploying all pages to production: - Validations - Services (if needed) - Theme - Journey Sender (if needed) - The process 6. Check the process in the production link NOTEWhen deploying to a production environment you immediately apply all changes to open transactions. ![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1726168756865.png) If you are deploying to a production server with version 36.4.0 or higher, you can choose whether the changes will affect live transactions. For more information, click [here](/v1/docs/deploying-and-viewing-a-digital-process#impacting-live-transactions).