Update Entity Action Advanced Customisations

1. Conditional Update: You can check the changes made by the user and update only the fields that have actually changed. For example:

• If the new Name value is different from the existing value, the update process is performed.
• This avoids unnecessary API calls.

2. Automatic Category Assignment: When an entity is created or updated, the CategoryId can be dynamically determined based on the user's screen or role. For example:

• Certain users can only update specific category IDs.

3. Form Validation: The accuracy of form fields can be checked before the update process. In particular, checks can be made to see if the Name field is empty or contains special characters.

4. Post-Update Chain Actions: After the entity update is complete:

• Refresh the relevant list
• Set the updated data to another form field (Set Value)
• Perform chain operations such as re-saving the updated information to the database or logging it.

5. Feedback and Follow-up: After the update process:

• A custom information message can be displayed to the user
• In case of incorrect updates, a custom error message or warning can be displayed
• Processes can be logged for auditability

6. Authorisation-Based Update Capability: Depending on the user's role, only certain fields can be updated. For example:

• Administrators can change both the name and category
• End users can only change the description

Technical Risks

• Missing Required Fields: If the Id and Name parameters are empty or invalid, the action will fail.
• Category ID Mismatch: If an invalid CategoryId is provided, the entity may be grouped incorrectly.
• Data Conflict: If there is another entity with the same name, the user should be notified.

The Update Entity action is one of the basic tools that makes asset management flexible and dynamic on the Kuika platform. It provides a powerful infrastructure for keeping entities up to date, organising them by category, and creating user-friendly forms.