System Service Actions

Delete Object

Execute Data Marketplace API

Input Fields

HTTP Method

Required. The HTTP method to invoke the Data Marketplace API such as GET, PUT, or POST.

Relative Path

Required. The relative path of the Data Marketplace API.

For example, to perform operations on the data assets in Data Marketplace, enter the following as the relative path:

dataAssets

To perform operations on the data elements in Data Marketplace, enter the following as the relative path:

dataAssets/{{id}}/dataElements

Payload

The JSON payload to be sent to the Data Marketplace API using the PUT or POST method.

For example, to send employee data to the Data Marketplace API, enter the data in the JSON format as shown in the following sample:

'{
"Employee": [
{
"firstName ": "Cindy",
"lastName": "Louis",
"department": "IT"
"status": "Employed"
}
]
}'

Query Parameter

The process object that returns the data associated with the Data Marketplace API query parameters.

You can use the API query parameters such as sort or status to sort or filter the data using the GET method. Based on the query parameter, the API returns the associated data in the XML format.

You can configure the Query Parameter field by using a formula or field.

For example, to use a formula to get the maximum number of assets with the enabled status, use the status query parameter as shown in the following sample:

<DataMarketplaceQueryParameters>
<queryParams>
<name>status</name>
<value>ENABLED</value>
</queryParams>
<queryParams>
<name>limit</name>
<value>10</value>
</queryParams>
</DataMarketplaceQueryParameters>

For information about using another field to configure the Query Parameter field, see Creating fields to execute Data Marketplace API.

Path Variable

The process object that is associated with the Data Marketplace API path variables.

You can configure the Path Variable field by using a formula or field.

For example, to insert data elements into the data asset, provide the ID in the path variable as shown in the following sample:

<DataMarketplacePathVariables>
<pathVariables>
<name>id</name>
<value>eu33-39839j2</value>
</pathVariables>
<pathVariables>
<name>categoryId</name>
<value>ad2c915-60c4</value>
</pathVariables>
</DataMarketplacePathVariables>

For information about using another field to configure the Path Variable field, see Creating fields to execute Data Marketplace API.

Output Field

Creating fields to execute Data Marketplace API

JMS Enqueue Service

Messaging Manager Name

The name of the messaging manager that contains the destination.

Destination Name

The name of the message's destination.

Format

The format to be serialized to the destination.

Message

The message to be sent to the destination.

Unwrap Root Element

Describes how the process object is serialized when it is sent to the destination.

Logging for the JMS Enqueue Service

1. 1Access the log4j2.xml file from the following directory:
<Secure Agent installation directory>\apps\process-engine\<latest_version>\conf
2. 2Add the following code:
<Logger name="org.apache.camel.component.file.remote" level="DEBUG" additivity="false"> 
<AppenderRef ref="catalina"/>
</Logger>
3. 3Save the log4j2.xml file.

MDM human tasks

• •Generic User Task. Defines actions for users included in the workflow.
• •Originator User Task. Defines actions for users who trigger a workflow with their actions.

Input Fields

Template

Required. The template field that you added to the Input Fields tab of the Start step.

TaskTypes

Required. The taskTypes field that you added to the Input Fields tab of the Start step.

Change List

Required. The input field that you added to the Input Fields tab of the Start step.

TaskName

Required. The unique name of the Service step that you specified on the General tab.

Task Actions

Required. The list of actions that the users can perform with this step. Use a semicolon as a delimiter. For example, Send for Translation;Send Back to Originator;Release. You can also use the action text to provide more information on the next process step. The output that returns from each task action must be handled within the process.

Output Fields

LastAction

The last task action, such as Send for Translation, Send Back to Originator, or Release.

LastApprover

The identifier of the user who took the last action.

Run a Shell Command

Enabling the Shell Command Service

1. 1In Application Integration Console, choose Server Configuration.
2. 2Choose the agent where you want to run the shell service from the Server Configuration list.
3. 3On the System Services tab, choose Shell Service.
4. 4Click Save.

Input and Output Fields

Run Cloud Task

1. 1Add a Service step to the process.
2. 2On the Service tab, select the service type as System Service, and then select the action as Run Cloud Task.
3. 3On the Input Fields tab, configure the required properties:
• - Task Name: The name of the Data Integration task that you want Process Designer to run. You can select from a list of mapping tasks and synchronization tasks. You can also enter keywords to search for a mapping task or synchronization task.
• - Wait for Task to Complete: Defines whether Process Designer waits for the task to complete before Process Designer resumes execution.
• - Max Wait: Defines the maximum number of seconds that Process Designer waits for a task to complete. The default value is 300 seconds.
Important: You must enter a Max Wait value that is lesser than 604800 seconds, that is, 7 days or fewer. Process Designer waits for a maximum of 7 days for a task to complete.
• - Fail on Cloud Task Errors: Defines whether the process faults when the mapping task or synchronization task fails.
The following image shows the input fields that you can configure for a Run Cloud Task Service step: