Popular Search how tohow to useagenthowdatarestbatchcustomskyvvasap
View Categories

1. Features

Button ‘New Property’ for creating new properties file is Agent #

  • When the user goes to Agent UI and then clicks on Integration Properties Setup it carries a button to create a new Property file.
  • This button is capable to create a new ‘Property File’ during the user wants to use another org.

The file name with Merge file. #

For an Outbound interface, Agent UI should carry the field File Name as like an inbound interface.
If the user wants to put the file name, the user must check on the merge file for an outbound interface on Agent UI.

Property File Cannot be Duplicated #

When the user creates a property file that carries the same credentials/username, password, and security token it cannot create.
When the user clicks on the save button it will be alerted that the message “Username” has already existed.

Web Service call through Agent #

  • ENHANCED CONNECTIVITY
    Support for flat files with any delimiter Connect to any ODBC or JDBC database complete web services support, including the Bulk API
  • ADVANCED FUNCTIONALITY
  • Excel-like functions allow users to transform their data, including concatenations, substrings, and trims parallel processing provides unmatched performance, including support for Bulk loads
  • EASY AUTOMATION & MANAGEMENT
    Set operations on a schedule to automate data loads Management console provides full logging and operation history.

The initial mode does not work with the auto-switch mode #

  • Currently, the initial mode is working with Batch and Bulk modes. For auto-switch mode is not working.
  • Integrate Max Size: Maximum number of records that the SKYVVA Integration Agent can integrate is bigger than this value; the Agent will switch data to Batch automatically.
  • Integrate Batch Max Size: Maximum number of records that SKYVVA Integration using method integrates Batch. If the number of records to be integrated is bigger than these values, the Agent will switch to using the Bulk API method automatically.

Retrieve more than 50K records from Salesforce with Agent Outbound Processing #

POWERFUL DATA OPERATIONS

  • Wizard-based point & click configuration Support for Insert, Update, Upsert, Query, Delete, and Bulk operations Save, edit, and reprocess operations, connections, and data mappings.
  • Users need to retrieve more than 50,000 records with Agent Outbound Processing. If the user needs to retrieve more records, we recommend you work with a Salesforce.com partner. Users need to retrieve an object that is not yet supported by web-based importing.

New properties name “Replace Header” in adapter type File with file type CSV #

There are basically two types of header files, standard header files, and user-defined header files. Standard header files consist of header files for strings, numeric, mathematical functions, language support, and algorithms. Despite the user-defined header files being created by users. For two Objects (Account contact) in the CSV file use dot”.” to specify between the object and field name. The question here dot is not allowed in the header CSV file and Agent with replace it with to underscore “_”. Regarding backward ability with the old customer we need to add new properties file name “Replace Header” with a default value is old functionality.

Update the Next Run Date after the schedule setting is changed in the Agent UI #

  • We are using these functions in conjunction, be aware that the time zone returned is the one configured on the machine running the agent. All Cloud Agents are in UTC. Private Agents will vary based on the specific machine each agent is running on. If the user is using a conversion function take this into account if your project is designed to run both in the cloud and on a Local Agent.
  • We update Salesforce with the new calculated Run date which we read from the crone file of the local Agent. So what we need to do is to write the new time definition whenever the user changes the schedule setting in Agent. After he has saved the setting we need to push the data to Salesforce immediately. It doesn’t matter if the user restarts the service or not.
  • The user could just save the scheduled setting without restarting the service. In this case, we also need to see the new time definition in Salesforce. Therefore the rule is updated to Salesforce when the scheduled time is changed.

Scheduler-based condition #

  • SKYVVA Agent, operations can be executed in a number of ways, such as manually, or automatically via a scheduler. The scheduler covers setting up a schedule to run user operations automatically. The scheduler contains information about when an operation will automatically be activated.
  • SKYVVA lets users define virtually any type of schedule user need, such as every Monday at 5 pm, the last Monday of each quarter, or every hour for one day.
  • The everyday user gets 4 files which come around 1:00 pm, 2:00 pm, or 3:00 pm. It comes only once a day. The next day 4 new files are expected again at the around same time. So to be sure user schedule a time window e.g. runs every hour at 12:00, 13:00,14:00,15:00, and 16:00. So the user defines a time window and add additional time slot at 12:00 and 16:00 to have some more security.
  • So, the Scheduler runs 6 times a day to make sure that the files get processed. It would be better if we don’t waste time running.
  •  In this case, if for example at 13:00 we have run and we finished at 13:30 then we don’t need to run again at 14:00, 15:00, and 16:00 because we run already and because for today there are no more files than we expected.
  • In this case, it would be better to schedule the other run based on the result of the first run. So the next run should run based on a condition and not based on a time. The condition needs to be defined by the user.
    In this case, the condition is the result of the first run. So if the first run has processed all 4 files then it can set some condition value so that the next run can evaluate it.

Read file extension with ignore case #

  • Read a file extension in the format specified by a format file extension with ignore case. (.csv|.CSV|.xml|.XML|.xls|.XLS|.xlsx|.XLSX). The format specification is the same as used in the format file extension. It is similar to the standard file extension formats.
  • This file extension can be used to set the input/output format for a target. It is useful when SKYVVA’s default output format for a file extension (such as XML, or CSV) is not as desired. The expected Format file extension function must be the call in a mapping formula to have it as the mapped value.

XML IChained with Hierarchical difference way #

  • When users create hierarchy relationships, each reference to a component is expanded under its parent element. The XML Wizard selects the default root and uses default settings to create an XML body.
    It can be a row in a database table or an XML element that might have a value or attributes or sub-elements. When the mapping of a target instance depends on possibly more than one instance of source, we call it “Instance Mapping”. The mapping of a source is represented by line items specifying batch, and bulk mapped to a target field.
  • Another example is the mapping of a source that contains multiple instances of name-value pairs to a target field that represents a username. “Instance Mapping” allows the user to define a mapping to reduce multi-instance sources to a single target instance. It essentially allows the user to move row-oriented data into column-oriented data, with the number of records generated dictated by the level of the data being mapped. This can be demonstrated by Hierarchical to Flat Structures mappings, where the user needs to resolve some information from one or more previous or “higher level” records.