Business case 5: Transfer data to third-party applications (After create)
Today’s corporations use different software tools for different functions like inventory, payroll, utility, and so on. Server scripts allow organizations to fetch data from these third-party software or websites, and list the same in cards.
Business Scenario
Zylker uses Jira to track issues in their products. Sometimes, Zylker’s partners or clients might create a card in Qntrl to file a bug. To collate all issues in one place, Zylker wants to create an issue in Jira every time a card related to a bug is created in Qntrl.
Solution
We can create a specific orchestration to record issues and trigger a server script each time a new card is created in it.
-
Create a new orchestration to record issues in product and save the issue link from Jira.
-
Create a server script to file issues in Jira when cards are created in Qntrl's orchestration.
-
Create a card and fill in the issue details to test the server script.
Sample Configuration
Step 1: Create an orchestration
Create a new orchestration titled 'Raise Issue' and add related custom fields to it.
- Add a link field--Issue Link--to record the issue link from Jira.
Once the form is saved, proceed to design the blueprint, set permissions, and publish the orchestration.
Step 2: Code server scripts
Now, proceed to code the server script to send details to Jira.
-
Create a new server script and enter the name as 'File issue in Jira'.
-
Choose
Raise Issue
in the
Form
dropdown.
-
Choose
Job
as the
Execution Location
to execute the script.
-
Choose
After Create
as the
Execution Trigger
to execute this script whenever the card page loads.
-
Copy and paste the below script into your script editor and replace the parameter names.
-
You can use the ? icon at the top-right corner of the script editor to refer to parameter names.
-
Once the script is ready,
Publish
it.
- function afterCreate(){
- var globalVars = ZDK.Vars.getGlobalVariables();
- var job = current.Job;
- var jiraAuthBase64 = ZDK.Crypto.base64Encode(globalVars["JiraEmail"] + ":" + globalVars["JiraApiKey"]);
- var payload = getJiraPayload(job.getTitle(), job.getDescription(), globalVars["JiraProjectKey"]);
- var url = "https://" + globalVars["JiraDomain"] + "/rest/api/3/issue";
- var headers = {
- 'Authorization': "Basic "+jiraAuthBase64,
- 'Accept': 'application/json',
- 'Content-Type': 'application/json'
- }
- var resp = ZDK.HTTP.request(
- url,
- "post",
- headers,
- "",
- payload,
- ""
- );
- if (typeof resp == "string") {
- resp = JSON.parse(resp);
- }
- console.log("Res = " + JSON.stringify(resp));
- if (resp && resp.body) {
- if (resp.status == 400) {
- console.log("Jira issue creation failed, "+JSON.stringify(resp));
- } else {
- if (typeof resp.body == "string") {
- resp.body = JSON.parse(resp.body);
- }
- var id = resp.body.id;
- var key = resp.body.key;
- var link = "https://" + globalVars["JiraDomain"] + "/browse/" + key;
- job.setVariable("JiraId", id);
- job.setVariable("JiraKey", key);
- //Select issue link parameter here
- job.setValue(current.Layout.Fields.<select issue link parameter here>.id, link);
- console.log("Jira issue created, id = " + id + ", key = " + key);
- }
- } else {
- }
- }
- function getJiraPayload(title, desc, project) {
- if (!title) title = "";
- if (!desc) desc = "";
- var payload = {
- "fields": {
- "summary": title,
- "issuetype": {
- "id": "10004"
- },
- "project": {
- "key": project
- },
- "description": {
- "type": "doc",
- "version": 1,
- "content": [
- {
- "type": "paragraph",
- "content": [
- {
- "text": desc,
- "type": "text"
- }
- ]
- }
- ]
- }
- }
- };
- return JSON.stringify(payload);
- }
Step 3: Add card
When the orchestration and server script are ready, we can test the script by creating a new card.
-
Navigate to
Cards
and click
Add Card.
-
Select
Raise Issue
from the Form dropdown.
-
Enter the bug details.
- Save the card.
Check if an issue with the same details has been created in your Jira account.
Access your files securely from anywhere
Zoho CRM Training Programs
Learn how to use the best tools for sales force automation and better customer engagement from Zoho's implementation specialists.
Zoho DataPrep Personalized Demo
If you'd like a personalized walk-through of our data preparation tool, please request a demo and we'll be happy to show you how to get the best out of Zoho DataPrep.
- Zoho Workerly Home
- Forums
- Connect With Us:
- Zoho Recruit Home
- Forums
- Connect With Us:
New to Zoho CRM Plus?
Deliver unforgettable customer experiences
New to Zoho CRM Plus?
Deliver unforgettable customer experiences
New to Zoho Marketing Plus?
Everything you need to run your marketing
New to Zoho Marketing Plus?
Everything you need to run your marketing
You are currently viewing the help pages of Qntrl’s earlier version. Click here to view our latest version—Qntrl 3.0's help articles.
New to Zoho Survey?
Zoho Sheet Resources
Zoho Forms Resources
New to Zoho Sign?
Zoho Sign Resources
Sign, Paperless!
New to Zoho TeamInbox?
Zoho TeamInbox Resources
New to Zoho ZeptoMail?
Zoho DataPrep Resources
Design. Discuss. Deliver.
New to Zoho Workerly?
New to Zoho Recruit?
New to Zoho CRM?
New to Zoho Projects?
New to Zoho Sprints?
New to Zoho Assist?
New to Bigin?
Related Articles
Business case 2: Fetch data from third party websites using Server Scripts (Before Create)
We might sometimes want to fetch external data from other applications or websites like weather details, stock rates, or flight status related to the card, when we create a card. Server scripts can be used to fetch such data and display it in Qntrl. ...Business case 3: Use client scripts to fetch data from third party applications or websites
While designing forms, we might sometimes want to display data from other websites or applications like stock rates, flight status, freight details, weather updates, and so on. To fetch such information from third party websites or applications and ...Business case 3: Validate new data entered in cards using Server Scripts (Before Update)
Performing operations and coordinating with teams can be quite a herculean task. If the information given in the card details is changed to corrupt information later, it may create chaos and slow down task completion. This is why if a user is to make ...Business case 6: Delete associated cards from third-party applications (After Delete)
Automate deleting records in third party applications, such as Zoho Desk or SAP, once they are deleted in Qntrl using the 'After Delete' server script. Business Scenario Zylker uses Jira to track issues in their products and every bug filed in ...Business case 4: Set conditions for users to delete cards using Server Scripts (Before Delete)
Organizations provide permissions and privileges to various sections of staff according to their roles and profiles. In order to make sure that the data within Qntrl can only be deleted by the right personnel, organizations can implement complex ...
New to Zoho LandingPage?
Zoho LandingPage Resources