- #1.3.9 PRACTICE COMPLETE YOUR ASSIGNMENT ANSWERS APEX UPDATE#
- #1.3.9 PRACTICE COMPLETE YOUR ASSIGNMENT ANSWERS APEX REGISTRATION#
As you might expect, both fields are currently empty. If you're curious, you can now verify that our user, Maria Thompson, has the two new custom fields in her Salesforce user account ( Account Type and Account ID).
Enter a username and nickname to use (or just use the auto-filled values) and Save. Since this is a test org, use your own email address. For Profile, select Standard Platform User. For User License, select Salesforce Platform. From Setup, enter Users in the Quick Find box, then select Users. In Salesforce, let’s create a user record for our client, Maria Thompson. Make sure that the field-level security is set to visible for profiles you use in your org and click Next, then Save. Leave the rest of the defaults, and click Next. For Field Label, use Account ID and for Length use 25. Make sure that the field-level security is set to visible for profiles you use in your org and click Next, then Save & New. For Field Label, use Account Type and for Length use 25. Under Data Type, select Text and click Next. Click Fields & Relationships, then click New (Custom Field). From Setup, select Object Manager, then select User. We’re about to use these actions in a flow of our own.įirst, in Salesforce, let’s create two custom fields, Account Type and Account ID, on the User object, so that we have fields in the user's record to store the bank account type and bank account ID values that we retrieve from the bank service. External services that you create can have many more actions it depends on the specific service that you use and how the API spec's schema is defined for your use case. These External Services actions are the API operations pertaining to our fictional bank that we can use in a flow to get information, add account records, and so forth. When you’re done viewing the available BankService actions, we can move on.įor example, you can see the getAccount action that we looked at in the External Services wizard, along with addAccount, DeleteAccount, and updateAccount. #1.3.9 PRACTICE COMPLETE YOUR ASSIGNMENT ANSWERS APEX REGISTRATION#
To see the actions grouped by an External Services registration (in this example, BankService), change Filter By to Category, select BankService, and click in the search box.
To see the actions imported by External Services based on the API spec we used in the previous unit, change Filter By to Type, select External Service, and click in the search box. From the toolbox, with the Elements tab selected, drag Action onto the canvas. Click New Flow, select Screen Flow, click Next, and then select Freeform. From Setup, enter Flow in the Quick Find box, then select Flows. To see the actions, let’s jump into Flow Builder. If you completed the previous unit, you’ve registered an external service using the External Services wizard and viewed the External Services actions in the wizard. We'll walk through these steps in the next section. And ( ding!) the bank has a new customer, so you, our trusty bank representative, will first create a new Salesforce User. Create two new custom fields on the User object: Account Type and Account ID, so that each time we enter a new bank customer, we have fields to store the bank account type and bank account ID in the Salesforce User record. If no Last Name match is found at the bank service, and a new bank account record is created, then it updates the Salesforce user record (if there's a matching name in Salesforce) with the new bank account type and bank account ID.Īnd to prepare our Salesforce Org we need to: #1.3.9 PRACTICE COMPLETE YOUR ASSIGNMENT ANSWERS APEX UPDATE#
Update Records Update Salesforce User Record: If the Salesforce user's last name matches a bank account record, then our flow updates the Salesforce user record with the bank account type and the bank account ID.Assignment Assign Existing Bank Account ID: If a bank account exists, assigns the account ID of the existing bank account and uses this value to update the Salesforce User account.Decision Bank Account Updated? Logic evaluates if a bank account exists and needs updating, or creates a new bank account, if needed.We use the addAccount action and specify the API's inputs and outputs which we'll assign to variables to be used between the Salesforce org and the bank service. Action Add Bank Account: Having registered the bank service's API specification with External Services, all API operations defined in our spec are now available for use within the flow as matching actions.Screen Bank Account Record: Captures account name and account type from information that the bank representative enters on the screen.Note the five "steps" that we'll make to complete this flow. Let’s take a closer look at the stages and logic so you can see how the information flows.
0 kommentar(er)
