1. Log in to the Kuika platform.
2. Open the relevant project from the Apps screen.
3. Switch to the UI Design module.
4. Open the Properties panel on the right side.
5. If only one parameter is to be updated, use Text Input; if multiple parameters are to be updated, use Dynamic Input.
6. For the process parameters to be updated, specify the relevant areas of your process design.

7. + ADD ACTION menu, add the Process > Set Process Data action according to the desired trigger event (OnClick, OnChange, Initial Actions, etc.).

Parameter Definitions

• ProcessId: The ID of the business process to which the data will be assigned. Example: process123
• ParameterName: The name of the process parameter to be updated. If Dynamic Input is used, all parameters are taken from here. Example: CustomerName
• Value: The value to be assigned to the parameter. It can be taken from the UI element or a fixed value. Example: txtCustomerName.value or dynamicInput1.value

In a project management tool, the manager is required to first retrieve the data of a specific process using the Get Process Data action, and then update it using the Set Process Data action according to user input.

Application Flow:

Elements:

• Text Input → ID: txtCustomerName
• Dynamic Input: ID: dynamicInput1
• Button → Label: “Update”

Action:

• The user enters the process ID and the current data is displayed with the Get Process Data action.
• The fields to be updated are entered via Text Input or Dynamic Input.
• When the “Update” button is clicked, the Set Process Data action is triggered and the selected parameters are assigned to the process.

Add Action:

• OnClick → Process → Set Process Data
• Parameters:
  
  • ProcessId: process123
  • ParameterName: CustomerName (or all parameters with Dynamic Input)
  • Value: txtCustomerName.value or dynamicInput1.value

• Updating Multiple Parameters with Dynamic Input: Dynamic Input is not used to update all parameters with a single action, but to ensure that each parameter can be processed flexibly according to its data type and number of records.
  
  • Each parameter is still processed individually; the logic does not update all parameters at once.
  • However, with Dynamic Input, even if the number of records in the list obtained with Get Process Data changes or the data types vary, each record can be handled correctly.
  • This ensures compatibility and flexibility in processes with parameters of different types and numbers.
• Chain Usage with Get Process Data: First, process data is read, the necessary parameters are selected and updated.
• Conditional Update: Parameters can be updated when certain rules are met.

Technical Risks and Controls

• Incorrect ProcessId: Entering a process ID that does not exist will cause the action to fail.
• Parameter Mismatch: The assigned value must be appropriate for the parameter type (e.g., text, number, date).
• Empty or Incorrect Value: When the value field is empty or incorrect, the process parameter may receive an incorrect or empty value.
• Use of Dynamic Input: If not all parameters are retrieved using Dynamic Input, some values may not be updated.

The Set Process Data action, when used in conjunction with Get Process Data, provides a complete solution for reading, analyzing, and securely updating process data. This makes workflows more flexible and manageable.