Appendix F Lists → List of Terms & Keywords
Keywords
A — C
Keyword:
A — C
Cryptography: Cryptography is a technique for ensuring secured-data transfers between the source and destination. To transfer data, two techniques are used.
Data Exchange: Specifies the data transfer such as EDI (Electronic Data Interchange) and X12.
D — F
Data Exchange: Specifies the data transfer such as EDI (Electronic Data Interchange) and X12.
Data exchange is the process of taking structured data from a source schema and transforming it under a target schema, so that the target data is an accurate representation of the source data. Various data structures are available such as EDI (Electronic Data Interchange), HL7 (Health Level-7), and X12. Therefore...
When you view/edit/create and then ultimately select a data-exchange type from a field option within the system, you are selecting the the schema for the EDI
The term "schema", relates to the word scheme, which originates from the Latin word for "figure." Therefore, a schema refers to the defining of each field and how incoming, or outgoing source data is "figure"-d (i.e., received, assessed and compartmentalized within the target schema).
Data Mapped:
Data Unmapped:
Decryption: The process of converting (cipher) text back into plain text (i.e., cipher text is turned into something readable) This is handled by the receiver.
Encryption: The process of translating plain text into cipher text (i.e., plain text is turned into something unreadable) – This is handled by the sender.
Facility: This is the name of your internal agency that the job belongs to. For instance, if Company A has three subsidiaries, the name of the subsidiary that a job originated from, or is being communicated to, is the name you want to choose.
File Name: Where "In File Name" is a generic template File Name is the name of the specific file that was processed. See In File Name description below.
G — K
In File Name: Files received by a job.
In File Name: This template field is used to describe the naming convention used for files received by a job. The actual name of the file may vary within the parameters set by the job, apparent in the In File Name itself.
For instance, a job set to Inbound File with an In File Name of "test_payment_updateyyyyMMdd.txt" will get a file named "test_payment_update20181121.txt" because the "yyyyMMdd" in the in file name is just filler text used to say that there is a year, month & day that will show up there.
Whether this is Static (i.e., the exact wording of incoming files), Dynamic (i.e., filler text of some kind like shown here), or REGEX (filler text with a function built into it) is determined by the selection made within the Inbound section on the Job Setup screen for that job.
In Path: See Input Path.
Input Path: The Input Path is where any inbound files for a specific job will be directed to and kept (i.e., stored). When setting up a job in the Job Setup screen, the Inbound step section has a selection field called "Input Path". The options within this selection field were created from the Path Configuration screen.
NOTE: If you do not see your path option within the Input Path field, you may have forgotten to create it. Exit Job Setup, or open a new browser window, and create your path within the Path Configuration screen first and then return to the Job Setup screen to select the newly created option. Remember to refresh your Job Setup screen if you created your new option via a separate browser window.
Inbound: Communication being transmitted into agency.
Invalid: Refers to the number of records within a file that were NOT processed successfully.
IP (i.e., IP Address): Refers to the IP (Internal Protocol) address of the remote system connecting to your computer.
Job: See Job ID
Job Name: Refers to the descriptive name given to a job. Usually is the name of the client. Not to be confused with File Name. NOTE: The job is what is doing the communicating and has its own name. The file is the information being communicated from the source and will have its own name as well. The two names are technically completely independent of each others. File names are sometimes similar to job names but that is merely a convention that EDI teams might sometimes use for clarity because the names of both are trying to be as descriptive as possible of the incoming information and process to handle that information.
Job ID: The unique identifier of a particular job. Not to be confused with File Name. NOTE: The job is what is doing the communicating and has its own name. The file is the information being communicated from the source and will have its own name as well. The two names are technically completely independent of each other. File names are sometimes similar to job names but that is merely a convention that EDI teams might sometimes use for clarity because the names of both are trying to be as descriptive as possible of the incoming information and process to handle that information.
L — Q
Not in Agency: A reconciliation job takes a client listing of accounts and compares that to the list of accounts listed within the facility for that client. If the list a client sent has an account listed that is not in the agency's listing for that client, it will be counted in this field. If you click on the number within this table's cell, you can view a listing of accounts located below this table for all the Not in Agency listings. Generally, reconciliation jobs will be set up with other supporting jobs that take this list and generate an account creation file for the accounts that the client shows should be listed in ARTrail but are not. The information from the account creation file would then be dropped into account staging ARTrail's Account Staging screen.
Not in Client: A reconciliation job takes a client listing of accounts and compares that to the list of accounts listed within the facility for that client. If the list a client sent does NOT have an account listed that is in the agency's ARTrail® listings for that client, it will be counted in this field. If you click on the number within this table's cell, you can view a listing of accounts located below this table for the Not in Client listings. Generally, reconciliation jobs will be set up with other supporting jobs that take this list and generate an account creation file for the accounts that the client shows are not listed in ARTrail.
Out File: Files sent by a job.
Out File Name: This template field is used to describe the naming convention used for files sent by a job. The actual name of the file may vary within the parameters set by the job, apparent in the Out File Name itself.
For instance, a job set to Outbound File with an Out File Name of "test_payment_updateyyyyMMdd.txt" will get a file named "test_payment_update20181121.txt" because the "yyyyMMdd" in the out file name is just filler text used to say that there is a year, month & day that will show up there.
Whether this is Static (i.e., the exact wording of incoming files), Dynamic (i.e., filler text of some kind like shown here), or REGEX (filler text with a function built into it) is determined by the selection made within the Outbound section on the Job Setup screen for that job.
* **Example: Job 9999**
* Under the Outbound screen, if the *Output Setting* is set to *Files,* the *Template Settings* form section appears.
Additionally, included in the *File Properties.* under *Template Settings,* there is a field called *File Name Format*. This field is greyed out because it will populate with whatever settings are entered in the *Attribute* table, located at the bottom of the *Template Settings* section. In other words, a user will select what parts of the file name they want and what goes in each part. Following is a listing of Columnar functionality:
* **Static:**: If "Static* is selected as the *attribute type*, the text in this part of the name will appear exactly as is entered under the "Value" column of the table. The *Format* field of this table, with an attribute of *Static* is not needed.
* **Dynamic_Date:**: If *Dynamic_Date* is selected as the *attribute type*, this portion of the file name will change based on the date and time the job is ran. Select your date/time format preference from the *Format* field. The *Value* field for this selection will be grayed out.
* **Set_Element:**: This is a portion of information that is furnished as an inbound element and will so depend on the content of the particular file that is run. The *Format* field will be diabled. Select your option from the *Value* field. -----
If there are 3 rows on the table (one of each with STATIC:"TEST",DYNAMIC:"MMdd",SET_ELEMENT:"CLIENT")
This job also has "File Extension" populated with ".txt"
Then for job 9999 ran on 12/13/2018 for client "CashCompany" the name would look like this:
TEST1213CashCompany.txt
This would then be the Out file Name. A file by this name will be delivered to the Out Path which may be somewhere owned by another company or just dropped on a local server. Notice the name may change based on the criteria set up so the out file name in places that are referring to the job in general will look more like: TESTMMddCLIENT.txt
Out Path: See Output Path
Outbound: Communication being transmitted out of agency.
Output Path: The Output Path is where any outbound files for a specific job will be sent to. When setting up a job in the Job Setup screen, the Outbound step section provides three radio-button options: Files, API or Databse. Every job whose outbound is set to File, needs to have an Output Path identified as to where it will be dropped, (i.e., sent to, dropped off at, etc.). If the File radio button is selected, a selection field will appear called, Output Path. The options within this selection field were created from the Path Configuration screen.
NOTE: If you do not see your path option within the Output Path field, you may have forgotten to create it. Exit Job Setup, or open a new browser window, and create your path within the Path Configuration screen first and then return to the Job Setup screen to select the newly created option. Remember to refresh your Job Setup screen if you created your new option via a separate browser window.
Path: Refers to the location of the path (url).
Path Name: Name given to identify a path.
Path Type: Refers to whether a path is: SFTP (Secure File Transfer Protocol), FTP (File Transfer Protocol), or (Folder) Net-Share folder.
Processed:
R — T
Received At: Refers to the date and time that any file was received by the agency.
Records: Refers to the number of records within a file.
Release Details: Refers to the details for any enhancements, additions and bug fixes.
Schema: Relates to the word scheme, which originates from the Latin word for "figure." Therefore, a schema refers to the defining of each field and how incoming, or outgoing source data is "figure"-d (i.e., received, assessed and compartmentalized within the target schema). In the RoboDX™ system, it is set up in the Destinatation Data Template and used within the Job Setup screens.
Source: Refers to where the data is coming from. In relation to reconciliation jobs, the source would be the client that is sending the information typically. A reconciliation job could be set up to compare a file from ABC company to an AAA Collections instance of AR Trail®. In this example, ABC company would be the source of the file.
Source Data Elements:
Target: Refers to where the data is going to or the table that an action is taking place on. In relation to reconciliation jobs, the target would be the database instance where the information is being looked for (usually an instance of ARTrail®). Example: A reconciliation job could be set up to compare a file from ABC company to an AAA Collections instance of AR Trail. In this example the ARTrail® instance of AAA collections would be the target of the job.
Template: Refers to how jobs, falling under a specific template will be formatted. For instance, when you create a new template, you set the Template Name, Input Path, Delimiter, Header, Trailer, File Extension, File Type and the Output Type as Individual or Consolidated, as well as the destination element for that particular destination template.
Template Name: Refers to the name of a template.
Total Elements: Refers to the total number of elements in each template.
Transaction Type: Refers to the type of transaction such as: New Accounts, New Loan Request, Cancellations, Payments, Balances, etc.
U — Z
Valid:
Keyword: