User Guide
This document provides the default TSANet Connect Power App user experience.
The following user types are used in this manual
Technical Support Engineer: Staff who are responsible for the resolution of customer cases. This group of users will initiate outbound collaboration requests with other Members and collaborate with Members who make inbound requests.
Customer Service / Management Team: This group handles the inbound request process. This documentation shows the manual method for responding to an inbound request, but Members can also implement automation in this area.
Collaboration Process Overview
The TSANet Connect collaboration process allows a Member to request collaboration with other TSANet Members with whom they have a relationship. The system is designed to create a consistent experience for all members. The diagram below shows the high-level process.
This Power App uses REST API to POST and GET data from the TSANet Connect system. The default interval for the GET polling is 15 minutes, and the user can manually Refresh Data from the main navigation.
TSANet Case Status Definitions
The following status definitions are used for the TSANet Collaboration Case.
Open (New waiting initial response)
Information (Sent if information is needed to accept or reject)
Accepted (Collaboration Accepted)
Rejected (Collaboration rejected. For example, end customer does not have support). This status is not used for solution support.
Closed (set by submitter or auto-close after 30 days of inactivity)
Technical Support Engineer
The Technical Support Engineer has two use cases:
Create a New outbound request
Work on a New inbound request that has been assigned to them
1. Create a New outbound request
Outbound Request to a Member
Go to TSANet Cases (LWC located on the Case Form)
Click NEW – search for a Member, fill out the required fields, and submit
View Screenshots below:
After submitting, the Case will appear under TSANet Cases with the status (Open). You can also view the case details in the Case Feed.
When the other member responds to the case, the TSANet Case will be updated with the Engineer’s contact information. The status will be updated to ACCEPTED, INFORMATION, REJECTED
2. Working on an Inbound Request from a Member
The inbound process will result in either a new case assigned to an engineer or a link to an existing case already assigned to an engineer. The functionality for working on this collaboration is the same as for outbound requests.
Multi-vendor collaborations are complex cases. Members should assign these cases to experienced Support Engineers and alert management.
When integrated into MS Dynamics, the Power App can trigger a notification to the case owner.
Response to Inbound Request from a Member
Customer Service / Management Team
The process for responding to inbound collaboration requests can be manual or automated. The manual steps are documented below.
The management team can also monitor the progress of all collaborations and define workflows that align with the organization's case management processes.
The Microsoft Dynamics install guide defines the details of the package, including flows that could be used to automate the process.
View the Inbound (Open) Requests
The TSANet Cases has several List views.
Respond to an Inbound Request from a Member
Opening the TSANet Case will show all details related to the request. The receiving Member can create or link an existing case in Microsoft Dynamics from this record. This section will be updated with examples of Microsoft Dynamics screens showing the link between the TSANet and Microsoft Dynamics Case.
Respond to the Case by clicking the “Approve, Reject or Request Information.”
Exception – Information Requested
The information requested status is set if the information provided does not allow for creating a case and assigning it to a Technical Support Engineer. This status could also be used when an entitlement issue is found and a customer service team is working on the case. When the TSANet Case is in this status, the user can exchange notes with the submitter to obtain the required information.
Exception - Rejected
Rejecting a case is like sending an Accept response. The user provides details on why the case was Rejected and any necessary steps to re-submit it in the future.
Example: The end customer is not found in the member’s system, or a supplied serial number is not supported.
Best practice is to use the information requested process to try to accept the case. Then, as agreed with the submitter, reject the case.
Ongoing Collaboration
Add Notes
Both Submitter and the receiver of the case can add a Note. The screenshots below show how to add from the TSANet Case object, but notes can also be added from the Timeline and flow into the TSANet Case.
To add a Note:
Select the TSANet Case from the list to view the detail.
Select "Add Note"
Add Note and hit Save
When the other member adds a Note to your case or Updates the Response, it will appear under the Case Feed. This Power App feed can also be integrated into the MS Dynamics case.
Outbound: Updating Case
The following actions will trigger a case update:
The submitter can re-assign the Microsoft Dynamics Case to a new case
Change the owner of the Microsoft Dynamics Case.
A notification will be sent to the other member, and a note will be added to the Collaboration Feed and Microsoft Dynamics timeline.
Inbound: Updating Case
The following actions will trigger a case update:
The receiver can change the Microsoft Dynamics Case
Change the link to the new Microsoft Dynamics Case
Press the update approval button
Changing the owner of the Microsoft Dynamics Case
Change the owner of the case
Press the update approval button
Closing a Collaboration Case
Submitters can close a case from the case detail view navigation. If a TSANet Collaboration case has not been active for 30 days, it will be automatically closed. A notification will be sent out 10 days before the case is closed.
Only the Submitter can close a case.
Last updated