These forums are a place for learning, helping and sharing experiences with others about any of our products. Feel free to ask a question and get answers from our community and our most advanced users.
Note that these are public forums - anyone can view the discussions here.
VISIT OUR DIFFERENT FORUMS:
Announcements > | |
CloudShell > | TestShell > |
Developers > | BI (Business Inteligence) > |
This is where you can suggest your ideas to help and improve the product for everyone.
Please make sure to read the following article before posting a new idea, to get more information about the required information and ideas lifecycle.
Feel free to vote and comment on other ideas to promote them.
Thanks for everyone who suggested the ideas and voted for them.
Find, download and share integrations that can extend and enhance the CloudShell experience.
Integrations have several levels:
Certified - Officially tested and supported by Quali.
Preview - Provides a sneak peek to what the Quali team is developing. Officially supported by Quali. Feel free to experiment and comment, but please take into consideration that it is not yet tested and released.
Community - Integrations shared by community users. Feel free to look into what other users have contributed, please take into consideration that these integrations are not tested by Quali.
To learn more about creating Shells and integrating with CloudShell, use the following links:
CloudShell's Dev Guide > | Configuration Management > |
Getting started with Shells > | Extending CloudShell with Cloud Providers > |
Getting started with Orchestration > | API Guide > |
To share your integration, follow the instructions in this guide >.
Richard Hill suggested an idea (#4609) · Jun 10, 2019 at 07:54 PM · cloudshell portalapiservicesConnectivity
We need to create a "ticketing system" so that CloudShell (in use as our Lab reservation and tracking system) users requests for currently unsupported, unavailable, or correction-of-function can be tracked, acted upon and Knowledgebase articles created.
We use SalesForce as our CRM and I am tasked with creating an interface between the two if possible so that such ticketing and tracking can be achieved I have not been able to find any reference to Quali having any methods, now or in upcoming releases, to allow enable internal or external communications (emails or messaging) that can be then be "linked" into SalesForce, or else an API that can be utilized to open a specific SalesForce page (authentication will need to be provided or established by the user on opening) from a Sandbox.
I will also be talking with our SalesForce team, to check if there may be an API that allows SalesForce to link to Quali.
I had discussed the existence and potential of internal messaging within the Portal with Quali support before in less definite terms but I am no re-opening that discussion with an eye on getting some traction in the next 4 months
Because of the nature of this need, an existing plan for a future release would be part of a resolution,
Maya Ber commented · Jun 12, 2019 at 08:26 PM
Hello Richard, thanks for the idea! There could be a few ways to tackle this, so I'm putting this idea on "waiting for info" and we will initiate a discussion to understand the best way to address this for you. One option is to do it through a sandbox command. Another option would be to consider using the "contact us" advanced customization (but that's not per sandbox).
I want to make sure that I get the challenge right: the person who uses the sandbox experiences some issue or has some requests while using the sandbox. You would like them to be able to open a salesforce ticket directly from the sandbox, and you would like this ticket to be populated with sandbox data and user data automatically. This would replace a current flow where this user has to open salesforce.com, login, open a ticket and enter the sandbox details manually.
Is that correct?
Thank you.
Richard Hill commented · Jun 17, 2019 at 08:13 PM
Yes Maya - the automatic process you describe is what we want and the manual process is our fallback if there is no other way:
Data we would like to link to opening a SalesForce ticket would be the Sandbox name and ID, the owner's name, the devices in that Sandbox, date and time
Minimum desired data would be Sandbox name and owner name
Thank you
Richard
Maya Ber commented · Jun 18, 2019 at 08:59 PM
Hi Richard, thanks you for providing more information today! Sounds like the best approach for this use case is creating a Cloud Service Shell for Salesforce integration. Such Shell can hold all the information required to connect and open a ticket in Salesforce and automatically populate salesforce fields with Sandbox data. It would then be possible to add a standard Blueprint Command that makes it possible to open a Salesforce ticket from sandboxes. End users would simply have to click on this command (or enter more data in additional input fields if needed) and this would create a Salesforce ticket and populate data automatically. This requires the Shell to call the relevant salesforce APIs of course, so need to look at the salesforce side too. We will follow up with more information specifically for your use case, but if anyone else is interested in the same capability please let us know!
These forums are a place for learning, helping and sharing experiences with others about any of our products. Feel free to ask a question and get answers from our community and our most advanced users.
Note that these are public forums - anyone can view the discussions here.
Announcements | |
CloudShell | TestShell |
Developers | BI (Business Inteligence) |
This is where you can suggest your ideas to help and improve the product for everyone.
Please make sure to read the following article before posting a new idea, to get more information about the required information and ideas lifecycle.
Feel free to vote and comment on other ideas to promote them.
Thanks for everyone who suggested the ideas and voted for them.
Find, download and share integrations that can extend and enhance the CloudShell experience.
Integrations have several levels:
Certified - Officially tested and supported by Quali.
Preview - Provides a sneak peek to what the Quali team is developing. Officially supported by Quali. Feel free to experiment and comment, but please take into consideration that it is not yet tested and released.
Community - Integrations shared by community users. Feel free to look into what other users have contributed, please take into consideration that these integrations are not tested by Quali.
To learn more about creating Shells and integrating with CloudShell, use the following links:
CloudShell's Dev Guide | Configuration Management |
Getting started with Shells | Extending CloudShell with Cloud Providers |
Getting started with Orchestration | API Guide |
To share your integration, follow the instructions in this guide.
Help us make things better. Share your great idea or vote for other people's.
Ability to Connect/Disconnect All Routes by device
API for getting Services Details
Automation API method to obtain APP / Service categories
Activate attribute change requests in the Default Sandbox Setup
API method to get Cloudshell DB version
Resource has the Ability to display an attribute of the designer's choice on the canvas
Custom browser tab titles for QualiX connections