Adjutant Wiki MW Pivot Skin

Overview

This guide covers the initial CID creation and basic CID Maintenance update process when creating a new CID using a MASTER CID as a template. This guide also covers the additional steps needed to update related system elements after a MASTER CID copy.

This is not a complete guide for System Manager setup. The System Manager Setup Guide should be followed to complete setting up a new CID.

Submit Request to Development

• Open a ticket (Install Adjutant Desktop) to Development to copy the MASTER CID database to the new customer server location. Include all necessary details and instructions for any special circumstances. Send an email with additional information (and copy all team members) if it is too much to fit into the ticket comments.

Verify the CID is Accessible and Create a Shortcut

• Once the ticket is complete, there should be a folder on the server named for the new customer*, with an RDP Desktop shortcut to the new installation. If there is no shortcut available, navigate to the customers folder in the RDP C:\ drive. From the Adjutant sub-folder in the customer’s folder, create a shortcut to the ‘AdjLoaderV9.exe’ file. Copy that shortcut to the RDP Desktop and rename it accordingly.

* For Non-Hosted installations, the Adjutant folder will generally be under an ‘Apps’ folder on one of the server resources. There should still be a C:\ drive location. Confirm with Development which network location the Adjutant software is installed under.

* If you create the shortcut from the C:\ drive location, you don’t get the security warnings that you get if the shortcut points to the network drive location.

Create the New CID Record

• From CID Maintenance, Add the CID details for the new customer. The ‘CID’ value sets the CID name. Saving the record will prompt a ‘Copy Settings From’ screen.

• You will not be able to fill in the MASTER ENT value until after you create the new CID and the new MASTER ENT record.

• Select the following records in the ‘Copy Settings from’ screen and press ‘Copy’. A series of processes will run to create the new CID. Do not interrupt these processes. It usually only takes a minute for hosted customers.
  • Fiscal Calendar
  • System Rules
  • CID Defaults and Setup Options
  • User Security Tokens

• Exit Adjutant and log back in to access the newly created CID.

Update the CSTRING.TXT File

• Locate the CSTRING.TXT file in the Adjutant folder and edit the CID name to match your new CID. This file determines which security method (New vs. Old) is used, among other things.

Create the Master ENT Organization

• Set the CID drop-down to the new customer, and create an Organization for the new company. Match the Organization ID to the CID. Assign the following attributes:
  • Bill To / Ship To / Sold To
  • Inventory Owner
  • Remit To / Sold From

Complete the Initial CID Basic Setup

Complete the following setup items in CID Maintenance.

Update Master ENT

• Update the 'Master ENT' value in CID Maintenance to the newly created Org ID from the previous step.

Set the GL Mask

• The GL Mask in the CID Maintenance - Accounts tab must be updated via SQL with the following QRY
  • Update CID set GLMASK = 'X-XXXX-XX' where CID = 'AAAA' (Set the GL Mask to the desired format using X and – characters. Replace ‘AAAA’ with actual CID)

Complete the GL Accounts / Warehouse / Held For Setup

In order to proceed with the next steps, you must add at least one GL account and a default Warehouse. Ideally, you should import the full chart of accounts at this step. However, If the complete chart of accounts is not available at this point, you can use a temporary GL account that will have to be replaced later.

• Once you have a chart of accounts, or at least one active GL account, add the default Warehouse record.

• The default Warehouse name should match the CID name. In most cases, the ‘Default Location’, ‘Active’, and ‘Production Plant’ checkboxes should be checked. You must complete the blank GL accounts in the ‘Account’ tab in order to save the record. The add process will create a new Organization with a ‘Warehouse Location’ attribute.
• Note - Do not check the "Distribution Whse' box unless you know how it is used. It will prevent the Warehouse from being used in Order Entry.

• Update the ‘Item Held For Codes (HOLDER) Rule Maintenance record to replace the entry for MASTER with the new customer name and vendor number.

Update the DROPFOLDERS Rule

The DROPFOLDERS rule will have the file path from the MASTER CID. Each rule detail record will need to be updated with the correct file path for the new installation.

All file paths should be entered with the full UNC path. Certain Inbox reader functions require the UNC path, rather than just the drive letter and folder structure.

• Follow the procedure outlined below (or perform 30 individual edits to paste the right path prefix into each rule detail)

• In SQL, run the following query to show the RHYKEYNO and the rule details associate with the DROPFOLDERS rule for the new CID. Replace the AAAA value in the query with the new CID name.
  • Select rhkeyno, keyno, text2 from rd where rhkeyno in (select keyno from rh where name = 'dropfolders' and cid = 'AAAA')

• All rule detail records from the SQL query above should have the same same RHEYNO value, which is the keyno value of the DROPFOLDERS rule header record that you will need to replace in the next query.
• All rule detail records should have '\\948121-APP01\ABIS\MASTER' in the TEXT2 field in front of the '\DROPFOLDERS\ . . .' path details. This is the base file path that you will need to replace in the next query. You will also need the new UNC file path that will replace the MASTER base file path.

• In SQL, run the query below to perform a find/replace on the file path in the TEXT2 field. Replace 'master file path' with '\\948121-APP01\ABIS\MASTER' from the query above. Replace 'new file path' with the new CID's base file path. Replace the '####' RHKEYNO value with the RHKEYNO shown from the query above. The single quotes around 'master file path' and 'new file path' are part of the query format and must be there.
  • Update rd set text2 = replace(text2,'master file path','new file path') where rhkeyno = ####
    • An example query would look like - Update rd set text2 = replace(text2,'\\948121-APP01\ABIS\MASTER','\\SERVER1234-APP\APPS\ADJ\STEELMAX') where rhkeyno = 2999

• You can re-run the first query above to confirm that the replace worked as expected. If there are any issues, adjust the second query as needed to replace the base/new file path text with the desired details. You can test that the DROPFOLDERS path is working by trying to access the Document Vault from an Adjutant organization record and checking the 'Open in Root Folder' button.

Fix the ABIS _ADMIN record

The hard-coded _ADMIN (or BACKDOOR) security record relies on a Contact record in the primary CID that has a USERID of '_ADMIN'. In order for this record to work properly, it needs to either be repointed to a Contact record in the new CID, or it needs to be recreated entirely.

• Option 1 – Point the existing ‘_ADMIN’ record from the copied MASTER CID to a new Contact record that you create in the new CID (retains all security overrides from MASTER)
  • Add an ‘Abis Admin’ Contact record and add the ‘User in Adjutant’ attribute, but click on the X to close the User in Adjutant screen without saving it.
    • Set the 'Email Address' value to your abiscorp.com address. This will be used throughout the implementation for the from address on system emails.
  • In SQL, look up the Contact record you just added for 'Abis Admin' and make a note of the CONTID in the VCONTACT table.
  • In SQL, find the KEYNO value for the existing '_ADMIN' Userid in the USERID table. This is the record that needs to get updated in the next step to link to the new 'Abis Admin' Contact record.
  • In SQL, run the QRY below and replace the CONTID value with the CONTID for the 'Abis Admin' record that you got from the VCONATCT table, and replace the KEYNO with the KEYNO from the '_ADMIN' Userid record in previous step:
    • update userid set contid = ##### where keyno = ###
  • Exit Adjutant and log back in, and clicking on the Contact button should display your Abis Admin contact.
  • Edit the User in Adjutant record to set the Default CID and Default WHSE values for you new CID.
  • Also in the User in Adjutant record, remove the SMTP settings or reset them to use the customer's email settings.
    • The abiscorp.com email settings should not be left in place or copied to other user records.

• Option 2 – Delete the ‘_ADMIN’ UserID and recreate it
  • In SQL, delete the entire USERID table (it should only contain _ADMIN and any test records from the MASTER CID at this point)
  • Add an ‘Abis Admin’ contact record and assign the ‘User in Adjutant’ attribute.
  • Set the UserID to ‘_ADMIN’ and set the Password to ‘XXXX’ (the password doesn’t matter, it is set elsewhere).
  • Clear the ‘Active User’ flag and any other ‘Named User’ flags. Set the default CID and WHSE fields, as well as any other settings appropriately.
  • Also in the User in Adjutant record, remove the SMTP settings or reset them to use the customer's email settings.
    • The abiscorp.com email settings should not be left in place or copied to other user records.
  • Exit Adjutant and log back in, and clicking on the Contact button should display your Abis Admin contact.

Fix Nite Inventory Emails and Overall Email Settings

• The Inventory vs GL Dump Accounts (INVDUMP) rule copied from MASTER contains an email setting that either needs to be updated or deleted.
  • Update the MASTER SysAdmin's email setting (currently fdonovan@abiscorp.com) to your email address to get the 'Night GL vs Inv Summary' reports to your email. This can be changed to the customer's email as the implementation progresses.
  • Alternatively, delete the rule detail for the email setting. This will prevent anyone from receiving the nightly email. This can be added back with a customer email address later.

• Verify that the 'Abis Admin' Contact record is set with your abiscorp.com email address (or a designated team member on the implementation) for the duration of the implementation. The email linked to the _ADMIN Contact record is used as the from address for several system emails. This can be set to the customer's email address for a Systems Administrator once they are in place.

• The poptext.txt and inboxtext.txt files that were copied from MASTER still have abiscorp.com settings and passwords. These should either to be set to the customer's desired email server settings, or they should be fixed so that emails are not being accidentally routed through abiscorp servers inappropriately.
  • Copies of these files named 'poptext - copy' and 'inboxtext - copy' should exist in the copied Adjutant folder. The text in these files has been updated to replace all of the abiscorp settings and passwords. These files can be renamed or their data can be copied and pasted to the respective poptext and inboxtext files until the customer provides the correct email settings for their system.
  • Alternatively, you can adjust any references in the poptext and inboxtext file that refer to abiscorp.com, as well as any password text so that the settings will not work.

• Once these email settings are updated, use the Server Tools utility to restart ALL running services for the new CID. The services pull the system email settings from the _ADMIN Contact at startup, so they must be restarted to pull any changes made to the _ADMIN record.

Move Email Templates to the New CID

Email Templates are currently not copied in the CID Copy process. They should all exist in the EMAILSETTING SQL table under the MASTER CID.

• Run the following SQL QRY to ‘move’ the MASTER Email Templates to the new CID:
  • update emailsetting set CID = 'AAAA'

Update Form and Report Filenames With the New CID

The MASTER customized forms and reports should all exist under the Adjutant main folder with ‘MASTER’ in the form name. These will need to be renamed in order to default as the Default Custom form in each application's Message Control screen.

Option 1 - Use PowerShell to replace the CID (MASTER) value on all file names

• Launch Windows PowerShell from the RDP Start menu.
• Type 'X:' (where X is the root drive letter of the Adjutant folder on the RDP server) and hit Enter to access the root folder. Or you can use 'CD\' and hit Enter.
• Change to the desired CID's Adjutant directory, one folder at a time with the 'CD XXXX' command. If PowerShell lets you change directly to a subfolder, can't figure it out.
  • Type 'CD CID' then Enter (Replace CID with your customer's CID folder name, or first-level folder name)
  • Type 'CD ADJUTANT' then Enter (If they are using something other than 'ADJUTANT' as their main folder, replace with their main folder name)
  • For example, to access the live Adjutant folder in 'X:\Resource\Apps\LiveAdj\', you would do that in 3 steps - 'CD RESOURCE', then 'CD APPS', then 'CD LIVEADJ'.
  • The 'DIR' command will list all folders and files in the selected directory.

• Copy the expression below and paste into the PowerShell cursor to rename all FRX files. IMPORTANT - replace the text 'newcid' with your customer's CID name

Get-ChildItem -Filter "*master.frx" | Rename-Item -NewName {$_.name -replace 'master.frx', 'newcid.frx'}

• Copy the expression below and paste into the PowerShell cursor to rename all FRT files. IMPORTANT - replace the text 'newcid' with your customer's CID name

Get-ChildItem -Filter "*master.frt" | Rename-Item -NewName {$_.name -replace 'master.frt', 'newcid.frt'}

Type 'EXIT' and then Enter to close PowerShell.

Option 2 - Use File Explorer to individually replace the CID (MASTER) value in each file name

• The FRT/FRX filenames can be renamed in File Explorer to replace ‘MASTER’ with the new CID name.
  • Set the view mode to detail, and set the search options to exclude subfolders.
  • Navigate to the customer's Adjutant folder.
  • Use the folder search tool and search for *MASTER.FR* to return a list of all files with MASTER in the file name. There may be more than just form files here.
  • Highlight each file, then single-click on the file name to edit the file name. Replace MASTER with the new CID. Do not change any other file name details. TIP – the arrow keys and TAB key will navigate you through each file and keep you in edit mode.
  • These do not all have to be changed at this time. They can be updated as setup proceeds in each module.

Update the Forms Logo File

All MASTER forms are set to use the generic logo file names listed below. Saving the customer's logo in the Adjutant folder with the correct name will automatically pull to each form.

• Replace the default logo files with customer logo files.
  • Save the customer logo in the Adjutant folder as three files:
    • LOGO_SM.BMP (small logo that should not be scaled up)
    • LOGO_MD.BMP (default logo, average size/quality that should scale well on most forms)
    • LOGO_LG.BMP (large logo, only used for custom forms with large logo)
      • The existing files with these names can be deleted or renamed.
  • After changing the logo files, you will need to exit and log back in to see any updates.

Delete the MASTER CID records

The MASTER CID can be deleted at any time after the steps above are complete, but MUST be deleted before customers begin accessing the system.

• MAKE ABSOLUTELY SURE you are in the right RDP and Environment before proceeding.

The functions in this screen rely on a special DBF file named CIDFLIST.DBF that should exist in the root Adjutant folder. The CIDFLIST DBF file contains the up-to-date datatables that are processed/checked/updated during the various functions for this screen. Since new database tables are added from time to time, it is best practice to obtain an updated CIDFLIST.DBF file before using this screen for any customer data.

• From the new CID, run Delete/Change CID, set the CID to MASTER and select ‘Delete CID’ then Process.

• You will see a series of warnings. If you are in the correct environment, proceed.
• Once that completes, run the ‘Remove Orphan Data’ option and Process.

Continue to the System Manager Setup Guide

At this point, the CID should be basically functional, and you can continue with setting up remaining CID Maintenance items and other applications.

http://www.abiscorp.com/faq/index.php?title=System_Manager_Setup_Guide