Fixed an issue for Agent Cache #

Fixed and changed the new flow of the “Rebuild cache after system refresh” button to working smoothly.

Not allow creating all adapter type while using different agent type of New agent #

There is an error that occurred while creating the adapter that is not the same agent type as a new agent. This issue has been fixed.

The messages are wrong while sending data is completed of SAP CPI adapter #

There is an error that occurred while we were callout V3 processing with the SAP CPI adapter. The message generated failed when the records reached the target system. This issue fixed by generating a message completed while the status code from 200 to 299.

No Data available for custom outbound processing #

In the sharing setting in salesforce, users can access only their records. Therefore they cannot execute callout on other user’s records. There is an error that occurred while you uses custom processing in the outbound interface with sharing keywords of our class. This issue was fixed by changing from with sharing to without sharing of GisOdbgIntegration class. The setting without sharing in apex class breaks the salesforce setting, and now you can access the records that are not sharing with them.

Fixed a few bugs on the Upload file of the Bulk Control Board #

• There is an error that occurred while the browse button did not select another file the second time. Therefore it gets the unexpected error. This issue has fixed by changing the old aura component(Browse) to the new aura component(Upload Files).
• We have added the validation on uploading the file in Bulk processing of the Bulk control board. For example, the user uploads the v2/v3 processing file, so the interface must be v2/v3 processing. Otherwise, it will get an alert message error “This file is not support with this Interface”.

Fixed a few bug on mapping #

• Fixed generating the wrong relationship on a set context level that equal to the parent level. For example, the mapping path will generate to Reference Field Uncle instead of Reference Field Parent And Above.
• There is an error that occurred while the mapping has been generating the wrong source and target. Therefore the outbound processing is not working correctly. This issue has been fixed.

Fixed several bugs on Agent Cache #

• Fixed changing flow for deleted, pushed, and synchronize cache.
• Add alert message “The connection destination name from interface[interface id] is a difference.” regarding the linking interface with different connection destinations issue by using Rebuild Cache After Transport.
• Fixed InterfaceGroup records not able to update existing records while the user process Rebuild Cache after Transport.
• Fixed cannot filter scheduler while choosing a name on scheduler type.
• Fixed cannot delete interface cache record while the integration has deleted.
• Fixed cannot update the old IMapping and IChain cache record while the existing interface has been imported.
• Fixed cannot synchronize the workflow cache record while interface added the adapter.

The mapping generates the wrong query on the Database Query #

Fixed generating wrong query table name of Database Query field while the mapping has third level mapping.

Not allowed doing next step while the type field is not selected #

There is an error that occurred while saving the agent setting. The type field is required, but we can continue to do the next step while we do not select it. This issue has been fixed.

The messages are wrong while sending data is completed of SAP PI/PO adapter #

There is an error that occurred while we were callout V3 processing with SAP PI/PO adapter. The message generated failed when the records reached the target system. This issue fixed by generating a message completed while the status code from 200 to 299.

Fixed set context level on mapping #

Fixed generate the wrong relationship on a set context level that equal to the parent level. For example, the mapping path will generate to Reference Field Uncle instead of Reference Field Parent And Above.

Change the Path URL Prefix to be an optional field in Agent SAP ERP Adapter and SAP Credential. #

Currently, the Path URL Prefix is a mandatory field on Agent SAP ERP Adapter and SAP Credential. Thus, sometimes it does not actually need it. Fixed changing this field to optional of Agent SAP ERP Adapter and SAP Credential.

Not visible for some salesforce fields #

Our SKYVVA tool is not visible in some salesforce fields. Therefore, they are required a higher API to accessible. This issue fixed by upgrading the API to version 50.

Fixed some issue for Agent Cache #

• Fixed All agent types cannot synchronous cache to h2 table that excluded Agent SAP ERP only.
• Fixed display hierarchy interface related with parent interface in Cache Monitor
• Fixed display adapter by Agent Destination in Cache Monitor.

Mapping is not generated correct sub-interface with outbound processing #

There is an error that occurred while we have mapped the source to the multiple-target node in the mapping tool of the outbound interface. Therefore, It will generate the wrong payload after we have a callout. This issue has been fixed.

CDATE Formula is not working with a year ending from Number 01 to 09 #

This error happened when the CDATA(Field Name,’m/d/y’) formula has the year ending from number 01 to 09. For example, the Field Name contains 12/18/08; thus, it will get an error as “Invalid date [12/18/08] with format [m/d/y]”. This error has been fixed.

Fixed status business message under API Message of REST and SOAP adapter #

The business message statuses will display wrong while it has the API message to cover the business message. We have fixed this issue by changing the parent of the business message from Partial Completed to Completed.

The message type field entries are missing after importing #

There is an error that occurred while importing the MetaData provider is missed the message type field entries. Therefore, The external field of IStrucutrue is generated wrong. This issue has been fixed.

Delete, Canceled, Reprocess Message function #

Fixed various issues related to delete, cancel and reprocess message function as following:
-Manual processing in Message Monitoring, Message Detail Page, and Scheduler processing

• Fixed the reprocessing API Message on the Message Monitoring and Message Detail Page.
• Fixed Delete child Messages that have “Partial Completed” status. The child message that allows deleting is Completed and Canceled.
• Fixed cancel child messages that have parent message is “Partial Completed”. The child message that allows canceling is new, failed, pending.

Fixed BAPI Message Type issue #

There was an issue BAPI message type. It was not created correctly and added “Item” message type for each message type with type “SAP Bapi Table” for direction Salesforce to SAP.

Added invokeCalloutMode inside new SKYVVA agent JSON payload #

The new agent could not get value from the mode in the invokeCalloutV3 method; therefore, it will not work correctly. This issue was fixed by adding InvorkCalloutMode inside the new agent JSON payload for every new agent adapter.

Fixed Agent cache issue #

We have fixed the cache when removing the adapter from an interface. Thus, it will delete caches for all outbound interfaces.

Fixed various issues regarding Agent Rest Adapter #

• The fixing issue does not update the API message correctly. For example, the users have requested callout with the Agent Rest Adapter. The record has been sent already. However, the messages are still new on the API message.
• Fixed handling inbound with rest template of async processing.

Fixed a few issues regarding Agent cache

• Fixed agent cache was not pushing cache through push-button while it connected Agent SAP ERP adapter.
• There is an error that occurred while the agent cache has the interface using workflow. After you save the mapping, then the status cache of the workflow will be red. This error has been fixed.
• Fixed cache pushing error while update interface group on the interface.

Fixed various issues on the mapping tool

• There are four relationships as Parent, Context, Ghost, and Uncle. We fixed to generate especially twice “Parent_Context” relationships.  It did not remove old relations when you are doing a formula that has these four relations.
• When you do mapping, if you set “Filter condition” on that field, we will generate Source_path with “_TargetFieldName” at the end. It is not clear the “Filter condition” value while you remove mapping or set “Filter Condition” by accident.
• Fixed another minor bug on mapping.

Fixed Fault Response of Agent SAP ERP adapter #

The Agent SAP ERP adapter is not working properly on the fault response. This issue has been fixed. Currently, the Agent SAP ERP adapter handled only a fault response.

Manual load not working correctly in the XML hierarchy #

This error happened when clicking the upload button in the manual load that is missing the child fields of the XML hierarchy format. This is issue has been fixed.

Cannot integrate V3 Rest API while using message type name that contains dot “.” #

There is an error that occurred while the message type name contains a dot “.”. Therefore, it cannot integrate v3 Rest API of inbound with JSON payload. This issue has fixed.

Include attribute of the roof element in Export MetaData #

Fixed issue where the MetaData exportation has attributes of roof element; therefore, it cannot import to the SAP PO system.

Fixed various issues in the import message type #

There are various issues in the import message type. We have fixed as follows:
-OpenAPI 3.0

• Missing message type fields entry in the request query parameter
• Missing message type fields entry in PATH Parameter.
• Not able to changed MetaData name
• Cannot import message type from the “RequestBody” of file.

-Swagger/OpenAPI 2.0

• If the file has the header fields, it will not generate correctly.

-XML/XSD

• Generate the wrong type of message type field entry
• Missing the description field of Message type field entry

-WSDL

• Missing message type in body response
• Missing description of the message type

Not able to integrate data while changing the interface name #

There is an error that occurred while you have changed the inbound interface. Therefore, it cannot integrate v3. This issue has fixed.

Cannot integrate V3 Rest API while using message type name that contains dot “.” #

There is an error that occurred while the message type name contains dot “.”. Therefore, it cannot integrate v3 Rest API of inbound with JSON payload. This issue has fixed.

Exportation of XSD, JSON Schema, Swagger 2.0/OpenAPI 2.0, and OpenAPI 3.0 file format in the Repository #

Fixed Various issues as following:

• Fixed generate message type referenced and referenced back and forth.
• Fixed fields and message type which is required.
• Fixed message type in response while the message type of request is the same response.
• Fixed generating undefined in some parts of the WSDL file format.

The DoMaintenance scheduler cannot delete the failed, pending, and new messages #

We have fixed the issue which DoMaintenance scheduler cannot delete the old failed, pending, and new messages. This issue occurs while reprocessing the message (MessageReprocessPerxxx), and the DoMaintenance schedulers are working at the same time. For example, the DoMaintenance set a day for the deletion. The scheduler will check the modification date for deletion. However, the message reprocessing (MessageReprocessPerxxx) scheduler tried to reprocess and updated the modification to the current date. Therefore, the deletion message function will be checked by the created date instead.

Fixed various issue in the mapping tool #

There are various issues that have been fixed in the mapping tool as following:

• Fixed generation incorrectly query of the outbound interface while you do only the formula mapping. Therefore, it will not generate the query anymore in this case.
• Fixed generate relation of parent field formula mapping into the expression box by selected field in Sobject message Type.
• Fixed issue to generate incorrect the uncle’s value into the “Reference Field Uncle” field in flat mapping. Therefore, the integrated inbound v3 was not working.
• Fixed issue to replace dot(.) of v3 inbound processing for “Reference Field Parent And Above” and “Reference Field Uncle” fields.
• Fixed Auto Mapping when selected node. Therefore, you do not expand the note to auto map anymore and you just selected only the node target and source.
• Fixed Auto Mapping when selected node. Therefore, you do not expand the node to auto-mapping anymore. You must select the target and source node. For inbound, you need to map the main node first.
• Fixed “set context level” of the inbound mapping while the user sets the message type low level to the interface name.

Cannot integrate V3 while using message type names that contain dot “.” #

There is an error that occurred while the message type names that contain dot “.”. Therefore, it cannot integrate v3 of inbound and outbound. This issue has fixed only V3 outbound processing.

Fixed bugs on the exportation of Swagger 2.0/OpenAPI 2.0 and OpenAPI 3.0 file format in generic page and interface detail page #

Fixed exportation to get REST message type template from Swagger 2.0/OpenAPI 2.0 and OpenAPI 3.0 file in generic page (Custom links of Integration page) and interface detail page.

Fixed issue which ISEMAIL(text) formula to support the domain name that contains only two or a character  #

ISEMAIL(text) formula function is checking whether the specified text is email or not. Fixed ISEMAIL() formula for checking the domain name that contains only two or a character. i.e “test@a2.co”.

Fixed bugs on the exportation of JSON schema file format in generic page and interface detail page #

• Fixed only exportation business structure with Rest template in generic page (Custom links of Integration page) and interface detail page.
• Disable Combo box “Chose an API name” and “Chose an operation” while we choose JSON Schema.
• Fixed exportation while using IChain Interface.

Fixed bug in the mapping tool #

The mapping was generating the wrong full path while the message type is using the SObjectType. Therefore, integrate V3 cannot process. This issue has been fixed.

Cannot reprocess messages manually filtered by the interface name #

There is an error that appears while you want to reprocess the messages manually in the Message Monitoring. If the messages are filtered by an interface name, they are not able to reprocess. This issue has been fixed.

Error in exported Metadata from the different file format #

Fixed various issues in metadata generation in lighting were in Generate Meta Link on Integration Details Page and Interface details page.

• Fixed exportation of JSON Schema
  • Get an error while export IChain Interface.
  • Not generate SKYVVA field.
  • Not generate IStructure from the file in IStructure of the interface.
  • Not generate manually IStructure of the interface.
• Fixed exportation of  WSDL File Format
  • Not generate IStructure into the file that does not Message Type.
  • Changed Skyvva__Message to SKYVVA__MessageId for all level request message type.
  • Generate SKYVVA Business Object type of message type to working correctly.
  • Generate message type link with other message types.
  • Merge message type that request, response, and Fault have the same message type.
  • Missing SKYVVA__MessageId in Sobject message type.
• Fixed exportation of XSD File Format
  • Missing description of message type field entry.
  • Missing message type field entry from message type rel.
  • Not merge message type field entry.

Error regarding with imported Metadata from the different file format #

Fixed various issues in imported message type in lighting in the repository.

• Fixed importation of OpenAPI 3.x to generate message type
  • Generate the wrong type of IStructure.
  • Not retrieve description value into IStructure description field.
• Fixed Importation of XSD and XML to generate message type
  • Importing functionality for XML and XSD currently supports files that are well-formatted line breaks. If the file is not formatted some structures might be missing.
  • Different types of XSD files are supported which has different structures for complex types including WSDL.
  • Primitive and derived data types from XSD are supported.
  • References used in XSD files are skipped and its child elements are assigned to the parent of reference where it defines as “type” or “ref”.
  • Attributes are created as Istructure with proper XSD data types supported. For duplicate names parent is assigned to attributes.
  • Elements from nodes “all” and “choice” are inserted. So users can choose elements from the choice node.
  • Elements referencing to the node which has Complex type and simple type as a child are created as fields. And elements referencing to the node which has complex type and sequence as the child are created as message types.
• Fixed Importation of JSON and JSON Schema to generate message type
  • The description of IStructure is showing undefined
  • Importing the JSON file that does not have a root tag name.

IMapping has generated an incorrect path after changing the interface name #

There is an error that occurred while the user changed the interface name of inbound v3 processing, and then the user saves the mapping again. It will generate the wrong path on “Reference Field Parent And Above” and “Reference Field Uncle” in IMapping records. This issue has fixed.

Output result returns wrong to ISEMAIL formula function in the mapping tool #

The mapping tool is able to use the formula function for adding or editing in mapping records. Fixed issue regarding output result returns wrong in the ISEMAIL formula. For example, the email does not have a domain “xxx.<domain>” like “xxx.skyvva.com”. When we write the mail like xxx@skyvva then it returns true, this is not correct. It should return ‘false’; therefore, the domain extension ‘.com’ is missing.

Cannot edit Interface group in Integration Page #

Fixed issue while the user wants to edit the existing interface group in the integration page, it will be creating the new interface group.

The scheduler does not update status and comment on the screen while the scheduler aborted #

There is an error that occurred while the user starts the scheduler in the Salesforce Classic interface, the scheduler has an aborted or unexpected error, and it will not update the status and comment correctly. This issue has been fixed.

Cannot handle long text error message in a message comment #

Fixed missing failed message comments for monitoring while it has too long text.

Missing message type field entry in the mapping tool #

Missing the message type field entry while the message type parent is SKYVVA Business Object type. This issue has fixed.

Getting errors while saving the mapping #

There is an error occurred while the mapping is saving the Sobject and SKYVVA Business Object picklists value in UsageType of IMapping Object. This issue has fixed.

Cannot process batch basket with EOIO type by the scheduler #

Fixed issue wherein the scheduler is not able to execute the apex class for processing batch basket with EOIO type at a specified time. The scheduler is still running; however, the batch basket still keeps in working baskets.

Export, Export to other org and Import Are Missing Attribute in Message Type Field Entry #

Missing attribute field in Message Type Field Entry while export, export to other org and import. This is error has been fixed.

Not able to get response message with Soap Adapter #

There is an error that occurred while request callout V3 outbound with SOAP adapter, the response message will not respond after request message has been completed. This issue has been fixed.

Errors in Generated WSDL in Lightning #

Fixed various issues in WSDL generation in lighting were in Generate Meta Link on Integration Details Page, for both WSDL 1.1 and 2.0

• SObject name undefined in generated WSDL.
• IStructure fields override SObject field when created from file.
• Manually created/queried IStructure fields included along with SObject fields when generating.
• When IStructure and SObject field has the same name, SObject field takes priority, no duplicate fields.
• Fields sorted by alphabetical order.

The Time Interval Changes after Being Edited on Scheduler Message Report Page #

To send Message Report to external email or to use email to get messages status such as New, Failed, Cancelled, and Pending, the scheduler needs to be defined. Fixed the error occurring after time interval is edited where it automatically changes from 10 to 90 min.

Missing Status Field When Cloning, Importing and Exporting Adapter  #

Fixed status fields value such as Active, Inactive and None missing when cloning, importing and exporting Adapter.

No Message Created When Sending Data Between Two Orgs.  #

Fixed issue where data is sent from sender org to receiver org, but receiver org does not create messages.

Delete and Refresh in Bulk Control Board has Error When Interface Deleted or Uncheck Bulk Mode #

This error has been partially fixed in patch 2.43.6, however, it was still present in Inbound Processing Tab in Bulk Control Board when attempting to another refresh an Interface that was deleted or had Bulk Mode unchecked.

Auto Generate Some Value for Repository Fields (hasChild, seqeuceNumber, level) #

Fixed auto-generating values in some fields hasChild, seqeuceNumber, and Level of Repository.

Unable to Customize Message Details Layout #

Message details page layout has been modified to allow users to edit the layout in order to display only required fields and related records.

Workflow Target Operation Type Hidden By Model Footer #

When defining operation type for a workflow target, the operation type options may be obscured by the model footer. Fixed this issue by displaying operation type options on top of model UI elements.

Unable to Upload Duplicate and Blank CSV #

Fixed issue was unable to create IStructure during uploading duplicate CSV fields and generating the wrong IStructure while uploading blank content CSV.

Export is Missing Sub-Interface and Missing Save INTERFACE WORKFLOW SETTING #

Fixed Export Interface where Interface Tab on Integration Details Page is missing some fields such as skyvvasolutions__WorkFlow_Processing_Mode__c, skyvvasolutions__WF_Runtime_Behavior__c, skyvvasolutions__WorkflowStatusHandling__c and generated the wrong root of the sub-interface name.

Upsert Auto External ID on Child Interface #

The issue occurs when two interfaces have chained Parent and Child e.g Account interface is a parent of Contact interface, an operation type of both interfaces is Update Auto External ID, and field name of Account sObject mix with contact e.g. NumberOfContacts__c then we call data for account data only no contact data.

The double value created after upload file on Repository #

Get double Message Type Field Entry on each Message Type when upload XML file to create message type two times.

InvokeCallout2 not working with Interface Id It is working with interface Name #

Because of invokecallout and invokecallout2 Need different Parameter so:

• We still need InterfaceId for invokecallout 1
• We use InterfaceName for invokecallout 2

Unable to create Chain Interface (SKYVVA version 2.43.1) #

Unable to create a chain interface in the SKYVVA32 demo system (SKYVVA version 2.43.1 installed). As soon as the “NEW” button is clicking to create a new child interface it gives an error.

Delete Failed message not working with v3(System.NullPointerException: Attempt to de-reference a null object ) #

There is an error occur when the JSON data request from SOAP UI. The picklist value “Delete Failed Message” on “What to do with the failed message” field is not working with V3.

Having Two Select in SOQL Query to select sObject data for Outbound Interface #

This error occurs because our old logic can handle only keyword “SELECT ” but when query from agent side our agent converts this keyword into small characters “select ” so make the code think these two are different. Users can also input query manually like “select or Select or SELECT or SeLecT….” etc.

Re-fix some functionalities in the mapping tool #

For patch version 2.43.1, some functionalities in mapping tool need to be fixed as:

• When contexted one node all the child node is displayed or incorrect level number.
• When showing an incorrect alert error when mapping with Salesforce first level it is should be allowed to map
• Validate No Foreign Key on salesforce first level is incorrect; it should be no validation for this level.
• Remove spinner when saving with No-records.
• Cannot mapping fields when the Parent or node was created auto or with AutoMapping. (Now we able to map normally).

Error with Stop button scheduler in Bulk Control Board #

An inbound processing tab and Schedulers tab of the Bulk Control Board contain the same interface to process the scheduler. However when we click stop any scheduler in the Inbound processing tab then go to Schedulers tab this scheduler has to show action stop as well in order to avoid user click stop again and get an error.