Save User

The Save User is an Authorization system action often used during an application development process to register or update users. This action allows users to create accounts in the application or update their existing accounts.

The Save User action has various functions in the applications where it is used:

• Saving User Information: This action is used to store user-provided data (e.g., name, surname, email, password) in a database or another data storage mechanism. This enables users to create an account in the application.

• Updating User Information: This action is used to update existing users' information (updating profile information). Users execute this action when they need to change or update their data.

• User Authentication and Authorization: The Save User action is used to verify users' identities and control their access permissions. This provides an authorization scheme where users are only allowed access to specific functions or content.

• Error and Validation Checks: Validation checks are carried out in this process to verify the accuracy of user-entered data and handle incorrect information entries, such as checking if an email address is valid or confirming matching passwords.

• User Feedback: Providing feedback to users about the transaction's result is crucial. Users are informed if the registration was completed successfully or if an error occurred. This enhances the user experience.

The Save User system action is supported in both Mobile and Web applications.

Adding the Save User Action

Click on +Add Action under the Properties panel. (A)

Click OnClick→ Authorization→ Save User and create the Save User action. (A)

The Save User system action comes with parameters like UserName, FirstName, LastName, RoleNames, StartingScreenId, PhoneNumber, and others.

• UserName: Represents the user's username (email). This parameter is used for user authentication when logging into the application.

• FirstName: Represents the user's first name. This parameter stores the user's personal information.

• LastName: Represents the user's surname. This parameter is used to complete the user's personal data.

• RoleNames: Represents the user's role or authority levels (e.g., User, Admin). This parameter determines the functions or content a user can access within the application. The role specified in Authorization must match the role name in this parameter. An exact match is crucial.

• StartingScreenId: Represents the screen's identity that should be displayed first when the user logs into the application. A screen role should be selected from the selectbox in this parameter.

• PhoneNumber: Represents the user's phone number. This parameter is used to store users' contact information or for verification processes.

These parameters are generally used for tasks like creating or updating a user account and are utilized for managing user data. Each parameter represents the relevant user information and ensures its proper use in transactions.

Within the created action, Symbol Picker (B) is used to select the parameter input method for the action.

You can perform various operations on the Context menu (C) for the actions you create.

You can easily copy the action with the Copy option. This way, you gain speed where action repetition is required.

You can add a confirmation message for the action to run using the Add Confirmation option.

Also, with the Add Condition feature, you can specify certain conditions under which the added action should execute.

You can easily delete the action created with the Remove option.