Use Case 2 Stolen Inject card holder to the screen to simulate a system request. “CTI” CRM trial the Degree screen”. “360 The representative navigates to the Cases grid The representative performs a search in the screen” : "Show all the from two ”Case last week’s", "Show all cases by provided specification and status". The representative a new case and populates the required fields then hits Save. This will trigger the "New Case" workflow which will run asynchronously. The representative will change the Credit Card status to “Stolen”. This will trigger the "Credit Card Status change" workflow will run synchronously and make a call to an external web service with a delay of 10 seconds. The representative will close the Case. Which means change its status field to and then hit Save. “Closed” This will trigger the "Closing Case" workflow which will run asynchronously. The coded web test used to simulate this request is embedded here: Use Case 2 360 The purpose of this use case was to simulate a more likely scenario the user views the 360 view of the customer as part of a call however they do not initiate a synchronous workflow. Instead a simpler a-synchronous workflow is initiated. This reduces the load on the workflow server and is more realistic of the expected load likely to occur on the system under real use. Inject card holder to the screen to simulate a system request. “CTI” CRM opens the Degree screen”. “360 The representative navigates to the Cases grid The representative performs a search in the screen” : "Show all the cases from ”Case two last week’s", "Show all cases by provided specification and status". The representative opens a new case and populates the required fields then hits Save. This will trigger the "New Case" workflow which will run asynchronously. The representative will close the Case. Which means change its status field to and then hit Save. “Closed” This will trigger the "Closing Case" workflow which will run asynchronously. The coded web test used to simulate this request is embedded here: Use Case 3 Opening a Potential New Business record – This process simulates the creation of a new business account: The representative will create the New Business Account entity and Populate the required fields for this entity.
Use Case 2 Stolen Inject card holder to the screen to simulate a “CTI” system request. CRM the “360 Degree screen”. The representative navigates to the Cases grid The representative performs a search in the ”Case screen” : "Show all the from two last week’s", "Show all cases by provided specification and status". The representative a new case and populates the required fields then hits Save. This will trigger the "New Case" workflow which will run asynchronously. The representative will change the Credit Card status to “Stolen”. This will trigger the "Credit Card Status change" workflow will run synchronously and make a call to an external web service with a delay of 10 seconds. The representative will close the Case. Which means change its status field to “Closed” and then hit Save. This will trigger the "Closing Case" workflow which will run asynchronously. The coded web test used to simulate this request is embedded here: Use Case 2 360 The purpose of this use case was to simulate a more likely scenario the user views the 360 view of the customer as part of a call however they do not initiate a synchronous workflow. Instead a simpler a-synchronous workflow is initiated. This reduces the load on the workflow server and is more realistic of the expected load likely to occur on the system under real use. Inject card holder to the screen to simulate a “CTI” system request. CRM opens the “360 Degree screen”. The representative navigates to the Cases grid The representative performs a search in the ”Case screen” : "Show all the cases from two last week’s", "Show all cases by provided specification and status". The representative opens a new case and populates the required fields then hits Save. This will trigger the "New Case" workflow which will run asynchronously. The representative will close the Case. Which means change its status field to “Closed” and then hit Save. This will trigger the "Closing Case" workflow which will run asynchronously. The coded web test used to simulate this request is embedded here: Use Case 3 – Opening a Potential New Business record This process simulates the creation of a new business account: The representative will create the New Business Account entity and Populate the required fields for this entity. trial