Defines the name of the category, up to 60 characters.

If checked, this record is active. Only active records may be used in the system.

Select the active BI Category that needs to be modified for security access.

Select the User Group that will have/not have access to the selected BI Category.

Defines the name of the color profile, up to 60 characters.

Allows users to add a new BI Data Set.

Allows users to modify the selected BI Date Set.

Click to switch the view of displayed BI Data Sets from "Active," "All," or "Inactive."

Click to run the selected BI Data Set.

If clicked, opens the Form Layout for the BI Data Sets grid.

If clicked, marks all BI Data Sets in the list as active.

Defines the name of the data set, up to 30 characters.

Describes the data set, up to 60 characters.

Defines the type of report. Only Combined Report is available.

• The user must have a Combined Report added on their profile via the "Published Data" button on the Edit User form.

Enter appropriate value

Option to determine how the Category will be displayed on the eCommerce site or applied to different eCommerce functions. Options are Best Seller, Featured Product, Navigation, None, or Tag.

Checked to make the Category active. Only active Categories may be used in the system.

If checked, will serve as the default Category.

If checked, this Category will be displayed in the footer of the eCommerce website.

When clicked, will take all changes made to the individual tabs and push them to the Site itself. For example, if a new user is setup on the Users tab and pages are configured on the Pages tab, clicking the "Publish All" button will push all changes to the Site. Each tab aside from the General tab also have their own "Publish" buttons, so if changes made to one tab but not all should take effect, use the "Publish" button on the individual tabs instead of the main toolbar's "Publish All" button.

Option to add images or documents to the eCommerce site. These images or documents can then be synced to the eCommerce website via the "Sync Documents To eCommerce Server" flag on the General tab of the Edit eCommerce Site form.

If clicked, tests for a valid connection between the database server and database indicated on the General tab. The connection test is successful if that user is able to connect and all of the expected tables with the correct table structure are present.

Click to have "Yes" displayed in the Selected column for all tables. Double clicking an individual table name allows users to toggle between "Yes" or "No".

Click to have "No" displayed in the Selected column for all tables. Double clicking an individual table name allows users to toggle between "Yes" or "No".

If clicked, only records in the selected tables that have been added or modified since the last sync will be synced to the eCommerce database.

• This option can be used to save time when syncing tables containing a large number of records.

Name of the eCommerce Site.

URL for the Site, which must include "http://" or "https://".

Server in which the databases are located.

Database that stores eCommerce data.

Stores the IP address of the server or the web service port number.

SQL Database user name.

SQL Database password.

Determines how the "Delivery Date" (to_deldate) field will be set when creating sales orders in the eCommerce application. Options are: None (default), Today, and Follow Sales Options.

• If Follow Sales Options is selected, the system will take the calculation in the "SO Date 3 Calc." in Sales > Options and use that to set the delivery date on the order.

Option to select the default order type for the selected eCommerce site. Options are Internet Sale, Master Order, and Sales Order. Internet Sale is set as the default.

Only available when the "Generate Site Map" is checked. Allows users to indicate the location (network, folder etc.) of the site map. A site map is a model of a website's content designed to help both users and search engines navigate the site. Additional information on the structure of a standard site map is available via https://www.sitemaps.org/protocol.html

Defines the Google Merchant Center credentials file (JSON). When a file is selected, its text contents are stored in cs_gcredentials.

• Only available if both the "Allow User Registration" and "Allow Cart Without Registration" flags are checked.

Defines the numeric merchant ID in cs_gmerchantid.

• Only available if both the "Allow User Registration" and "Allow Cart Without Registration" flags are checked.

Pick list used to indicate if Users who create logins on the eCommerce Site are automatically approved or not. Options are:

• Approved - If selected, users who register on the eCommerce site will have the "Login Approved" flag checked automatically on their User profile, accessed via the Edit eCommerce User form.
• Not Approved - If selected, users who register on the eCommerce site will have to be manually reviewed and have their "Login Approved" flag checked before logging in to the site.

Determines, in minutes, when an eCommerce session will expire if no activity has occurred. Default time is 5 minutes.

• When an eCommerce user account has gone idle for longer than the Session Expiration value on the CMS Site Settings, the user will be sent a reminder email about the unpurchased items in their cart. This only occurs if the user has opted into Cart Reminder Emails. The email template sent to the user is configurable in the CMS Site Settings.

Determines, in minutes, how frequently Instant MRP reports will be run to update the "Onhand Quantity" field on the Edit Saleable Part form located on the eCommerce Products tab. The maximum value allowed is 999.

• The value in the "Onhand Quantity" field is only calculated if an item is selected in the "Part Number" field on the Edit Saleable Part form.
• The system will run an Instant MRP report for each Facility with the "Include in eCommerce Inventory" flag checked, and tally the results for the item indicated in the "Part Number" field.

Sets a pre-defined Time-Phased MRP pre-filter template to be used when MRP reports are generated via Item/Getting Inventory Labels in eCommerce.

• Pre-filter templates are created using the "Settings" button on the pre-filter with all desired fields completed.
• The pre-filter template must be saved for "All Users".
• If no selection is made in this field, the system will run an Instant MRP report, using the default of 6 buckets with the bucket type of "Weeks".

Option to have documents with the selected Document Category pulled into the eCommerce application when the GetImage API is called.

• Designed to allow image documents that are assigned to Item Master records to be added to eCommerce sites.
• Image documents are added via the "View Docs" button on the Item Master record.

Defines the number of minutes to wait after an eCommerce user abandons their shopping session before attempting to send a reminder email about their un-purchased items.

• Field accepts a range between 0-9999.
• Used in conjunction with the "Cart Reminder Email" field above.
• Added in version 16.04.112.

Indicates the total dollar amount limit for a single purchase (for any/all users) on the eCommerce site. This field prevents items from being added to the cart if they would cause the total dollar value of the purchase to exceed the value of the field.

• Additionally, checkout calls are prevented if the maximum dollar value is exceeded.
• Added in version 16.04.127.

If checked, this record is active. Only active records may be used in the system.

If checked, opens the "Site Map Path" field where users can specify the location of the site map. When the user hits the "Publish All" button, Deacomwill generate a site map and store it in the location specified in the "Site Map Path" field. The site map file will be an xml with the naming convention of dxcmssite.cs_name + ' Site Map ' + Date(MMDDYY) + TIME (999999).xml. If the "Site Map Path" field is empty or not able to be navigated to, the system will display the "Invalid Site Map Path" prompt and will not save the form.

This box must be checked in order for users to register themselves.

Check to allow users to make a cart in the eCommerce application without first registering as a user. If unchecked, users cannot create a cart without registering as a user.

If checked, when a user registers on the site and creates a Bill-to/Ship-to, a contact is created and linked.

Determines if security questions will be required when users login to eCommerce sites. This field is checked by default. Additional information on the security questions option is available via the Managing Authentication Methods page.

Check to enforce the use of at least 1 number when a user creates a password on eCommerce Sites. When this box is checked, the following alert message will be displayed to the user: "Password must include at least 1 number." If users attempt to enter a password without a number they will be prompted.

• If the "Require Symbol In User Password" field is checked, the user will receive an alert message that both a number and symbol are required.

Check to enforce the use of at least one symbol when a user creates a password on eCommerce Sites. When this box is checked, the following alert message will be displayed to the user: "Password must include at least 1 special character." If users attempt to enter a password without a special character they will be prompted.

• If the "Require Number In User Password" field is checked, the user will receive an alert message that both a number and symbol are required.
• Any symbol on the standard keyboard, such as !@#$%^&*()-_=+|\{}[];:'"<>,.?/~` may be used when creating a password.

If checked, documents or images attached to the eCommerce site or item master records defined as saleable on the site will be synced to the eCommerce website. This results in a physical copy of the image or document being saved directly to the website which allows for quick retrieval and display.

• Images are attached to the eCommerce site and item master records via the "View Docs" button on the toolbars of the Edit eCommerce Site and Edit Item Master forms respectively.
• Users define which items or categories/sub-categories of items are saleable on the eCommerce site via the eCommerce Products tab.

If checked, allows eCommerce API calls to be logged to the Microsoft Windows Event Viewer. Useful for diagnosing session issues, such as when carts and users are no longer recognized by the session.

Example of logged API call:

-API call made: Cart/AddTo

-IP Address: 127.0.1.1

-SiteID: 3

-SessionID: aff57abab5c649589a70aff4899db32d

-Ecommerce User ID: 2095

-Cart ID: 3086

If checked, the EasyPost API will be used to calculate shipping rates in the DeacomeCommerce application.

Displays the name of the import schedule/External.

Pick list used to select the type of schedule. Options are: Data Import Profile External Program

Search field used to select the Data Import Profile or External that will be used for this schedule.

Pick list used to select how often the schedule/program should run. Options are: Daily Minutes Month Week

Pick list used to select the day of the month or week that the schedule/program should run. Options are: 1-31 if "Interval Type" is set to "Month". Sunday-Saturday if "Interval Type" is set to "Week".

Used to set the specific time for the schedule/program to run.

Determines the interval of when the schedule/program will run when "Interval Type" is set to "Minutes".

Allows profiles to be imported. The system will open the file chooser form to allow selection and import of an XML file.

Name of the Export Profile (The Paymerang Export File should come preloaded. If not, you will need to make the necessary changes based on the information on this page.)

Defines the group type for files that will be exported from Deacom. Options are None and Payment Files (default)

Specifies the format type used to translate the grid data to the exported format. Options are Template, Script, or External Program.

Defines the expression/parameters when using a Type of Template or Script. When using a Type of External Program, this field is used to select an External Program from the list.

• Template will read the contents of the memo box to the Expression Processor. Tags will be parsed, and expressions evaluated. The cursor will be scattered to the Expression Processor one row at a time. Tags are enclosed in <<tag>> where the tag should correspond to a field in the memory environment.
• Script will assume the memo box contents are a well formed Deacom (JavaScript) script that results in a string array output.

Check to make the profile active in the system.

Specifies that this profile should be the default selected profile for this group. Each group may have a different default.

Defines the type of export. Options are Download, File, or FTP.

Specifies the file name for the resulting output of the export profile. The field uses the expression processor and tag parsing to allow for more dynamic file naming conventions such as incorporating a date.

• If this field is left blank the system will supply a default file name of DeacomExport.txt. Furthermore, if the file name includes a file extension of .xlsx then the resulting file will be encoded and created as an Excel file. All other extensions are currently treated as Text files using the default encoding based on the system’s ANSI code page.

Specifies the directory location to which the file should be saved. Only enabled when using a Destination type of FTP or File.

• This location must be accessible by the Web Service user and be included in the Allowable Data File Paths system option.
• For any Export types that result in the file being sent to a remote destination such as with FTP (and eventually Email and API), the destination path in combination with the file name will specify the local archival location for the file resulting from the export profile.

The FTP server field specifies the server address for the FTP to which the file shall be uploaded. The server field may include the remote path.

The FTP port field allows the user to specify which TCP Port number to use for the FTP Command connection. This value must be a positive integer number.

• Most FTP servers will use port 21. If you are sending via SSH/SFTP please use port 22.

The FTP user name field provides the user name to use for the FTP connection targeted by this export profile. The user name along with the password comprise the credentials to authenticate the FTP connection.

Defines the name of the note.

Pick list used to determine where in the system this Predefined Note will be available for use. Options are:

• Accounting
• All
• Contacts
• Inventory
• Production
• Purchasing
• Quality Control
• Sales
• Ticket

Memo field used to store the note itself.

If checked, this record is active. Only active records may be used in the system.

Displays the name of the System Constant.

• Cannot contain any spaces.
• The name will be referenced throughout the system and should be easy to understand.

Defines the numeric value that will be used in calculations and expressions throughout the system.

Memo field used to store internal notes containing additional details about the record.

• This information is not used when the constant is referenced by the system.

If clicked, any changes to the record selected will be re-assigned to all BOMs, Jobs, Purchase Orders, or Sales Orders based on the "Retro Since" date defined on the record. In other words, if the expression of the selected User Calculation is updated and this button is used, the lines on all BOMs/Jobs/Orders containing this User Calculation will be updated to reflect the result of the new expression.

• This button changes all Purchase Order Types and Sales Order Types and modifies orders in all statuses including Not Received, Received, Invoiced, Not Shipped, Shipped, Invoiced, and Paid. Historical copies of these orders are updated as well.
• Use this button with caution as the action cannot be undone.
• If User Calculations for Jobs are needed or are added after one or more Jobs have been created, the calculation will need to be made Retroactive via this button.
• If User Calculations for BOMs are needed or are added after BOMs/Formulas have been created in the system, users will need to obtain and run a "RecalcFormulas" External

Pick list used to select the table where the User Calculations will be stored. Options are:

• BOM
• Jobs
• Purchase Order
• Sales Order (Sales order calculations are enabled in DSD. The calcs will fire, and store against the orders the same as in main application. Calculations will also add parts to orders when saved the same as in the main application. This occurs when the device is online. If the device is not online, the system will track what calculations need to be fired, and fire/sync them when the device is back online.)

The name or description of the calculation that will appear on screen when viewing User Calculations.

• Important: For the User Calculation to select the correct item when adding a line to the BOM, Job, Sales Order, or Purchase Order, the "Description" of User Calculation must match the "Part Number" of the item that will be added to the BOM/Job/Sales Order/Purchase Order.

The name that will appear in the database table and also on the variable display when viewing reports. Supports User Defined Fields.

• Recommended format for naming is "uc_description"

Pick list that allows for greater text and character limits, particularly when using SDS forms which may require large amounts of text descriptions and regulatory information. Options are:

• Character
• Date
• Numeric
• Text

Note: When using a BOM User Calc with a "Field Type" of "Character" and a "Type" of "Minimum", "Maximum", or "Sum", the following rules are applied:

• Character BOM User Calc Max takes the max based on "largest" string alphabetically.
• Character BOM User Calc Min takes the min based on "smallest" string alphabetically.
• Character BOM User Calc Sum sums the results.
• Date Calcs are refreshed after the selection/re-selection of a Bill-to or Ship-to Company on the Sales Order header.

Pick list used to determine how the resulting calculation will be presented. Options are:

• Average - takes the average, across all the lines, of whatever expression is in the expression field. Average is valid only for expressions that evaluate to a numeric type of result.
• Maximum - takes the maximum, across all the lines, of whatever expression is in the Expression field. Maximum is valid for expressions that evaluate to numeric, string, date, or logical. The maximum of a string expression will produce the highest alphabetical result, meaning the expression that would be last in an alphabetic list. The maximum of a logical would only be false if all the line expressions are false, but would be true if any were true.
• Minimum - takes the minimum, across all the lines, of whatever expression is in the Expression field. Minimum is valid for expressions that evaluate to numeric, string, date, or logical. The minimum of a string expression will produce the lowest alphabetical result, meaning the expression that would be first in an alphabetic list. The minimum of a logical would be false if any the line expressions are false, and would be true if all were true.
• Sum - takes the sum, across all the lines, of whatever expression is in the Expression field. Sum is valid only for expressions that evaluate to a numeric type of result.
  • For example, a sum of lj_quant would give the total units on the job, across multiple lines.
  • Since each item has a unit weight, and lj_quant is in the stock unit of measure, a sum of lj_quant * pr_unitwgt would give you total weight being made on the job, regardless of the different units being produced.
• Secondary Total - Calculates once after non-secondary calculations are completed in sort order and can reference other User Calcs and header fields. All of the basic calculation types listed above are calculated in parallel and independent of each other, which means that you can’t have a basic calculation that looks at the results of another basic calculation. This is where the Secondary Total calculation type is used. Unlike the basic calculation types, Secondary Total does NOT look at the lines, but looks at the header, header-related fields (customer and vendor), the results of the basic calculation types, and other secondary total calculations.
  • All basic calculation types are done first, in parallel and independently of each other, so the sort order of basic calculation types doesn’t matter.
  • Secondary total calculations are done one at a time, in the order in which they are sorted. The sort order is used for both display of results and to control calculation order. Each secondary calculation has available to it the results of all the secondary calculations that are ahead of it in the sort order.
  • Secondary Totals don’t have to look at basic calculation results, as the name might imply. Since they look at header level fields they can be used to provide logic based on header level variables. Calculations can force lines onto the sales order, so a secondary calculation could look at the terms code and add a 2% charge to the order if the terms code indicated that a credit card was being used. Users need to be careful in their choice of variables here, because to_totdue is the natural total of all the lines on the sales order, including the added credit card charge. So you need another total that ignores the credit card charge and perhaps freight, which would be a Sum type calculation with a condition to return a zero in those cases. The secondary total would then be conditional (IIF statement) on certain terms codes or the credit card checkbox on the terms code, and return 2% of the result of the sum calculation.
  • A Secondary Total can be used inside the Secondary Total after it.

Examples:

• Assume a User Calculation exists with a "Type" of "Secondary Total" and an "Expression" of "1+7 (total11)". Another User Calc can be added with a "Type" of "Secondary Total" and an "Expression" of "total11 + 14 (total22)".
• Calculate average density of a blend. One basic BOM calculation can sum the weights of the lines on a BOM (bo_quant * pr_unitwgt) or already multiplied for you as totwgt. Another basic BOM calculation can sum the volumes of the lines on a BOM (bo_quant * pr_unitwgt) or already multiplied for you as totvol. A secondary total type calculation can take the result of the total weight calc and divide it by the result of the total volume calc, resulting in the density of the blend.

Note: When applying user calcs to child orders, the appropriate value of the weight of the order is pulled from the specific child, rather than the master order.

Defines the format or mask that will be used to display the calculation result. Used for numeric and calculation field types.

Memo field used to define the expression, which will be evaluated to produce a calculation result.

• Expressions may contain a combination of functions and field references.
• Calculated User Calcs may reference other User Calcs in their calculation.
• BOM Calcs will not calculate if the Part is not flagged as "Stocked" on the Item Master Properties tab.
• Bill of Material User Calculations are only re-calculated when saving a line item or any other action that causes the batch yield to be re-calculated. Revision fields (i.e. re_yield) are available to BOM calculations but must be prefixed by "cREV."
• For Sales Engineering information, the engineering values related to a given order line are available to use in the expression for a calculated, order line User Field.
• Calculations may make use of the log() function by using the keyword LOG(a, b) where a is the number the logarithm is for and b is the base of the logarithm.
• The basetotwgt and basetotvol variables are available to this field. These variables contain the same calculations as the totwgt and totvol variables less overage, scrap, and overissue.

When Table is set to BOM – The following fields are available to the expression. Revision header (dmrev) fields, which must be prefixed by “cRev.”. BOM Line Fields (dmbom) including BOM Line User Fields. Item Master fields (dmprod), including Item Master User Fields. Additional fields, prfact - pricing factor, bo_prid, bo_subtot, un_type, un_name, bocount, dispcnt, totwgt, totvol, totcub, exten, futext, wgtcost, volcost, wgtper, volper, and idfld.

• Secondary BOM Calcs can reference Revision header Item Master (dmprod) and Revision header Item Master User Fields.

When Table is set to Job – The following fields are available to the expression. Job header and Job Line fields (including User Fields), Item Master fields (including User Fields), Routing Groups fields (including User Fields), Sales Order Line and Sales Engineering data for linked orders.

• Notes:
  • BOM calculation results are available to Job calculations. To reference a BOM calculation result in a Job calculation expression, use an “m.” prefix and the user-defined calculation field name, such as “m.uc_bottles_per_case”.
  • Note that results for new BOM calculations are not stored in the underlying table and available to the Job calculations until the BOM has been modified and saved, so Job calculations based on them will be empty also. The Deacom Data Conversion team has a program available that can update all existing BOM calculation results at the same time. Because Job calculation results are available to be displayed in Job Reporting reports and calendars, this provides a pathway for the display of BOM values, like the number of bottles in a case or allergen presence, in those reports and their use in further calculations.

Pick list used to determine whether the User Calc will calculate the price or quantity on new lines added to Sales or Purchase Orders. Options are:

• Price
• Quantity - If chosen, the price will be determined based on the Sales or Purchasing pricing hierarchy. Useful in situations where the physical characteristics or assay levels of a product may be different based on production processes or QC testing.
  • Example: A customer sells product at an assumed assay level. The actual assay of the shipped Lot may be different than the assumed assay level. In this case, setting this field to “Quantity” will allow the extended price on the shipped Sales Order to be adjusted up or down based on the actual assay level of the Lot shipped.

Pick list used to determine at what point User Calcs should stop recalculating for a Sales Order or a Purchase Order. Options are:

• Always - User Calcs will continue to recalculate.
• Invoiced - User Calcs will cease recalculating once the Sales/Purchase Order is invoiced.
• Paid - User Calcs will cease recalculating once the Sales/Purchase Order is paid.
• Shipped - User Calcs will cease recalculating once the Sales Order is shipped. This option will only appear when Sales Orders are chosen for user calculation.
• Received - User Calcs will cease recalculating once the Purchase Order is received. This option will only appear when Purchase Orders are chosen for user calculation.

Memo field used to store additional information regarding the purpose or use of the calculation.

Determines the starting date when using the "Retroactive" button.

Pick list used to determine if BOM User Calcs will calculate at only the bottom level, only the top level, or at all BOM levels.

• Example: Assume (1) there is a BOM revision for an item called FINI1 that contains parts SUB1 and RAW3, (2) the default revision for SUB1 contains parts RAW1 and RAW2, (3) the Item Master for SUB1 has a "Current Labor" cost of 10, (4) the Item Master for RAW2 has a "Current Labor" cost of 2, (5) the Item Master for RAW3 has a "Current Labor" cost of 21, and (6) there are three BOM User Calcs configured as follows:
  • Table = BOM
  • Desc/Field Name = Calc1, Calc2, and Calc3, respectively
  • Type = Sum
  • Expression = pr_stanlab for all three User Calcs
  • Level = Bottom, Top, and All, respectively Editing the BOM revision for FINI1 and viewing the Calculations will display the following: Calc1 = 23, Calc2 = 31, Calc3 = 33.

Note: BOM calculations store the calculations done at every sequence so it can be used by the next sequence regardless of level.

If checked, Regulatory Parts will be considered by the system when performing BOM calcs.

If checked, this record is active. Only active records may be used in the system.

If checked, this calculation will only be available for display when printing Part Forms and will not be available for display on grids throughout the system with the exception of the grid on the Calculation tab of the Edit BOM form.

• This field is only available when selecting the "BOM" option in the Table field on this form.
• This field was added to handle a Foxpro limitation of only allowing 255 fields to be displayed on a grid at one time.
• Part Form Only User Calculations are displayed on the Calculation tab of the Edit BOM form in order to allow users to see what the calcs will be on Part Forms at the time that the Formula is edited.

If checked, the User Calculation will be applied to Sales Orders with an "Order Type" of "Master Order" and will calculate based on values from all Child Orders associated with the Master Order.

• For example, if the expression is simply 'or_quant', the calc value should only appear on master orders, no other order type, and should be the sum of or_quant values for all child order line items on the master order.
• Only available when "Table" is set to "Sales Order".

Allows the user to sort the order in which user-defined fields are displayed.

Opens the Edit Pick List form, which allows the user to enter an unlimited number of items and corresponding memo fields to be used in the pick list when information is entered in this User Field.

• When deactivating a pick list value users will be prompted if they wish to clear the pick list option for any records in which it is already set.

Pick list used to determine where in the system the User Field will be available for use. Options are:

• Attached Document - Available when accessing the "View Docs" part of a record.
• BOM Line - The "bo_quant" (BOM Quantity) field and all BOM User Fields are available to print on Part Forms.
• BOM Revision - The "bo_quant" (BOM Quantity) field and all BOM User Fields are available to print on Part Forms. Additionally, all User Fields on Formulas (BOM Revisions) are available to print on batch tickets.
• Billing Group
• Bill-To Company
• Bill-To Facility
• CRM Project
• Campaigns
• Campaign Email Results
• Category
• Chart of Accounts
• Commissions / Rebates
• Contact
• Contact Notes
• Contact Person
• Contact Search 1-5, listed separately and using their specified captions.
• Container
• CRM Project
• CRM Project Notes
• Customer Part - Available to print on all Sales documents and Part Forms.
• Deal
• DSD Route (requires DSD license)
• Facility
• Freight Type
• Item Facility
• Item Master - Available to the Grid Layouts for the Inventory "Lots", "Lot Summary - User Lot", "History", "History Summary", "Transaction", and "Aged" reports and on the Issue/Reserve Inventory form. Additionally, if these fields should be printed on the BOM report, these fields must be prefixed with "cUSERPROD".
• Item Search 1-5, listed separately and using their specified captions.
• Job Category - The Job Category fields are available to the following Grid Layouts: jobsum, expmat, jobcostdet, jobcostsum, jobdet, jmatcost, prodhist, prodhistsum, jobqcdet, jobqcsum, wcostsum, and wcostdet
• Job Header - Available to the Job pick list.
• Job Line - Available to Job Labels, all batch tickets, and all job picklist report layouts.
• Job Time Entry
• Journal Entries (available beginning in version 17.04.008)
• Location
• Location Type
• Operation
• Package
• Payment Type
• Part Form
• Print Substitution
• Project
• Promotion
• Purchase Order Header - All Purchase Order User Fields are available to the Purchase Order reports such as order confirmations and receivers.
• Purchase Order Line - Available to all Purchase Order reports. Users with the security setting "Purchase orders -- edit user fields from View Order form" set to Yes may edit both header and line PO User Fields when clicking the "View Detail" button on Purchase Order reports and forms throughout the system. This ability was added to support various different scenarios including the need to indicate the reason for Vendor returns after the Purchase Order is marked as received in the system.
• PO Search 1-2, listed separately and using their specified captions.
• Quality Control Group - Available as a file type and available to the QCINFO block.
• Quality Control Group Test
• Quality Control Pass - Available as a file type and accessible on the C of A report through two methods: (1) In the QCINFO block using the field name (i.e. field "u_approver_1" should be written in the report as "u_approver_1") and (2) m. notation. by using m.u_approver_1 (or whatever the field name is) into the report to produce that value on the report.
• Quality Control Test - Available as a file type and available to the QC INFO and QC PARENT INFO block types on COA reports. For additional info on the QC INFO and QC PARENT INFO blocks visit Managing Part Forms.
• Report Layout
• Restricted Selling
• Route - Option to the File combobox on the tabadd form, when a record is saved into dmd1, store 'dtroute' in d1_table. This report displays information regarding Direct Store Delivery (DSD) routes in the system including route start date and time, end date and time, total number of order shipped, the Ship Via, Location and User.
• Routing
• Routing Sequence
• Sales Order Header
• Sales Order Line - Allows the use of "in_Engineering" fields in calculated Sales Order line User Fields.
• Sales Rep
• Sales Search 1-5, listed separately and using their specified captions.
• Scale Model
• Ship-To Company
• Ship-To Facility
• Ship Via
• Shop Area
• Sub-Category
• Territory
• Term
• Ticket
• Ticket Contact
• Ticket Search 1-5, listed separately and using their specified captions.
• Unit Of Measure
• User
• User Group
• Vendor
• Vendor Facility
• Vendor Group
• Vendor Part - Vendor Part User fields are available on the Vendor of Parts grid
• Work Center
• Worker

Defines the caption that will appear as the field name.

Indicates the field name that will be stored in the user field database table.

• Preferred format is "u_(user field name)" i.e. "u_boiling_point".

Pick list used to determine the kind of field, or the type of options or forms of entry that will be allowed when filling in this User Field. Existing User Fields that are in use can not have their "Field Type" changed; If the User Field is in use, the "Field Type" pick list is disabled. Options are:

• Character - Allows users to enter a text statement up to 60 characters in length.
• Date - Requires entry to be made in the following date format: 00/00/00 (month, day, and year can be entered in any order).
• Logical - Only allows a selection of "Y" for yes or "N" for no.
• Memo - Allows user to enter text, up to approximately 6,000 characters.
• Numeric - Requires user to enter a number value based on the format/value defined on the "Picture" field.
• Pick List - Used in connection with the “Edit Pick List” button and allows for the definition of an unlimited amount of pick list options.
• URL - allows users to create a URL Textbox user field designated with "link" symbol.
• Search Box - Used in connection with the "Search Box" and "Search Box Override" fields below to create a user field utilizing any existing search box in the system.

Defines the search box that will be used for the selected user field. Only available when using a Field Type of "Search Box." The list contains all active search boxes available in the system.

Option to override the filter on the search box with an expression, for example an SQL WHERE clause.

• All fields available to the search box are available for this expression.

Defines the minimum acceptable value that may be entered in this field when "Field Type" is set to "Numeric".

• Only enforced when the user modifies the value from its default value of 0 or if a non 0 default value is set in this field.

Defines the maximum acceptable value that may be entered in this field when "Field Type" is set to "Numeric".

• Only enforced when the user modifies the value from its default value of 0 or if a non 0 default value is set in this field.

Defines the format used to enter results in the field when "Field Type" is set to "Character" or "Numeric".

Memo field used to store a calculation for the selected User Field when flagged as "Calculated".

• When selecting a "File" option of "Item Master," the following fields are available: Dmprod fields including pr_id and User Fields, Dmcats and Dmcats2 fields, Category and Sub-Category User Fields.
• When selecting a "File" option of "Item Facility," the following fields are available: Dmprod3 fields and dmprod3 User Fields where p3_waid = the Facility that the user is viewing.
• The jo_id field is available when selecting a "File" option of "Job Header".

Option to set a default value, memo, or search value as it will appear in the system for the selected user field. Note: Setting a default value does not affect existing records, only new records created after the default has been set will be affected. For example, if you modify an existing Item Master User Defined Field and set a default value, this default value will not be populated on the user field of existing Item Master records, rather it will take effect when you create a new Item Master record.

• The fields available for use depend on the Field Type selected. For example, the Default Search Value field is only available when selecting a Field Type of "Search Box."
• Logical user fields use the Default Value field and should have 0 for False and 1 for True.
• Date user fields use the Default Value field and should use the syntax of mm/dd/yyyy

If checked, this record is active. Only active records may be used in the system.

If checked, indicates the field is not open for direct entry and will be populated based on a pre-defined User Calculation.

• Calculated User Fields may reference other User Fields in their calculation.
• All in_fields are available to calculated Sales Order User Fields.

If checked, a user must enter a value in this field when creating or modifying the "File" type for this User Field in the system.

If checked, values entered in this field cannot be the same or duplicates of other previous values entered for this field.

• When this field is checked, the "Copy To Backorder" flag is set to false and disabled.

If checked, when "Field Type" is set to "Pick List", pick list options for this User Field will be sorted alphabetically as opposed to the order in which they were created/are listed.

If checked, when "Field Type" is set to "Pick List", pick list options for this User Field will be displayed using the "Caption" selected (rather than the "Name" defined) in the Edit Pick List Item form.

If checked, the system will re-fire Sales Order User Calculations applicable to the order when the value in this User Field is modified.

• Available when "File" is set to "Sales Order Header" and for Sales Order Line user fields on the "Add" form.
• Example: A customer adds charges to Sales Orders based on the values inputted in certain Sales Order header User Fields. Assume the values in the User Fields are normally entered or updated when printing out the Sales pick list when drivers pull up to the shipping window. In this case, an option to have Sales Calculations fired when User Field values changed is required.

If checked, the user field will be available for use in the DSD application.

If checked, the value in the user field will be copied over when creating backorders.

• Only available when creating a Purchase Order Header, Purchase Order Line, Sales Order Header, or Sales Order Line user field.
• This field and the "Unique" field cannot both be checked.

Defines the text the will appear as the pick list option.

Memo field used to store a description of the option.

Search field used to select a Caption to use as the text that will appear as the pick list option.

Pick list used to select the general system process for which this Work Flow will be used. Options are:

• Bill-to Companies - used when managing Bill-to Companies via Sales > Customers.
• Contacts - used when managing Contacts via CRM > CRM Reporting.
• CRM Projects - used when managing CRM Projects via Tools > Workflow Reporting.
• Formulas - used when managing Formulas and Revisions via Inventory > Bills Of Material.
• Items - used when managing Parts via Inventory > Item Master.
• Jobs - used when managing orders via Production > Job Reporting.
• Journal Entries - used when managing journal entries via Accounting > Journal Entry or Accounting > Journal Entry Reporting > Add/Modify.
• Purchase Orders - used when managing orders via Purchasing > Order Reporting.
• Quality Control Groups - used when managing QC Groups via Inventory Maintenance > Quality Control Groups.
• Sales Orders - used when managing orders via Sales > Order Reporting.
• Ship-to Companies - used when managing Ship-to Companies via Customers.
• Ticket - used when managing tickets via CRM > Ticket Reporting.
• Vendors - used when managing Vendors via Purchasing > Vendors.

The name of the Work Flow, which will appear in the search box when selecting the Work Flow to add to a transaction or master data record.

Pick list used to determine which Sequence will be displayed as the next one to complete. Options are:

• After Last Completed - Points the user to the next uncompleted Sequence in the Work Flow.
• First Uncompleted - Points the user to the first uncompleted Sequence in the Work Flow.

For example, if there are four Sequences on the Work Flow, numbered 1-4 in order, and Sequence 3 is completed, this determines if Sequence 1 (shown by selecting "First Uncompleted") or Sequence 4 (shown by selecting "After Last Completed") will be shown as the next to complete. Note: The "Next Sequence Type" field also determines the colors that will Sales Orders will be displayed in when using the Sales Calendar. For example, if the first Sequence is set to the color green, the second Sequence set to red, the third Sequence set to blue, and the "Next Sequence Type" is "First Uncompleted," then when the second Sequence is completed, the order will display green on the Sales Calendar. Also, changing the value in the "Next Sequence Type" field is not retroactive. If Work Flows are setup sequentially, the first uncompleted Sequence will always be the same as the Sequence after the last completed Sequence.

If checked, this record is active. Only active records may be used in the system.

If checked, this will be the default Work Flow for the "Type" selected on forms throughout the system that contain a "Work Flow" field. Users may override the default if necessary.

Only selectable for Work Flows with a "Type" of "Formulas". If checked, the Work Flow on the Work Flow tab of the Formula will be reset any time the "Revision" name of a Formula is changed. This option is useful in situations where companies need to re-certify Formulas that have been changed.

• Not available when selecting a "Type" of "Journal Entries".

Name of the Work Flow Sequence.

Works in conjunction with User security to control which users have access to modify, complete, and return the Work Flow Sequence.

• Any value from 0 through 9 is allowed.

Controls which user, or users, will be able to approve this Work Flow Sequence on records throughout the system. Added primarily to prevent self approval. (i.e. to prevent users from approving Work Flow Sequences for records (Jobs, Sales Orders etc..) that they create. The field is available beginning in version 16.04.108. Options are:

• All Users - Same system behavior as before. The system will check the "Security Level" field above to determine if the user(s) have access to modify, complete, and return the Work Flow Sequence.
• Not Entered by User - The system will check the user that creatred the record the Work Flow is attched to against the user attempting to complete the Work Flow Sequence. If the users are different, the system will check the "Security Level" setting field as before. If the user is the same, the following prompt will be displayed: "This work flow sequence cannot be approved by the user that created this record."
• Not Entered by User Group - The system will check the User Group of the user that created the record the work flow is attached to against the user group of the user attempting to complete the work flow sequence. If the users are different, the system will check the "Security Level" setting field as before. If the User Group is the same, the following prompt will be displayed: "This work flow sequence cannot be approved by users in the user group."

Note: The Approve By setting in this field is checked against the user that created the BOM, Sales Order or Purchase Order, and the user completing the work flow sequence, not the user that created the work flow sequence or the user that attached the work flow sequence to the record.

Pick list used to specify the User responsible for completing the Work Flow Sequence.

Used to store an expression which will dynamically assign the work flow sequence to a user, instead of the hard-coded Assigned User of the previous field. Expression is only available to be edited if the Assigned User field is left empty, and must evaluate to an integer that is a currently (at the time of assignment) an active user ID. Functionality available in version 17.00.013 and higher. Example expressions:

• Assign to the user who originally created the purchase order (or requisition)
  • SQLVAL("lo_usid", "dxlog", "lo_table='dttpur' AND lo_recid = " + TRANS(tp_purnum), "N")
• Assign to the user who originally created the sales order (or quote), going back to the original copy of the order number, and not just the user who saved the most recent copy
  • SQLVAL("to_usid", "(SELECT TOP 1 to_usid FROM dttord WHERE to_ordnum=" + TRANS(to_ordnum) + " ORDER BY to_id ASC) temp", "1=1", "N")

Pick list used to specify the Sequence that the system will go back to when a user clicks the "Return To" button while modifying a Work Flow Sequence attached to a record.

• When the "Return To" button is clicked, all fields in between and including the current and Return To Sequences will be cleared of data.
• Useful if a process needs to be started from scratch or the Sequences should be re-completed for additional security.
• The "Return To" button is only available on Sequences that contain a value in the "Return To" field.
• Only selectable on Work Flow Sequences 2 and higher.

Allows the user to select the color that will be used to display the Order or Job in the Sales Calendar or Job Calendar.

• This field does not apply to the Sales Inventory, Job Inventory, or Master Production Calendars.

Used to store an expression that the system uses to automatically calculate the Planned date of completion for the selected Sequence.

• The calculation is fired when the Work Flow on a record is added or updated.
• Example: A calculation of “DATE() + 10” will set the Planned date to 10 days after the current date.

If a value is entered, the selected Sequence will only appear on the Work Flow of the record if the total order extension is greater than the value specified. If an order is originally configured with a total extension greater than the Minimum specified but is later modified and the total extension falls below the Minimum specified, the Sequence will be removed from the Work Flow on the order.

• Only available for Work Flows with a "Type" of "Sales Orders" or "Purchase Orders".
• Example: If a value of "50,000" is entered in this field, the Work Flow Sequence will not appear in the list of Work Flow Sequences located on the Work Flow tab of the Sales or Purchase Order until the total order extension has exceeded 50,000.

Stores additional details for the user, such as what needs to be done to complete the Sequence.

• When Notes are entered in this field, they will appear on the Edit Work Flow Sequences form when modifying this Sequence on the appropriate record (Sales Order, Formula, Job, etc.).

Used to store an expression that, if true, results in the Work Flow being applied per usual. If false, the Work Flow will not be applied.

• Useful if an order is entered with a total due that falls below the target margin. Instead of putting a hard stop on the order entry process, a Work Flow is utilized to control the process and put the order on hold until further review.
• Example: An expression of "to_totdue < 1000" that is applied to a Work Flow with a "Type" of "Sales Orders" will only be applied to new orders when the total due is less than 1,000.
• The fields available to use in the expression depend on the type selected on the Edit Work Flow form. All fields for the type's native table as well as user defined fields are available. For example, if the type is set to "Bill-to Companies," then all fields from the dmbill table as well as all Bill-to user defined fields can be used in the expression.

Optional. Used to specify the number of E-signatures required for this Work Flow Sequence.

• The "E-Signature Required" field must be checked to use the value specified in this field.
• For a given sequence, each e-signature must come from a unique user.
• The text field has a mask of "9" and 9 is the maximum value that may be entered in this field.
• Added in version 17.00.028. Useful in scenarios such as when an employee and supervisor must sign the Work Flow Sequence.
• When upgrading to version 17.00.028, the system will check for any Work Flow Sequences that have the "E-Signature Required" field checked and insert "1" in this field.

Pick list used to specify if Work Flow Sequences and any existing approvals should be copied to backorders. Only available when "Type" is set to "Purchase Orders" or "Sales Orders". Options are:

• Approval - The selected Work Flow Sequence WILL be copied to the back order, and WILL copy approvals onto the copied sequence.
• None - The selected Work Flow Sequence will NOT be copied to the back order.
• Sequence Only - The selected Work Flow Sequence WILL be copied to the back order, but will NOT copy approvals on the sequence.

If checked, this record is active. Only active records may be used in the system.

If checked, this Work Flow Sequence may only be completed once the Sequence directly before it has been marked as Complete.

• Example: If there are five Sequences to a Work Flow and the fourth and fifth are flagged as "Sequential", Sequence 4 may only be marked as Complete once Sequence 3 has been completed, and Sequence 5 may only be marked as Complete once Sequence 4 has been completed.

If checked, the Work Flow Sequence will function normally until the task with the Recurring End is completed. This will then place all tasks from Recurring Start to Recurring End back into the sequence. User must designate both a Recurring Start and Recurring End in order to save the sequence.

• Example: Sequence 2 is flagged Recurring Start, and Sequence 6 is flagged Recurring End. Once Sequence 6 is completed, Sequences 2-6 will return back into the Work Flow.
• Note: Only one task in the sequence can be flagged Recurring Start and Recurring End respectively, there cannot be multiple.

If checked and the Work Flow Sequence is marked as completed, the transaction (Sales Order, Purchase Order, or Formula) will be unable to be modified by other users. In order to unlock the order, the Sequence must be uncompleted by a user with the proper security. This field may only be checked if the "Type" field is set to Sales Order, Purchase Orders, or Formulas.

• When this flag is checked for a Work Flow with a "Type" of "Formula," users will still be able to uncheck the "Active" checkbox on BOMs.
• When a BOM Work Flow task has been completed, and this flag is checked, users will still be able to view, not edit, the Bill of Materials when attempting to modify the BOM. This allows users to access the Default Job Work Flow, Routing, and QC Groups attached to the formula in order to verify information after the Work Flow task has been completed.
• When editing a BOM, and after modifying and saving a Formula Work Flow that is marked as "Lock For Editing,", all fields on the Edit Bill of Materials form will be immediately disabled.
• When a Formula revision has been locked by a Work Flow sequence using the "Lock to Prevent Editing" option, the "QC Specs" button on the QC/Stability Tests tab will still be enabled allowing users to view and not edit the Formula's QC Specs. The "Default" and "Lab Only" flags can also be checked.
• If this flag is checked, for a sales order or purchase order type, and the work flow sequence has been completed, users will be unable to perform the following functions: delete, modify, or add new lines, copy order, mass delete, import Excel or perform the recalc prices option.
• This field will prevent a user form making changes to a temp entry, but still allow them to post it, assuming security allows.

If checked, when "Modify" is clicked on a Quality Control Group, the system checks to see if any Formulas have the QC group assigned that have a completed Work Flow Sequence with "Lock to Prevent Editing" checked. If so, the user is prompted with "This QC Group cannot be modified because the following formulas using this QC Group are locked: <<Display Part Number and Revision Name>>". The user is only able to click "OK" and return to the previous form.

If checked, when "Modify" is clicked on a Routing, the system checks to see if any Formulas have the Routing assigned that have a completed Work Flow Sequence with "Lock to Prevent Editing" checked. If so, the user is prompted with "This routing cannot be modified because the following formulas using this routing are locked: <<Display Part Number and Revision Name>>". The user is only able to click "OK" and return to the previous form.

If clicked, when "Modify" is clicked on a Work Flow for a Type of Jobs, the system checks to see if any Formulas have the Work Flow assigned that have a completed Work Flow Sequence with "Lock to Prevent Editing" checked. If so, the user is prompted with "This work flow cannot be modified because the following formulas with this work flow as the Default Job Work Flow are locked: <<Display Part Number and Revision Name>>". The user is only able to click "OK" and return to the previous form.

If checked, if a user clicks "Complete" without entering any notes for that sequence, the user will receive a prompt indicating "This sequence requires notes to be completed".

If checked, and the "Lab Only" flag is not checked on a Formula, when a Work Flow Sequence is not yet completed but applied to the Formula, the Formula cannot be saved unless the "Lab Only" flag is checked. The user is prompted with "This formula cannot be saved until the following work flow sequence is completed or the Lab Only checkbox is checked: <<Sequence Name>>". If the sequence is completed or the "Lab Only" flag is checked, the Formula can be saved.

If checked, the Work Flow Sequence is required to be completed before shipping a Sales Order.

If checked, the Work Flow Sequence is required to be completed before items may be picked from inventory/issued for the order, both in the Main Application and WMS.

• On Issue/Reserve Inventory form, the system will check for uncompleted Sequences with the "Required For Picking/Required to Issue" flag checked. For Sales Orders, it will prevent all the same shipping actions plus any picking actions, including printing pick lists and reserving inventory via WMS and the main application.
• Logic was added for Job Final Staging (in the Main Application and WMS via the Final Staging transaction) that applies only during the final iteration of staging for jobs. If any incomplete Work Flow Sequences on the job have this field checked, a system prompt/incomplete sequences form is displayed which blocks the staging operation from completing.

If checked, the Work Flow Sequence is required to be completed before receiving a Purchase Order.

If checked, no production can be completed on the Job, until this Sequence is marked as Complete.

• Reports and Job Labels may be printed even with this flag checked.

If checked, no job may be created in the system, until this Work Flow Sequence on the selected BOM revision is marked as Complete.

• Only available when selecting "Formulas" as a type.
• System checks this flag as parts are added to the job and prompts users accordingly. This allows users to take action without adding multiple parts to the job and then hitting the save button to validate the sequence(s) are marked as complete.

If checked, the Work Flow Sequence is required for a Sales Order to be marked with an "Order Type" of "Sales Order".

• Useful in preventing certain users from modifying a Sales Order into an order that is going to impact MRP or automatically create a Job through the header Job process.

If checked, the Work Flow Sequence is required for a Purchase Order to be marked with an "Order Type" of "Purchase Order".

• Useful in preventing certain users from modifying a Purchase Order into an order that is going to impact MRP.
• The system checks to see if new workflow sequences are added to existing POs that have this flag checked and that have other conditions, such as crossing a new higher minimum order extension enabled. In these situations, the system will only allow the user to save the order as a requisition, and not a purchase order, until the workflow has been approved. The exception to this is would be any time a PO order type is not allowed to be changed, for example when a pre-payment is applied to the PO.
• The "Drop Shipment Order Type" field (via Purchasing > Options) works in conjunction with this field when attaching/validating Work Flows on Drop Shipment Purchase Orders.

If checked, this Work Flow Sequence must before completed before a Job can be closed.

• This flag does not prevent material form being produced or relieved.

If checked, the system will copy all the Work Flow details from the original order to the backorders.

• Useful in situations where customers do not wish to have previous approvals and other information cleared when backorders are created.

If checked, the Work Flow Sequence is required for a QC Group to be marked with type "Quality Control Groups".

If checked, the Work Flow Sequence must be completed before a new journal entry, or existing temporary journal entry may be posted.