RIOCONSOLE FRC SCREENSTEPS HOW TO
How to add contacts from Gmail using Cirrus.To continue the example from above, instead of writing one big article titled "Contacts" just write a dozen little articles that each answer one specific question: Their documentation is a great example of how to write end user/customer documentation. HubSpot does a great job writing useful titles, and then demonstrating the workflow using pictures, text, and annotations. If each article has its own, great title, then your end users can quickly answer their own questions by performing a keyword search or by browsing through your table of contents. Instead of going right to the information they need, end users will have to sift through all of the other stuff to find an answer. So you create an outline of all the "Contacts" topics you can think of, take screenshots of the Contacts object, explain all of the menu options, and write a history of the Contacts object - all useless to an end user who just wants to know how to create a partner contact in Salesforce. This not only makes it easier for your end users to find what they are looking for, but it helps you write better articles.įor example, think about how much time it would take to write an article titled "Contacts." You wouldn't know where to start. Great end user documentation consists of titles that are specific, and often in the form of performing a task.
We call them Interactive Conversation Flows because they help call center agents respond to callers in a conversational way and because when customers use them for self-service, they can recreate the conversation a support rep would have to narrow down what needs to be done. These articles come in very handy when you want to direct users (either employees, customers, or call agents) to specific instructions that need to be tailored to a situation. Here's another example of the same type of article, but this one is meant for customers to use as self-service (click on one of the options to go through the procedure). If you want to create an Interactive Conversation Flow like the one above and the one below, check out ScreenSteps. Otherwise, continue on." Not quite as easy to read, but can still be effective if that's all you have. Note: If you're writing complex documentation in Word or Wikis that aren't interactive, then you could include instructions that say, "If this is the situation, jump down to step #7. The idea is to help the end-user (in this case a call center agent) respond to any scenario related to questions coming in around the Paycheck Protection Program by including prompts and decision trees. Here's an example of what ScreenSteps calls an Interactive Conversation Flow that a call center agent could use to respond to a call about the Paycheck Protection Program. If your documentation needs to explain a complex procedure, make sure you account for all of those variations. Urn:oasis:names:tc:SAML:2.Some procedures are straightforward while other procedures include a lot of "if this, then that" situations. MIIBrTCCAaGgAwIBAgIBATADBgEAMGcxCzAJBgNVBAYTAlVTMRMwEQYDVQQIDApDYWxpZm9ybmlhMRUwEwYDVQQHDAxTYW50YSBNb25pY2E圎TAPBgNVBAoMCE9uZUxvZ2luMRkwFwYDVQQDDBBhcHAub25lbG9naW4uY29tMB4XDTEwMDMwOTA5NTg0NVoXDTE1MDMwOTA5NTg0NVowZzELMAkGA1UEBhMCVVM圎zARBgNVBAgMCkNhbGlmb3JuaWExFTATBgNVBAcMDFNhbnRhIE1vbmljYTERMA8GA1UECgwIT25lTG9naW4xGTAXBgNVBAMMEGFwcC5vbmVsb2dpbi5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAOjSu1fjPy8d5w4QyL1+zd4hIw1Mkkff4WY/TLG8OZkU5YTSWmmHPD5kvYH5uoXS/6qQ81qXpR2wV8CTowZJULg09ddRdRn8Qsqj1FyOC5slE3y2bZ2oFua72of/49fpujnFT6KnQ61CBMqlDoTQqOT62vGJ8nP6MZWvA6sxqud5AgMBAAEwAwYBAAMBAA= YiveKcPdDpuDNj6shrQ3ABwr/cA3CryD2phG/xLZszKWxU5/mlaKt8ewbZOdKKvtOs2pHBy5Dua3k94AF+zxGyel5gOowmoyXJr+AOr+kPO0vli1V8o3hPPUZwRgSX6Q9pS1CqQghKiEasRyylqqJUaPYzmOzOE8/XlMkwiWmO0= We will check the AttributeStatement for a 'mail' value.īelow is an example SAML response with the NameID set to :.We will check the AttributeStatement for an 'email' value.ScreenSteps will check three values for the user email address:
RIOCONSOLE FRC SCREENSTEPS CODE
0 kommentar(er)
