Informatica Cloud Application Integration - October 2019

Informatica® Cloud Application Integration

October 20199a. Release Notes

October 2019© Copyright Informatica LLC 1993, 2019

ContentsPreface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2019. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

October 2019. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

September 2019. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Summer 2019 July. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

May 2019. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

April 2019. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

March 2019. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

January 2019. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2018. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

December 2018. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

November 2018. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

October 2018 (Summer 2018). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

September 2018. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

August 2018. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

July 2018. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

May 2018. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

April 2018. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

March 2018. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

2017. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

December 2017. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

October 2017. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

August 2017. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

June 2017. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

May 2017. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

April 2017. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

March 2017. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

February 2017. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

January 2017. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

2019-10-07 1

2016. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

December 2016. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

October 2016. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

September 2016. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

August 2016. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

July 2016. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

June 2016. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

May 2016. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

April 2016. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

March 2016. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

February 2016. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

January 2016. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

PrefaceRead the Release Notes to know about upgrades, new features and enhancements, changed behaviors, fixed limitations, and known limitations for Informatica Cloud Application Integration.2019

October 2019

Upgrading to the October 2019 release

The following topics provide information about the tasks that you must perform after you upgrade to the October 2019 release:

Process Server restart

As part of this release, updates were made to the Process Server service on the Secure Agent to correct defects. The updates do not affect the service and the agent processes will continue to work as is. As a result of the deployment of the updates, you will see that the status of the Process Server service shows up as Restart Required.

Perform the following steps to restart the Process Server at your own convenience and get the latest updates:

1. Open the Administrator service and select Runtime Environments.

2. On the Runtime Environments page, click the name of the Secure Agent.

Note: You might have to expand the Secure Agent group to see the list of Secure Agents within the group.

3. Click the Details tab.

4. In the Agent Service Start or Stop area, select the service as Process Server.

2 2019-10-07

5. Click Stop.

6. Click Start to restart the Process Server service. After the service starts, the status changes to Up and Running. If the service fails to start, check the audit log to find the cause of the error.

Salesforce managed package URLs

The Salesforce managed package for Informatica Cloud Real Time version 1.25 uses version 46.0 of the Salesforce API.

You can install or upgrade to the latest managed package version 1.25.

Log in to the following URLs to install or upgrade to the latest managed package:

• To install the latest version 1.25, use the following URL: https://login.salesforce.com/?ec=302&startURL=%2Fpackaging%2FinstallPackage.apexp%3Fp0%3D04t1J0000007uro

• To install the latest sandbox version, use the following URL: http://test.salesforce.com/?ec=302&startURL=%2Fpackaging%2FinstallPackage.apexp%3Fp0%3D04t1J0000007uro

New features and enhancements

There are no new features in the October 2019 release of Application Integration.

Changed behavior

There are no changed behaviors in the October 2019 release of Application Integration.

Fixed limitations

There are no fixed limitations in the October 2019 release of Application Integration.

Known limitations

The following table describes the known limitations in the October 2019 release of Application Integration:

Defect Description

ICAI-15348 Salesforce connections to Salesforce organizations that use the Salesforce managed package version 1.25 do not display the labels for the following Salesforce objects:- AuthorizationForm- AuthorizationFormConsent- AuthorizationFormDataUse- AuthorizationFormText- EnhancedLetterhead

ICAI-15034 When you stop a subprocess that is in the Compensatable state, the parent process that contains the subprocess does not get stopped.

2019-10-07 3

https://login.salesforce.com/?ec=302&startURL=%2Fpackaging%2FinstallPackage.apexp%3Fp0%3D04t1J0000007uro


http://test.salesforce.com/?ec=302&startURL=%2Fpackaging%2FinstallPackage.apexp%3Fp0%3D04t1J0000007uro


Defect Description

ICAI-12885 If a process uses the Run Cloud Task system service and you edit the task name specified as content to use a formula, the process fails.

ICAI-10333 If you export a process that references a process object and import it into another organization, the process no longer references the process object.When you validate the process, you see the following Start step error:Field "<FieldName>" references to unknown Process Object: "<ProcessObjectName>".Workaround: Perform the following steps:1. Save the process and log out of Informatica Intelligent Cloud Services.2. Log in to Informatica Intelligent Cloud Services and select theApplication Integration service.3. Open and validate the process.You see that the validation error no longer appears.

ICAI-9787 In a process, if you use a Salesforce connection that does not have the suffix 'Salesforce', you do not see a Salesforce OBM URL.Workaround: Suffix all Salesforce connection names with the term 'Salesforce'. For example, name the connection 'AccountDetails-Salesforce' or 'TestSalesforce.'

September 2019

Upgrades

Process Server restart

As part of this release, a monthly Cloud Application Integration Service update was made to correct defects. The update does not affect the service and the agent processes will continue to work as is.

Updates were also made to the Process Server service on the Secure Agent. As a result of the deployment of this update, you will see that the status of the Process Server service shows up as Restart Required.

Perform the following steps to restart the Process Server at your own convenience and get the latest updates:

1. Open the Administrator service and select Runtime Environments.

2. On the Runtime Environments page, click the name of the Secure Agent.

You might have to expand the Secure Agent group to see the list of Secure Agents within the group.

3. Click the Details tab.

4. In the Agent Service Start or Stop area, select the service as Process Server.

5. Click Stop.

6. Click Start to restart the Process Server service. After the service starts, the status changes to Up and Running. If the service fails to start, check the audit log to find the cause of the error.

4 2019-10-07







New Features and Enhancements

There are no new features in the September 2019 release of Application Integration.

Fixed Limitations

The following table describes the fixed limitations in the September 2019 release of Application Integration:

Defect Description

ICAI-14717 If a process contains Japanese characters in its name, the soap:address value in the generated WSDL file is not valid. Therefore, you cannot invoke the process by using the WSDL file.

Known Limitations

The following table describes the known limitations in the September 2019 release of Application Integration:

Defect Description

ICAI-15348 Salesforce connections to Salesforce organizations that use the Salesforce managed package version 1.25 do not display the labels for the following Salesforce objects:- AuthorizationForm- AuthorizationFormConsent- AuthorizationFormDataUse- AuthorizationFormText- EnhancedLetterhead

ICAI-15034 When you stop a subprocess that is in the Compensatable state, the parent process that contains the subprocess does not get stopped.


2019-10-07 5





Defect Description



Summer 2019 JulyThis section describes the upgrades, new features, fixed limitations, and known limitations in the Summer 2019 July release of Application Integration.

Upgrades








The Summer 2019 July release of Application Integration includes the following new features and enhancements:

6 2019-10-07





Asset dependencies

You can view asset dependencies on the Explore page. When you view dependencies for an asset, Informatica Intelligent Cloud Services lists the objects in your organization that the asset uses as well as the objects that use the selected asset.

For more information about viewing asset dependencies, see Asset Management.

Fault information for process steps

When a process faults, the Process View Detail page displays fault information for the steps that faulted. Click a faulted step and click the Fault tab to view the fault information. The Fault tab displays a code, reason, source, and details for the fault that help you resolve the faults.

For more information about faulted steps, see Monitor.

RabbitMQ Connector

You can use RabbitMQ Connector to create a RabbitMQ connection and listen to specific message events. You can create a RabbitMQ consumer to read messages from a queue and create a RabbitMQ producer to write messages to an exchange. You can use the RabbitMQ consumer and the RabbitMQ producer within a process.

For more information about RabbitMQ Connector, see RabbitMQ Connector Guide for Informatica Cloud Application Integration.

Salesforce Lightning theme

You can use the Salesforce Lightning theme when you configure a guide. The Guide Launcher in Salesforce also supports the Salesforce Lightning theme.

For more information about the Salesforce Lightning theme, see Design.

Salesforce Platform events and PushTopic queries

Salesforce Connector supports the Salesforce Streaming API. You can configure an event source in a Salesforce connection to subscribe to Salesforce platform events and PushTopic queries. You can use the event source in a process to consume changes from Salesforce platform events and PushTopic queries in near real time.

For more information about subscribing to Salesforce platform events and PushTopic queries, see Salesforce Connector Guide for Informatica Cloud Application Integration.

Validation for service connectors and connections

When you create a service connector or a connection, you can use the Validation panel to verify if there are validation errors and view the error details.

In the Validation panel, errors are grouped based on the tab where they occur. Click the arrow corresponding to a tab name as shown in the following image to view a list of errors that occur in the tab:

2019-10-07 7

Click an error row as shown in the following image to move to the erroneous field and take corrective action:

As and when you correct the errors, the error list in the Validation panel is refreshed.

For more information about validating service connectors and connections, see Design.

Fixed Limitations

The following table describes the fixed limitations in the September 2019 release of Application Integration:

Defect Description

ICAI-14717 If a process contains Japanese characters in its name, the soap:address value in the generated WSDL file is not valid. Therefore, you cannot invoke the process by using the WSDL file.

8 2019-10-07

Known Limitations

The following table describes the known limitations in the Summer 2019 release of Application Integration:

Defect Description




May 2019This section describes the upgrades, new features, fixed limitations, and known limitations in the May 2019 release of Application Integration.

Upgrades







2019-10-07 9






The May 2019 release of Application Integration includes the following new feature:

Support for new HMAC functions in Process Designer

You can generate a digital signature by using the following HMAC functions in Process Designer:

hmacSignature

Generates an HMAC signature using the specified algorithm such as HMACSHA256 or HMACSHA512 and the optional encoding.

Use the following syntax:

dsig:hmacSignature( $data as xs:string, $key as xs:string, $algorithm as xs:string, $encoding as xs:string? ) as xs:stringhmacSHA512signature

Generates an HMAC SHA512 signature using the optional encoding.

Use the following syntax:

dsig:hmacSHA512signature ( $data as xs:string, $key as xs:string, $encoding as xs:string? ) as xs:string

Changes

The May 2019 release of Application Integration includes the following changed behaviors:

Tomcat version for Process Server on Secure Agent

Process Server that runs on a Secure Agent now uses Tomcat version 8.5.39.

Previously, Process Server that ran on a Secure Agent used Tomcat version 7.0.65.

ae-message.log files

The ae-message.log files are now available in the following directory:

<Informatica Cloud Secure Agent installation directory>\apps\process-engine\logs\enginePreviously, the ae-message.log files were available in the following directory:

<Informatica Cloud Secure Agent installation directory>\apps\process-engine\logs\engine1The contents under the engine1 folder that was created before the upgrade will no longer be used. You can manually delete the folder if needed.

10 2019-10-07

Fixed Limitations

The following table describes the fixed limitations in the May 2019 release of Application Integration:

Defect Description

ICAI-13422 When you export a process object, the dependent process objects do not get exported even if you choose to export the dependent process objects.

Known Limitations

The following table describes the known limitations in the May 2019 release of Application Integration:

Defect Description




April 2019This section describes the upgrades, new features, fixed limitations, and known limitations in the April 2019 release of Application Integration.

Upgrades




2019-10-07 11





There are no new features in the April 2019 release of Application Integration.

Fixed Limitations

There are no fixed limitations in the April 2019 release of Application Integration.

Known Limitations

The following table describes the known limitations in the April 2019 release of Application Integration:

Defect Description


ICAI-10333 If you export a process that references a process object and import it in to another organization, the process no longer references the process object.When you validate the process, you see the following Start step error:Field "<FieldName>" references to unknown Process Object: "<ProcessObjectName>".Workaround: Perform the following steps:1. Save the process and log out of Informatica Intelligent Cloud Services.2. Log in to Informatica Intelligent Cloud Services and select theApplication Integration service.3. Open and validate the process.You see that the validation error no longer appears.


March 2019This section describes the new features, upgrades, fixed limitations, and known limitations for the March 2019 release of Application Integration.

12 2019-10-07





Upgrades








The Winter 2019 March release of Application Integration includes the following new features:

Kafka Connector

You can use Kafka Connector to create a Kafka connection and listen to specific message events. You can create a Kafka consumer to read messages from a topic and create a Kafka producer to write messages to a topic. You can use the Kafka consumer and the Kafka producer within a process.

Service Connectors on GitHub 

Informatica has uploaded several REST and SOAP API-based service connectors on GitHub. You can download these connectors for free and import them into your organization.

Access the following URL to download the service connectors:

https://github.com/InformaticaCloudApplicationIntegration/Service-Connectors

You can also upload your service connector files and contribute towards enriching the repository.

Fixed Limitations

There are no fixed limitations in this release.

2019-10-07 13





https://github.com/InformaticaCloudApplicationIntegration/Service-Connectors

Known Limitations

The following table describes the known limitations in the January 2019 release:

Defect Description




January 2019This section describes the upgrades, fixed limitations, and known limitations for the January 2019 release of Application Integration.

Upgrades







14 2019-10-07






There are no new features in the January 2019 release of Application Integration.

Fixed Limitations

The following table describes the fixed limitations in the January 2019 release:

Defect Description

ICAI-13044 Guides that are embedded into third-party pages fail because of the CORS policy.

ICAI-10994 If you enter a group in the Allowed Groups field of a process deployed to a Secure Agent, you cannot invoke the process.When you invoke the process, you see the following HTTPS 500 error:User [email protected] not authorized to access service

Known Limitations

The following table describes the known limitations in the January 2019 release:

Defect Description



2018

December 2018This section describes the upgrades, fixed limitations, and known limitations for the December 2018 release of Application Integration.

2019-10-07 15

Upgrades








There are no new features in the December 2018 release of Application Integration.

Fixed Limitations

The following table describes the fixed limitations in the December 2018 release:

Defect Description

ICAI-12566 If there are multiple HTTP invokes within a process and the number of threads exceeds 600, the service call times out and the Process Engine restarts automatically several times.

ICAI-12494 When you invoke a service connector that requires a client-side certificate, the endpoint returns a 403 forbidden error. The error occurs even if you have imported the private key and certificate to the keystore, and restarted the Secure Agent.

ICAI-12442 If the Secure Agent runs on a German locale and you configure the Wait step to pause at a specific time that uses the 24-hour time format, the Process Editor does not load.

ICAI-12242 When the data contains multi-byte characters, the Delimited Content Writer of the File Connector writes corrupted data.

ICAI-12199 When you add an object into an object list of a process object, the following validation error occurs:The source field is not configured for the operation. Configure a source field.

16 2019-10-07





Known Limitations

The following table describes the known limitations in the December 2018 release:

Defect Description


ICAI-10994 If you enter a group in the Allowed Groups field of a process deployed to a Secure Agent, you cannot invoke the process.When you invoke the process, you see the following HTTPS 500 error:User [email protected] not authorized to access service


November 2018This section describes the upgrades, new features, fixed limitations, and known limitations for the November 2018 release of Application Integration.

Upgrades







2019-10-07 17






There are no new features in the November 2018 release of Application Integration.

Fixed Limitations

The following table describes the fixed limitations in the November 2018 release:

Defect Description

ICAI-11356 In a guide, if you use a process object field in a Decision step, the guide does not always follow the correct path.Workaround: Use an Assignment step to assign the process object field to a temporary field. Then, use the temporary field in the Decision step.

Known Limitations

The following table describes the known limitations in the November 2018 release:

Defect Description


ICAI-10994 If you enter a group in the Allowed Groups field of a process deployed to a Secure Agent, you cannot invoke the process.When you invoke the process, you see the following HTTPS 500 error: User [email protected] not authorized to access service

ICAI-9787 In a process, if you use a Salesforce connection that does not have the suffix "Salesforce", you do not see a Salesforce OBM URL.Workaround: Suffix all Salesforce connection names with "Salesforce'. For example, name the connection 'AccountDetails-Salesforce' or 'TestSalesforce.'

October 2018 (Summer 2018)This section describes the upgrades, new features, fixed limitations, and known limitations for the October 2018, also known as Summer 2018, release of Application Integration.

18 2019-10-07

Upgrades








The Summer 2018 (October 2018) release of Application Integration includes the following enhancements:

Asset Management

You can view projects, folders, and assets for all of the services that you use on the Explore page. If you select an asset that was created in another service, the service opens in a new browser tab.

Asset Migration

The following enhancements improve the asset import and export functionality:

• You can view the export and import logs for all services in Informatica Intelligent Cloud Services that your organization uses on the My Import/Export Logs page. Previously, you could only view logs for Application Integration assets.

• When you export an Application Integration asset, you get a ZIP file that contains the asset in XML format. Previously, the ZIP file contained assets in the JSON format.

Note: You can successfully import export files that you created before Spring 2018. Backward compatibility has been maintained.

• You can publish Application Integration assets at the time of import. Based on where the asset was published in the source organization, the import ZIP file contains details of whether the asset is to be published to a Secure Agent or to Cloud Server.

Custom Roles

When you create a custom user role in the Administrator service, you can assign privileges that give the role targeted access to multiple features of the Application Integration and Application Integration Console services.

You can assign the following privileges to a custom role:

• Administration

• Console Administration

2019-10-07 19





• Development

• Data Viewer

• Monitoring

• Publish Assets

• View Application Integration Console

• View Application Integration Designer

Fixed Limitations

The following table describes the fixed limitations in the Summer 2018 (October 2018) release:

Defect Description

ICAI-10035 If you create a custom role with the necessary permissions and assign only the custom role to a user, the user sees the following error when they select the Application Integration or Application Integration Console service:cloud.ui.unable.to.connect

ICAI-8116 Publishing or unpublishing an asset affects the Updated On time stamp of the asset. The time stamp reflects the time at which the asset was published or unpublished, and not the time at which it was last modified.

CCON-13061 Changes to the structure of a table that is associated with an SAP BAPI do not get reflected at run time until you restart the Secure Agent.

Known Limitations

The following table describes the known limitations in the Summer 2018 (October 2018) release:

Defect Description


ICAI-11356 In a guide, if you use a process object field in a Decision step, the guide does not always follow the correct path.Workaround: Use an Assignment step to assign the process object field to a temporary filed. Then, use the temporary field in the Decision step.

20 2019-10-07

Defect Description

ICAI-10994 If you enter a group in the Allowed Groups field of a process deployed to a Secure agent, you cannot invoke the process.When you invoke the process, you see the following HTTPS 500 error: User [email protected] not authorized to access service


September 2018This section describes the upgrades, new features, fixed limitations, and known limitations for the September 2018 release of Application Integration.

Upgrades








The September 2018 release of Application Integration has no new features.

2019-10-07 21





Fixed Limitations

The following table describes the known limitations in the September 2018 release:

Defect Description

ICAI-11159 When you use the Run Cloud Task system service in a process, you cannot select the following Data Integration tasks:- Replication- Linear taskflow

Known Limitations

The following table describes the known limitations in the September 2018 release:

Defect Description

ICAI-11356 In a guide, if you use a process object field in a Decision step, the guide does not always follow the correct path.Workaround: Use an Assignment step to assign the process object field to a temporary filed. Then, use the temporary field in the Decision step.


ICAI-10035 If you create a custom role with the necessary permissions and assign only the custom role to a user, the user sees the following error when they select the Application Integration or Application Integration Console service:cloud.ui.unable.to.connectWorkaround:In addition to the custom role, assign the user a system-defined role such as Monitor.


August 2018This section describes the upgrades, new features, fixed limitations, and known limitations for the August 2018 release of Application Integration.

Upgrades



22 2019-10-07






The August 2018 release of Application Integration includes the following enhancement:

Get HTTP Headers

You can use header functions in the Expression Editor to get details about the HTTP headers that you pass when you invoke a process.

You can use header functions to perform the following tasks:

• Get all header names and values.

• Get a Date header name and value.

• Get a specific header value.

• Get a sequence of header names without values.

• Get either a header value or some default value.

• Check if a specific header exists.

Fixed Limitations

The following table describes the fixed limitations in the August 2018 release.

Defect Description

ICAI-10931 If you use a picklist that is associated with a process object in a process Data Decision step, you cannot add custom answers.

ICAI-9673 If you create a process that calls a Data Integration task and deploy the process to a Secure Agent, process execution fails when you invoke the process. You see an HTTPS 503 (service unavailable) error in the Process Engine log if you execute the process.

2019-10-07 23





Known Limitations

The following table describes the known limitations in the August 2018 release:

Defect Description




July 2018This section describes the upgrades, new features, fixed limitations, and known limitations for the July 2018 release of Application Integration.

Upgrades








The July 2018 release of Application Integration includes the following enhancements:

24 2019-10-07





Guides

A new asset type called 'guide' is now available. A guide is a set of screens that prompts users to review, enter, or confirm data. For example, you can create a guide to automate the process that a sales manager follows to create a new account or update an existing account in Salesforce.

For more information, see Design > Designing Guides in the Application Integration online help.

Allowed Groups and Allowed Users

When you create a process, you can specify the users and groups that have access to the service URL. Previously, you could specify a role that would have access to the service URL.

For more information, see Design > Designing Processes > Setting Process Properties > General Properties in the Application Integration online help.

Existing processes with Allowed Roles specified will continue to work.

However, you can edit the process to remove roles and add users and groups.

Fixed Limitations

There are no fixed limitations in the July 2018 release.

Known Limitations

The following table describes the known limitations in the July 2018 release:

Defect Description


ICAI-9673 If you create a process that calls a Data Integration task and deploy the process to a Secure Agent, process execution fails when you invoke the process. You see an HTTPS 503 (service unavailable) error in the Process Engine log if you execute the process.

ICAI-10931 If you use a picklist that is associated with a process object in a process Data Decision step, you cannot add custom answers.


May 2018This section describes the upgrades, new features, fixed limitations, and known limitations for the May 2018 release of Application Integration.

2019-10-07 25

Upgrades








The May 2018 release of Application Integration includes the following enhancements:

Microsoft Internet Explorer 11

You can use Application Integration and Application Integration Console on Microsoft Internet Explorer 11.

You must first make some browser setting changes. For more information, see System Requirements under Getting Started.

Tags

You can assign tags to assets so that you can easily view associated assets on the Explore page.

For example, your company has four regional offices. You want to view assets by the region that manages them. You create a tag for each region and associate each asset with the appropriate tag.

You can create tags and assign tags to assets on the Explore page.

26 2019-10-07





Fixed Limitations

The following table describes the fixed limitations in the in the May 2018 release:

Defect Description

ICAI-10010 When you invoke a process that requires authentication and that is deployed to a Secure Agent, you sometimes see an HTTP 401 response. This is because of a timeout issue.

ICAI-10076 You sometimes face a problem when you test or invoke a service connector that requires authentication. This happens because the service connector is deployed to a Secure Agent that has a proxy server configuration enabled.

ICAI-8729 You see an Unable to load the catalina.pid file required to terminate tomcat error when you start the Secure Agent on a Windows machine if the <agent home> path contains spaces. You see this error if you start the Secure Agent through the Informatica Cloud Secure Agent Manager or on command line, with the agent_start.bat file. As a result, you are unable to start Process Server.

Known Limitations

The following table describes the known limitations in the May 2018 release:

Defect Description



April 2018This section describes the upgrades, new features, fixed limitations, and known limitations for the April 2018 release of Cloud Application Integration.

Upgrades




2019-10-07 27





There are no new features the April 2018 release.

Fixed Limitations

There are no fixed limitations in the April 2018 release.

Known Limitations

The following table describes the known limitations in the April 2018 release:

Defect Description


ICAI-8729 You see an Unable to load the catalina.pid file required to terminate tomcat error when you start the Secure Agent on a Windows machine if the <agent home> path contains spaces. You see this error if you start the Secure Agent through the Informatica Cloud Secure Agent Manager or on command line, with the agent_start.bat file. As a result, you are unable to start Process Server.Workaround: Perform the following steps to start the Secure Agent:1. In the Search Windows field, enter Services.2. Select the Services Desk top app.3. In the Services list, right-click Informatica Cloud Secure Agent and then select Start.If this workaround does not work in your environment, uninstall and then reinstall the Secure Agent in a path that does not contain spaces. For example, install the Secure Agent in the D:\Programs\InformaticaCloudSecureAgentFlorence directory.

March 2018This section describes the upgrades, new features, fixed limitations, and known limitations for the March 2018 release of Cloud Application Integration.

28 2019-10-07





Upgrades








March 2018 marks the inaugural release of theApplication Integration an Application Integration Console services on Informatica Intelligent Cloud Services.

For details about the release, see the blog post at: https://life.informatica.com/informatica-cloud-application-integration-and-api-management-launch/.

Fixed Limitations

The following table describes the fixed limitations in the March 2018 release:

Defect Description

ICAI-9721 When you publish a process that contains a Salesforce connection, you cannot view the Salesforce OBM URL under the Process Properties tab of the process. Instead, you need to manually construct a Salesforce OBM URL for the process.

ICAI-9774 If you re-publish a connection after you modify the service connector, the connection does not reflect the modification. Subsequently, any process that uses the connection does not have access to the latest version of the service connector.

ICAI-9510 In Application Integration Console, if you click the (+) icon on the subprocess step of the Process View Detail page of a parent process, the subprocess Process View Detail page does not open.

2019-10-07 29





https://life.informatica.com/informatica-cloud-application-integration-and-api-management-launch/

Known Limitations

The following table describes the known limitations in the March 2018 release:

Defect Description


2017

December 2017This section describes the upgrades, new features, fixed limitations, and known limitations for the December 2017 release of Cloud Application Integration.

Upgrades

Salesforce Managed package URLs

The Salesforce Managed Package for Informatica Cloud Real Time version 1.24 uses version 40.0 of the Salesforce API.

You can install or upgrade to the latest managed package, version 1.24. If you have managed package version 1.09 or earlier, first upgrade to version 1.10 and then install version 1.24.

Use the following URLs to install or upgrade to the latest managed package:

• To upgrade to version 1.10, use this URL: https://login.salesforce.com/packaging/installPackage.apexp?p0=04to00000003YPD

• To install the latest version, 1.24. use this URL: https://login.salesforce.com/packaging/installPackage.apexp?p0=04t1J000000gOtF

• To install the latest sandbox version, use this URL: http://test.salesforce.com/packaging/installPackage.apexp?p0=04t1J000000gOtF


The December 2017 release of the Cloud Application Integration service includes the following enhancements:Amazon S3 Service Connector

You can configure eight new properties for Amazon S3 source events. With these properties, you can configure how you want the connector to handle processed objects and set a maximum retry interval value.

30 2019-10-07

https://login.salesforce.com/packaging/installPackage.apexp?p0=04to00000003YPD

https://login.salesforce.com/packaging/installPackage.apexp?p0=04t1J000000gOtF

http://test.salesforce.com/packaging/installPackage.apexp?p0=04t1J000000gOtF

For more information, see the Object Operations Settings properties and the Failure Handling Settings properties sections at Amazon S3 Connector Guide > Amazon S3 Connector Guide > Amazon S3 Event Sources > Amazon S3 Event Source Properties.

Fixed Limitations

The following table describes the fixed limitations in the December 2017 release:

Defect Description

ICAI-8460 The Address Doctor API connector returns an incorrect address if the house number is greater than three digits.

ICAI-8370 If you use WebSphere MQ messaging service and enable the "Rollback On Error" property in the Queues and Listeners section, rejected messages do not move to the DLQ after the configured number of retry attempts. Instead, the following events occur:- WebSphere MQ performs more than the configured number of redelivery attempts. If the number

of redelivery attempts is large, the Secure Agent might become unresponsive. This is because WebSphere MQ resends messages faster than normal.

- WebSphere MQ clones rejected messages in the DLQ.

ICAI-8308 If you enable custom fault handling in a process that contains a Throw step, Process Server does not set the <faultCode> and <faultstring> values. This happens in a SOAP environment.

ICAI-8283 The following might occur when you publish a Process Developer process:Error deploying BPR:'<name.pdd>' is invalid and will not be deployedThe error occurs if the process has two or more Jump steps that jump to the success branch of a fault handling container.

ICAI-8249 The Scheduling page in the Process Console takes an unusually long time to load or respond.

ICAI-8053 Chinese characters in the response payload of a service connector appear garbled.

CCON-9811 When you simultaneously run multiple instances of a task that contains an SAP BAPI Service Call, some instances fail randomly.

Known Limitations

The following table describes the known limitations in the December 2017 release:

Defect Description

CCON-1935 You cannot publish an SAP BAPI connection in which a BAPI function parameter contains a field name that starts with numbers.

October 2017This section describes the upgrades, new features, fixed limitations, and known limitations for the October 2017 release of Cloud Application Integration.

2019-10-07 31

Upgrades

Salesforce Managed package URLs





• To install the latest version, 1.22. use this URL: https://login.salesforce.com/packaging/installPackage.apexp?p0=04t1J000000Kb2b

• To install the latest sandbox version, use this URL: http://test.salesforce.com/packaging/installPackage.apexp?p0=04t1J000000Kb2b


The October 2017 release of the Cloud Application Integration service includes the following new features and enhancements:

OData

You can now use OData to page through result sets when used in conjunction with JDBC connections. This capability is enabled for the Oracle, Microsoft SQL Server, IBM DB2, and MySQL databases. Use the OData $skip directive to page through large result sets.

With this feature, Salesforce customers using Lightning will benefit from the ability to work with large lists.

Service Connector Bindings

You can generate an MD5 signature in the HTTP Headers section when you define actions for a service connector. For more information, see the HTTP Headers section of the Designing Service Connectors topic under Design.

Fixed Limitations

The following table describes the fixed limitations in the October 2017 release:

Defect Description

ICAI-8159 When you generate a JSON payload, the service connector suppresses all line feeds (\n). This causes issues with the text formatting.

ICAI-7996 When you test or publish a PostgreSQL JDBC connection, the connection sometimes fails. This is because of a class loading conflict with the PostgreSQL drivers available.

32 2019-10-07


https://login.salesforce.com/packaging/installPackage.apexp?p0=04t1J000000Kb2b

http://test.salesforce.com/packaging/installPackage.apexp?p0=04t1J000000Kb2b

Defect Description

ICAI-7839 When you use the Amazon S3 connector to create an object in an S3 bucket, you might later face issues when an application reads this object. This happens if you do not specify the content encoding metadata property when you create the object and the connector uses an incorrect default value of UTF-8.

ICAI-7706 When you invoke an endpoint URL and specify an application/xml accept header, the service still returns JSON instead of XML.

CCON-2066 You cannot publish an SAP BAPI connection in which a BAPI function parameter contains the slash character in the namespace.

Known Limitations

The following table describes the known limitations in the October 2017 release:

Defect Description

ICAI-8053 Chinese characters in the response payload of a service connector appear garbled.

CCON-1935 You cannot publish an SAP BAPI connection in which a BAPI function parameter contains a field name that starts with numbers.

August 2017This section describes the upgrades, new features, fixed limitations, and known limitations for the August 2017 release of Cloud Application Integration.

Upgrades

Salesforce Managed Package URLs





• To install the latest version, 1.21, use this URL: https://login.salesforce.com/packaging/installPackage.apexp?p0=04t1J000000KatE

• To install the latest sandbox version, use this URL: https://test.salesforce.com/packaging/installPackage.apexp?p0=04t1J000000KatE

2019-10-07 33


https://login.salesforce.com/packaging/installPackage.apexp?p0=04t1J000000KatE

https://test.salesforce.com/packaging/installPackage.apexp?p0=04t1J000000KatE


The August 2017 release of the Cloud Application Integration service includes the following new features and enhancements:

Service Connector Actions

Effective in this release, you can configure the following new properties for an action:

• Max Redirects: Specify the maximum number of endpoints to which a service connector can redirect.Previously, there was no limit to the number of redirects that a service connector could make. This could lead to the service connector performing an infinite loop of redirects.

• Preemptive Auth: Send authentication details along with a request to an endpoint. This enhancement reduces the number of exchanges between a service connector and an endpoint.Previously, the service connector would send authentication details to an endpoint only after the endpoint requested authentication.

Salesforce API

The Informatica Salesforce Managed Package now uses version 40.0 of the Salesforce API. Previously, the managed package used version 37.0 of the Salesforce API.

Salesforce Connector and Synchronization

We’ve improved the way we discover Salesforce metadata such as picklists. Previously, customers with a large list of picklists and record types might fail to complete metadata discovery successfully

Service Connector Bindings

The following enhancements were made to the Basic authentication option of service connector bindings:

• You can specify user credentials as text or as a field.

• Use the Show password option to see or hide the password on screen and when you export the service connector.

JMS Messaging Service

A new property, Rollback on Error, was added to the Queues and Listeners section of the JMS Messaging service. Select Rollback on Error if you want to ignore failed messages or messages that have encountered an exception and move to the next message. You must configure the JMS broker to reprocess messages that Process Server cannot process and rejects using Dead Letter Queueing or a similar service.

Scheduled Maintenance

A new property, Default Faulted Process Retention, is available on the ADMIN > Maintenance > Storage page. Use this property to specify the time for which Process Server retains faulted processes in the database.

34 2019-10-07

Fixed Limitations

The following table describes the fixed limitations in the August 2017 release:

Defect Description

ICRT 7705 If you want to view the Swagger JSON specification of a process payload, you cannot use path parameters.

ICRT 7570 When you set the Max Messages Per Poll event source property of the Amazon S3 connector to greater than 1, the connector sometimes stops or gets unpublished.

ICRT 7496 When you run an Amazon S3 mapping to read or write data to an Amazon S3 bucket that requires Signature Version 4 authentication, the mapping fails with the following error message: The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.

ICRT 7489 When you enable Overwrite mode and import a process, the publication status of the process remains up-to-date instead of changing to out-to-date.

ICRT 7429 If you publish a process with a function that contains both single and double quotes you see the following error: String index out of range.

ICRT 7278 You cannot test a service connector on a Secure Agent group whose name contains characters that are URL encodable. For example, you cannot test a service connector on a Secure Agent group whose name contains a blank space.

ICRT 7203 Sometimes, a service connector does not escape special characters and generates an incorrect JSON payload.

ICRT 7168 When you create a service connector with two output fields, the first output field sometimes returns empty. This happens if the first output field is a process object and the second output field contains an XQuery expression that uses the first output field.

ICRT 7094 You see an error if you use the empty function with a guide that has an empty process object or process object list.

ICRT 6264 You see an error when you launch a datasource from the Admin screen of the Process Console. This happens if the data source name contains a slash (/).

CON 8684 SAP BAPI Connector does not support table type that refers to a pre-defined line type.

CON 8569 You cannot use a BAPI parameter with a nested table type.

Known Limitations

The following table describes the known limitations in the August 2017 release:

Defect Description

CON 2066 You cannot publish an SAP BAPI connection in which a BAPI function parameter contains the slash character.

CON 1935 You cannot publish an SAP BAPI connection in which a BAPI function parameter contains fields that start with numbers.

2019-10-07 35

Defect Description

ICRT 4232 If you do not assign input to the SAP BAPI service call, the publish process shuts down unexpectedly at run time.

ICRT 4231 When you first select an object from the XML Object list in the Formula Editor during the Assignment step configuration, you cannot view the object fields.Workaround: Clear the contents in the Formula Editor and reselect the object from the XML Object list.

ICRT 6932 If you pass an input string prefixed with space characters, the Formula Editor does not retain the space characters. Instead, the Formula Editor removes all space characters except one.

June 2017This section describes the upgrades, new features, fixed limitations, and known limitations for the June 2017 release of Cloud Application Integration.

Upgrades

Salesforce Managed Pakcage URLs

The latest Salesforce Managed Package URLs for Informatica Cloud Real Time (Version 1.20) is available for install or upgrade.

If you are upgrading from a managed package version 1.09 or below, first upgrade to version 1.10 and then install version 1.20.

• To upgrade to version 1.10, use this URL: https://login.salesforce.com/packaging/installPackage.apexp?p0=04to00000003YPD.

• To install the latest version, 1.20, use this URL: https://login.salesforce.com/packaging/installPackage.apexp?p0=04to0000000X43p

• To install the latest sandbox version, use this URL: https://test.salesforce.com/packaging/installPackage.apexp?p0=04to0000000X43p.

Connectors

This section describes the upgrade impact for connectors in the April 2017 release.

SAP BAPI Connector

If you upgrade the Secure Agent from a 32-bit operating system, the Process Engine copies the 32-bit SAP JCo libraries to the following directory:<Secure Agent Installation Directory>\apps\process-engine\extYou must replace the 32-bit JCo libraries with 64-bit JCo libraries.

If you upgrade the Secure Agent from a 64-bit operating system, you do not need to perform any post-upgrade task for SAP BAPI Connector. The Process Engine copies the 64-bit SAP JCo libraries to the following directory:

36 2019-10-07


https://login.salesforce.com/packaging/installPackage.apexp?p0=04to0000000X43p

https://test.salesforce.com/packaging/installPackage.apexp?p0=04to0000000X43p

<Secure Agent Installation Directory>\apps\process-engine\extEffective in the Spring 2017 release, you must copy the SAP JCo libraries to the following directory:

<Secure Agent Installation Directory>\apps\process-engine\extPreviously, you copied the SAP JCo libraries to the following directory and configured the JAVA_LIBS property:

<Secure Agent Installation Directory>\main\bin\rdtm-extra\tpl\sap


The June 2017 release of the Cloud Application Integration service includes the following new features and enhancements:

HTTP/HTTPS Proxy Servers for the FTP Connector

Effective in this release, you can use an HTTP or HTTPS proxy server to connect to an FTP server. To enable an HTTP or HTTPS proxy server, use the new Proxy Settings FTP connection properties. For more information, see the FTP Connection Properties topic in the FTP Connector Guide.

Enhanced Fault Details on the Process View Detail Page

Effective in this release, detailed fault information is available on the Process View Detail Page. You can view fault information such as Code, Reason, Source, and Exception Message, for example.Previously, you could only see the fault name and a generic fault reason. For more information, see the Fault Details topic under the Examining Processes section of the Monitor guide.

Fixed Limitations

The following table describes the fixed limitations in the June 2017 release:

Defect Description

ICRT 6873 When you run a guide in the Salesforce Managed Package and enable the Content Sniffing Protection option, the following error appears: Refused to execute script from '...' because its MIME type ('application/json') is not executable, and strict MIME type checking is enabled.

ICRT 6014 When you use a JDBC connection with OData version 4 to retrieve data from an SQL table with a datetime field that contains milliseconds, you encounter an error.

2019-10-07 37

Known Limitations

The following table describes the known limitations in the June 2017 release:

Defect Description






May 2017This section describes the upgrades, new features, fixed limitations, and known limitations for the May 2017 release of Cloud Application Integration.

Upgrades

Salesforce Managed Pakcage URLs






Connectors


38 2019-10-07




SAP BAPI Connector







The May 2017 release of the Cloud Application Integration service includes the following new features and enhancements:

Group Process Server Instances

Effective in this release, you can group multiple Process Server instances into a single logical group if you have the Secure Agent Cluster license. You can cluster two or more Process Server instances to ensure high availability. You can also balance the workload across Process Server instances using the load balanced Process Server configuration. For more details, see the Secure Agent Groups topic under Administer

Set the Database Time Zone Value for the JDBC Connection

The JDBC connection includes the TimeZone field in the connection properties. When you read date and time values using a JDBC connection enabled with OData and the machines that host the database and the Secure Agent are in different time zones, you must select the time zone value of the database to ensure that OData returns the correct date and time values.

2019-10-07 39

Known Limitations

The following table describes the known limitations in the May 2017 release:

Defect Description






Fixed Limitations

The following table describes the fixed limitations in the Spring 2017 release:

Defect Description

ICRT 6084 You see a Not valid for Property <property> error if you execute an OData service URL that contains a Datetime field with precision.

April 2017The April 2017 release of Cloud Application Integration coincides with the Spring 2017 release of Informatica Cloud.

Though there is no explicit April 2017 Cloud Application Integration release, this section describes the upgrades, new features, and known limitations for the April 2017 period.

Upgrades



40 2019-10-07





Connectors


SAP BAPI Connector







The April 2017 release of the Cloud Application Integration service includes the following new features and enhancements:

Secure Agent Version 33.0

Informatica will upgrade Cloud Application customers who run Secure Agent version 30.0 and earlier to Secure Agent version 33.0 in April, 2017. The automatic upgrade will happen with the Spring 2017 release of Informatica Cloud Services.

As a Cloud Application Integration customer, you gain the following benefits from Secure Agent version 33.0:

• The Process Server service is a new engine of the Secure Agent platform that executes independent of other engines to help overall resilience.

2019-10-07 41




• The underlying Secure Agent database for Secure Agent version 33.0 is PostgreSQL. The PostgreSQL database can handle a larger amount of data than the earlier underlying database, H2. You will also see performance improvements.

• You can run processes published to a Secure Agent from within the enterprise through HTTPS/REST or HTTPS/SOAP calls in addition to JMS and AMQP queues and topics.

Informatica will upgrade Cloud Application Integration customers to Secure Agent version 33.0 in the following phases:

• Customers that Informatica hosts on APP1: On 15 April, 2017.

• Customers that Informatica hosts on APP2 and APP3: On 22 April, 2017.

To prepare for this release, see the Prepare the Secure Agent for Upgrade topic in the Before You Upgrade section of the Informatica Cloud Spring 2017 What's New guide.

If you are Linux user with more than one Secure Agent installed on a single server, see the How To Learn article Upgrading Multiple Secure Agents on the Same Linux Server to Secure Agent Version 33.0 .

API Manager

You can use the new API Manager feature with the Informatica Cloud Real Time Advanced and Informatica Cloud Premium editions. Use API Manager to perform the following tasks:

• API-enable services and create managed service APIs using REST or SOAP.

• Expose managed APIs to partners, customers, and internal consumers through the API Gateway. In conjunction with API Manager, you can use can use API gateway to control and secure access to the APIs you expose.

Known Limitations

The following table describes the known limitations in the Spring 2017 release:

Defect Description






42 2019-10-07

March 2017This section describes the upgrades, new features, fixed limitations, and known limitations for the March 2017 release of Cloud Application Integration.

Upgrades







Secure Agent Version 30 and Later

Informatica will automatically upgrade all Cloud Application customers who run Secure Agent version 30 and earlier to Secure Agent version 33 in mid-April, 2017. The automatic upgrade will happen with the Spring 2017 release of Informatica Cloud Services.

Informatica will upgrade Cloud Application Integration customers to Secure Agent version 33 in the following phases:





The March 2017 release of the Cloud Application Integration service includes the following new features and enhancements:


Informatica will upgrade the Secure Agent to version 33 in the Spring 2017 release of Informatica Cloud. Cloud Application Integration customers can choose to perform an early upgrade to Secure Agent version 30 and later. For details, see Early Migration Guide: Secure Agent Version 30 and Later at https://network.informatica.com/docs/DOC-17175.

2019-10-07 43




https://network.informatica.com/docs/DOC-17175

If you are a Cloud Application Integration customer, you gain the following benefits from Secure Agent version 30 and later:

• The Process Server service is a new engine of the Secure Agent platform that executes independent of other engines to help overall resilience.

• The underlying Secure Agent database for Secure Agent version 30 and later is PostgreSQL. The PostgreSQL database can handle a larger amount of data than the earlier underlying database, H2. You will also see performance improvements.

• You can run processes published to a Secure Agent from within the enterprise through HTTPS/REST or HTTPS/SOAP calls in addition to JMS and AMQP queues and topics.

Service Connector Timings

You can see the HTTP Execution Time, the HTTP Response Parsing Time, and the Redirect Count of a service connector on the Test Results tab of the service connector UI.

Fixed Limitations

The following table describes the fixed limitations in the March 2017 release:

Defect Description

ICRT-6561 You see an exception when you use a Service Connector that contains an action that receives a redirect response. You see the exception if the Location header of the service connector contains a relative path like "Location: /".

ICRT-6282 You see an error If you deploy a process to the Secure Agent and use the data returned by the process in a service connector. You see the error if the process runs an SQL statement and returns textual data containing characters that are not valid according to XML specifications.

ICRT-5901 You cannot use the SAP BAPI Connector with Secure Agent version 30.0 and higher. When you test a SAP BAPI connection, a JCo exception occurs.

Known Limitations

The following table describes the known limitations in the March 2017 release:

Defect Description

ICRT 6849

The service URL of a process deployed to the Secure Agent does not work if you change the server host name or the HTTPS port number. The process service URL reflects the change but the Secure Agent does not. Tis happens if you use Secure Agent version 30 and later.Workaround: If you change the server host name or HTTPS port number, restart the Secure Agent before you invoke a process service URL.

February 2017This section describes the upgrades, new features and known limitations for the February 2017 release of Cloud Application Integration.

44 2019-10-07

Upgrades













Migrating from H2 to PostgreSQL

Cloud Application Integration customers who migrate to Secure Agent version 30.0 or later need to migrate data from the H2 database to the PostgreSQL database. Informatica provides a migration tool that does most of the migration for you. Follow the steps below to migrate to Secure Agent version 30.0 and higher and migrate your data from H2 to PostgreSQL:

1. Shut down the current Secure Agent, that is, a Secure Agent that is versioned lower than 30.0.

2. Install the new Secure Agent, that is, a Secure Agent versioned 30.0 or higher.

3. Check that the new Secure Agent is up and running, and then shut it down.

4. Download and unzip the migration tool, H2toPostgreSQLdatamigration_tool.zip, from the Informatica Cloud Network.

5. Open the migration.properties file in the Resources directory of the data migration tool and make the following changes:

a. Enter the correct absolute path to the old Secure Agent.

b. Enter the correct absolute path to the new Secure Agent.

2019-10-07 45




Important: Use a forward slash as the path separator when you enter paths in steps a and b.

c. Enter the correct H2 database credentials if you have changed them from the default credentials.

6. Save and close the migration.properties file.

7. Go to the root directory of the data migration tool and run the script migrate_data.bat (for Windows) or migrate_data.sh (for Linux).

8. After the scripts have successfully migrated your data from H2 to PostgreSQL, start the new Secure Agent.

After Upgrading the SAP Connector

Configure the JAVA_LIBS Property

After you upgrade the SAP Connector and copy the sapjco3.jar file, you must configure the JAVA_LIBS property in Informatica Cloud.

Perform the following steps to configure the JAVA_LIBS property:

1. Log in to Informatica Cloud.

2. Click Configure > Runtime Environments to access the Runtime Environments page.

3. To the left of the agent name, click Edit Secure Agent.

4. From the Type list, select Tomcat JRE.

5. Enter the JAVA_LIBS value based on the operating system on which the Secure Agent runs.

Operating System Value

Windows ../bin/rdtm-extra/tpl/sap/sapjco3.jar;../bin/rdtm/javalib/sap/sap-adapter-common.jar

Linux ../bin/rdtm-extra/tpl/sap/sapjco3.jar:../bin/rdtm/javalib/sap/sap-adapter-common.jar

6. Click OK to save the changes.

7. Restart the Secure Agent.

8. Repeat steps 1 through 7 on every machine where you installed the Secure Agent.

Update the SAP JCo Libraries Directory

After you upgrade the SAP Connector, you must copy the sapjco3.jar file to the following directory to process data through BAPIs:

<Informatica Secure Agent installation directory>\main\bin\rdtm-extra\tpl\sapBefore you copy the jar file, you must create the tpl\sap directory within the rdtm-extra directory if the tpl\sap directory does not already exist.

If you had created the data\process-engine-custom-lib folder earlier, you must delete the sapjco3.jar file from the data\process-engine-custom-lib folder after you upgrade the SAP Connector.

46 2019-10-07


The February 2017 release of the Cloud Application Integration service includes the following new features and enhancements:

Process Tracing Level 'Terse' maps to Logging Level 'Fault'

Effective in this release, the Terse tracing level maps to the Fault logging level. At the Fault logging level, Process Server logs only fault information, which decreases the size of the log file and improves processing speed.

To improve processing speed, perform no logging or minimum logging. Informatica recommends that you use the None or Terse logging levels.

For more information, see the following topics in the Cloud Application Integration online help:

• Tracing Level Considerations under Design.

• Logging Properties under Administer.

Previously, the Terse tracing level mapped to the Execution logging level.

PostgreSQL Database Utility Scripts

Effective in this release, use the db_maintenance.bat utility script to manually vacuum or reindex the entire PostgreSQL database or a single table in the PostgreSQL database.

For more information, see the following topics in the Administer section of the Cloud Application Integration online help:

• Managing the PostgreSQL Database on Windows.

• Managing the PostgreSQL Database on Linux.

Also see the Informatica Knowledge Base article How to: Perform manual vacuuming of the PostGreSql data records located in the AAP agent at: https://kb.informatica.com/howto/6/Pages/19/507480.aspx

Fixed Limitations

The following table describes the fixed limitations in this release:

Defect Description

ICRT 6476

If you are a user with only the Service Consumer role assigned, you cannot invoke a Process Developer process deployed on the Secure Agent.

ICRT 6424

If a subprocess modifies a part of a process object provided by a parent process, the parent process might not work as expected.For example, consider a parent process that uses process object A. Process object A contains a complex field, process object B. The following events occur:1. The parent process calls the subprocess.2. The subprocess executes but uses only process object B.3. As a result, for the rest of the execution of the parent process, process object B replaces process

object A.

2019-10-07 47

https://kb.informatica.com/howto/6/Pages/19/507480.aspx

Defect Description

ICRT 6282

If a process uses an XML payload that contains Latin or ASCII characters that are not valid according to XML specifications, you see a javax.xml.soap.SOAPException and a corrupted message.

ICRT 5609

If you use a JDBC connector to run a WHERE query that contains errors Process Server does not throw an error message. Instead, the Process Server ignores the error and executes the correct part of the WHERE query. This can lead to unpredictable behavior and data loss.

Known Limitations

The following table describes the known limitations in this release:

Defect Description

ICRT 6547 If you use HTTP or HTTPS to invoke a process on the Secure Agent, you might incur a time lag.Each time you invoke a process, the Secure Agent authenticates your Informatica Cloud Services (ICS) user credentials and caches these credentials for five minutes. If you invoke another process after the five minute cache period, the Secure Agent needs to authenticate your ICS user credentials again. This might cause time lag.Workaround: As a temporary measure, Informatica has exposed the default cache period and increased the default cache period from five minutes to 60 minutes. You can invoke processes to the Secure Agent over a period of 60 minutes and incur zero lag time.If you want to edit the default cache period, perform the following steps:1. Open the file aeEngineConfig.xml.mustache at <agent home>\downloads\package-process-engine.980\package\app\webapps\process-engine\WEB-INF\classes.

2. Search for Find <entry name="ICSAuthCacheTTL" value="3600"/> . Here, 3600 is the ICS credentials cache period in seconds.

3. Replace 3600 with the new cache period value, in seconds.For example, if, for security reasons, you want to change the cache period to 30 minutes, replace 3600 with 1800. This means that you can invoke process to the Secure Agent through HTTP or HTTPs for up to 30 minutes without authentication.

4. Save and close theaeEngineConfig.xml.mustache file.5. Restart the Secure Agent.

ICRT 6084 If you invoke an OData URL associated with database tables that contain a datetime field, you see a not valid for this property error.

January 2017This section describes the upgrades, new features, fixed limitations, and known limitations for the January 2017 release of Cloud Application Integration.

Upgrades

This is the start of the concept.

48 2019-10-07













Migrating from H2 to PostgreSQL

Cloud Application Integration customers who migrate to Secure Agent version 30.0 or later need to migrate data from the H2 database to the PostgreSQL database. Informatica provides a migration tool that does most of the migration for you. Follow the steps below to migrate to Secure Agent version 30.0 and higher and migrate your data from H2 to PostgreSQL:

1. Shut down the current Secure Agent, that is, a Secure Agent that is versioned lower than 30.0.

2. Install the new Secure Agent, that is, a Secure Agent versioned 30.0 or higher.

3. Check that the new Secure Agent is up and running, and then shut it down.

4. Download and unzip the migration tool, H2toPostgreSQLdatamigration_tool.zip, from the Informatica Cloud Network.

5. Open the migration.properties file in the Resources directory of the data migration tool and make the following changes:

a. Enter the correct absolute path to the old Secure Agent.

b. Enter the correct absolute path to the new Secure Agent.

Important: Use a forward slash as the path separator when you enter paths in steps a and b.

c. Enter the correct H2 database credentials if you have changed them from the default credentials.

2019-10-07 49




6. Save and close the migration.properties file.

7. Go to the root directory of the data migration tool and run the script migrate_data.bat (for Windows) or migrate_data.sh (for Linux).

8. After the scripts have successfully migrated your data from H2 to PostgreSQL, start the new Secure Agent.

After Upgrading the SAP Connector

Configure the JAVA_LIBS Property

After you upgrade the SAP Connector and copy the sapjco3.jar file, you must configure the JAVA_LIBS property in Informatica Cloud.

Perform the following steps to configure the JAVA_LIBS property:

1. Log in to Informatica Cloud.

2. Click Configure > Runtime Environments to access the Runtime Environments page.

3. To the left of the agent name, click Edit Secure Agent.

4. From the Type list, select Tomcat JRE.

5. Enter the JAVA_LIBS value based on the operating system on which the Secure Agent runs.

Operating System Value

Windows ../bin/rdtm-extra/tpl/sap/sapjco3.jar;../bin/rdtm/javalib/sap/sap-adapter-common.jar

Linux ../bin/rdtm-extra/tpl/sap/sapjco3.jar:../bin/rdtm/javalib/sap/sap-adapter-common.jar

6. Click OK to save the changes.

7. Restart the Secure Agent.

8. Repeat steps 1 through 7 on every machine where you installed the Secure Agent.

Update the SAP JCo Libraries Directory

After you upgrade the SAP Connector, you must copy the sapjco3.jar file to the following directory to process data through BAPIs:

<Informatica Secure Agent installation directory>\main\bin\rdtm-extra\tpl\sapBefore you copy the jar file, you must create the tpl\sap directory within the rdtm-extra directory if the tpl\sap directory does not already exist.

If you had created the data\process-engine-custom-lib folder earlier, you must delete the sapjco3.jar file from the data\process-engine-custom-lib folder after you upgrade the SAP Connector.

50 2019-10-07


The January 2017 release of the Cloud Application Integration service includes the following new features and enhancements:

HTTPS Listener Support

You can run processes published to a Secure Agent from within the enterprise through HTTPS. You can instantiate processes on premises using HTTPS/REST or HTTPS/SOAP calls in addition to JMS and AMQP queues and topics. If you use an HTTPS listener, replace the default key store and certificate trust store that Informatica provides.

Bulk Retry on the Process Console

You can retry multiple faulting suspended processes on the Active Processes page. Earlier, you could only retry a single process at a time.

Scheduled Deletion of Server Log Data

Effective in this release, you can specify a Server Log Retention period. Process Server deletes Server Log data that is older than the time period you specify.

For more information, see the Scheduled Maintenance topic in the Administer section of the Cloud Application Integration online help.

Previously, you could not schedule Server Log data deletion. You had to manually delete Server Log data when needed.

Fixed Limitations


Defect Description

ICRT 5586 Service Connectors process an HAL JSON response as an attachment instead of a JSON.

Known Limitations

There are no known limitations in the January 2017 release.2016

December 2016


The December 2016 release of the Cloud Application Integration service includes the following new features and enhancements:

2019-10-07 51

Limit on Attachments Size

As of this release Informatica enforces a maximum attachment size for API requests made on the Cloud Server. Previously, Informatica enforced a maximum message payload size of 5 MB. Now, if you have attachments to a message, the maximum total size of attachments is also 5 MB.

This only affects processes that you deploy to the Cloud Server. If you deploy processes to the Secure Agent, the default size remains 5 MB for both payload and attachments. There is no upper size limit.

Secure Agent V31 and Higher

Informatica has created utility script based on PostgreSQL binaries. These utility scripts make it easier for you to manage the PostgreSQL database.

Swagger 2.0 Specification for Processes

You can obtain the Swagger 2.0 JSON specification of the API exposed by a process that you create in Informatica Process Designer. Service consumers can now use Swagger 2.0, JSON Schema, and WSDL interface documents to introspect endpoints for processes developed in Process Designer.

New Connectors

The Workday and OData connectors are now available to customers that license these capabilities. See the Informatica Cloud OData and Workday connector guides for information specific to Cloud Application Integration.

Max Wait Value for Service Call Step

When you use the Service Call step to run Informatica Cloud applications, you can no longer enter a Max Wait value of greater than seven days.

Improved XQuery Expression Syntax Support

The following enhancements were made to support XQuery expression syntax:

• Improved handling of spaces, tabs, and new lines.

• Removal of limits on the complexity of supported XQuery expressions.

• Comments and strings can now include temporary fields. For example:$temp.x(: comment variable $temp.x/a - :)/a

• Improved field references processing. For example, the following are now equivalent:$output.x/y$output.x/y/text()$output.x/y/node()

Prior to this release the second and third forms did not work as expected.

• Improved local and process variable support. Prior to this release, the following expression did not function as expected. This has been corrected:

let $temp.x (:local:) := $temp.x(:IPD variable:) return $temp.x• Improved expression predicate handling.

You can now use any number of predicates in XPath expressions. Previously this was limited to the first predicate. In this release, for example, the following is possible:

$output.x/a[$temp.i]/b[$temp.j]/c[$temp.n]

52 2019-10-07

You can now nest predicates, as shown here:$output.x/a[$temp.i*$temp.j]/b[let $temp.j:=1 return $temp.j]/c[$temp.n[$x[$y[$z]]]]

• Corrected array handling. Prior to this release, the following expression would return all "object values rather than the value of the first object of the array:

$input.event[1]/body/object[1]This limitation no longer occurs and the first array element is now returned.

Fixed Limitations


Defect Description

ICRT-5483 When you receive a payload that includes text content types with illegal XML characters, such as invalid white space, an exception error occurs and the content is not serialized to XML. As of this release, any illegal characters are replaced with a "?" character.

ICRT-5736 If you specify a value for the following Process Console properties, processes complete successfully with no limit applied and no errors returned:- Message size limit- Message with attachments size limit

Known Limitations


Defect Description

ICRT-6183 When you use the Secure Agent V31 or later and the embedded PostgreSQL database reaches a size of approximately 30 GB, Process Server startup can be slow. You can employ the purge function to control the growth in the database size.

After You Upgrade

Move Keystore Certificates

Starting in the December 2016 release, Informatica Cloud Services will install default keystore and truststore certificates for the Secure Agent with each upgrade.

In the December 2016 release, the certificates are located in this directory:

<agent-install-dir>/process-engine/<latest-version>/shared/classes/ae.cacert,ae.keystore

After the December 2016 release, if you add truststore and keystore certificates to this location, those certificates will not be preserved in the January 2017 release because directories in this path are modified or deleted during regular upgrades.

2019-10-07 53

You can retain your certificates if you place the consolidated certificate in a location that is not modified or deleted during an upgrade of Informatica Cloud Services. For example, you can move the certificates to this directory:

<agent-install-dir>/apps/process-engine/confIn the January 2017 release and subsequent releases, this will be the default directory for certificates and any certificates you add to this location will be preserved.

If you do not move the certificates, any certificates you add will not be preserved and only the default certificates will be present after the January 2017 upgrade.

October 2016


The October 2016 release of Cloud Application Integration includes the following new features and enhancements:

Support for the Latest Salesforce API

You can use the latest version of the Salesforce API, version 37.0. With this enhancement, you can use Cloud Application Integration to query any Salesforce object. Before this enhancement, you were unable to query a few Salesforce Territory fields.

Fixed Limitations


Defect Description

ICRT-5466 When you modify a schedule on the Process Console, sometimes, you see that you have modified a schedule that you did not intend to modify. This happens especially when you apply filters to the list of schedules.

ICRT-5489 You get the error " You do not have sufficient privileges to access the requested resource" when you download an attachment. This happens when you access the Process Detail page of the Process Console and download an attachment from a step that sends attachments.

ICRT-5493 You face an issue when you run a process that uses a service connector to get an attachment. The service connector gets the attachment, but the name and extension of the attachment is incorrect.

ICRT-5292 If you use the Go Back button while running a guide, you sometimes see the error " guide session no longer available."

ICRT-5430 When you update a process object field in an embedded guide, the change does not reflect in the main guide.

54 2019-10-07

Known Limitations


Defect Description

ICRT-5901 You cannot use the SAP BAPI Connector with Secure Agent version 30.0 and higher. When you test a SAP BAPI connection, a JCo exception occurs.

ICRT-5588 If you have upgraded to Secure Agent version 30.0 and higher, you sometimes see an " access denied" error when you start the Secure Agent.Work Around: Contact customer support to uninstall the Secure Agent and re-install it outside of the Program Files directory.

September 2016


There are no new features for this release.

Fixed Limitations


Defect Description

ICRT-5053 When you deploy an email process on the Secure Agent, sometimes, the Secure Agent does not send the email to the intended recipient.

ICRT-5070 You get the error "Id for host object not set" when you run a Salesforce guide. that contains a created object as well as an embedded guide that references the same object.

ICRT-5151 If a process has a service call step that catches faults, followed by a jump step, you cannot remove the fault-catching property from the step.

ICRT-5088 You are sometimes unable to disable a process schedule that you created on the Secure Agent

ICRT-5418 If you use Microsoft Internet Explorer, you are unable to run a guide that attaches files to a Salesforce object.

ICRT-5248 If you use a service connectors to handle JSON content, the service connector is sometimes unable to parse numeric fields in scientific notation.

2019-10-07 55

Known Limitations

There are no known limitations for this release.

August 2016


The August 2016 release of Cloud Application Integration includes the following new feature:

OData Enhancements

When you use OData to access a JDBC connector, you can define and edit custom composite keys. You define a custom composite key when a database entity does not have a primary key. With this custom composite key that you create, you can perform read operations on the JDBC database.

Fixed Limitations

The following table describes known limitations in this release:

Defect Description

ICRT-5180 You see an exception when you access the Schedule page under Monitor > Service & Process Console. This happens when you have at least 20 schedules that occur concurrently and repeatedly for around 20 Process Designer tasks.

Known Limitations

There are no known limitations for this release.

July 2016


There are no new features in this release.

Fixed Limitations

There are no fixed limitations in this release.

56 2019-10-07

Known Limitations


Request Number

Description


ICRT 5123 When you use a JDBC connector, you can not use the GROUP BY or ORDER BY functions to send OData requests.

June 2016


The June 2016 release of Cloud Application Integration includes the following new features and enhancements:

Assignment Steps Reorder

You can reorder fields in the Assignment step. You no longer need to rebuild the assignment step if you omit a field. Instead, you can add the new field, open the reorder dialog box, and reorder the fields.

Swagger (JSON) to Service Connector

You can use the service connector import facility to import a Swagger (JSON) file and create a service connector.

Single Page Published Metadata View

You have an option to see all the objects associated with a published connector on a single page. Previously, connector objects were spread across multiple pages. You can switch between these views.

ORDER BY and GROUP BY for JDBC Connections

When you use a JDBC connector, you can use the ORDER BY and GROUP BY functions to sort data. For example, you can sort a list of names by a person's last name.

Fixed Limitations

The following table describes fixed limitations:

Request Number Description

ICRT 5011 You are unexpectedly locked out of Informatica Cloud Application Integration and face authentication issues when you try to log in.

2019-10-07 57

Known Limitations


Request Number

Description

ICS 6305 If you enable Two-Factor Authentication and specify trusted IP Ranges, you cannot access the WSDL interface document of a process from the service URL.Work around: Contact Global Support Services for a list of trusted Cloud Application Integration IP addresses. Then, manually add the Cloud Application Integration IP addresses to the list of trusted IP Ranges.

ICRT 5025 When you create a nested data decision step in a process, all paths before the path containing the nested step disappear from the UI. For example, consider a process with a data decision step that has five paths. If you create a nested data decision step on path three, paths one and two disappear from the UI.Work around: Click the Insert button to add the nested data decision step. Do not use the Palette on the right side to add the nested data decision step.


ICRT 5123 When you use a JDBC connector, you can not use the GROUP BY or ORDER BY functions to send OData requests.

May 2016


The May 2016 release of Cloud Application Integration includes the following new features and enhancements:

OData Version 4

When you use OData Version 4, you can use the one-to-many relationship to access data that consists of say, many products under one category.

WSDL to Service Connector

We continue to enhance our WSDL to Service Connector import capability. When you create a service connector from a WSDL file, you can use a WSDL schema file with the following definitions:

• elementFormDefault

• 'choice' elements

Alert Service

You can create a process in the Process Designer to act as an alert service. When you create the process, select Runtime Alert Service as the Event Source Name.

58 2019-10-07

Fixed Limitations


Request Number Description

ICRT 5011 You are unexpectedly locked out of Informatica Cloud Application Integration and face authentication issues when you try to log in.

Known Limitations


CR Description

ICS 6305 If you enable Two-Factor Authentication and specify trusted IP Ranges, you cannot access the WSDL interface document of a process from the service URL.Work around: Contact Global Support Services for a list of trusted Cloud Application Integration IP addresses. Then, manually add the Cloud Application Integration IP addresses to the list of trusted IP Ranges.

ICRT 5025 When you create a nested data decision step in a process, all paths before the path containing the nested step disappear from the UI. For example, consider a process with a data decision step that has five paths. If you create a nested data decision step on path three, paths one and two disappear from the UI.Work around: Click the Insert button to add the nested data decision step. Do not use the Palette on the right side to add the nested data decision step.


April 2016


The April 2016 release of Cloud Application Integration includes the following new features and enhancements:

Data Types

You can use the XML data type in an Informatica Process Designer process. Use the XML data type in either of the following ways:

• You can use the XML data type in the assignment step of a process.

• You can use XML data type with JMS or AMQP.

For more details, see the Data Types and Available Field Properties section of the Application Integration Guide.

2019-10-07 59


You can import a .zip file to create a service connector from a WSDL file. The .zip file must contain either a self contained WSDL file, or a WSDL file along with a WSDL schema file (XSD) file.

Process Console

You can see the receive queue on the Monitor menu of the Process Console when you use a cloud tenant.

1604 Fixed Limitations

There are no Fixed Limitations in this release.

Known Limitations


CR Description


March 2016


The March 2016 release of Cloud Application Integration includes the following new features and enhancements:

Email Service

You can use attachments with the email service in Process Designer to send emails as part of a published process.

Note: To use attachments with the email service, first republish existing connections created prior to this release, to generate the required metadata. If the attachment name is not provided in the email request, a process uses the CID as the attachment name and a guide uses the form, screen_temp_tEmailInp[1]/attachments[1]/content.


A new utility was added so you can import an existing WSDL file and generate a service connector from it. Refer to the Service Connectors section of the Application Integration Guide for more information.

Connectors

• You can use the Informatica StrikeIron DaaS API connector to interact with StrikeIron.

• You can use the Informatica Address Doctor Cloud API connector to interact with Informatica AddressDoctor.

60 2019-10-07

Custom Functions

You can use the function setProcessTitle to set the title of a process in Informatica Process Designer.

OData Connections

• You can search for a simple text in OData. For OData V4, use $search, and for OData V2, use doSearch.

• You can filter based on simple text.

• You can log OData requests if you enable 'Log all messages' on the Logging Properties page of your agent's Process Console.

Process Console

You can see the alarm queue on the Monitor menu of the Process Console when you use a cloud tenant.

Fixed Limitations


CR Description

ICRT 4519 In an imported service connector, you can change the output field type of an action from text to objeclist.

ICRT 4544 When you configure an email service, you must enter a username and a password even if you use an SMTP exchange that has no authentication mechanism, or a has disabled authentication mechanism.

ICRT 4747 The charset you specify in the HTTP Header section of a Service Connector binding is ignored and the content is not decoded properly.

Known Limitations


CR Description

ICRT 4544 When you configure Informatica Process Designer's email service, you have to enter a username and a password even if you use an SMTP exchange that has no authentication mechanism, or a has disabled authentication mechanism.

ICRT 4484 You cannot send an attachment with an email when you use Informatica Process Designer's email service.

ICRT 4457 When you use the Import wizard to add a tag with cyrillic characters, the characters in the tag appear incorrectly in the Process Editor.


2019-10-07 61

CR Description

ICRT 4231 In the SAP BAPI Connector, when you first select an object from the XML Object list in the Formula Editor during the Assignment step configuration, you cannot view the object fields.Workaround: Clear the contents in the Formula Editor and reselect the object from the XML Object list.



February 2016


The February 2016 release of Cloud Application Integration includes the following new features and enhancements:

Email Service

You can use the Informatica Process Designer to send an email as a part of a published process. To send an email, you must configure an Email connection on an agent, on the cloud, or on both, to connect to an SMTP server.

Connectors

You can use the Amazon AWS Simple Notification Service (SNS) connector to interact with Amazon SNS.

Custom Functions

You can use the function util:base64Decode() to see a Base64 decoded version of the input string on Informatica Process Designer, Guides, or Service Connectors.

Import Wizard

When you import objects in Informatica Process Designer, you can enter tags that describe the imported files. You can also see an expanded view of each imported object within the Import dialog box itself.

Agent Database Compact Time

The maximum compact time of the default agent database, H2, overrides the 200 milliseconds default.

Process Logging on the Agent

If you create a new process on the agent, the default Logging Level is set to None, and the default Persistence Type is set to Brief. The earlier default Logging Level for a new process on the agent was Execution with Service Data.

62 2019-10-07

Fixed Limitations


CR Description

ICRT 4334 If you make edits to an object in an embedded guide, the changes are not reflected in the parent guide.

ICRT 4275 You cannot import a WSDL in the SOAP client if the process contains a space in the field or event name.

ICRT 4183 When you reuse a subprocess that contains the Receive step, an error occurs when you publish the process.

ICRT 4014 You cannot view Salesforce data from a V4 OData endpoint.

Known Limitations


CR Description

ICRT 4544 When you configure Informatica Process Designer's email service, you have to enter a username and a password even if you use an SMTP exchange that has no authentication mechanism, or a has disabled authentication mechanism.

ICRT 4484 You cannot send an attachment with an email when you use Informatica Process Designer's email service.

ICRT 4457 When you use the Import wizard to add a tag with cyrillic characters, the characters in the tag appear incorrectly in the Process Editor.


ICRT 4231 In the SAP BAPI Connector, when you first select an object from the XML Object list in the Formula Editor during the Assignment step configuration, you cannot view the object fields.Workaround: Clear the contents in the Formula Editor and reselect the object from the XML Object list.

2019-10-07 63

CR Description



January 2016


The January 2016 release of Cloud Application Integration includes the following new features and enhancements:

ICS API Connector

With the ICS API Connector, you can create a connection to access parameters and actions in the Informatica Cloud REST API and configure a service call to access services exposed by Informatica Cloud.

New Shell Command Service

To run a shell command within a process, you can define it as a Service Call step using the Run a Shell Command action. The shell command runs on a Secure Agent, which can also be called from the Cloud Server as a subprocess. You enable this service option at run time using the Process Console.

Alert Service and Email Service Enhancements

When you define processes that suspend on uncaught faults, you can set up an alert service and email service to notify administrators, for both a Secure Agent and for your organization's processes that run on the Cloud Server.

New Functions

Several new functions were added to the Formula Editor, including util:resolveURN, to retrieve the value of a mapped URN and util:getCatalogResource, to return a resource from the catalog location URL.

Fixed Limitations


CR Description

ICRT-3791 In the Process Console, there is no property available to set a threshold for rejected Dispatch service messages.

ICRT-3854 When you make a service call with a custom binding and attachment, an exception error occurs.

64 2019-10-07

CR Description

ICRT-3997 When you synchronize a Salesforce connection, the metadata collected has these limitations:1. There are no keys for the composite *_IID auto-generated field.2. The native datatype for reference and objectlist fields is not retained.

ICRT-4240 If you define a process that specifies the Applies To field, the endpoint SOAP WSDL does not include the Applies To value.

ICRT-4357 In a process that includes a Data Decision step, if an item in the list of possible outcomes includes an apostrophe ('), the step always follows the Otherwise Path.

ICRT-4378 If you define an Automated Step with an output field of type reference, when the process executes, it returns an error similar to:Invalid JSON input: Unexpected character '3' (\u33) at position 1

Known Limitations


CR Description

ICRT-3924 When you display data in a guide, if the display field is read-only and set to type text (not textarea), the data is displayed without new lines or formatting.Workaround: Assign the content of a "text" type field to a "textarea" type field so it displays correctly when the content is read-only.

ICRT-4275 When you define a process exposed as a WSDL, an error occurs while importing the WSDL in the SOAP client. This occurs if your process includes a space in a field or event name.Workaround: Remove any spaces from field or event names and republish the process.

ICRT-4375 If you define a process to allow anonymous access, you cannot use basic authentication to a public context endpoint.

ICRT-4380 In the ICS API Connector, when you use the Create DNB360 Workflow or Update DNB360 Workflow service, the workflow is not created or updated.

ICRT-4383 If you create a process object that includes a property of type picklist, the picklist values are not saved in the process object.

ICRT-4407 When you define a non-interrupting event path, you cannot merge that path back to the main path. By default, a non-interrupting path contains an End step.Workaround: Retain the End step when you use a non-interrupting event, so the path does not merge back to the main path.

2019-10-07 65

Informatica Cloud Application Integration - October 2019

Documents

Transcript of Informatica Cloud Application Integration - October 2019