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 updates in the card, server scripts allow to validate the new data before it is updated in the card.
Business Scenario
Zylker Corp associates with a set of vendors whose details are saved in a cloud database. When vendor details in an existing card are updated, the details have to be validated with the existing values in the database. If the updated detail is wrong, the card must not be allowed to be saved.
Solution
When a vendor detail field is updated in the card, the new value can be validated with the database using server scripts. To execute this:
-
Create a server script to validate data from the third-party application.
-
Create a card and update a field to test the functionality.
Sample Configuration
Step 1: Code server scripts
Create a new server script to validate vendor details if they are updated.
-
Create a new
server script
and enter the name as 'Validate vendor details'.
-
Choose
Contract Initiation
in the
Form
dropdown. We've used the previous use case's orchestration here. Learn more.
-
Choose
Job
as the
Execution Location
to execute the script.
-
Choose
Before Update
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.
-
This code is to validate the vendor name alone. You can use similar logic to validate other details.
-
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 beforeUpdate(){
- //select Vendor ID parameter here
- var vendorId = current.Job.getValue(current.Layout.Fields.<select-VendorID-parameter-here>.id);
- if (!vendorId) {
- console.log("Vendor ID not present");
- return;
- }
- var url = "https://jsonplaceholder.typicode.com/users/"+vendorId;
- var params = {};
- var headers = {};
- var res = ZDK.HTTP.get(url, params, headers);
- if (res.status != 200) {
- console.log("Unable to fetch vendor details");
- return;
- }
- var responseBody = res.body;
- if (typeof responseBody == "string") {
- responseBody = JSON.parse(responseBody);
- }
- //select Vendor Name parameter here
- var orginalVendorName = responseBody.name;
- var presentVendorName = current.Job.getValue(current.Layout.Fields.<select-VendorName-parameter-here>.id);
- if (orginalVendorName != presentVendorName) {
- current.Job.addError(current.Layout.Fields.<select-VendorName-parameter-here>.id, "Vendor name is not matching in vendor database");
- }
- }
Step 2: Add card
When the orchestration and server scripts are ready, we can test the script by creating a new
card
.
-
Navigate to
Cards
and click
Add Card.
-
Select
Contract Initiation
from the
Form
dropdown.
-
Enter the vendor ID to auto-populate other vendor details and
Save
the card.
-
In the card details page, update any vendor detail, such as Vendor name, Address, Website, Contact, or Vendor email.
-
If the detail entered does not match with the details in the database, an error will be displayed and the card will not be allowed to be saved.
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:
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 SalesIQ Resources
New to Zoho TeamInbox?
Zoho TeamInbox Resources
New to Zoho ZeptoMail?
New to Zoho DataPrep?
Zoho DataPrep Resources
Design. Discuss. Deliver.
New to Zoho Workerly?
New to Zoho Recruit?
New to Bigin?
New to Zoho CRM?
New to Zoho Projects?
New to Zoho Sprints?
New to Zoho Assist?
Related Articles
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 ...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 1: Populate read recipients list for a card using Server Scripts (On Load)
Managers find it useful to know which employees have viewed a new card or comment, like a read receipts list. It helps managers know if an employee has viewed his assigned task and evaluate how informed employees are about new updates in the ...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 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. ...