Changes

A [[An '''Autoloader''' is a SmartSimple]] feature used to automatically upload files of import data related to [[organization|companies]], [[contact]]s and or [[Universal Tracking Application]]s. This allows you the ability to automatically update information with data from external text files which can be vital if you need to keep customer or project data in sync with an existing legacy or enterprise resource planning (ERP) system.

An ==Overview==The '''Autoloader can be triggered whenever a file is added ''' feature provides the ability to a designated [[SmartFolder]]. These files can be added manually or uploaded automatically using the create/update SmartSimple information with data from an external file synchronization plug-in – [[SmartSync for Folder Synchronization|SmartSync]].A general overview of the process is as follows: 

* Once a file is added to the [[SmartFolders Overview|SmartFolder]]/[[SmartFolders_Overview#Configuration_Folders|Configuration Folder]], the autoloader Autoloader process will recognize that a file has been added and start the upload process.

* Each record from the upload uploaded file will update the associated record in the database.* A log file will be created indicates to indicate the success or failure of each record update and an email can be sent to a designated user indicating to notify them of the success (or failure) of the upload.* If a new version of the file is added to the folder, then this flag is reset and the new file will be processed.* You can create any number of Autoloaders within the system to provide for different upload processes.* An Autoloader can upload to different objects within your SmartSimple instance: [[organization|companies]],  [[contact]]s and , [[Universal Tracking Application]] {{l1}} or {{l2}} data, {{l3}},[[Category:Transactions|Transactions]], [[Notes_Overview|Notes]], [[Associations/|Associations]].

Before you can deploy this =Autoloader===Prerequisites==* You must be a {{GUA}} in your [[instance]] of SmartSimple to access the Autoloader feature it and set up an upload process.* The user uploading the file must have write permissions to the folder where the file is necessary to:be stored.* You '''must''' not use the upload folder for any purpose other than uploading files, as the autoloader will attempt to process any file added to the folder.

===Creating a SmartFolder/Configuration Folder===* Define the Any [[SmartFolders Overview|SmartFolder]], where /[[SmartFolders_Overview#Configuration_Folders|Configuration Folder]] can be used as the upload file will be storedsource for an Autoloader.* Define the format and layout of the data file – the number of columns in The folder must be used '''exclusively''' for the upload fileAutoloader, the delimiter between each field and the field order.* Specify a field in the upload since every file that the system uploaded will use to match an upload record to an existing customer recordbe processed.* Determine if you wish to use an automated process for Incorrect files by using the SmartSync utility or manually add the incorrectly formatted files '''will be processed''' and could lead to the folder. Each record in the upload file is used to update one set data loss and/or creation of fields in the entity to be updated.The existing value in the SmartSimple field will be replaced by the value on the field in the upload fileinvalid data.

==Creating a SmartFolder==* Any SmartFolder can be used as the source for an Autoloader.* The folder must be used '''exclusively''' for the Autoloader, since every file uploaded will be processed.* Incorrect files or incorrectly formatted files '''will be processed''' so could lead to data loss and/or creation of invalid data.'''IMPORTANT:  ''' Because any file uploaded to a [[SmartFolders Overview|SmartFolder ]]/[[SmartFolders_Overview#Configuration_Folders|Configuration Folder]] that is attached is associated to an autoloader will be processed , it is extremely important that the SmartFolder /Configuration Folder is permissioned and labelled appropriately.* SmartFolders for autoloaders should be permissioned such that only contacts that need to be able to upload files for autoloading are permitted to do so. * It is '''best practice''' to put all Autoloader enabled SmartFolders into a parent folder named '''Autoloader''' (with role-restricted access) to help ensure no inappropriate files are uploaded to the folder.

===Preparing the Upload Filefile to upload into the autoloader===Define the format and layout of the data file - the number of columns in the upload file, the delimiter between each field and the field order.

* This common field needs to be present in each record on the upload file and in each customer record. For instance, a unique account number field that you add to the customer table can be linked to the same account number field in the upload data.* The file to be uploaded must be in '''ASCII''' format. There is no specific file naming convention.

:This can be accomplished either using Notepad to create and edit the data for import which can be saved with '''txt''' as the file extension.:Alternately you can use the '''Save As''' feature within Microsoft Excel and save the document as a '''csv''' file.'''Notes:'''* If any of the data to be imported contains commas and you are creating a '''csv''' file from Excel you should export the data using pipes (|) as the separators rather than commas. To do this you need to change the settings on your PC prior to creating the '''csv''' file. The method of doing this depends on your PCs Operating System, but is roughly outlined below:

==Configuration - Essentials=Autoloader Constraints=These are the mandatory fields in creating a basic autoloader: 1. Essential settings in the '''General Tab'''<ul style="margin-left: 50px;"><li>Set the '''Loader Name'''</li><li>Select the '''Folder Type''': [[SmartFolders Overview|SmartFolder]] or [[SmartFolders_Overview#Configuration_Folders|Configuration Folder]]<li>Click the Folder Lookup button and select the folder assigned to this autoloader</li><li>Select the '''File Type'''</li><li>Select the '''File Encoding'''</li><li>Define the '''Record Type''' for this autoloader</li><li>Select '''Item''' of the '''Record Type'''</li><li>Activate the autoloader</li></ul>2. Essential settings in the '''File Layout Tab'''<ul style="margin-left: 50px;"><li>Select the '''Number of Columns''' - based on the file sample to be uploaded into this autoloader</li><li>'''Ignore Lines''' should be 1, if the file has header in row 1</li><li>Select '''Field Delimiter''' from the dropdown list</li><li>Define the column mapping based on the field columns of the file to the '''Record Type''' fields from the dropdown</li></ul><p style="margin-left: 50px;">Note that you can toggle the identifier if the file has a unique identifier.This will ensure integrity of the data being added/updated.</p>3. Essential settings in the '''Process Tab'''<ul style="margin-left: 50px;"><li>Go to the '''Create / Update Options''' section and select '''Create / Update Behaviour''' for the autoloader.</li></ul><p style="margin-left: 50px;">Once all three tabs have been configured, click on '''SAVE''' button.The autoloader is now ready to process the file that will be fed to the [[SmartFolders Overview|SmartFolder]] or [[SmartFolders_Overview#Configuration_Folders|Configuration Folder]] selected for this autoloader.</p> ==Configuration - Advanced=====Column Mapping===Once you have defined the number of fields, you define the field order to match the column order in the upload file. : [[Image:Auto9.png|thumb|none|900px]]* The '''number of columns''' you select determines the number of fields you can map.* '''Identifier'''. Enable the column that you have identified as the identifier.  This is important when you are updating existing records. Single/multiple field(s) is/are required to match an uploaded record to an existing record within the system.  * The''' Table header''' field is only required if you are using an XML or JSON file. You can fill out this section with the column headers of the file you want to upload.* '''Field '''is selected thru a dropdown box. (see the Reference section below for information on standard field names)  <span style="font-size: medium;">'''IMPORTANT:''' </span><br />The following fields must only be included in the Autoloader field mappings if you are updating '''existing''' records. These fields '''must not''' be a used when using the Auto Loader to create new records. ::* '''Company ID''' (Company Auto Loader)::* '''User ID''' (Contact Auto Loader)::* '''Resource ID''' (Resource Auto Loader)::* '''Tracking ID''' ({{l2}} / {{GUAl3}} in your Auto Loader)  * When using the fields above the IDs being Auto Loaded must match IDs of records present within the system.* If used the fields should be marked as the Identifier.* These fields would normally be used if you have extracted data from [[instanceSmartSimple]] including those ID fields, updated the data outside of [[SmartSimple ]] and wish to access import the updated information.  '''NOTE:'''   1. If you wish to deactivate a user using the Autoloader feature then select the '''Disable User Login (use value of 1)''' Field option and ensure that the uploaded file has a value of 1 in the relevant cells. 2. If the Item or App Level option is set to one of the Association options then you can only have Associations ID as identifier. The system we will force the Identifier when Associations ID is selected in mapping, and will only alert them when they try to set up an upload any other columns as identifier. ===Manual/Automated Autoloader=======Triggered by sending a file to the SmartFolder/Configuration Folder====  ====Automated Schedule====Here is a more detailed look at the automated [[Scheduler]]. ===Decryption===<!-- 128992 - PGP encryption keys added in the Integration Key Management-->PGP decryption is now available in the autoloader.PGP encryption and decryption keys should be added in the [[Integration Key Management|Integration_Key_Management]] section. To configure this setting, go to the autoloader configuration page and under the General tab go to the ''Decryption'' section, select from the dropdown list of the pgp keys to use for decrypting files before autoloader processthe file.* ===Uploading Specific Files to Specific Records in Bulk===The autoloader also allows you to upload specific files to specific records in bulk. Previously, if you had several files across multiple records that needed to be updated within a specific UTA, user , or company, finding each record and manually uploading those files would be tedious, especially if the files needed to be updated on a regular cycle. Now you can upload all the files in bulk and the system will unpack and distribute those files to the fields you specified accordingly. To use this feature, follow these steps: # Create a CSV file containing mandatory columns ('''File Name''' and '''Custom Field ID''') and the relevant identifier columns for the record type.# Create a ZIP file that contains the files you want to upload or replace. Make sure the ZIP file and the CSV file must have write permissions the same name.# Go to '''Menu Icon''' > '''Autoloaders''' > Create or edit an autoloader > Select the desired '''Processing Folder'''.# Set the '''File Type''' to “CSV, Text”.# Under '''Record Type''', select the desired record type you want to target ("UTA", "People", or "Company").# Under Item, select the new “File Upload” option. If you selected a UTA as a your '''Record Type''', you will be prompted to select the desired Level 1, 2, or 3.# Configure the column mappings as usual.# Upload the CSV and ZIP file to the processing folder where you selected in Step 3. <u>'''Note:'''</u> This new option does not create new records or update other columns. The “File Upload” item only uploads files.<!-- 143944 - New feature in autoloader to upload files -->[[File:2023-07-ticket-143944-1.png|thumb|none|800px|Use the new "File Upload" option to have the autoloader unpack a ZIP file and upload/replace files to specific upload fields as specified in a CSV file.]] [[File:2023-07-ticket-143944-2.png|thumb|none|800px|The CSV file must have the same name as the ZIP file and it must specify the record ID, upload field ID, and file name.]] ===External Data Source===This section allows for the configuration of an external file source if the user does not want to manually upload the file . [[Image:Autoloader_DS1.png ]] The '''External Data Source''' is a drop-down list with 5 options available: Additional fields are exposed when one of these options is selected, with the exact number and type of fields dependent on the selected option. ====FTP and SFTP====[[Image:AutoFTP2.PNG]] * '''Disable processing. Download file only''' - if checked then the system will only pull the file across into SmartSimple, but will not load the contents of the file* '''Delete File from Data Source After Downloaded''' - file will be deleted from the sftp site* '''Append Datetime Stamp to File Name''' - will append date and time when the file picked up from the sftp do not have a datestamp<!--see ticket 18426 - autoloader FTP settings-->* '''URL''' - the URL where the file(s) can be storedretrieved from. e.g. ''my.sftp.com'' or ''my.sftp.com:2222''* '''Login Name''' - username to allow access to the system* You '''mustLogin Password''' not use - password to allow access to the system* '''Use Private Key''' - enable this setting when using keys as credentials to authenticate* '''Private Key File''' - upload the private key file* '''Path''' - exact folder location on the system where the files can be found i.e. "/" for any purpose other than uploading root directory or "/in" or "/out"* '''File Names''' - name of the filesto be loaded via the Autoloader. e.g. HRFeed.csv, Payment_*.csv (Use '''*''' for wildcards in filenames. < br/> Note that when settings are saved, a '''Verify Connection''' button will appear next to the Login Name Textbox. This button can be used to verify that the url, username, password are correct. ====HTTP====[[Image:AutoHTTP.png]] * '''Disable processing. Download file only''' - if checked then the system will only pull the file across into SmartSimple, as but will not load the contents of the file <!--see ticket 18426 - autoloader FTP settings-->* '''URL''' - the URL where the file(s) can be retrieved from* '''File Names''' - name of the files to be loaded via the Autoloader ====SOAP====[[Image:AutoSOAP.png]] * '''Disable processing. Download file only''' - if checked then the system will only pull the file across into SmartSimple, but will attempt not load the contents of the file <!--see ticket 18426 - autoloader FTP settings-->* '''URL''' - the URL where the file(s) can be retrieved from* '''Login Name''' - username to process any file added allow access to the system* '''Login Password''' - password to allow access to the system* '''Function''' - The function called by the Web Service call.* '''Request Body''' - The content of the Web Service message to be sent to the external service.* '''Callback''' - Method to sends the response back to the client. ====OData====<!--Upgrade May 2018 - Ticket#62753-->[[Image:External-OData1.PNG]]* '''OData Version''' - Version of OData available from the endpoint* '''URL''' - the endpoint of OData* '''Login Name''' - username to allow access to the system* '''Login Password''' - password to allow access to the system ===File Preparation===This section allows for manipulation of the data prior to the folderAutoloader actually loading the data onto the system. It is only available when the '''File Type''' is either '''CSV,Text''' or '''Fixed Length Text'''. It is not available when '''File Type''' is XML. See [[Autoloader File Preparation]] for configuration instructions.

 :[[ImageFile:Auto3.pngPNG|thumb|none|400px]] ==='''Setting the SmartFolder===Folder Type''' * Click the Select Folder Lookup button to display the Type: [[SmartFolders Overview|SmartFolder]], list  or [[SmartFolders_Overview#Configuration_Folders|Configuration Folder]]* Click the Folder Lookup button to display the list.

==='''Setting the File Properties===''' 

The File Encoding can be UTF-8, UTF-16 or ANSI. This option is hidden if the File Type is XML.  :[[Image:AutoFile.png|thumb|none|400px]] ==='''Defining the Record Type===''' 

If the selected Record type is Company or Contact then the user is required to populate an additional Item field. The possible options here can include Company or Contact, Event ,Transactions, Address and TransctionsAssociations (User or Company) .

If the selected Record type is a [[UTA]] then the user is required to populate an additional Level field. The possible options here can include Level 1, Level 2, Level 3 , Transactions, L1 Company Association, L1 Contact Association, L2 Company Association and TransctionsL2 Contact Association.

:[[Image:Auto5.png|thumb|none|400px]]If the selected Record type is a [[UTA]] and the selected Level is Transaction then the user is required to populate an additional drop-down field reflecting all the levels that the transactions are enabled against.

If the selected Record type is a [[UTA]] and the selected Level is Transaction then the user is required to populate an additional drop-down field reflecting all the levels that the transactions are enabled against. :[[Image:Auto5b.png|thumb|none|400px]]'''Activate Autoloader'''

You must set the following additional settings::[[Image:Auto6.png]]* '''Activate''' – enables the Autoloader. Until Enable this check box is enabled for the Autoloader will not execute.* '''Trigger Formulas''' – enables the triggering of any template formulas that may exist for the selected record type and item/level. If this check box is not enabled then these formulas will not execute.* '''Delete First (use with caution)''' – all existing data will be deleted from the [[UTA]] level selected ('''This setting only applies to UTA data''').::* '''IMPORTANT''': Delete First is only used to delete UTA data where the data will be completely replaced with uploaded data. '''Use with caution'* '''Email Log To''' – Sets the email address of the person that you wish to receive a message every time the autoloader executes with a report of the upload process. Multiple email addresses can be included separated by commas. (Note: The log file is also stored in the same folder as the uploaded file.)* '''Frequency''' – drop-down list that allows the user to select when the autoloader should be run. Options are '''On File Upload''' or '''Scheduled'''. * '''Launch Hour''' - only displayed if '''Frequency''' is set to '''Scheduled'''. Sets the time on a daily basis that the autoloader will execute. This should be a comma delimited list of the hour values in 24-hour format.* '''Workflow before loader starts''' – drop-down list that contains a list of all workflows in the system. It defaults to No and if users wants to have a workflow execute before the autoloader adds the data to the system they should select the relevant workflow. * '''Workflow after loader ends''' – drop-down list that contains a list of all workflows in the system. It defaults to No and if users wants to have a workflow execute after the autoloader adds the data to the system they should select the relevant workflow.

The exact fields that are displayed vary depending on Autoloader can be connected an external data source to pull the '''Record Type''' file and '''Item''' or '''List''' values previously selectedmove the file to the SmartFolder.

====Company Record / Company Item====:[[ImageFile:Auto7Connectiontypes.pngPNG|thumb|none|400px]]* '''Create''' - If you wish to create new record, then enable the Create check box. If you do not enable this check box Select a connection type and new records are located in the upload file they will be rejected.* '''Account''' – determines where in the organisational hierarchy new records should be added.* '''Is External''' – choose this option when creating external companies under complete the root company.* ''Schedule'Category''' – determines the organisational category that you wish section below to be associated with specify the new records.* '''Trigger Workflow''' – drop-down list launch times of all workflows related to the '''Record Type'''. It defaults to N/A. * ''' Trigger On All Records ''' - check-box that is populated is you wish to have a workflow execute against all records, whether new records or updated records. This can be used to create companies with multiple categoriesautoloader everyday.

====Company or Contact Record / Event or Transaction Item====:[[Image:Auto7c.png]]* '''Create''' - If you wish The File Layout section is used to create new record, then enable determine the Create check box. If you do not enable this check box and new records are located number of columns in the upload file they will be rejected.* '''Type''' – drop-down list of all Event or Transaction types, depending on the exact '''Item''' selected. It defaults to N/A* '''Status''' – drop-down list of all Event or Transaction statuses, depending on and the exact '''Item''' selected. It defaults to N/A* '''Trigger Workflow''' – drop-down list that of all workflows related to the '''Record Type'''. It defaults to N/A. * ''' Trigger On All Records ''' - check-box that is populated if users wants to have a workflow execute against all records, whether new records or updated recordsField Delimiter.

====UTA Record / all Levels ='''Process''' tab===:[[Image:AutoloaderNewRecordUTAAuto6.png|link=]]* '''CreateWorkflow before loader starts''' – drop- If you wish to create new record, then enable down list that contains a list of all workflows in the Create check boxsystem. If you do not enable this check box It defaults to No and new records are located in if users wants to have a workflow execute before the Autoloader adds the data to the upload file system they will be rejectedshould select the relevant workflow.* '''TypeWorkflow after loader ends''' – drop-down list that contains a list of all Level 1, Level 2, Level 3 or Transaction types, depending on workflows in the exact '''Level''' selectedsystem. It defaults to N/ANo and if users wants to have a workflow execute after the Autoloader adds the data to the system they should select the relevant workflow.* '''StatusRun report after loader ends ''' – drop- drop-down list that contains a list of all Level 1, Level 2, Level 3 or Transaction statuses, depending reports in the system.  It will ran the configured '''Scheduled Export''' of the report.''' Frequency''' on the exact report should bet set to '''ItemOn Demand''' selected. It defaults to N/A* '''Run sequencial Autoloader after loader ends''' – [[Linking Autoloaders]]* '''Trigger WorkflowFormulas''' – drop-down list enables the triggering of all workflows related to any template formulas that may exist for the selected record type and item/level. If this check box is not enabled then these formulas will not execute.* '''Record TypeSend email with log when Autoloader is done'''– Sends email every time the Autoloader executes with a report of the upload process.(Note: The log file is also stored in the same folder as the uploaded file. It defaults )* '''Send email notification when Autoloader failed to Ncomplete''' – Sends email when ftp/Asftp connection failed, or when autoloader process was terminated unexpectedly. * ''' Trigger On All Records Send email with log when Autoloader has any failed records ''' - check-box that is populated if you wish Sends email when autoloader fails to have complete.* '''Email To''' – Sets the email address who will receive a workflow execute against all records, whether new records or updated recordsmessage. Multiple email addresses can be included separated by commas.

===Defining the Column Mapping=Create Options====This section of the Autoloader is used to determine how new records in the upload file should be handled.

Once you have defined the number of fields, you define the field order to match the column order in the upload file.:[[Image:Auto9.png]]* The number of columns you select determines the number of exact fields you can map.* The field name is selected from the Field combo box.* In order for the update to succeed, a single field is required to match an upload record to an existing database record this is indicated as the Identifier field. Customer data will generally be an account number type field.* The Table header field is only required if you that are using displayed vary depending on the HTML Table feature '''Record Type''' and '''Item''' or when loading an XML or JSON file.* The '''Duplicate Match BeahviourList''' drop-down allows user to specify the behaviour whenever multiple records are matched using the Identifier field(s)values previously selected. :* Update Unique Match Only - will only update when one matching record is found:* Update All Matches - will update all matching records

<font size="3">====Company Record / Company Item=====: [[Image:Auto7.png]]* '''IMPORTANT:Create/Update Behavior''' </font><br>The following fields must only be included in - If you wish to create new record, then enable the Autoloader field mappings if '''Create new or update matching record''''' check box. If you are updating enable the other check box '''''existingUpdate only, do not create new''' , existing recordswill be updated but new records will be rejected. These fields * '''must notDuplicate Match Behavior''' be used - behavior when multiple records are matched by the same identifier key. Drop-down allows user to specify the behaviour whenever multiple records are matched using the Auto Loader to create Identifier field(s).** Update Unique Match Only - will only update when one matching record is found** Update All Matches - will update all matching records* '''Account''' – determines where in the organisational hierarchy new recordsshould be added.::* '''Company IDIs External''' (Company Auto Loader)– choose this option when creating external companies under the root company.::* '''User IDCategory''' (Contact Auto Loader)– determines the organisational category that you wish to be associated with the new records.::* '''Resource IDTrigger Workflow''' – drop-down list of all workflows related to the '''Record Type' (Resource Auto Loader)''. It defaults to N/A.::* '''Tracking IDTrigger On All Records ''' ({{l2}} / {{l3}} Auto Loader)- check-box that is populated is you wish to have a workflow execute against all records, whether new records or updated records. This can be used to create companies with multiple categories.

=====Contact Record / Contact Item=====: [[Image:Auto7b.png]]* When using '''Create/Update Behavior''' - If you wish to create new record, then enable the fields above '''Create new or update Matching record''' check box. If you do not enable the IDs being Auto Loaded must match IDs of other check box '''Update only, do not create new''' existing records will be updated but new records will be rejected.* '''Duplicate Match Behavior''' - behavior when multiple records present within are matched by the systemsame identifier key.* If used '''Account''' – determines where in the fields organisational hierarchy new records should be marked as the Identifieradded.* These fields would normally '''Role''' – determines a user role that you wish to be used if associated with the new records. If you wish to have multiple roles associated with a user then you will need to trigger a workflow against each record (see below for further details).* '''Trigger Workflow''' – drop-down list that of all workflows related to the '''Record Type'''. It defaults to N/A.* ''' Trigger On All Records ''' - check-box that is populated is users wants to have extracted data from [[SmartSimple]] including those ID fieldsa workflow execute against all records, whether new records or updated the data outside of [[SmartSimple]] records. This can be used to activate users with multiple roles and wish to import the updated informatione-mail a password to newly created contacts automatically.

NOTE=====Company or Contact Record / Event or Transaction Item=====: If [[Image:Auto7c.png]]* '''Create/Update Behavior''' - If you wish to deactivate a create new record, then enable the '''Create new or update Matching record''' check box. If you do not enable the other check box '''Update only, do not create new''' existing records will be updated but new records will be rejected.* '''Duplicate Match Behavior''' - behavior when multiple records are matched by the same identifier key. Drop-down allows user to specify the behaviour whenever multiple records are matched using the Autoloader then select Identifier field(s).** Update Unique Match Only - will only update when one matching record is found** Update All Matches - will update all matching records* '''Type''' – drop-down list of all Event or Transaction types, depending on the exact '''Item''' selected. It defaults to N/A* '''Status'''Disable User Login (use value – drop-down list of 1)all Event or Transaction statuses, depending on the exact '''Item''' selected. It defaults to N/A* '''Trigger Workflow''' Field option and ensure – drop-down list that of all workflows related to the uploaded file has '''Record Type'''. It defaults to N/A.* ''' Trigger On All Records ''' - check-box that is populated if users wants to have a value of 1 in the relevant cellsworkflow execute against all records, whether new records or updated records.

==Updating Account Owners===UTA Record / all Levels=====: [[Image:AutoloaderNewRecordUTA.png|link=]]* '''Create/Update Behavior''' - If you wish to create new record, then enable the '''Create new or update Matching record''' check box. If you do not enable the other check box '''Update only, do not create new''' existing records will be updated but new records will be rejected.* '''Duplicate Match Behavior''' - behavior when multiple records are matched by the same identifier key. Drop-down allows user to specify the behaviour whenever multiple records are matched using the Identifier field(s).** Update Unique Match Only - will only update when one matching record is found** Update All Matches - will update all matching records* '''Type''' – drop-down list of all Level 1, Level 2, Level 3 or Transaction types, depending on the exact '''Level''' selected. It defaults to N/A* '''Status''' – drop-down list of all Level 1, Level 2, Level 3 or Transaction statuses, depending on the exact '''Item''' selected. It defaults to N/A* '''Trigger Workflow''' – drop-down list of all workflows related to the '''Record Type'''. It defaults to N/A.* ''' Trigger On All Records ''' - check-box that is populated if you wish to have a workflow execute against all records, whether new records or updated records.

====Updating Account Owners====When you are updating company type information you can automatically associate an account field to a user field in order to establish “account ownership”. This section is only displayed at the bottom of the Autoloader page if you have set the Record Type to Company and Item to company.:[[Image:Auto10a.png]]:''For example, if the imported account file contains an employee ID field, then this can be matched to the user table – providing each user with an employee ID field.''

====Updating Account Parent====

: [[Image:Auto10b.png]]<br />: ''For example, if the imported account file contains a parent ID field, then this can be matched to the account table – providing each company with a parent company.''<br />: '''Example: Updating Account Parent AutoLoader Configuration Example:'''<br />: [[File:Update_Account_Parent_Example.JPG]]<br />: '''The AutoLoader Parent ID field is an Account field that will get populated with the second value (Parent ID) from the CSV record below.'''<br />: '''Example: AutoLoader Source File Example:'''<br />: [[File:Update_Account_Parent_Example_-_Source_File.JPG]]<br />: '''Action: A two column report with the Company ID and the Parent ID needs to be created, exported to a CSV file and uploaded to the associated AutoLoader SmartFolder. '''<br />: Result: The Account records with a Company ID IN (278520,297733,316703) will have their Parent ID changed to 349238.

====Updating Event / Transaction Parent Company ====When you are updating company type information related to an Event or a Transaction you can automatically associate an account field to a transaction or event field in order to establish a parent for the transaction. This includes using Account standard fields.If no matches exist then you can select the required action using the '''No parent matched action''' drop-down. * Reject Record - record is not loaded into the system* Add as orphan record - record is loaded into the system but without being attached to a parent company* Attach to dummy account - record is loaded into the system and is attached to the parent company specified in the '''Default Parent ID''' field.

When you are updating people type information you can automatically associate an account field to a user field in order to attach the user to the correct account. This section is only displayed at the bottom of the Autoloader page if you have set the Type to People.:[[Image:Auto10fAuto10c.png]]

====Updating Event / Transaction Parent User====When you are updating user type related to a Transaction information you can automatically associate a user field to a transaction field in order to establish a parent user for the transaction.

This section * Reject Record - record is only displayed at not loaded into the bottom of system* Add as orphan record - record is loaded into the Autoloader page if you have set system but without being attached to a parent company* Attach to dummy account - record is loaded into the '''Record Type''' system and is attached to People and the parent company specified in the '''ItemDefault Parent ID''' to either Event or Transaction.:[[Image:Auto10dfield.png]]

==Branch, Company This section is only displayed at the bottom of the Autoloader page if you have set the '''Record Type''' to People and Owner Custom Field Matching==the '''Item''' to either Event or Transaction.

When you are updating UTA information you can automatically associate a standard field on the UTA with user and company fields in order to establish individual or organizational ownership. This section is only displayed at the bottom of the Autoloader page if you have set the Record Type to [[UTAImage:Auto10f.png]] and the Level to Level 1.

:====Branch, Company and Owner Custom Field Matching====When you are updating UTA information you can automatically associate a standard field on the UTA with user and company fields in order to establish individual or organizational ownership. This section is only displayed at the bottom of the Autoloader page if you have set the Record Type to [[Image:Auto10e.pngUTA]]and the Level to Level 1.

====Updating Tracking Parent====When you are updating UTA Level 2 or 3 information you can automatically associate a field on the level 2 with a field on the level 1, or associate a field on the level 3 with a field on the level 1, in order to establish a relationship between the entities.

* Attach to dummy account - record is loaded into the system and is attached to the parent entity specified in the Default Parent ID field.  

:[[Image:Auto10g.png]]  ==Parent record match field ids==

:[[Image:AutoXML.png]] ==File Preparation== This section allows for manipulation of the data prior to the Autoloader actually loading the data onto the system. It is only available when the '''File Type''' is either '''CSV,Text''' or '''Fixed Length Text'''. It is not available when '''File Type''' is XML. See [[Autoloader File Preparation]] for configuration instructions.

:[[Image:AutoFilePreparation====Ad hoc upload url====This is an Autoloader setting that provides a more friendly and accessible user interface for importing data into the system as well as allowing users to verify the file before uploading it to a SmartFolder for processing by the Autoloader. This feature is intended to be used when External Data Source is not configured.png]]

This section allows for ==='''History''' Tab===<span style="color: #ff0000;">Available after February 2019 upgrade.</span> <br/>A new Autoloader feature that shows a new History information tab. The list includes the configuration of an external file source if the name, user does not want to manually upload who uploaded the file, start time, end time, records added/updated and status of last run.

:[[Image:AutoDataSourceAutoloader-History.pngPNG]]

The * '''#''' - item number* '''File''' - filename that was processed. If the file is deleted from the SmartFolder, the filename will not be displayed on the list.* '''Uploaded By''' - name of the user who uploaded the file* '''Start Time''' - date and time the file was processed* '''End Time''' - date and time the file was completed* '''Added''' - number of records that were added* '''Updated''' - number of records that were updated* '''Failed''' - number of records that failed to update/add* '''Status''' - status of the process.   ** '''''Processing''''' - the file is currently being processed and is not yet complete** '''''Completed''''' - the file was successfully processed and was completed** '''''Interrupted''''' - the process was terminated i.e. GORT was terminated abruptly (someone restarted the server)** '''''External Data SourceProblem''''' is a drop -down list the file has data problem i.e. pound sign at the start of the column . data with 4 options available:# should be enclosed in double quotes e.g. ,"another column","#111 Peter Street","another column",** '''''Connection Failed''''' - external data source connection failed** '''''No file / download file failed''''' - connection was established but no file was existing in the external data source subfolder:* FTP* '''''File problem''''' :* HTTP* '''''File failed pre-processing''''' ** '''''Error processing file''''' :* SFTP* '''''Wrong file type''''' :* SOAP'''Process ID''' - unique identifier of the process

===FTP and SFTPHR Feed autoloader===

* Disable processing. Download file only - if checked ===Example how to use '''''ad hoc upload url'''''===When you click on the Upload File button then the system you will only pull the file across into SmartSimple, but will not load the contents be presented with page one of the file <!--see ticket 18426 - autoloader FTP settings-->* URL - the URL where Ad Hoc Autoloader screen. Use the 'Choose file(s) can be retrieved from * Login Name - username to allow access ' button to select the system * Login Password - password to allow access to the system * Path - exact folder location on the system where the files can be found * File Names - name of the files file to be loaded via and then click the Autoloader'Upload' button.

:[[Image:AutoHTTPYou will be presented with page 2 of the Ad Hoc Autoloader screen, which provides users the option to review the file being uploaded, including what data us being mapped to what field.png]]

* Disable processing[[Image:AdhocAutoload2. Download file only - if checked then the system will only pull the file across into SmartSimple, but will not load the contents of the file <!--see ticket 18426 - autoloader FTP settings-->* URL - the URL where the file(s) can be retrieved from * File Names - name of the files to be loaded via the Autoloaderpng|100.px|border]]

:[[Image:AutoSOAPAdhocAutoload3.png|100.px|border]]

===Important note about XML Files===

* *:<span style="font -size="2: small;">&lt;![CDATA[ '''''CONTENTS''''' ]]></fontspan>

<firstname>Jane</firstname> <lastname>Smith</lastname> <address><![CDATA[145 Main Street]]></address> <companyname><![CDATA[Acme & Friends]]></companyname>

* It is advisable to use CDATA for any field containing text since ===Note about JSON Files===JSON format should start with a '''data''' node, as shown in the contents are often unpredictable. example below

==Note about JSON Files==JSON format should start with a '''data''' node, as shown in the example below<pre>{

==Ad hoc upload url=Reference: Standard Field Names and Variables===The below table can be used to compare Level 1 Standard Field terminology found in the [[UTA]], on the Autoloader, in the Database, and Variable syntax]]

This is an {||-| style="background-color: #c8c8c8;"|'''UTA L1 Standard Field Name '''| style="background-color: #c8c8c8;"|'''Autoloader setting that provides Standard Field Name'''| style="background-color: #c8c8c8;"|'''Database name'''| style="background-color: #c8c8c8;"|'''Variable List'''|-| style="background-color: #f0f0f0;"|n/a more friendly and accessible user interface for importing data into the system as well as allowing users to verify the file before uploading it to a SmartFolder for processing by the Autoloader| style="background-color: #f0f0f0;"|Level 1 ID| style="background-color: #f0f0f0;"|opportunityid| style="background-color: #f0f0f0;"|@opportunityid@|-| style="background-color: #dcdcdc;"|Application Type| style="background-color: #dcdcdc;"|Type Name| style="background-color: #dcdcdc;"|opportunitytypename| style="background-color: #dcdcdc;"|@type@|-| style="background-color: #dcdcdc;"| | style="background-color: #dcdcdc;"|Type ID| style="background-color: #dcdcdc;"|opportunitytype| style="background-color: #dcdcdc;"|@typeid@|-| style="background-color: #f0f0f0;"|Application Name| style="background-color: #f0f0f0;"|Name| style="background-color: #f0f0f0;"|name| style="background-color: #f0f0f0;"|@name@|-| style="background-color: #dcdcdc;"|Customer| style="background-color: #dcdcdc;"|Client| style="background-color: #dcdcdc;"|company| style="background-color: #dcdcdc;"|@client@|-| style="background-color: #dcdcdc;"| | style="background-color: #dcdcdc;"|Client ID| style="background-color: #dcdcdc;"|companyid| style="background-color: #dcdcdc;"|@clientid@|-| style="background-color: #dcdcdc;"| | style="background-color: #dcdcdc;"|Client Custom Field| style="background-color: #dcdcdc;"|companycfield| style="background-color: #dcdcdc;"| |-| style="background-color: #f0f0f0;"|Status| style="background-color: #f0f0f0;"|Status| style="background-color: #f0f0f0;"|stagename| style="background-color: #f0f0f0;"|@status@|-| style="background-color: #f0f0f0;"| | style="background-color: #f0f0f0;"|Status ID| style="background-color: #f0f0f0;"|stageid| style="background-color: #f0f0f0;"|@stausid@|-| style="background-color: #dcdcdc;"|Revenue| style="background-color: #dcdcdc;"|Revenue| style="background-color: #dcdcdc;"|revenue| style="background-color: #dcdcdc;"|@revenue@|-| style="background-color: #f0f0f0;"|Currency| style="background-color: #f0f0f0;"| | style="background-color: #f0f0f0;"| | style="background-color: #f0f0f0;"| |-| style="background-color: #f0f0f0;"| | style="background-color: #f0f0f0;"|Currency (USD,CAD etc.)| style="background-color: #f0f0f0;"|currencyid[[Image| style="background-color:AdhocAutoload#f0f0f0;"|@currencyname@/ @currencycode@|-| style="background-color: #f0f0f0;"| | style="background-color: #f0f0f0;"|Currency Exchange (USD,CAD etc.png)| style="background-color: #f0f0f0;"|excur| style="background-color: #f0f0f0;"|@excurrencycode@/ @excurrencyname@|-| style="background-color: #f0f0f0;"| | style="background-color: #f0f0f0;"|Exchange Rate| style="background-color: #f0f0f0;"|excur_rate| style="background-color: #f0f0f0;"|@exrate@|-| style="background-color: #dcdcdc;"|Close Date| style="background-color: #dcdcdc;"|Close Date (yyyy-mm-dd)| style="background-color: #dcdcdc;"|closedate| style="background-color: #dcdcdc;"|@closedate@|-|borderstyle="background-color: #f0f0f0;"|100Probability| style="background-color: #f0f0f0;"|n/a| style="background-color: #f0f0f0;"| | style="background-color: #f0f0f0;"|@probability@|-| style="background-color: #dcdcdc;"|Description| style="background-color: #dcdcdc;"|Description| style="background-color: #dcdcdc;"|description| style="background-color: #dcdcdc;"|@description@|-| style="background-color: #f0f0f0;"|Requirement| style="background-color: #f0f0f0;"|n/a| style="background-color: #f0f0f0;"| | style="background-color: #f0f0f0;"|@requirements@|-| style="background-color: #dcdcdc;"|Owner| style="background-color: #dcdcdc;"| | style="background-color: #dcdcdc;"| | style="background-color: #dcdcdc;"| |-| style="background-color: #dcdcdc;"| | style="background-color: #dcdcdc;"|Owner ID| style="background-color: #dcdcdc;"|updatedby| style="background-color: #dcdcdc;"|@ownerid@|-| style="background-color: #dcdcdc;"| | style="background-color: #dcdcdc;"|Owner (firstname lastname)| style="background-color: #dcdcdc;"|updatedbyname| style="background-color: #dcdcdc;"|@owner@|-| style="background-color: #dcdcdc;"| | style="background-color: #dcdcdc;"|Owner Email| style="background-color: #dcdcdc;"|updatedbyemail| style="background-color: #dcdcdc;"|@owner.px]]email@|-| style="background-color: #dcdcdc;"| | style="background-color: #dcdcdc;"|Owner Custom Field| style="background-color: #dcdcdc;"|updatedbyfield| style="background-color: #dcdcdc;"| |-| style="background-color: #f0f0f0;"|Branch| style="background-color: #f0f0f0;"|Branch| style="background-color: #f0f0f0;"|branch| style="background-color: #f0f0f0;"|@branch@|-| style="background-color: #f0f0f0;"| | style="background-color: #f0f0f0;"|Branch ID| style="background-color: #f0f0f0;"|branchid| style="background-color: #f0f0f0;"|@branchid@|-| style="background-color: #f0f0f0;"| | style="background-color: #f0f0f0;"|Branch Custom Field| style="background-color: #f0f0f0;"|branchcfield| style="background-color: #f0f0f0;"| |-| style="background-color: #dcdcdc;"|Workflow| style="background-color: #dcdcdc;"|n/a| style="background-color: #dcdcdc;"|n/a| style="background-color: #dcdcdc;"|n/a|-| style="background-color: #f0f0f0;"|ContactsWhen you click | style="background-color: #f0f0f0;"|n/a (added Import Contacts on the Upload File button then you will be presented with page one of the Ad Hoc Autoloader screenUTA)| style="background-color: #f0f0f0;"|n/a| style="background-color: #f0f0f0;"|n/a|-| style="background-color: #dcdcdc;"|Activity List| style="background-color: #dcdcdc;"|n/a (needs separate autoloader)| style="background-color: #dcdcdc;"|n/a| style="background-color: #dcdcdc;"|https://wiki. Use the 'Choose file' button to select the file to be loaded and then click the 'Upload' buttonsmartsimple. com/wiki/Web_Page_View_Field_Variables|-| style="background-color: #f0f0f0;"|End Date| style="background-color: #f0f0f0;"|End Date (yyyy-mm-dd)| style="background-color: #f0f0f0;"|oenddate| style="background-color: #f0f0f0;"|@enddate@|-| style="background-color: #dcdcdc;"|Start Date| style="background-color: #dcdcdc;"|Start Date (yyyy-mm-dd)| style="background-color: #dcdcdc;"|ostartdate| style="background-color: #dcdcdc;"|@startdate@|-| style="background-color: #f0f0f0;"|Modified Date| style="background-color: #f0f0f0;"|n/a| style="background-color: #f0f0f0;"| | style="background-color: #f0f0f0;"|@modifieddate@|-| style="background-color: #dcdcdc;"|Institutions| style="background-color: #dcdcdc;"|n/a (needs a workflow)| style="background-color: #dcdcdc;"| [[Image| style="background-color: #dcdcdc;"|https:AdhocAutoload1//wiki.smartsimple.pngcom/wiki/Web_Page_View_Field_Variables|-| style="background-color: #f0f0f0;"|End Time| style="background-color: #f0f0f0;"|n/a| style="background-color: #f0f0f0;"| |borderstyle="background-color: #f0f0f0;"|100@hour(fullenddate)@:@minute(fullenddate)@|-| style="background-color: #dcdcdc;"|Start Time| style="background-color: #dcdcdc;"|n/a| style="background-color: #dcdcdc;"| | style="background-color: #dcdcdc;"|@hour(fullstartdate)@:@minute(fullstartdate)@|-| style="background-color: #f0f0f0;"|Person| style="background-color: #f0f0f0;"| | style="background-color: #f0f0f0;"| | style="background-color: #f0f0f0;"| |-| style="background-color: #f0f0f0;"| | style="background-color: #f0f0f0;"|Person ID| style="background-color: #f0f0f0;"|oppeopleid| style="background-color: #f0f0f0;"|@personid@|-| style="background-color: #f0f0f0;"| | style="background-color: #f0f0f0;"|Person (firstname lastname)| style="background-color: #f0f0f0;"|oppeoplename| style="background-color: #f0f0f0;"|@person@|-| style="background-color: #f0f0f0;"| | style="background-color: #f0f0f0;"|Person Email| style="background-color: #f0f0f0;"|oppeopleemail| style="background-color: #f0f0f0;"|@person.px]]email@|-| style="background-color: #f0f0f0;"| | style="background-color: #f0f0f0;"|Person Custom Field| style="background-color: #f0f0f0;"|oppeoplefield| style="background-color: #f0f0f0;"| |-| style="background-color: #dcdcdc;"|UTA ProvidersYou will be presented with page 2 of the Ad Hoc Autoloader screen, which provides users the option to review the file being uploaded, including what data us being mapped to what field| style="background-color: #dcdcdc;"|n/a (needs a workflow task)| style="background-color: #dcdcdc;"| | style="background-color: #dcdcdc;"|https://wiki.smartsimple. com/wiki/Web_Page_View_Field_Variables|-[[Image| style="background-color:AdhocAutoload2#f0f0f0;"|Status Indicator| style="background-color: #f0f0f0;"|n/a| style="background-color: #f0f0f0;"| | style="background-color: #f0f0f0;"|n/a|-| style="background-color: #dcdcdc;"|Transactions| style="background-color: #dcdcdc;"|n/a (needs separate autoloader)| style="background-color: #dcdcdc;"| | style="background-color: #dcdcdc;"|https://wiki.smartsimple.pngcom/wiki/Web_Page_View_Field_Variables|-| style="background-color: #f0f0f0;"|borderUTA Providers (L2)|100.px]]style="background-color: #f0f0f0;"|n/a| style="background-color: #f0f0f0;"| If there is no issue with the data and the mappings then click on the 'Add to SmartFolder and Autolader queue' button| style="background-color: #f0f0f0;"|https://wiki. You should be presented with page 3 of the Ad Hoc Autoloader screen, which confirms that the file has been successfully added to the SmartFoldersmartsimple. com/wiki/Web_Page_View_Field_Variables|-[[Image| style="background-color:AdhocAutoload3.png#dcdcdc;"|Modified By| style="background-color: #dcdcdc;"|n/a| style="background-color: #dcdcdc;"| | style="background-color: #dcdcdc;"|@modifiedby@/ @modifiedbyid@|-| style="background-color: #f0f0f0;"|Created Date| style="background-color: #f0f0f0;"|n/a| style="background-color: #f0f0f0;"| | style="background-color: #f0f0f0;"|@createddate@|-| style="background-color: #dcdcdc;"|Created By| style="background-color: #dcdcdc;"|n/a| style="background-color: #dcdcdc;"| | style="background-color: #dcdcdc;"|n/a|-| style="background-color: #f0f0f0;"|Invitations| style="background-color: #f0f0f0;"|n/a| style="background-color: #f0f0f0;"| |borderstyle="background-color: #f0f0f0;"|100.px]]n/a|}