Updating Deacom Main Application

While running the update itself has several technical steps, there are some details to consider beforehand. Also keep in mind, we strongly advise against downgrading as this can cause major data issues.

Reviewing IT considerations

The following must be taken into consideration prior to completing a Deacom update:

As of March 1^st, 2017, Microsoft .NET 4.6.2 or higher is required. Ensure .NET is up to date before running any updates.
- Note: The .NET framework for the updated build must be running on every machine running Deacom along with the server.
For customers utilizing triggers and EDI, it is suggested that a separate SQL server be setup for testing purposes. If unable to setup a different SQL environment, install from a different computer onto the server. A warning message will appear regarding triggers and everything except triggers and outbound EDI may be tested.
Confirm full testing of all functions was performed in a test environment, including EDI, triggers, scanners, integrated applications, IIS, printing, faxing, emailing, mobile, etc.

Assessing the impact of new security features

With any new build, there is a possibility of added security features. The access to these new security features is always set to "No" initially. It is important to review any new security options with a Deacom representative to ensure that business is not interrupted due to insufficient access. For a list of security features and what functions they impact, refer to the Edit User Access page. To find a list of security features that have been added to a new build, perform the following.

Navigate to System > Maintenance > User Groups.
Highlight the Deacom Admin record, click "Modify" then "Edit Access".
Double click on the "Group" column. If there are any records listed with "No", these are new security options.
Click "Set All to Yes" to provide access for this user to all security options. Repeat for other Users and User Groups as necessary.
Click "Save" to commit the changes then click "Exit".

Reviewing Externals, APIs, EDIs, and Triggers

If Externals, APIs, EDIs, or Triggers are used in the current build, there are many additional considerations and Support should be contacted prior to running an update to ensure these all work properly with the new updated version.

Process

We recommend the steps below for a successful update of Deacom. These are the nuts-and-bolts steps to actually running the update, and do not include other important steps such testing, evaluating user permissions, making changes to grids, etc. For successful results, when necessary, follow the Deacom update path.

Log out all users. The update file will not execute if there are any users logged in to Deacom or any active connections (i.e. Consoles and/or Services).
- Click the 'person' icon on the top right of the Deacom Main Menu and select the View Active Users option. If there are one or more active users listed, they must be logged out, either manually or using the Logout.exe file.
  - To manually log out a user, select the record and click "Logout User". Once complete, exit the Deacom application.
  - To use the Logout.exe file, locate it in the Deacom Production folder and run as an administrator, which will force log-out all users. If server credentials are required, it is best to use administrative server credentials.
    - Note: the logout function is integrated with the updater. If users are logged in while the update is being run, the system will display a message asking if any active users should be logged out. If "Yes" is clicked all users will be logged out and the update will continue. If "No" is clicked, the update will exit.
Close all connections (Automation, Web) to Deacom. The update file will not execute if there are active connections (i.e. Consoles and/or Services) to Deacom.
- Note: In most cases, either a Service or a Console is being used, not both. If using an Automation and/or Web Service, follow step 2.1, if using an Automation and/or Web Console, follow step 2.2.
  1. Stop all Deacom Automation and Web Services:
    1. On the Start menu, open the Control Panel, click "Administrative Tools", then click "Services".
    2. Locate the Deacom Web Services file and click "Stop the service". Repeat for Deacom Automation Services.
    3. Set the Startup Type to "Disabled" on both services to avoid the possibility of the services starting back up during the update.
  2. Stop the Deacom Consoles:
    1. Click on the console icon and exit.
The update makes changes to both the Deacom Production folder and the databases. Therefore, before running an update, it is critical that you back the Production folder and the databases up, so that you retain your environment should the update process fail.
1. Backup the Deacom Production folder by compressing or copying it to a backup directory.
  - Tip: Name and place this copy of the Production folder in a place that prevents confusion with the Production folder to be updated.
2. Backup all Company, Documents, and System databases.
  - Tip: Save these backups on a server separate from the server running Deacom
Clear out the temp directory on the server running Deacom.
1. Open RUN: Hold down the Windows button and R keys simultaneously.
2. Type %temp% and hit ENTER.
3. Hit Ctrl + A (selects all) then DELETE (deletes all). This deletes temp files for the logged-in user. If you're running as Admin, then also make sure you're deleting from Admin temp directory by logging in as admin to the machine itself.
Place a copy of the Update.exe file(s) you will be running to the server housing the Deacom Production folder
Right click on the first Update.exe file and click "Run as administrator"
When prompted by Winzip Extractor, enter the update password for that file.
Navigate to the Deacom Production folder which is mapped to the Deacom environment you intend to update. Be sure to click and select the Production folder, and not a parent or child folder of it.
Click "No" when prompted to change the SQL password. This would change the Deacom security account on the SQL server.
Click "No" when prompted to print the Change Log.
Click "OK" when prompted that the update was successful.
Reopen all connections (Consoles and/or Services) with Deacom.
- Note: Again, in most cases, either a Service or a Console is being used, not both. If using an Automation and/or Web Service, follow step 12.1, if using an Automation and/or Web Console, follow step 12.2.
  1. Start the Deacom Automation and Web Services:
    1. On the Start menu, open the Control Panel, click "Administrative Tools" then click "Services".
    2. Locate the Deacom Web Services file and click "Start the service". Repeat for Deacom Automation Services.
    3. Set the Startup Type back to "Automatic (Delayed)" on both services so they run when needed.
  2. Start the Deacom Consoles:
    1. Navigate to the Deacom Production folder.
    2. Double click on the Deacom.automation.console and/or Deacom.webserver.console executable files.
Open the Deacom application, login, and confirm access.
- If you were using any APIs, integrations, externals, or triggers, now is when you should follow supplementary update instructions from Support. These change on a case-by-case basis.

Post-Update checklist

To check the overall update of Deacom and for end users to assess any changes at their level, refer to the checklist below.

Mission critical business processes

Critical processes will be specific to the company performing the update and must be tested before performing an update. The below table is a high-level overview of some mission critical business processes that companies may wish to test prior to updating.

Category	Business Process to Test
Sales	Create a new Sales Order and validate the pricing rules and user calculations.
Sales	Ship a Sales Order. If applicable, ship a Sales Order through the Sales Calendar.
Sales	Invoice a Sales Order and validate the invoice report layout.
Sales	Receive the Sales Order payment for the transaction and validate all the GL and inventory postings for the transactions.
Sales	Create an inter-company transfer and validate the receipt of the inter-company transfer.
Purchasing	Create a new Purchase Order and validate the pricing rules.
Purchasing	Receive a Purchase Order and, if a QC test exists, validate that the inventory went into QC testing status.
Purchasing	Complete purchasing QC for a lot and validate that the inventory moves to regular inventory status.
Purchasing	Enter a vendor invoice.
Purchasing	Complete a check run and validate that the check prints correctly, process a manual check and validate that the check prints correctly. Validate all the GL postings and inventory transactions.
Inventory	Create a new formula revision.
Inventory	Adjust inventory on hand for a lot and validate the adjustment was processed correctly through a "Lots" report.
Inventory	Move inventory between locations and validate that the move was processed correctly through a "Lots" report.
Inventory	Complete the Pre-Staging and Final Staging transactions.
Production	Create a new Job and validate the custom BOM for the Job is correct. Print the batch ticket.
Production	Schedule Jobs through the Job Calendar.
Production	Issue materials to a Job and validate the inventory and GL postings associated with the transactions.
Production	Complete during production QC tests for the Job.
Production	Input production or close/relieve materials for the Job. If a post production QC group is assigned to the formulation, validate that the Lots are now in QC testing inventory status.
Production	Complete post production QC tests for the Job and verify that the inventory is now in regular inventory status.
Production	Print a COA, SDS, or other regulatory document for the completed inventory.
Accounting	Complete a journal entry.
EDI	Complete an EDI transaction and validate that the transaction is completed correctly.
WMS	Validate that the WMS successfully connects to the automation console.