Added Scrollbar for viewing the hierarchical messages #
Added the scrollbar to view all hierarchical messages at the left side in the message detail page, making it easier to check all messages.
Added the scrollbar to view all hierarchical messages at the left side in the message detail page, making it easier to check all messages.
ISEMAIL(text) formula function is checking whether the specified text is email or not. Enhanced ISEMAIL() formula for checking with the domain name that contains only two or a character. i.e test@a2.com.
At the moment, the SFDC Rest adapter type doesn’t have the default properties field while the user creates new this adapter type. The new enhancement is added to display default Properties field for SFDC Rest adapter type such as username, password, sfEnvironment, sfConsumerkey, sfConsumerSecret, token, targetIntegrationId, targetInterfaceName.
A new enhancement has been added to SKYVVA Bulk to handle hierarchical data using SKYVVA inbound integrated v2 for the SAP-PO connector.
The Monitor tab is a place that users can check the message after integrated. The Monitor Tab has been added into Agent Control Board Old. Therefore, users can check the message without jump up to Integration Cloud Tab.
At the moment, SKYVVA can push records by the only element with XML hierarchical. The new feature has been added to handle attribute hierarchical payload for the inbound processing.
Note: The two fields added into MsgTypeFieldEntry__c such as Category and Parent:
Category field is defined MsgTypFieldEntry__c was attribute or element.
Parent filed is defined MsgTypeFieldEntry__c looks up to element of attribute.
Currently, we update the message using SkyvvaMessageId. Therefore, external id has been added for update message with Rest API using Synchronous mode.
Currently, the Rest adapter uses authentication with Basic, Certificate, and Oauth2.0 property. Due to some Rest API using API-Key for authentication, therefore SKYVVA has been added a new feature to the REST Adapter to be able to use with API-Key property.
Add new Enhanced to monitor the Request Message of API message on Message Monitoring, wherein Outbound processing using Rest and Soap Adapter.
Currently, SKYVVA agent application is being able to create an adapter. Therefore, added a new feature to create an adapter on Agent Control Board(old) Instead of creating in SKYVVA Agent application.
A new button, Interface Group, is added in Batch Control Board. You will be able to create a new interface group in the interface group tab.
This feature is using existing of Message Monitoring feature but we add a few conditions to it:
This is a new feature, which is created to export attachment files from salesforce to FTP Server through Agent. In the previous version, we can only export and import the Attachment file between SF and local PC storage. Now we can export and import the Attachment file between SF and FTP Server using Agent.
This is a new feature, which is created to export attachment files from salesforce to FTP Server through Agent. In the previous version, we can only export and import the Attachment file between SF and local PC storage. Now we can export and import the Attachment file between SF and FTP Server using Agent.
Previously, our tool can only create JSON Payload File to create Message Type and IStructure. However, now we are able to handle the JSON Schema file. You are now can create a JSON Schema upload file to generate Message Type and IStructure.
For an inbound message, we often see that a message is waiting on the other message because it failed. In the comment, we clearly tell the user that this message waits for the other message and we show the link in the comment field box. It will be good for the user to have a hyperlink here and jump to that message.
The current workflow processing is independent which means that we always pass all messages e.g. the complete block of for example 50 messages to the step independent if the first step has filtered out 15 messages. The dependent processing works like we have joined the condition of step 1 with AND-operation with condition 2 of the second step. Such a use case we could have where we do not pass all the 50 messages to the next step but only those messages which have been passed e.g. evaluated to ‘true’ by the first step. We have to remove the messages which do not match the condition from the map.
Due to the new logic that was implemented on the IStructure and MessageType, the old way of generating MesssageType from WSDL may encounter a problem and need to fix. We re-enable this feature.
We need to respond to JSON data as parent and child on SAP after called request data from SAP by use Searchservice Rest API. This is an enhancement feature which is offering in the latest version of our patch release.
This is an old feature which hasn’t use often. We feature this in our patch in order to remind the user that you can use VLOOKUP and Foreign Key base on Salesforce External ID and External Mapping. You can define the VLOOKUP formula on SoapUI request to call Salesforce now.
We Create Combobox that contained the Edit and Delete button on Istructure in IStructure section which is easy for changing some fields of Istructure. There is no need to click istructure to edit on-page.
Previously, we have field MESSAGE (old version) and currently, we have the field SKYVVA_MESSAGE. With our current implementation, we cannot set an application text in case of a successful case. Because when we pass the field ‘MESSAGE’ or ‘SKYVVA__MESSAGE’ then we use this as a flag to set the message to status ‘Failed’. So anyway independent of the content of this field the message is always set to the status ‘Failed’. We want to set the comment field with the successful application text. We have enhanced this feature.