If Then Else

Adding If Then Else Action to the Project

1. Open your project in Kuika.
2. Select the relevant screen from theUI Design module.
3. Select a component (for example a button) and open the Properties panel.

4. From the+ ADD ACTION menu, select an appropriate trigger action (event) such as Initial Actions, OnClick, OnBlur → Condition → If Then Else.

Configuring If Then Else Action

You can create condition-based transaction flows by configuring the following fields in the drop-down menu:

• Will Execute If: This is the field where the condition is checked. If true, the If block will execute, if false, the Else block will execute.
• If Actions: Actions to be executed if the condition is true.
• Else Actions: Actions to run if the condition is false (optional).

These actions may include system or custom actions such as page redirection, data update, warning.

So what we are doing here is setting up an “if-conditional” structure: If the condition you specified is met → do these actions, if not → do these actions.

All Common Condition Descriptions

• Is Equal To: If the value is exactly equal to the specified value, the condition is met.
• Ex: “User Name” = “admin”
• Is Not Equal To: If the value is different from the specified value, the condition is met.
• Ex: “Role” ≠ “Manager”
• Is Empty: If the value is empty (null or empty string), the condition is met.
• Is Not Empty: The condition is met if the value is full.
• Is In List: If the value is in the specified list, the condition is met.
• Ex: “Status” ∈ [“New”, “Waiting for Approval”]
• Starts With: If the value starts with the specified text, the condition is met.
• Ex: If “abc123” → starts with “abc”
• Does Not Start With: The condition is met if the value does not start with the specified text.
• Contains: The condition is met if the value contains the specified text.
• Ex: “abc123” → contains “c1”
• Does Not Contain: The condition is met if the value does not contain the specified text.
• Ends With: Condition is met if the value ends with the specified text.
• Length Shorter Than: Condition is set if the character length is shorter than specified.
• Length Shorter Or Equal To: If the character length is shorter or equal to the specified value.
• Length Longer Than: If the character length is longer than the specified value.
• Length Longer Or Equal To: If the character length is greater than or equal to the specified value.
• Length Equal To: If the character length is equal to the specified value.
• Is Guid: The condition is met if the value is in a valid GUID (unique ID) format.
• Ex: 123e4567-e89b-12d3-a456-426614174000

Condition Types and Usage Explanations

Now (Current Date-Time)

• Used for time comparisons:
  
  • Is Earlier Than / Or Equal: The condition is met if the present is earlier than or equal to the specified date.
  • Is Later Than / Or Equal: If now is greater than or equal to the specified date, the condition is met.
  • Empty / Null / Space (Space Controls)

• Checks whether text fields are empty or conform to certain formats.
• Can be used with all common operators listed above.

True / False (Boolean Fields)

• It is only used with the following operators:
  
  • Is Equal To
  • Is Not Equal To
  • Is Empty
  • Is Not Empty
  • Is In List
• Ex: For the field “Active?”

New Guid / Empty Guid

• GUID format is checked.
• Especially the Is Guid operator is used in this field.

Current User Name

• Checks the name of the user logged in to the system.
• Can be used with all text-based operators.

Client IP Address

• It is used in IP address controls.
• It can be controlled by textual operations such as start, end and inclusion.

Version Info

• Textual checks are made to compare application or system versions.

Role List (User Role)

• It allows the user to be processed according to his/her role.
• Ex: Comparison can be made with roles such as “Manager”, “Personal”.

If-Then-Else Structure

• If: One of the above condition types is selected.
• Then: This block runs if the condition is met.
• Else: This block is executed if the condition is not met.

If Actions

• Tip: Action
• Necessity: Yes
• Description: Allows you to select actions to be executed when the condition is true.
• Input: It is usually defined using data sources such as Action Result, Current, Form Component, Screen Input or Fixed and can be linked via Symbol Picker.

Else Actions

• Tip: Action
• Necessity: Optional
• Description: Allows you to select alternative actions to be executed when the condition is false.
• Input:It is usually defined using data sources such as Action Result, Current, Form Component, Screen Input or Fixed and can be linked via Symbol Picker.

In an application, it may be desired to redirect to separate screens according to different user roles (for example, Admin, User, Guest). Kuika's If Then Else action allows you to easily perform such role-based routing operations. With this action, the role of the user logging in to the application is checked and redirected to the appropriate screen. This provides a custom experience for the user and authorization management.

Add If Then Else Action

1. Log in to the Kuika platform.
2. Open the project you will work on from the Apps screen.

3. While in the UI Design module, open the Properties panel on the right side.
4. Select the component you want to add an action to (for example, the “Sign In” button).
5. From the+ ADD ACTION drop-down menu, follow these steps:
6. Onclick → Condition → If Then Else.

Configuring If Then Else Parameters

In the window that opens, configure the following fields:

The “Will Execute If” field is the section that checks whether the condition you define is true. A condition is written here that specifies in which case the system will execute the “If Actions” section. If this condition is met, “If Actions” will run.

If it is not met, i.e. the condition is false, “Else Actions” is activated.

Example Usage

• Condition (Will Execute If): data.user.role == “Admin”
• If Actions: Navigate to AdminPanel
• Else Actions: Navigate to UserPanel

In this example:

• If the user's role is “Admin” → redirect to the AdminPanel screen.
• If not → redirected to the UserPanel screen.

What Kind of Conditions Can I Write?

In the “Will Execute If” field;

• Text comparisons (==, !=, contains, starts with)
• Space checks (is empty, is not empty)
• Date/time comparisons
• List checks
• GUID validations
• you can write logical expressions like

If Actions: Here you can define the actions to be executed if the condition is true.

Example: If the condition “data.user.role” =“Admin” is met, redirect to the AdminPanel screen.

Else Actions: You can define the actions to be executed if the condition is false.

Example: Redirect to UserPanel screen if not admin.

Dynamic Routing:

Routing can be done according to the user's profile or transaction history.

Condition Creation Sources:

• Action Result (result of previous action)
• Form Component, Screen Input, Fixed values
• Can be determined using Symbol Picker (data binding tool).

Action Input Configuration:

• If Actions: Required. Actions that will run when the condition is met.
• Else Actions: Optional. Actions that will run if the condition is not met.

Post Action Usage

• The condition is evaluated.
• If true, the If block is executed, if false, the Else block is executed.
• A user-specific transaction flow is created.

Technical Risks and Recommendations

• Condition Errors: Make sure that condition expressions are written correctly.
• Lack of Alternate Flow: If the Else block is not defined, no action is taken when the condition is not met.
• Performance: Multi-layered conditions can cause slowness, keep it simple.

If Then Else action allows you to make condition-based decisions in your application. It improves the experience by creating flexible action flows based on user interactions and application data. It is an effective tool for routing, form validation and approval processes.