Last Data cannot display a number of file attachment #

The screen of the interface Agent UI is not so good #

Stabilize Agent Scheduling – Problem when more than one process at the same time #

Agent – XML file creation uses the Salesforce subject Name instead of taking the target field “SecondLevelXML” #

An agent does not yet support schedule UI every hour from X hour to X hour #

Scheduling AgentUI read data from crontab file with different Instance has Integration and Interfaces the same name #

Select integration box one time 2 integrations or more than #

Lock File immediately before reading it #

The “Stop” Button Integrate not working #

Error schedule outbound interface when the query does not select field Id #

No Cron Expression was found in the Cron file #

Integration Setup Wizard-Interface Test Integrate filter is not pop up anymore #

An agent doesn’t refresh the cache file and thus reads old content #

Related To link on the message board has a problem #

Error test query with SFTP adapter #

JCRONTEST>EXECUTE>ERROR: Null #

Streaming API doesn’t work anymore #

This patch is released to cover following bug:

• The Basket did not move, when it contains a message which is not met the Workflow condition

The connection status of the old Agent Control Board always OFFLINE while the user saved adapter #

There is an error that occurred while the user has saved the adapter in the old agent control board. Therefore the connection status of the Old Agent Control Board always reloads to OFFLINE. This issue has been fixed.

Fixed following bugs in this patch: #

• Created the wrong Message while pushing file that not match the file type in file adapter.
• Remove properties application/XML request format and response format when we choose protocol rest in business one Adapter..
• API Message status with adapter sap business one is wrong.
• Remove SAP IDOC Configuration on SAP Control board and add System Information as the same Agent control Board.
• API Message status with adapter sap business one is wrong.
• Remove properties username, password, and CompanyDB on SAP business one adapter. And we need to add properties Connection destination.
• Remove SAP IDOC Configuration on SAP Control board and add System Information as the same Agent control Board.
• Old Agent Control Board always OFFLINE when user edit and saved adapter

Fixed following bugs in this patch: #

• Raw payload not created while the message is reprocessing
• DEFECT: Not generate raw logging payload while callout is failed on Sync processing mode
• DEFECT: Encoding csv is not working with V3 of New agent
• New Agent source encoding in Linux instance not working on SFTP protocol
• Fixed Mapping issue to generation path and runtime
• The issue on inbound v3 processing through the new Agent
• ExecuteInterface Scheduler missing
• Enable ODBC on Agent

Fixed some minor issues regarding generating metadata as the old way #

• Convert all type of IStructure to string in generating as the old way (WSDL 1.1 and XSD)
• Reverse some parts of WSDL 1.1 lightning like the classic UI generating.

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.

Fixed a few bug on mapping #

• Fixed not generating value after applying the set filter.
• Missing target field in filter path.
• Generate the wrong path while applying set context level.

Fixed a few Cache on mapping #

• Fixed not displaying correctly on Cache Monitor while the property blank in cache_status object.
• Fixed error is not refreshing old value selected in rebuild cache transport after push.

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.

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

This error happened when the CDATA 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.

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.

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

This error happened when the CDATA 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.

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.

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

This error happened when the CDATA 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 issue which ISEMAIL formula to support the domain name that contains only two or a character #

ISEMAIL 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”.

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.

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

This error happened when the CDATA 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.

Missing minimum occurrence in generating MetaData #

There is an error that occurred while generating WSDL 1.1 and XSD metadata as the old way is missing minimum occurrence which is cause problem in SAP PI. We have an additional minOccurs=”0″ attribute on those elements (<xsd:element default=”a0Y7F00000F26cvUAB” minOccurs=”0″ name=”fromSystem” type=”xsd:string”>) and (<xsd:element default=”Account Data Loader” minOccurs=”0″ name=”targetObject” type=”xsd:string”>). This issue has been fixed.

Apex heap size in message reprocessing #

There is an error that occurred while the message reprocessing has many failed messages that reach up to apex heap size. This is issued has been fixed.

Bypassing apex heap size #

There is an error that occurred while integration writes the log in the attachment that increased heap-size in the apex. This issue has fixed by providing the option to set in the SKYVVA custom setting object <Key>. IsSavingLogFile: false, it will not write integration’s log into the attachment.
To set SKYVVA custom setting object<Key>custom setting:

1. From Setup, enter Custom Settings in the Quick Find box, then select Custom Settings.
2. You will see “Key” SKYVVA Custom Setting, please click manage on “Key”
3. Click New button
4. Fill IsSavingLogFile in the Name box, fill “false” in the key box, and click save.

Cannot reprocess messages filtered by the interface name #

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

The 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 handle long text error message in a message comment #

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

Cannot sort manually mapping in the mapping tool #

Fixed issue which users map IStructure source field to IStructure to target field with the outbound interface. Therefore, the mapping will be sort by the ascending source field automatically. Now users can sort manually mapping or ascending, descending order in the target field.

Cannot import outbound interface #

There is an error that occurred while import outbound interface, it will validate all interface mapping fields whether they have been selected query or have not. If one of the fields does not select in the query statement, it will be raising the error. This issue has fixed.

Not Increase message counter for interface with custom class #

Users are able to use custom processing with their code; therefore, their custom code overrides SKYVVA functionality that affects the retry counter message. Fixed issue which increases retry counter message that does not work properly for Interface with custom class while using scheduler to reprocess the messages.

Bypass Message Layer not working with Manual Load of XML hierarchy format, CDC and Batch Mode #

Bypass Message Layer is using for none creation message after pushing the records into salesforce. Fixed issue getting messages while the interface is using the Bypass Message Layer flag with XML hierarchy format (Manual Load), CDC, and Batch Mode.

Messages cannot be processed due to waiting for each other #

There is an error that occurred while the failed messages have the same external id, and they are waiting for each other to reprocessing like the cycle. This issue has fixed, and the earliest one can be reprocessed.

Always Delete Child Records while processing the same batch apex execution #

Skyvva has Delete First mode in Init Operation on IChained Interface Inbound for deleting child records. There is an error while the user is processing integration with batch mode. The baskets contain many records; therefore, batch apex will split messages into small packet sizes per batch execution. The records repeat the parent, so the last execute will be deleted the child records of the first execute. This issue has been fixed.

Partial Complete Message Not Working Properly #

An error occurred which handle to message hierarchical status. The partial complete message always jumps to complete status while reprocessing one of child messages is completed, though others are still failed, pending, new, and canceled messages. The issue has been fixed.

Error in Edit and Create New IStructure #

Fixed various IStructure issues were in Interface Related Page and MessageType Related page.

• To edit existing IStructure while the user is able to save & new button, but the IStructure has still modified the old existing one. It does not create the new IStructure.
• To create new IStructure while the user is able to save & new button, but IStructure has only saved.

Saving Input Parameter in Massage with Callout V3 #

Fixed issue that message reprocessing is not able to have parameter by passing from API call of V3 outbound processing.

Link API Message and Request Message of V3 Outbound by MessageRel for SAOP And Rest Adapter #

Message outbound of v3 is able to forward different target interfaces by using workflow conditions. This issue got from the first API message has lost request message for monitoring when the outbound has been passed to the second interface in the second workflow. This issue has been fixed by linking API and request messages to the junction table (skyvvasolutions__MessageRel__c) on Soap and Rest Adapter.

Error on Pushing JSON Data Payload of v3 Inbound Processing #

There is an error that occurred while you push record using JSON data payload because of generating the wrong of v3 inbound processing.

The Refresh Button on Transport Route page is not Working Correctly #

To send interface into other org. Therefore, the users need to choose Integration first before the users can transport interface. Fixed issue in which the refresh button is not refreshed Integration was in Transport Route page.

Generate double dot field related object on Query Editor #

Query Editor is a place that can retrieve query by selecting sObject field or manually add query, however, this error occurred is selected field related object after getting double dot like “CreatedBy..AdapterUrl” because of none accessible and none usable on Object in second level relationship query.

Errors in generated WSDL and XSD Format in Lightning  #

Fixed various issues in WSDL and XSD generation in Interface Details Page Lightning, for WSDL 1.1 and 2.0 and XSD:

• SObject name undefined in generated WSDL in Generate Meta Link in Integration Details Page
• IStructure fields override SObject fields when created from the file in Generate Meta button in Interface Details Page
• Manually created/queried IStructure fields included along with SObject fields when generating in Generate Meta button in Interface Details Page.
• When IStructure and SObject field has same name, SObject field takes priority, no duplicate fields​​ in Generate Meta Button in Interface Details Page.
• Fields sorted by alphabetical order in Generate Meta Button in Interface Details Page.
• Remove type in element and remove name of compleType type with old ways of XSD and WSDL in Generate Meta Link in Integration Details Page.
• Added Integration and Interface name attributes for WSDL generated from outbound interface in Generate Meta Button in Interface Details Page.

Unable to display Working Baskets Records #

There is an error that occurred while baskets more than ten thousand records. The baskets are not able to display on the working baskets screen. The issue has been fixed.

Not able to Display JSON Data in Salesforce Classic #

The error occurred while storing JSON in Data_c, so it cannot display the message’s data in Message Details in Salesforce Classic. This issue has been fixed both classic and lightning.

Can’t remove the selected mappings #

The error occurs when trying to remove the mapping. We get an alerting message error as shown”System.DmlException: Update failed. First exception on row 8 with id a0tf0000000uqjpAAA; first error: FIELD_FILTER_VALIDATION_EXCEPTION, Value does not exist or does not match filter criteria.: [skyvvasolutions__Interface_Group__c]”

Parent Relationship name is dropdown in lightning version #

When creating a child interface the value shown as blank (in the drop-down) and cannot proceed this further. To proceed with this you have to switch to the classic version and create the child interface manually. This error is fixed in patch version 2.43.3.

SKYVVA generate trigger to handle CDC Event in salesforce #

The current script of Change Event Trigger is not working with sObject Change Event. So now add 4 modes into Trigger mode of Change Event Trigger FUTURE, BATCH, QUEUEABLE, and AUTO.  Also, some new operation type has added as CREATE, UPDATE, DELETE, and UNDELETE. Add “Show” info if the user forgets to choose Operation Type.

The refresh button is not working which interface Tab stays in Batch Control Board #

The refresh button is not working when the “Batch Mode” flag have removed on the interface. It’s still showing the interface view.

Re-fix some functionalities in the mapping tool #

Some of the functionalities in the mapping tool have fixed:

• 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 Auto Mapping. (Now we able to map normally).
• When the user map leaf without map its parents there will be auto-generate parent’s node for the user (this is correct) but when the user maps the next level There is a wrong validation “Leave Main Not Map Yet!” but the main node already generated (fixed by validating only when Level Main does not yet have in-store).

Cannot Create a custom class for inbound #

Encounter the error when trying to create the custom class for the inbound interface. This error is fixed in patch version 2.43.3.

Get error when import IRepository and import Message Type #

The error occurring when trying to import the repository from other organizations.

Don’t add an element which is blank (for particular condition) – Salesforce Outbound Interface #

When the interface is testing, it is creating a blank line in the message payload for that mapping(where NOTHING is getting used). So cannot add an element, which is blank (for particular condition).

Skyvva Scheduler #

The problem is that SKYVVA scheduler is always aborted itself after the execution and submit a new schedule for the next run.

Not able to create new Interface if sObject name is WorkOrder(Salesforce Standard sObject) #

The issue is occurring while creating a new inbound interface in one of the customer’s instances. Issue is only happening if Source Name is “WorkOrder”, it is working fine if it is either “Account or Case” sObject. Now, we have fixed the issues and release a new patch version 2.41.9.

SOAP API searchService return not correct JSON response anymore and thus break old customer with SAP-PI/PO #

When the searchService API is executed the query interface, it returns a JSON response with an empty array like “result”: []. This error is fixed in patch version 2.42.9.

Can not delete MetaData Provider #

It’s impossible to delete Metadata providers that contain Message Type Re. This issue is fixed in version 2.42.9.

Upload file on Repository has missing Sample content #

The file which upload on Repository has a mission Sample content. This error is fixed in patch version 2.42.9.

Mapping of Child Interface isn’t executed #

Somehow the mapping of the child interface isn’t executed. This error is fixed in patch version 2.42.8.

Two default interface groups, Baskets aren’t processed #

The issue is that the Baskets in two-default interface groups aren’t processed anymore by the scheduler. We have fixed this problem in patch version 2.42.7

Error when save a soql statement with syntax check #

Operation type, Query and pullQuery, make a syntax check while saving SOQL statement. This is not right since we are using formula template in the WHERE clause and this is not syntactically correct.

Not able to add mapping to outbound interfaces with nested query #

Since subquery is not supported with outbound interface for mapping. We have fixed this issue in patch version 2.42.6.

Target Namespace display undefined in Lightning #

The field targetNamespace is displayed as “undefined” but when switch from lightning to Classic mode and generate WSDL file this field is display value normally. This problem fixed in patch version 2.42.5 as now generating XSD or WSDL now also saves Target Namespace to integration record, using the value specified in the manage middleware WSDL screen.

Show Incorrect interface on Bulk Control Board #

When the interface is created and the flag Bulk Mode set to true, it shows incorrectly on the interface tab in Bulk Control Board. This problem only happens to the interfaces which have the set flag Bulk Mode to true.

Integration Import is failing #

The issue is occurring when trying to import the integration as it fails a few times. This error is fixed in patch version 2..42.5.

An issue with Chained Interfaces #

When an interface is setup with Chain (Child) interface, the output will not happen as we expected. As some of the child, data are missing. For this patch version, we have fixed the missing message data of child object when interface have two chain of the same object.

Remove require Streaming API in package #

We have implemented to remove the require Streaming API in the package.

Problem with Transport Route #

There is a problem with standard transport Route functionality. The error is happening with transport SKYVVA configuration as the transport started but the messages remain in source sandbox even though we get a green message. There is no message by mail from Apex Job. Since the configuration does not appear in the target sandbox, checking in apex job to see the message error is required.

Message Reprocess staying failed in workflow processing #

Due to there were many failed messages, the user has defined some workflow to bypass the error. After then user started scheduler and message have been reprocessed and match some workflow condition, but it staying similar to the previous failed. The issue is fixed in patch version 2.41.6.

Always get message error after deleted Message Type #

We always get the popup message error after deleted Message Type. The error needs to be deleted from the screen.

The problem on delete message in Message Monitoring #

There is a problem on delete message in Message Monitoring. When the Delete or Delete All button is the click, it got successful but the records did not delete.

SearchService API response JSON is grammatically not correct #

The error is that our SearchService API returns an invalid JSON format response. The keyword supposed to be put into the double quote however, there is no double quote.

The license key cannot full copy for other users #

The license key cannot be copied as fully from a user for another user since it shows incompletely.

Message Board on manual load must link in one interface #

The problem is the Message Board on manual load is not displayed the correct interface name. It supposes to display a specific interface when selected however, “All Interface always display.

Show incorrect date time on Last Run Time in Queues tab on CDC Control Board #

The error is on the Last Run Time column in Queues tab on CDC Control Board show incorrect date time. I have use Scheduler to process CP record to the external system. After that, when looking at on Queues tab, for Last Run Time it shows incorrect date time.

XML payload generation for adapter SFDC2SAPPI does not follow the WSDL structure #

The error occurs as the XML payload was generated and it doesn’t follow the WSDL structure and thus SAP-PI rejects the message saying that the XML payload is syntactically not well-formed. To solve the problem we have to generate the WSDL, which is well-formed based on the WSDL.

Wrong order in Workflow #

Since the workflow is wrong in order by being sorted by creation Date/Time, it fixed now, as it will sort by interface Source first then sort by Sequence.

Edit button of adapter property not working #

The value of property adapter did not change after edited and saved.

Some error with Export Data on Integration Details page #

There is some error occur with Export Data on Integration Details page as:

• Even the interface isn’t deployed it still can export the data
• The interface has no adapter but still can export data
• It still can export the data even there is no license key input and display the unspecific message.

Name of SuppressNullVaule property not correct #

The name of SuppressNullVaulue property is incorrect and it has to be changed.

Visualforce URL format change for Organization with MyDomain deployed #

It only shows the endpoint in visualforce page Manage Middleware WSDLs but this endpoint is not used anywhere. Now we just correct with view endpoint.

Error in Query Editor #

This error occurred when we click the Query Editor to write more statement e.g: Where Name = ‘Test’ plus with sobject existing before.

Add the help text for the fields #

We have many fields without Help Text in interface detail so we need Help Text for all fields to help for user to understand each field.