Invoke

Back Next

Rules and guidelines for process inputs

Consider the following rules and guidelines when you create process inputs to run a process:

If a process contains input fields with space characters in them, you cannot use the XML encoding type while creating the process input.

You cannot create a process input of the Image, Attachment, and Attachments data types.

If you create a process input of the Rich Text Area data type, you must verify that the process input is properly encoded. You must encode

< >

< >.

Consider the name of the text input field as

InputField

and the text input value as

HelloWorld

in bold font. For this example, you must edit the process input code as follows:

{ "InputField": " <bold> HelloWorld </bold> " }

If you create a process input of the Any data type, you must specify the process input as a key value pair.

Consider the name of the input field of the Any data type as

InputFieldAnyType

and the value as

valueHelloWorld

. For this example, the process input code with JSON encoding must be as follows:

 {{ "InputFieldText": "HelloWorld", "InputFieldAnyType": { "key": "valueHelloWorld" }}

If you select the encoding type as

XML

, the process input code must be as follows:

<root> 
<InputFieldText>HelloWorld</InputFieldText> 
<InputFieldAnyType> 
<key>HelloWorld</key> 
</InputFieldAnyType> 
</root>

In the

Process Objects

section, only the input fields that contain process objects appear.

When you make changes to the input fields in the published process, you must manually refresh the

Run Using

dialog box to see the changes.

When you make changes to the process input and cancel the changes without saving them, the changes persist.

If a process contains an output field of the list of number data type with a precision greater than 7, the value is displayed in the exponential format for JSON payloads in the advanced view of a process in

Application Integration Console

Running a process

Download Guide

Watch

Comments

Cloud Application Integration Homepage

0 COMMENTS

We’d like to hear from you! Log in to comment.

Rename Saved Search

Table of Contents

Invoke

Invoke

Rules and guidelines for process inputs

Rules and guidelines for process inputs