Adjutant Wiki - User contributions [en]

MASTER CID Copy Guide

2025-05-05T17:49:30Z

LNICOLOSI:

== 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.

*Create the '6.4.4 Install Adj 2020' task on the 1st of the month after the Needs Analysis is complete because when that task is completed it fires a route to start recurring monthly invoices for licensing.

== 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.

:: <nowiki>*</nowiki> 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.

:: <nowiki>*</nowiki> 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

[[File:Copy CID.png]]

*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.

[[File:CSTRING.png]]

== 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.

[[File:Warehouse1.png]]

[[File:Warehouse2.png]]

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

===Delete Unwanted Fiscal Calendar Header Records (FISCALH)===

Data copied from MASTER will have many years of fiscal calendar details that clients do not need loaded. These fiscal calendars are copied in the first step to create the new CID. They can either be deleted before that first step, or any time after the new CID is created. The fiscal calendars must be deleted via SQL and should be reviewed carefully before deciding which years will be needed for the customer.

Review the calendars that exist in the FISCALH SQL table. Fiscal Calendar header records are saved by CID and Fiscal Year. Delete any KEYNO records in this table that will not be needed for the new customer. A good rule of thumb is that you can delete all but the current and prior year in the new CID.

The FISCALD SQL table contains the individual months/periods for each KEYNO listed in the FISCALH table. These records can be left in place and should not affect anything once the FISCALH KEYNO value is deleted.

== 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.

'''NOTE - DO NOT set the Active User flag for the ABIS _ADMIN record. By design, the _ADMIN user should not use a customer license. Flagging the Active User field will prevent the _ADMIN user record from working and will exhibit all types of problematic behavior until you clear the Active User flag.'''

*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.

* Update the email setting (text2) in the AUTOBATCH rule to either remove fdonovan@abiscorp.com or update it to a customer or Strategist email address.

* 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 & Update ==

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 where 'AAAA' is the new CID:
** '''update emailsetting set CID = 'AAAA' where CID = 'MASTER''''
** Note that there are database entries for MASTER and JONESCO. The above query should prevent duplicate template records from getting created for the multiple CIDs in MASTER data.
*Review and update the Email Templates Subject lines and update these to the new customer's name. Replace references to MASTER CID with the customer in all templates.

== 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', 'NEWCID'}'''

*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', 'NEWCID'}'''

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.

[[File:RenameFile2.png]]

== Update the Forms Logo File ==

'''Desktop Process'''

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.

'''Adjutant 20/20 Process'''

Email the company logo file to Development so they can place the file in the /images folder on the customer's web server.

* Generally, the file name should be ''reportlogo.png'', but there may be execptions.

== 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.

[[File:Delete CID.png]]

*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.

==Verify the Licensed User Counts==

Review the License Status screen for the new CID and confirm that the values in the License column match the number of licensed users on the contract.

If the Desktop Login screen, the License Status screen, or the License Update screen still show '''Registered To: MASTERCID''', send a request to Development to update the license file for the new CID. Do not update any license counts until the CID shows as registered to the correct customer.

If the counts do not match the customer's contracted license counts, update them to match the contract. If any changes are made to the license counts, email your supervisor and copy Karen Egan with details on the changes you made.

[[File:LicenseStatus.png]]

If there are any discrepancies, notify your supervisor.

== 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

[[Category:Setup Guides]]

[[Category:System Manager]]

MASTER CID Copy Guide

2025-05-05T17:47:19Z

LNICOLOSI:

== 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.

*Create the '6.4.4 Install Adj 2020' task on the 1st of the month after the Needs Analysis is complete because when that task is completed it fires a route to start recurring monthly invoices for licensing.

== 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.

:: <nowiki>*</nowiki> 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.

:: <nowiki>*</nowiki> 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

[[File:Copy CID.png]]

*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.

[[File:CSTRING.png]]

== 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.

[[File:Warehouse1.png]]

[[File:Warehouse2.png]]

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

===Delete Unwanted Fiscal Calendar Header Records (FISCALH)===

Data copied from MASTER will have many years of fiscal calendar details that clients do not need loaded. These fiscal calendars are copied in the first step to create the new CID. They can either be deleted before that first step, or any time after the new CID is created. The fiscal calendars must be deleted via SQL and should be reviewed carefully before deciding which years will be needed for the customer.

Review the calendars that exist in the FISCALH SQL table. Fiscal Calendar header records are saved by CID and Fiscal Year. Delete any KEYNO records in this table that will not be needed for the new customer. A good rule of thumb is that you can delete all but the current and prior year in the new CID.

The FISCALD SQL table contains the individual months/periods for each KEYNO listed in the FISCALH table. These records can be left in place and should not affect anything once the FISCALH KEYNO value is deleted.

== 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.

'''NOTE - DO NOT set the Active User flag for the ABIS _ADMIN record. By design, the _ADMIN user should not use a customer license. Flagging the Active User field will prevent the _ADMIN user record from working and will exhibit all types of problematic behavior until you clear the Active User flag.'''

*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.

* Update the email setting (text2) in the AUTOBATCH rule to either remove fdonovan@abiscorp.com or update it to a customer or Strategist email address.

* 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 & Update ==

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 where 'AAAA' is the new CID:
** '''update emailsetting set CID = 'AAAA' where CID = 'MASTER''''
** Note that there are database entries for MASTER and JONESCO. The above query should prevent duplicate template records from getting created for the multiple CIDs in MASTER data.
*Review and update the Email Templates Subject lines and update these to the new customer's name. Replace references to MASTER CID with the customer in all templates.

== 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', 'NEWCID'}'''

*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.

[[File:RenameFile2.png]]

== Update the Forms Logo File ==

'''Desktop Process'''

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.

'''Adjutant 20/20 Process'''

Email the company logo file to Development so they can place the file in the /images folder on the customer's web server.

* Generally, the file name should be ''reportlogo.png'', but there may be execptions.

== 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.

[[File:Delete CID.png]]

*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.

==Verify the Licensed User Counts==

Review the License Status screen for the new CID and confirm that the values in the License column match the number of licensed users on the contract.

If the Desktop Login screen, the License Status screen, or the License Update screen still show '''Registered To: MASTERCID''', send a request to Development to update the license file for the new CID. Do not update any license counts until the CID shows as registered to the correct customer.

If the counts do not match the customer's contracted license counts, update them to match the contract. If any changes are made to the license counts, email your supervisor and copy Karen Egan with details on the changes you made.

[[File:LicenseStatus.png]]

If there are any discrepancies, notify your supervisor.

== 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

[[Category:Setup Guides]]

[[Category:System Manager]]

System Manager Setup Guide

2025-04-03T19:17:10Z

LNICOLOSI: /* Hosted vs. Non-Hosted Installations */

==General Information==

This guide covers the initial setup and configuration of a new customer CID. Following this guide will ensure that the base system features are set up completely. There may be additional system-level setup and configuration activities for optional features and integrations that are required beyond this guide.

===Hosted vs. Non-Hosted Installations===

'''Hosted Installations'''

A hosted CID installation means that the database and folder structure exist on ABIS’s controlled Rackspace network environment. Development has all the administrative rights to manage files, databases, processes, user access, and more.

*For hosted customers, Development will generally determine which server is used.
*When creating the ‘Install Adjutant Desktop’ ticket for Development to create the CID and database structure, indicate the CID name (used for SQL and ODBC) and which MASTER CID should be used to create the installation.

*Create the '6.4.4 Install Adj 2020' task on the 1st of the month after the Needs Analysis is complete because when that task is completed it fires a route to start recurring monthly invoices for licensing.

'''Non-Hosted Installations'''

A non-hosted installation is one that exists on customer-controlled server resources. Non-hosted installations require more information gathering and generally require more communication to secure the necessary network rights and privileges to assist setting up the installation.

Coordinate closely with the customer and ABIS Development on who will be responsible for the initial installation.
* Customers with a strong IT department may want to complete the process themselves.
* Some customers want ABIS to complete the process and ‘hand over the keys’ once it is complete.

ABIS will need the following from the customer’s server (at a minimum)
* IT-Level contact with adequate server administration rights
* Server IP address and access credentials

The following resource documents, available on the FTP Implementation folder, should be shared with customers that are completing their own Adjutant installation
* Adjutant Requirements (reference of minimum standards for server and SQL versions)
* Adjutant Install Notes (high-level checklist of server and workstation setup steps)
* Adjutant ODBC Datasource Setup (step-by-step checklist for setting up the SQL/ODBC connections)

Coordinate the Adjutant installation and remote access privileges with the customer and ABIS Development resources as needed. We will need solid, reliable access to the customer's server for setup and support in the form of a dedicated, licensed RDP account, or a dedicated VPN account for remote access. We should not allow any remote access solutions that are temporary, unlicensed, free-ware, trial periods, shared remote connections that may be unavailable because someone logged out for the day, or anything that requires us to pretend we are students. Escalate to your supervisor immediately if the customer is unable to provide secure, licensed remote access to their server.

The process and flow of non-hosted installations varies greatly from one to the next. Once you have a reliable connection and Adjutant is running without database errors, you can proceed with setup.

*Create the '6.4.4 Install Adj 2020' task on the 1st of the month after the Needs Analysis is complete because when that task is completed it fires a route to start recurring monthly invoices for licensing.

===Notes on CID Initial Setup (Copied from MASTER vs. other methods)===

*All new CIDs should be created by copying from a MASTER CID setup.

*Refer to the MASTER CID Copy Guide page to complete the initial CID setup by copying and modifying the MASTER CID database elements.
http://www.abiscorp.com/faq/index.php?title=MASTER_CID_Copy_Guide
* There are some overlapping steps between the MASTER CID Copy guide and this guide. Setup steps that have additional or different details will reference the MASTER CID Copy guide with (See MASTER).
* For installations that are not going to be copied from a MASTER CID, installation details such as setup option settings, rule maintenance records, and other setting will vary depending on how the installation was created. Ask another consultant or your supervisor if there are any setup issues that seem unusual.

==Verify the Licensed User Counts==

Review the License Status screen for the new CID and confirm that the values in the License column match the number of licensed users on the contract.

If the Desktop Login screen, the License Status screen, or the License Update screen still show '''Registered To: MASTERCID''', send a request to Development to update the license file for the new CID. Do not update any license counts until the CID shows as registered to the correct customer.

If the counts do not match the customer's contracted license counts, update them to match the contract. If any changes are made to the license counts, email your supervisor and copy Karen Egan with details on the changes you made.

[[File:LicenseStatus.png]]

If there are any discrepancies, notify your supervisor.

==Verify/Update the CSTRING.TXT File==

The CSTRING.TXT file is found in the main Adjutant folder. This file holds information essential to the databases. Development generally sets the correct information at CID creation. If there are any questions about editing this file, consult your supervisor.

*Verify that the CID name in the file matches your CID.

[[File:CSTRING.png]]

==CID Initial Setup==

===Set the Adjutant Desktop Background Image===

*To set the background image for the CID, place a .BMP or .JPG file of the customer logo in the main Adjutant folder with the filename matching the CID name. For example, if the new CID is 'STEEL', the file should be named STEEL.BMP (or JPG).
*Exit Adjutant and log back in to display the image.

===Update the CID Maintenance – Master Tab Details (See MASTER)===

*Update the CID Company Name, Address, Phone, Email, and TaxID (if available) details.

*Update the ‘Master ENT’ value with the Organization ID that matches the CID name, or verify that the Organization record has the correct details and all of the following attributes.
**Bill To / Ship To / Sold To
**Remit To / Sold From
**Inventory Owner

===Set the CID GL Mask (See MASTER)===

*If the GL Mask field in the CID Maintenance – Accounts tab is open for editing, set the GL Mask value to match the customer’s GL account structure, using X and - characters.

*Generally, the GL Mask in the ‘Accounts’ tab must be updated via SQL with the following query
**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)

===Import the GL Chart of Accounts (See MASTER)===

In order to proceed with the CID Setup, the GL chart of accounts (or at least a single GL account) must be set up. If the complete chart of accounts is not available at this point, you can add a suspense GL account manually in the ‘GL Accounts’ screen that will be used to fill in required GL setup fields.

*Keep in mind that any setup fields pointed to the temporary suspense account will have to be reviewed and corrected once the complete chart of accounts has been set up.

*The GL Chart of Accounts import template can be found in the \Data Files\Accounting folder of the Adjutant directory (if copied from MASTER), or a copy can be found in the Implementation Files folder on the FTP.

*Import the customer’s complete chart of accounts using the ‘Chart of Accounts Import’ screen.

*Verify that the imported GL Accounts exist and are correct in the ‘GL Accounts’ screen.

=== Set Up the Default Warehouse / Held For Records (See MASTER)===

In order to proceed with the next steps, you must have added at least one GL account and a default Warehouse.
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.
*'''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.
*The add process will create a new Organization with a ‘Warehouse Location’ attribute.
*You must complete the blank GL accounts in the ‘Account’ tab in order to save the record.

[[File:Warehouse1.png]]

[[File:Warehouse2.png]]

*Update the ‘Item Held For Codes’ (HOLDER) Rule Maintenance record with the new customer name and vendor number.

==Review/Update/Complete all CID Maintenance Screens==

===CID Maintenance – Paths / Remote Transfer Tab===

This screen sets the destination path for several system level functions. Generally all values in this screen should have the same base folder structure tied to the Adjutant working folder.

*Confirm that each file path matches the customer’s file structure. If not, update as needed.
*Not all file paths are used. Generally, the first six fields are used.
*If these folders are not accessible, Adjutant will display a warning message at login.
*The 'Mail Link' path should contain the full UNC path info (rather than just a drive letter) because mail service functions require the full server path.

===CID Maintenance – Accounting Backend Tab===

This screen is used to integrate with third-party accounting and payroll systems, which is rare for new installations. Consult with development for the correct entries in this screen if you are setting up an interface.

*Otherwise, update the following fields as indicated:
**Name should be set to ‘None’
**Backend Type should be set to ‘Foxpro/None’
**Posting Window should be set to an appropriate date range for the current year (and beyond if desired)
***Note – these fields must be updated annually if they are set to a year at a time
**Default Costing Method should be set to the customer’s desired method (SI-AVG is generally best practice)

===CID Maintenance – Map/Password Info Tab===

This screen controls the default password settings that are established for new user records. It also controls the internet mapping details for certain applications (not common).

*Review and update the Password Settings fields to match the customer’s requests.

===CID Maintenance – Defaults Tab===

This screen controls default entries for various applications in Adjutant, in addition to setting the background color for the CID Desktop.
The system default entries, or entries copied from MASTER CID, are generally acceptable to begin an installation, and can be adjusted later during individual application setup.

*AR Credit Limit should be set to ‘5000’ if there is no preference given by customer.
*Set the desired background color by editing the screen, and clicking the ‘?’ button next to ‘Screen Color’.
**Choose from the color palette provided, or create a custom color.
**You must log out and log back in to see the updated background color.

===CID Maintenance – Counters Tab===

This screen controls how document numbers are generated for most documents and records in Adjutant. Prefix and Suffix entries can also be set up to differentiate documents. Some document types have setup options and/or rule maintenance controls that can further customize the numbering criteria.

*Set up the required counter details per customer’s request. The common types are detailed below.
**BOL – Bill of Lading
**CUSTNO – Organization ID (Customer Number), only used when the ENTCOUNTER option is set
**FCINV – Finance Charge Invoice, must access ‘Generate Finance Charges’ screen to create this record.
**INVNO – AR Invoice
**LOTNO – Serial/Lot Number, only used when POAUTOLOT option is set, otherwise, lot numbers are manually entered. '''RARE''' - Make sure the customer's item codes do not overlap with the LOTNO counter values. Lot numbers and Item code numbers should never overlap.
**MSN – Project Number, prefix can be set by project type in PROJTYPE rule
**PONO – Purchase Order Number
**RFQNO – Quote Number, prefix can be set by quote type in RFQTYPE rule
**SONO – Sales Order Number, prefix can be set by sales order type in SOTYPE rule
**TASK – Task/Service Order Number, used instead of the SONO counter when TASKNEWSEQ is set
**WONO – Production Work Order Number, only used for PWOs added without a SO (i.e. Make For Stock)

===CID Maintenance – Accounts ===

Complete the GL account entries in each field as per customer’s request.

'''Clearing'''

*Work in Progress – WIP account for order/job cost, clears when invoiced, can be overridden by Warehouse entries, or Item-level entries
*Payroll – no longer used, but an entry is required in order to generate batches - enter the suspense account, or another unused account
*Equipment – Clearing account for equipment billing
*Inventory – Clearing account used in Inventory Adjustment transactions, can be overridden by Warehouse entries, or Item-level entries
*Purchase Orders – Clearing account between PO Receipt and AP Invoice entry, credited at PO Receipt and debited at AP Invoice entry, can be overridden by Warehouse entries, or Item-level entries. This account is also used as the default AP Distribution account for non-PO transactions if no default distributions are set up at the vendor level.
*Suspense – GL account used when the system can’t determine a valid GL account, forced balance
*Over/Under Billing – Clearing account for draw billing transactions in Project Control
*Retainage – Clearing account for retainage billing in Project Control
*Retained Earnings – Profit/Loss GL account used at EOY closing
*Exchange Gain/Loss -
*Sales Tax Clearing -

'''Accounts Payable'''

*Payables – Control account for accounts payable, can be overridden at the Sold From level
*Discount – Default account for calculated or approved AP Invoice discounts
*Adjustments – Default account for AP Invoice adjustments, can be overridden at Remit To level, or AP Invoice Approval level
*Checking – Default checking account for AP transactions
*Purchase Variance – Default balancing account between PO Receipt value and AP Invoice value
*PrePay Expense – Default account used when creating a PrePaid Check,
*Retainage AP – Used in AP Invoice transactions where retainage is calculated

'''Accounts Receivable'''

*Accounts Receivable – Default AR account, can be overridden by POS AR account, AR Account in SOTYPE2 rule, or at the Bill To level
*Sales Tax – Default sales tax liability account used at invoicing, can be overridden by STATES rule
*Cash Receipts – Default checking/cash account, also set in System Cash/Checking Accounts screen, can be overridden during Apply Cash Receipts
*Payment Discounts – Default account used for discounts applied against invoice, can be overridden at the Bill To level
*Payment Adjustments – Default account used for cash receipt adjustments, can be overridden during Apply Cash Receipts
*Retainage AR – Used in AR transactions where retainage is calculated
*POS AR – (optional) AR Account used for point-of-sale receipts; Refer to the [http://www.abiscorp.com/adjwiki/Setting-the-AR-GL-account-by-sales-order-type.ashx AR GL Account Hierarchy] wiki for more information.
*Open Credit/AR – Default account used when creating an open credit in Apply Cash Receipts, can be overridden

'''Inventory'''

*Stock Inv – Default stock inventory control account, can be overridden at Warehouse, or item level
*Non-Stock Inv – Default non-stock inventory control account, can be overridden at Warehouse, or item level
*Return Loss – Inventory control account that is debited when stock items are returned, but not returned to stock
*Transfer Clearing – Clearing account for inventory transfers
*Modification Clearing – Clearing account for certain Modification Processor transactions
*Scrap Adjustment – Offset account for scrap adjustment transactions

===CID Maintenance – Fiscal Calendar===

This screen holds the valid fiscal periods and all associated dates for the accounting system.

*Edit the screen to set the ‘Current Year’ and ‘Current Period’ values. These set the default posting period in a variety of screens. They are updated when ‘Close GL Period/Year’ is processed.
*Fill out the Period Names/Start/End Dates for the current year based on the customer’s fiscal calendar. If the customer operates on a calendar year fiscal calendar, use the ‘Fill out DefCalYear’ button during an edit function to fill out the default start and end dates for the displayed year.
**Double-check the entry for February if you are adding a leap year

===CID Maintenance – New User Defaults===

This screen sets the default values for several fields in the User in Adjutant attribute screen. Defaults set here can be overridden during user entry. Entries in this screen do not affect previously added user records.

*Complete the Whse, Menu, Lang and SMTP default fields, at a minimum.

===CID Maintenance – DropFolder Structure===

Do not use this screen unless you have guidance from a Supervisor, or a Development resource.

===CID Maintenance – CID Setup Options===

This screen allows users to set the desired system setup options that control the way applications, features, and fields behave in Adjutant.
Edit the screen to select or unselect options as needed.

==Import CID Items==

The CID Items file contains all of the system default item codes required by the different applications. If the CID Items are not set up, several basic functions in Accounts Receivable, AP, Tasks, and Data Imports will not work.

*A copy of the ‘cid_items_new.xls’ file can be found in the \Data Files\Items folder of the Adjutant directory (if copied from MASTER), or a copy can be found in the Implementation Files folder on the FTP.
*Edit the file and update the HeldFor, WHSE, and OwnerID values so they match your environment. Save the file as a Microsoft Excel 5.0/95 Workbook. Or, you can leave the XLS file fields blank and use the Default Whse, Owner, and HeldFor fields on the Item Import screen to set the OHF values.

*Import the file as-is using the ‘Import Item Master’ screen. No special attributes are needed.

==Review and Update Rule Maintenance Records==

===Air Hammer Default Days (AIRHAMMERDEF)===

This rule overrides the default number of days used for the Start/End range in the various Air Hammer screens.
If no entries exist, each screen’s Air Hammer will default to 30 days.

http://www.abiscorp.com/adjwiki/RULE-AIRHAMMERDEF.ashx

===Auto Batch Options (AUTOBATCH)===

This rule sets enables/disables processing and posting of GL Batches, as well as processing nightly invoices. It also controls options for routing the nightly batch summary report.
The AUTOBATCH CID Setup Option must be enabled, and the AutoBatch Process must be scheduled on the Auto Process Schedule screen in order to automate batching.

http://www.abiscorp.com/AdjWiki/RULE-AUTOBATCH.ashx

===Doc Vault Drop Folders (DROPFOLDERS)===

This rule controls the directory structure for each application’s Document Vault data. It also sets the email tag for the Inbox Mail Reader.
If the CID was copied from MASTER, and the MASTER CID Copy guide was followed, this step should be complete. (See MASTER)

*Otherwise, export the latest DROPFOLDERS rule from a MASTER CID and import the rule into the new CID. The MASTER CID should always have a complete and accurate record of all Doc Vault Codes.
*NOTE: The file path must be entered with the full UNC path in order for certain inbox reader functions to work.

http://www.abiscorp.com/AdjWiki/RULE-DROPFOLDERS.ashx

===ETemplate Lower List Values (ETEMPEXTRA)===

This rule contains the custom-coded Email Template fields that do not fit in the existing Data Sources in the Email Templates screen.

===Event List (EVENTLIST)===

This rule contains custom event codes used for alerts and routes.

*The rule is manually maintained at each customer, and may be incomplete. Review the rule in MASTER, ask another consultant, or consult with Development if there are event codes that need to be added.

http://www.abiscorp.com/AdjWiki/RULE-EVENTLIST.ashx

===Note Description Types (NOTETYPE) ===

This rule controls the entries in the Type drop-down in the Notes screen. These are user-defined and can be customized to display only the types that matter to the customer.

*An entry for AR Collection Notes with a code of ‘AR’ should be added to work with the AR Aging Collection Notes feature.

===Note Priority (NOTEPRIORITY)===

This rule controls the entries in the Priority drop-down in the Notes screen. The priority can be used to categorize notes that require follow-up.

===Note Status Codes (NOTESTATUS)===

This rule controls the entries in the Status drop-down in the Notes screen.

*An entry for an Open status should be added as the default status.

*An entry for a Closed status should be added with the system-defined Code of ‘CL’.

===Quick Search Desktop Overrides (QUICKLIST)===

This rule allows users to customize the Desktop Quick Search drop-down details.

*Search items in the list can be hidden, re-sorted, or the descriptions can be customized.

==Review the Desktop Menu Generator==

*The ‘Default’ menu is appropriate for most customers, and should be available on every installation.
*Customize the menu as needed as per customer request. Use the ‘Copy From’ feature to make a backup of any menu you plan to change, or to create new menu name.

==Update System to the Latest Beta Version==

*Access the End User Update Tool screen, select the ‘Beta’ radio button, and click ‘Check For Update’
** ''If you delay more than a few seconds on any step during this process, you may be disconnected from the FTP server, and will receive error messages. Generally, you can simply restart the process without any issues.''
*The system will connect to the update FTP server and return a message with the latest version, or that the running version is the most current.
*If the version needs to be updated, click ‘Download and Install Full Update’
*Accept the EULA agreement
*In the next window, Adjutant Update Processor, click on ‘Install’
*Once this step completes, answer ‘Yes’ to update the Help Database.
*Click on ‘Disconnect and Exit’ once the process completes.

==Review System Functionality==

Once all core system setup has been completed, perform the following system functionality tests. Some of these will require additional setup in other areas in order to create transactions and report data for testing. Work through each associated setup guide to complete the required setup and verify that each area below is functioning as expected in the new server setup.

* Verify that reports can be previewed
* Verify that drilldowns work, this uses an HTML viewer different than previewing a regular report
* Verify that the doc vaults are accessible
* Verify that printing is working
* Verify that both outbound/inbound emailing are working

==Set up User Records==

Setting up User Records and providing the customer with user credentials should take top priority once the core system is set up and accessible. User in Adjutant details and all of the appropriate named user license flags should be set up as soon as possible once the core system setup items have been completed. User licenses are generally billed from the very beginning of the implementation, so customers should be able to access the system as soon as it is available. Setting up user records immediately avoids a situation where customers are being billed for user licenses that they are unable to use.

Follow the [[Contact Import Guide]] to import employee contact records and assign the contact IDs.

Follow the [[User Record Import Guide]] once Contact records have been created to create the User in Adjutant records.

[[Category:Setup Guides]]

[[Category:System Manager]]

System Manager Setup Guide

2025-04-03T19:16:10Z

LNICOLOSI: /* Hosted vs. Non-Hosted Installations */

==General Information==

This guide covers the initial setup and configuration of a new customer CID. Following this guide will ensure that the base system features are set up completely. There may be additional system-level setup and configuration activities for optional features and integrations that are required beyond this guide.

===Hosted vs. Non-Hosted Installations===

'''Hosted Installations'''

A hosted CID installation means that the database and folder structure exist on ABIS’s controlled Rackspace network environment. Development has all the administrative rights to manage files, databases, processes, user access, and more.

*For hosted customers, Development will generally determine which server is used.
*When creating the ‘Install Adjutant Desktop’ ticket for Development to create the CID and database structure, indicate the CID name (used for SQL and ODBC) and which MASTER CID should be used to create the installation.

**Create the '6.4.4 Install Adj 2020' task on the 1st of the month after the Needs Analysis is complete because when that task is completed it fires a route to start recurring monthly invoices for licensing.

'''Non-Hosted Installations'''

A non-hosted installation is one that exists on customer-controlled server resources. Non-hosted installations require more information gathering and generally require more communication to secure the necessary network rights and privileges to assist setting up the installation.

Coordinate closely with the customer and ABIS Development on who will be responsible for the initial installation.
* Customers with a strong IT department may want to complete the process themselves.
* Some customers want ABIS to complete the process and ‘hand over the keys’ once it is complete.

ABIS will need the following from the customer’s server (at a minimum)
* IT-Level contact with adequate server administration rights
* Server IP address and access credentials

The following resource documents, available on the FTP Implementation folder, should be shared with customers that are completing their own Adjutant installation
* Adjutant Requirements (reference of minimum standards for server and SQL versions)
* Adjutant Install Notes (high-level checklist of server and workstation setup steps)
* Adjutant ODBC Datasource Setup (step-by-step checklist for setting up the SQL/ODBC connections)

Coordinate the Adjutant installation and remote access privileges with the customer and ABIS Development resources as needed. We will need solid, reliable access to the customer's server for setup and support in the form of a dedicated, licensed RDP account, or a dedicated VPN account for remote access. We should not allow any remote access solutions that are temporary, unlicensed, free-ware, trial periods, shared remote connections that may be unavailable because someone logged out for the day, or anything that requires us to pretend we are students. Escalate to your supervisor immediately if the customer is unable to provide secure, licensed remote access to their server.

The process and flow of non-hosted installations varies greatly from one to the next. Once you have a reliable connection and Adjutant is running without database errors, you can proceed with setup.

===Notes on CID Initial Setup (Copied from MASTER vs. other methods)===

*All new CIDs should be created by copying from a MASTER CID setup.

*Refer to the MASTER CID Copy Guide page to complete the initial CID setup by copying and modifying the MASTER CID database elements.
http://www.abiscorp.com/faq/index.php?title=MASTER_CID_Copy_Guide
* There are some overlapping steps between the MASTER CID Copy guide and this guide. Setup steps that have additional or different details will reference the MASTER CID Copy guide with (See MASTER).
* For installations that are not going to be copied from a MASTER CID, installation details such as setup option settings, rule maintenance records, and other setting will vary depending on how the installation was created. Ask another consultant or your supervisor if there are any setup issues that seem unusual.

==Verify the Licensed User Counts==

Review the License Status screen for the new CID and confirm that the values in the License column match the number of licensed users on the contract.

If the Desktop Login screen, the License Status screen, or the License Update screen still show '''Registered To: MASTERCID''', send a request to Development to update the license file for the new CID. Do not update any license counts until the CID shows as registered to the correct customer.

If the counts do not match the customer's contracted license counts, update them to match the contract. If any changes are made to the license counts, email your supervisor and copy Karen Egan with details on the changes you made.

[[File:LicenseStatus.png]]

If there are any discrepancies, notify your supervisor.

==Verify/Update the CSTRING.TXT File==

The CSTRING.TXT file is found in the main Adjutant folder. This file holds information essential to the databases. Development generally sets the correct information at CID creation. If there are any questions about editing this file, consult your supervisor.

*Verify that the CID name in the file matches your CID.

[[File:CSTRING.png]]

==CID Initial Setup==

===Set the Adjutant Desktop Background Image===

*To set the background image for the CID, place a .BMP or .JPG file of the customer logo in the main Adjutant folder with the filename matching the CID name. For example, if the new CID is 'STEEL', the file should be named STEEL.BMP (or JPG).
*Exit Adjutant and log back in to display the image.

===Update the CID Maintenance – Master Tab Details (See MASTER)===

*Update the CID Company Name, Address, Phone, Email, and TaxID (if available) details.

*Update the ‘Master ENT’ value with the Organization ID that matches the CID name, or verify that the Organization record has the correct details and all of the following attributes.
**Bill To / Ship To / Sold To
**Remit To / Sold From
**Inventory Owner

===Set the CID GL Mask (See MASTER)===

*If the GL Mask field in the CID Maintenance – Accounts tab is open for editing, set the GL Mask value to match the customer’s GL account structure, using X and - characters.

*Generally, the GL Mask in the ‘Accounts’ tab must be updated via SQL with the following query
**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)

===Import the GL Chart of Accounts (See MASTER)===

In order to proceed with the CID Setup, the GL chart of accounts (or at least a single GL account) must be set up. If the complete chart of accounts is not available at this point, you can add a suspense GL account manually in the ‘GL Accounts’ screen that will be used to fill in required GL setup fields.

*Keep in mind that any setup fields pointed to the temporary suspense account will have to be reviewed and corrected once the complete chart of accounts has been set up.

*The GL Chart of Accounts import template can be found in the \Data Files\Accounting folder of the Adjutant directory (if copied from MASTER), or a copy can be found in the Implementation Files folder on the FTP.

*Import the customer’s complete chart of accounts using the ‘Chart of Accounts Import’ screen.

*Verify that the imported GL Accounts exist and are correct in the ‘GL Accounts’ screen.

=== Set Up the Default Warehouse / Held For Records (See MASTER)===

In order to proceed with the next steps, you must have added at least one GL account and a default Warehouse.
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.
*'''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.
*The add process will create a new Organization with a ‘Warehouse Location’ attribute.
*You must complete the blank GL accounts in the ‘Account’ tab in order to save the record.

[[File:Warehouse1.png]]

[[File:Warehouse2.png]]

*Update the ‘Item Held For Codes’ (HOLDER) Rule Maintenance record with the new customer name and vendor number.

==Review/Update/Complete all CID Maintenance Screens==

===CID Maintenance – Paths / Remote Transfer Tab===

This screen sets the destination path for several system level functions. Generally all values in this screen should have the same base folder structure tied to the Adjutant working folder.

*Confirm that each file path matches the customer’s file structure. If not, update as needed.
*Not all file paths are used. Generally, the first six fields are used.
*If these folders are not accessible, Adjutant will display a warning message at login.
*The 'Mail Link' path should contain the full UNC path info (rather than just a drive letter) because mail service functions require the full server path.

===CID Maintenance – Accounting Backend Tab===

This screen is used to integrate with third-party accounting and payroll systems, which is rare for new installations. Consult with development for the correct entries in this screen if you are setting up an interface.

*Otherwise, update the following fields as indicated:
**Name should be set to ‘None’
**Backend Type should be set to ‘Foxpro/None’
**Posting Window should be set to an appropriate date range for the current year (and beyond if desired)
***Note – these fields must be updated annually if they are set to a year at a time
**Default Costing Method should be set to the customer’s desired method (SI-AVG is generally best practice)

===CID Maintenance – Map/Password Info Tab===

This screen controls the default password settings that are established for new user records. It also controls the internet mapping details for certain applications (not common).

*Review and update the Password Settings fields to match the customer’s requests.

===CID Maintenance – Defaults Tab===

This screen controls default entries for various applications in Adjutant, in addition to setting the background color for the CID Desktop.
The system default entries, or entries copied from MASTER CID, are generally acceptable to begin an installation, and can be adjusted later during individual application setup.

*AR Credit Limit should be set to ‘5000’ if there is no preference given by customer.
*Set the desired background color by editing the screen, and clicking the ‘?’ button next to ‘Screen Color’.
**Choose from the color palette provided, or create a custom color.
**You must log out and log back in to see the updated background color.

===CID Maintenance – Counters Tab===

This screen controls how document numbers are generated for most documents and records in Adjutant. Prefix and Suffix entries can also be set up to differentiate documents. Some document types have setup options and/or rule maintenance controls that can further customize the numbering criteria.

*Set up the required counter details per customer’s request. The common types are detailed below.
**BOL – Bill of Lading
**CUSTNO – Organization ID (Customer Number), only used when the ENTCOUNTER option is set
**FCINV – Finance Charge Invoice, must access ‘Generate Finance Charges’ screen to create this record.
**INVNO – AR Invoice
**LOTNO – Serial/Lot Number, only used when POAUTOLOT option is set, otherwise, lot numbers are manually entered. '''RARE''' - Make sure the customer's item codes do not overlap with the LOTNO counter values. Lot numbers and Item code numbers should never overlap.
**MSN – Project Number, prefix can be set by project type in PROJTYPE rule
**PONO – Purchase Order Number
**RFQNO – Quote Number, prefix can be set by quote type in RFQTYPE rule
**SONO – Sales Order Number, prefix can be set by sales order type in SOTYPE rule
**TASK – Task/Service Order Number, used instead of the SONO counter when TASKNEWSEQ is set
**WONO – Production Work Order Number, only used for PWOs added without a SO (i.e. Make For Stock)

===CID Maintenance – Accounts ===

Complete the GL account entries in each field as per customer’s request.

'''Clearing'''

*Work in Progress – WIP account for order/job cost, clears when invoiced, can be overridden by Warehouse entries, or Item-level entries
*Payroll – no longer used, but an entry is required in order to generate batches - enter the suspense account, or another unused account
*Equipment – Clearing account for equipment billing
*Inventory – Clearing account used in Inventory Adjustment transactions, can be overridden by Warehouse entries, or Item-level entries
*Purchase Orders – Clearing account between PO Receipt and AP Invoice entry, credited at PO Receipt and debited at AP Invoice entry, can be overridden by Warehouse entries, or Item-level entries. This account is also used as the default AP Distribution account for non-PO transactions if no default distributions are set up at the vendor level.
*Suspense – GL account used when the system can’t determine a valid GL account, forced balance
*Over/Under Billing – Clearing account for draw billing transactions in Project Control
*Retainage – Clearing account for retainage billing in Project Control
*Retained Earnings – Profit/Loss GL account used at EOY closing
*Exchange Gain/Loss -
*Sales Tax Clearing -

'''Accounts Payable'''

*Payables – Control account for accounts payable, can be overridden at the Sold From level
*Discount – Default account for calculated or approved AP Invoice discounts
*Adjustments – Default account for AP Invoice adjustments, can be overridden at Remit To level, or AP Invoice Approval level
*Checking – Default checking account for AP transactions
*Purchase Variance – Default balancing account between PO Receipt value and AP Invoice value
*PrePay Expense – Default account used when creating a PrePaid Check,
*Retainage AP – Used in AP Invoice transactions where retainage is calculated

'''Accounts Receivable'''

*Accounts Receivable – Default AR account, can be overridden by POS AR account, AR Account in SOTYPE2 rule, or at the Bill To level
*Sales Tax – Default sales tax liability account used at invoicing, can be overridden by STATES rule
*Cash Receipts – Default checking/cash account, also set in System Cash/Checking Accounts screen, can be overridden during Apply Cash Receipts
*Payment Discounts – Default account used for discounts applied against invoice, can be overridden at the Bill To level
*Payment Adjustments – Default account used for cash receipt adjustments, can be overridden during Apply Cash Receipts
*Retainage AR – Used in AR transactions where retainage is calculated
*POS AR – (optional) AR Account used for point-of-sale receipts; Refer to the [http://www.abiscorp.com/adjwiki/Setting-the-AR-GL-account-by-sales-order-type.ashx AR GL Account Hierarchy] wiki for more information.
*Open Credit/AR – Default account used when creating an open credit in Apply Cash Receipts, can be overridden

'''Inventory'''

*Stock Inv – Default stock inventory control account, can be overridden at Warehouse, or item level
*Non-Stock Inv – Default non-stock inventory control account, can be overridden at Warehouse, or item level
*Return Loss – Inventory control account that is debited when stock items are returned, but not returned to stock
*Transfer Clearing – Clearing account for inventory transfers
*Modification Clearing – Clearing account for certain Modification Processor transactions
*Scrap Adjustment – Offset account for scrap adjustment transactions

===CID Maintenance – Fiscal Calendar===

This screen holds the valid fiscal periods and all associated dates for the accounting system.

*Edit the screen to set the ‘Current Year’ and ‘Current Period’ values. These set the default posting period in a variety of screens. They are updated when ‘Close GL Period/Year’ is processed.
*Fill out the Period Names/Start/End Dates for the current year based on the customer’s fiscal calendar. If the customer operates on a calendar year fiscal calendar, use the ‘Fill out DefCalYear’ button during an edit function to fill out the default start and end dates for the displayed year.
**Double-check the entry for February if you are adding a leap year

===CID Maintenance – New User Defaults===

This screen sets the default values for several fields in the User in Adjutant attribute screen. Defaults set here can be overridden during user entry. Entries in this screen do not affect previously added user records.

*Complete the Whse, Menu, Lang and SMTP default fields, at a minimum.

===CID Maintenance – DropFolder Structure===

Do not use this screen unless you have guidance from a Supervisor, or a Development resource.

===CID Maintenance – CID Setup Options===

This screen allows users to set the desired system setup options that control the way applications, features, and fields behave in Adjutant.
Edit the screen to select or unselect options as needed.

==Import CID Items==

The CID Items file contains all of the system default item codes required by the different applications. If the CID Items are not set up, several basic functions in Accounts Receivable, AP, Tasks, and Data Imports will not work.

*A copy of the ‘cid_items_new.xls’ file can be found in the \Data Files\Items folder of the Adjutant directory (if copied from MASTER), or a copy can be found in the Implementation Files folder on the FTP.
*Edit the file and update the HeldFor, WHSE, and OwnerID values so they match your environment. Save the file as a Microsoft Excel 5.0/95 Workbook. Or, you can leave the XLS file fields blank and use the Default Whse, Owner, and HeldFor fields on the Item Import screen to set the OHF values.

*Import the file as-is using the ‘Import Item Master’ screen. No special attributes are needed.

==Review and Update Rule Maintenance Records==

===Air Hammer Default Days (AIRHAMMERDEF)===

This rule overrides the default number of days used for the Start/End range in the various Air Hammer screens.
If no entries exist, each screen’s Air Hammer will default to 30 days.

http://www.abiscorp.com/adjwiki/RULE-AIRHAMMERDEF.ashx

===Auto Batch Options (AUTOBATCH)===

This rule sets enables/disables processing and posting of GL Batches, as well as processing nightly invoices. It also controls options for routing the nightly batch summary report.
The AUTOBATCH CID Setup Option must be enabled, and the AutoBatch Process must be scheduled on the Auto Process Schedule screen in order to automate batching.

http://www.abiscorp.com/AdjWiki/RULE-AUTOBATCH.ashx

===Doc Vault Drop Folders (DROPFOLDERS)===

This rule controls the directory structure for each application’s Document Vault data. It also sets the email tag for the Inbox Mail Reader.
If the CID was copied from MASTER, and the MASTER CID Copy guide was followed, this step should be complete. (See MASTER)

*Otherwise, export the latest DROPFOLDERS rule from a MASTER CID and import the rule into the new CID. The MASTER CID should always have a complete and accurate record of all Doc Vault Codes.
*NOTE: The file path must be entered with the full UNC path in order for certain inbox reader functions to work.

http://www.abiscorp.com/AdjWiki/RULE-DROPFOLDERS.ashx

===ETemplate Lower List Values (ETEMPEXTRA)===

This rule contains the custom-coded Email Template fields that do not fit in the existing Data Sources in the Email Templates screen.

===Event List (EVENTLIST)===

This rule contains custom event codes used for alerts and routes.

*The rule is manually maintained at each customer, and may be incomplete. Review the rule in MASTER, ask another consultant, or consult with Development if there are event codes that need to be added.

http://www.abiscorp.com/AdjWiki/RULE-EVENTLIST.ashx

===Note Description Types (NOTETYPE) ===

This rule controls the entries in the Type drop-down in the Notes screen. These are user-defined and can be customized to display only the types that matter to the customer.

*An entry for AR Collection Notes with a code of ‘AR’ should be added to work with the AR Aging Collection Notes feature.

===Note Priority (NOTEPRIORITY)===

This rule controls the entries in the Priority drop-down in the Notes screen. The priority can be used to categorize notes that require follow-up.

===Note Status Codes (NOTESTATUS)===

This rule controls the entries in the Status drop-down in the Notes screen.

*An entry for an Open status should be added as the default status.

*An entry for a Closed status should be added with the system-defined Code of ‘CL’.

===Quick Search Desktop Overrides (QUICKLIST)===

This rule allows users to customize the Desktop Quick Search drop-down details.

*Search items in the list can be hidden, re-sorted, or the descriptions can be customized.

==Review the Desktop Menu Generator==

*The ‘Default’ menu is appropriate for most customers, and should be available on every installation.
*Customize the menu as needed as per customer request. Use the ‘Copy From’ feature to make a backup of any menu you plan to change, or to create new menu name.

==Update System to the Latest Beta Version==

*Access the End User Update Tool screen, select the ‘Beta’ radio button, and click ‘Check For Update’
** ''If you delay more than a few seconds on any step during this process, you may be disconnected from the FTP server, and will receive error messages. Generally, you can simply restart the process without any issues.''
*The system will connect to the update FTP server and return a message with the latest version, or that the running version is the most current.
*If the version needs to be updated, click ‘Download and Install Full Update’
*Accept the EULA agreement
*In the next window, Adjutant Update Processor, click on ‘Install’
*Once this step completes, answer ‘Yes’ to update the Help Database.
*Click on ‘Disconnect and Exit’ once the process completes.

==Review System Functionality==

Once all core system setup has been completed, perform the following system functionality tests. Some of these will require additional setup in other areas in order to create transactions and report data for testing. Work through each associated setup guide to complete the required setup and verify that each area below is functioning as expected in the new server setup.

* Verify that reports can be previewed
* Verify that drilldowns work, this uses an HTML viewer different than previewing a regular report
* Verify that the doc vaults are accessible
* Verify that printing is working
* Verify that both outbound/inbound emailing are working

==Set up User Records==

Setting up User Records and providing the customer with user credentials should take top priority once the core system is set up and accessible. User in Adjutant details and all of the appropriate named user license flags should be set up as soon as possible once the core system setup items have been completed. User licenses are generally billed from the very beginning of the implementation, so customers should be able to access the system as soon as it is available. Setting up user records immediately avoids a situation where customers are being billed for user licenses that they are unable to use.

Follow the [[Contact Import Guide]] to import employee contact records and assign the contact IDs.

Follow the [[User Record Import Guide]] once Contact records have been created to create the User in Adjutant records.

[[Category:Setup Guides]]

[[Category:System Manager]]

MASTER CID Copy Guide

2025-04-03T18:03:11Z

LNICOLOSI:

== 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.

*Create the '6.4.4 Install Adj 2020' task on the 1st of the month after the Needs Analysis is complete because when that task is completed it fires a route to start recurring monthly invoices for licensing.

== 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.

:: <nowiki>*</nowiki> 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.

:: <nowiki>*</nowiki> 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

[[File:Copy CID.png]]

*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.

[[File:CSTRING.png]]

== 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.

[[File:Warehouse1.png]]

[[File:Warehouse2.png]]

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

===Delete Unwanted Fiscal Calendar Header Records (FISCALH)===

Data copied from MASTER will have many years of fiscal calendar details that clients do not need loaded. These fiscal calendars are copied in the first step to create the new CID. They can either be deleted before that first step, or any time after the new CID is created. The fiscal calendars must be deleted via SQL and should be reviewed carefully before deciding which years will be needed for the customer.

Review the calendars that exist in the FISCALH SQL table. Fiscal Calendar header records are saved by CID and Fiscal Year. Delete any KEYNO records in this table that will not be needed for the new customer. A good rule of thumb is that you can delete all but the current and prior year in the new CID.

The FISCALD SQL table contains the individual months/periods for each KEYNO listed in the FISCALH table. These records can be left in place and should not affect anything once the FISCALH KEYNO value is deleted.

== 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.

'''NOTE - DO NOT set the Active User flag for the ABIS _ADMIN record. By design, the _ADMIN user should not use a customer license. Flagging the Active User field will prevent the _ADMIN user record from working and will exhibit all types of problematic behavior until you clear the Active User flag.'''

*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.

* Update the email setting (text2) in the AUTOBATCH rule to either remove fdonovan@abiscorp.com or update it to a customer or Strategist email address.

* 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 & Update ==

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 where 'AAAA' is the new CID:
** '''update emailsetting set CID = 'AAAA' where CID = 'MASTER''''
** Note that there are database entries for MASTER and JONESCO. The above query should prevent duplicate template records from getting created for the multiple CIDs in MASTER data.
*Review and update the Email Templates Subject lines and update these to the new customer's name. Replace references to MASTER CID with the customer in all templates.

== 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.

[[File:RenameFile2.png]]

== Update the Forms Logo File ==

'''Desktop Process'''

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.

'''Adjutant 20/20 Process'''

Email the company logo file to Development so they can place the file in the /images folder on the customer's web server.

* Generally, the file name should be ''reportlogo.png'', but there may be execptions.

== 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.

[[File:Delete CID.png]]

*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.

==Verify the Licensed User Counts==

Review the License Status screen for the new CID and confirm that the values in the License column match the number of licensed users on the contract.

If the Desktop Login screen, the License Status screen, or the License Update screen still show '''Registered To: MASTERCID''', send a request to Development to update the license file for the new CID. Do not update any license counts until the CID shows as registered to the correct customer.

If the counts do not match the customer's contracted license counts, update them to match the contract. If any changes are made to the license counts, email your supervisor and copy Karen Egan with details on the changes you made.

[[File:LicenseStatus.png]]

If there are any discrepancies, notify your supervisor.

== 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

[[Category:Setup Guides]]

[[Category:System Manager]]

MASTER CID Copy Guide

2025-04-03T18:01:27Z

LNICOLOSI: /* Submit Request to Development */

== 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.

*Create the '6.4.4 Install Adj 2020' task on the 1st of the month after the Needs Analysis is complete because when that task is completed it fires a route to start recurring monthly invoices for licensing.

== 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.

:: <nowiki>*</nowiki> 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.

:: <nowiki>*</nowiki> 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

[[File:Copy CID.png]]

*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.

[[File:CSTRING.png]]

== 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.

[[File:Warehouse1.png]]

[[File:Warehouse2.png]]

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

===Delete Unwanted Fiscal Calendar Header Records (FISCALH)===

Data copied from MASTER will have many years of fiscal calendar details that clients do not need loaded. These fiscal calendars are copied in the first step to create the new CID. They can either be deleted before that first step, or any time after the new CID is created. The fiscal calendars must be deleted via SQL and should be reviewed carefully before deciding which years will be needed for the customer.

Review the calendars that exist in the FISCALH SQL table. Fiscal Calendar header records are saved by CID and Fiscal Year. Delete any KEYNO records in this table that will not be needed for the new customer. A good rule of thumb is that you can delete all but the current and prior year in the new CID.

The FISCALD SQL table contains the individual months/periods for each KEYNO listed in the FISCALH table. These records can be left in place and should not affect anything once the FISCALH KEYNO value is deleted.

== 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.

'''NOTE - DO NOT set the Active User flag for the ABIS _ADMIN record. By design, the _ADMIN user should not use a customer license. Flagging the Active User field will prevent the _ADMIN user record from working and will exhibit all types of problematic behavior until you clear the Active User flag.'''

*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.

* Update the email setting (text2) in the AUTOBATCH rule to either remove fdonovan@abiscorp.com or update it to a customer or Strategist email address.

* 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 & Update ==

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 where 'AAAA' is the new CID:
** '''update emailsetting set CID = 'AAAA' where CID = 'MASTER''''
** Note that there are database entries for MASTER and JONESCO. The above query should prevent duplicate template records from getting created for the multiple CIDs in MASTER data.
*Review and update the Email Templates Subject lines and update these to the new customer's name. Replace references to MASTER CID with the customer in all templates.

== 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.

[[File:RenameFile2.png]]

== Update the Forms Logo File ==

'''Desktop Process'''

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.

'''Adjutant 20/20 Process'''

Email the company logo file to Development so they can place the file in the /images folder on the customer's web server.

* Generally, the file name should be ''reportlogo.png'', but there may be execptions.

== 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.

[[File:Delete CID.png]]

*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.

==Verify the Licensed User Counts==

Review the License Status screen for the new CID and confirm that the values in the License column match the number of licensed users on the contract.

If the Desktop Login screen, the License Status screen, or the License Update screen still show '''Registered To: MASTERCID''', send a request to Development to update the license file for the new CID. Do not update any license counts until the CID shows as registered to the correct customer.

If the counts do not match the customer's contracted license counts, update them to match the contract. If any changes are made to the license counts, email your supervisor and copy Karen Egan with details on the changes you made.

[[File:LicenseStatus.png]]

If there are any discrepancies, notify your supervisor.

== 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

[[Category:Setup Guides]]

[[Category:System Manager]]