Enhanced Capability to Create IStructure from Database within the Interface #
In the previous version, you could not retrieve columns to create an IStructure for the old V2 interface design for flat mapping. We have now enhanced this functionality by adding a new ‘Import Database IStructure’ button on the IStructure related to the Interface sObject. This allows you to retrieve columns to create an IStructure for the old interface v2 design for mapping purposes. You no longer need to create it manually or upload a file; you can directly obtain the IStructure from the database.
Automated Connection URI Generation in Enhanced Database Adapter Configuration #
In the previous version, all adapter properties for the database adapter, such as Driver, Hostname, Port, Database Name, and Connection URI, had to be manually input, resulting in duplicate values. To enhance efficiency, we will automate the rendering of the Connection URI and introduce new Connection Properties to handle extra parameters for the connection URI. Additionally, we will include a Schema Name property in the adapter to specify your schema.
Added a Warning Alert on Mapping while doing Update and Delete operations on the Agent Database #
We have added a warning alert while the user performs updates and deletes operations in the V3 and V2 interface designs. If a user did not specify a WHERE clause for V3 or an external key for V2 when updating or deleting all records in external databases such as SQL, MySQL, MS Access, Oracle, or Postgres. In such instances, it is very important to give a warning to alert the user, making sure they are fully aware that all records will be updated or deleted.
- For Update operation warning: It seems that you have not specified a where condition for your update operation. Without a where condition, all records in a table will be updated with the same data. Do you really want to update all records with the same data?
- For Delete operation warning: “It seems that you have not specified a where condition for your delete operation. Without a where condition, all records in a table will be deleted. Do you really want to delete all records from the table?”
Implementing Query Data from External Database for Inbound Processing and Query Editor via Inbound Agent Database #
In the previous version, you were unable to use the Query Editor to query records from the external database for inbound processing. In this version, you can now perform manual inbound processing by selecting ‘Manually select the external database record using the Query Editor.’ Additionally, you can use the Query Editor for the Inbound Agent Database by selecting ‘Query data from the external database’
Add New ‘Database CDC Event’ to Capture Data Change to Do Inbound Processing Using Agent Database Adapter #
We have added a new picklist value ‘Database CDC Event’ to the ‘Event Type’ field on the Salesforce Interface Screen to capture data changes from the database according to the selected ‘Notification For Operation’ with the ‘Database CDC Event’ Event Type. By choosing ‘Create’ under the ‘Notification For Operation’ for the Database CDC Event Event Type, only newly created data will be consumed for integration with this interface.
Add ‘Notification For Operation’ for ‘Salesforce CDC Event’ #
Now, with your ‘Salesforce CDC Event’, you can filter notifications to receive operations by selecting Create, Delete, Update, or Undelete under ‘Notification For Operation’. By choosing ‘Update’ under the ‘Notification For Operation’ for the ‘Salesforce CDC Event’ Event Type, only newly updated data will be utilized for integration with this interface.
Added new ISINTEGER(text) Formula #
We have introduced a new formula called ‘ISINTEGER(text).’ This formula verifies if a given string can be converted into a valid integer. If the conversion is successful, it returns true; otherwise, it returns false. For example, ISINTEGER(’12’) returns true, while ISINTEGER(‘ABC’) returns false.
Enhanced Outbound Manual Processing with “Manually select the sObject using the Query Builder?” Option #
Currently, when you use manual process with ‘Manually select the sObject using the Query Builder?’ option for outbound processing, any ‘WHERE’ conditions on the ‘Filter’ and ‘Filter Query’ will not work if you manually select records outside those conditions. We have now enhanced the selection of records to disregard where the conditions are placed in the ‘Filter’ and ‘Filter Query’ sections
