1. Log in to the Kuika platform.
2. Select your project from the Apps screen.
3. Go to the UI Design module.
4. Open the page where you want to retrieve user information.

5. Select the button and add the Authorisation > Get User By ID action from the + ADD ACTION menu according to the trigger event you want (Initial Actions, OnClick, OnBlur, etc.).

Parameter Configuration

• ID (String): The user's unique ID number in the system.
  
  • It is usually defined using data sources such as Action Result, Current, Form Component, Screen Input or Fixed, and can be linked via the Symbol Picker.

After the user logs into the system, their information (name, email, phone number, etc.) should be automatically displayed in the form fields when they enter their profile page. If necessary, the user should be able to edit this information.

Application Flow:

1. Element: ‘My Profile’ page
2. Trigger: When the page is loaded (Initial Actions)
3. Action: Authorization → Get User By ID
4. Parameter: ID → Current.UserID (dynamically retrieved using Symbol Picker)
5. Next Action: The retrieved user information is assigned to the form fields (FirstName, LastName, Email, PhoneNumber, etc.).
6. Update: The user information is modified, and when the ‘Save’ button is clicked, the data is updated in the system (e.g., using the Update User action).

• Role-Based Filtering: Before retrieving user information, actions can be restricted based on the user's role using If Then Else.
• Detail Page Redirection: After the Get User By ID action is executed, redirection to the detail screen can be performed (using the Navigate action).
• Complex Information Sets: If additional information such as the user's role or subscription information is required, it can be supported with additional queries (e.g. Get Roles + Get Subscription).

Technical Risks and Precautions

• Invalid ID Use: No data will be retrieved if an invalid or incorrectly formatted ID is entered. Validation should be performed on form inputs.
• Unauthorised Access: This action should only be used by authorised users.
• Empty Data Return: If the user ID does not exist in the system, empty data may be returned. In this case, the user should be informed (e.g., ‘User not found’ warning).
• Data Freshness: If the retrieved user information is displayed without being updated, a trigger should be set for concurrent changes (e.g., a Refresh action can be added).

Get User By ID is a basic action used to access a user's data based on their ID. It plays an effective role in user detail screens, form pre-filling, or user update operations. Thanks to its dynamic data source support, it can be easily integrated into different screens and components in a flexible manner.