Salesforce Fact #555 | validate() lwc inputs in screen flow

Do you know we can use a validate() method to put some validation on lwc input components in screen flow.

Suppose, we have a combobox in lwc which we are using in the screen flow and it is marked as required. But if we click the next button in screen flow, it goes to the next screen even if no value is selected. To add validation, we can use the validate() method. The UI can be improved in terms of showing the message.

Reference: https://developer.salesforce.com/docs/component-library/documentation/lwc/use_flow_validate_user_input_for_custom_components.html

Attached are the screenshots.










Comments

Post a Comment

Popular posts from this blog

Salesforce Fact #192 | Call batch apex from flow

Image
Generally apex batch jobs are scheduled to run at particular time intervals. But suppose we have a use case where we need to run the batch job on adhoc basis. We can call the batch apex from a screen flow in that case and the screen flow can be invoked from a button. So, the batch job can be executed on demand. Attached are the screenshots.
Read more

Salesforce Fact #457 | Get current user role name in flow

Image
In apex, in order to get the current user role name we need to query the UserRole object. We cannot get it directly using UserInfo object since it has only one method related to role i.e  getUserRoleId(). Using this Id returned we can get the data from UserRole object. But that is not that complex in flow. In case of flow, we can directly get the current user role name using the syntax: {!$UserRole.Name}. Attached are the screenshots.
Read more