Genesys Cloud Architect Module 6.3 Hands-On Exercise: Data Action to Check User Logged in скачать в хорошем качестве

Genesys Cloud Architect Module 6.3 Hands-On Exercise: Data Action to Check User Logged in

!!MAKE SURE TO HIT THE SUBSCRIBE BUTTON!! Objective: By the end of this exercise, you should be able to create a data action that checks if a user is logged in and ready to take a call in Genesys Cloud's Architect. Instructions: 1. Log into your Genesys Cloud account • Open your web browser and navigate to login.mypurecloud.com. • Enter your Genesys Cloud username and password, then click 'Log in'. 2. Navigate to Architect • After logging in, click on the 'Admin' tab on the navigation bar located on the left side of the screen. • In the dropdown menu, select 'Architect'. 3. Create or Open an Inbound Call Flow • If you're creating a new flow, click on the '+ Create' button located in the upper right corner of the screen, then select 'Inbound Call Flow'. • If you're modifying an existing flow, find it in the list of flows and click on its name to open it. 4. Create a User Variable • Click on the 'Variables' tab on the toolbar at the top of the Architect interface. • Click '+ Add' and select 'User' from the dropdown menu. • Name the variable 'SelectedUser'. This variable will hold the user that will be checked for their availability. 5. Set User to Variable • Drag and drop a 'Set Value' action from the toolbox on the left into the workspace. Connect the 'Start' point to the 'Set Value' action. • Configure the 'Set Value' action to set the 'SelectedUser' variable to your desired user. 6. Create a Data Action to Check User Status • Navigate to 'Admin' 'Integrations' 'Actions'. • Click '+ Add Action' and give it a name, such as 'Check User Status'. • Select the 'Check User Status' API under the 'Genesys Cloud APIs' category. • In the 'Input Contract' section, create a 'userID' input field of type 'String'. • In the 'Output Contract' section, create a 'loggedIn' output field of type 'Boolean' and a 'ready' output field of type 'Boolean'. • In the 'Action Configuration' section, set the 'userID' field to the 'SelectedUser' variable and map the API response fields to the 'loggedIn' and 'ready' output fields. • Save and activate the action. 7. Use Data Action in Call Flow • Go back to your call flow in Architect. • Drag and drop a 'Call Data Action' action from the toolbox into the workspace. Connect the 'Set Value' action to the 'Call Data Action' action. • Configure the 'Call Data Action' action to call the 'Check User Status' data action. • Drag and drop a 'Decision' action into the workspace. Connect the 'Call Data Action' action to the 'Decision' action. • In the 'Decision' action, add conditions that check if the 'loggedIn' and 'ready' fields are true. Connect the 'true' and 'false' paths to appropriate actions. 8. Save, Validate, and Publish • Click 'Save' at the top right of the Architect interface to save your call flow. • Click 'Validate' to check for any errors. If any issues are found, correct them and validate again. • Once your flow has been validated without any errors, click 'Publish'. 9. Test Your Call Flow • Click the 'Test' button located in the top right corner of the Architect interface. • In the 'Test Call' window, enter a phone number for the test call and click 'Start'. • Observe the path of the test call through your call flow. Ensure that the 'Check User Status' data action is called and the 'Decision' action correctly routes the call based on whether the selected user is logged in and ready. 10. Debug Your Call Flow • If your test call doesn't follow the expected path, use the Architect's built-in debugging tools to identify any issues. • Check the values of the 'loggedIn' and 'ready' fields in the 'Data' panel during the test call. • If necessary, modify your call flow and test again until it functions correctly. 11. Deploy Your Call Flow • Once your call flow is functioning correctly in tests, it's time to deploy it. • Click 'Publish' in the top right corner of the Architect interface. Enter a note about the changes you made, then click 'Publish'. • Your call flow is now live and ready to handle real calls. Recap: In this exercise, you've learned how to create a data action that checks if a user is logged in and ready to take a call. You used this data action in a call flow, routing calls based on the user's status. You also tested, debugged, and deployed your call flow. Next Steps: Continue practicing these skills with different scenarios, such as checking the status of multiple users or incorporating other conditions into your decision-making process. To learn more about Dunamis Consulting, go to https://www.getdunamis.com To learn more about our training, go to https://www.getdunamistraining.com