Datacard TruCredential Software

Transcription

1 Datacard TruCredential Software TruCredential Developer s Guide July 2017 Part No , Rev. C

2 Notice This publication and the accompanying software are proprietary to Entrust Datacard Corporation and are protected by U.S. patent and copyright laws as well as various international laws and treaties. This publication may not be copied, translated, sold, or otherwise transferred to a third party, in whole or in part, without the express written permission of Entrust Datacard Corporation. Information in this publication is subject to change without notice. Entrust Datacard Corporation assumes no responsibility for any errors that may appear in this publication. Names and logos in sample screens are fictitious. Any similarity to actual names, trademarks, or trade names is coincidental. Trademark Acknowledgments Proprietary Notice Datacard is a registered trademark and service mark of Entrust Datacard Corporation in the United States and other countries. Entrust is a registered trademark and service mark in the United States and other countries. MasterCard is a registered trademark of MasterCard International Incorporated. Visa is a registered trademark of Visa International Service Association. All other product names are the property of their respective owners. The design and information contained in these materials are protected by US and international copyright laws. All drawings and information herein are the property of Entrust Datacard Corporation. All unauthorized use and reproduction is prohibited. Entrust Datacard 1187 Park Place Shakopee, MN Phone: Fax: Copyright 2017 Entrust Datacard Corporation. All rights reserved. ii

3 Revision Log TruCredential Developer s Guide Revision Date Description of Changes A June 10, 2015 The first release of this document. B January 2017 Added batch API information Added an example for batch API printing Reorganized and renamed the document to reflect the contents and intended use C July 2017 Add Custom Process information. Rename manual. iii

4 iv

5 Contents Chapter 1: Introduction About This Document Audience Conventions Used in This Document Related Resources In This Manual Chapter 2: API Overview Availability TruCredential API Functionality TruCredential API Prerequisites Run an Application Over HTTPS Chapter 3: TruCredential API Methods personalizewithdata() getstatus() executeworkflowwithdata() Data for executeworkflowwithdata() Chapter 4: API Sample Application About the Samples Changes to the Samples Web Service Details Run a Sample Resources Samples BatchExecuteWithData CreatePrinters LoadAndDeleteRecords PrintAndTrackRecords PrintWithData Create a Request to Print a Batch of Cards Batch Printing Example Chapter 5: Custom Processes Overview Steps JavaScript Notes TruCredential Notes Common Field Properties Radio Buttons i

6 Custom Process Examples Script Input Sample Input Sample Notes Sample Script Sample Script Sample Script Messages Script with Message Display ii

7 Chapter 1: Introduction This section provides information about how to use this manual, and describes the content of each section. About This Document This document describes how to develop custom applications or processes to use with TruCredential Suite software. Audience This document is for developers using TruCredential software who are knowledgeable about Java, Apache CXF, JAX-WS, JSON, and web service concepts or for individuals trained by Entrust Datacard Corporation. Conventions Used in This Document Placeholder text displays in italic font. Replace the placeholder text with information that is correct for your environment. For example, User interface text displays in boldface font. For example, when work is complete, select user ID > Sign Out. Code is displayed in Code font. This is an example of a note. Notes contain important information that you should read carefully. Related Resources The TruCredential Installation and Administration Guide provides information for installing and setting up TruCredential software. Review it for basic information about TruCredential software. The TruCredential Software Online Help system is the primary documentation for this product and provides procedures for tasks that you must do in TruCredential software. It is available by clicking the help button on any page of the application. TruCredential Developer s Guide 1

8 The ID Works to TruCredential Migration Guide provides information for moving your card program from ID Works software to TruCredential software. In This Manual This manual describes the customization interfaces available in TruCredential Suite software. Use the application programming interface (API) to send print requests to TruCredential software, and receives status information from the software. Refer to the following for information: API Overview TruCredential API Methods API Sample Application Write a custom process for use with the Customization Toolkit option. Refer to the following for information: Custom Processes Support and Service Resources Go to entrustdatacard.com/support for information about technical support in your region. For hardware support, have your product model and serial number available. For software support. have the software version number and product key available. Refer to the shipping documents (before installation) or the TruCredential software (after installation) to retrieve this information. 2 Introduction

9 Chapter 2: API Overview This section provides an overview of the prerequisites to use the TruCredential application programming interface (API) and the web services application samples, which integrate with TruCredential software. Availability The application sample package is available from the Entrust Datacard Trusted Care website. The package expands into a folder named integrations. The features described in this manual apply to TruCredential software version 7.3 and the TruCredential API version 7.3. TruCredential API Functionality Use the TruCredential API to do the following: Send a print request to TruCredential software. The request is a Simple Object Access Protocol (SOAP) call that includes the card name, printer name, and the data to print on the card. If the request is valid, TruCredential software returns a print job ID. Then, you can use the print job ID (above) to send a SOAP request to get the print job status. After a pause, the API sends the SOAP request until it receives a completion status for the print job. The API does not handle exceptions. The API sample application is a basic demonstration of integration possibilities with TruCredential s software SOAP services. TruCredential API Prerequisites Complete these tasks before you use the TruCredential API samples: Install TruCredential software on the same computer as the TruCredential API samples. A workflow design and a credential design have been created in the TruCredential application. The workflow design is connected to the database.refer to Resources on page 10 for information about a workflow to import. TruCredential Developer s Guide 3

10 Configure a printer in TruCredential software and confirm that the printer Test Configuration succeeds. (Optional) Configure SSL certificates in TruCredential software. (Optional) Configure TruCredential software to use secure (HTTPS) communication. The J2SE Development Kit (JDK) 8 and Gradle must be installed on the computer. The JAVA_HOME environment variable must be set to run the sample integrations. Specify the JAVA_HOME environment variable to be the location where JRE is installed on your computer. For example, C:\Program Files\Java\jdk1.8.0_11. To request batch printing using TruCredential API calls, use TruCredential software to set up the following: A TruCredential workflow with the following characteristics: It contains the Personalize or External DB Operation step with the Mode configured to Batch or Both, rather than the default Single. Do not include the following workflow element types in a workflow for batch printing through the TruCredential API: Auto-Sequence and Print Count. Data connections between the workflow and card design components. If the workflow includes an External DB Operation step, and the step is configured to perform the Read operation, connect the database primary key to the workflow using the Field Connections page. Run an Application Over HTTPS TruCredential software can run in the secure, HTTPS protocol. This requires uploading the HTTPS certificate to the software. Refer to the TruCredential software documentation for information about configuring the software for HTTPS connections. If the software is running over HTTPS, the sample application must also run over HTTPS. For secure communication of the SOAP service, the sample application must have a Java keystore. This keystore requires the trusted certificates used by the TruCredential software. Therefore, import all required certificates from the TruCredential software keystore into the sample application keystore. Refer to the TruCredential Installation and Administration Guide for the information needed to configure SSL for TruCredential software and for your application. 4 API Overview

11 Chapter 3: TruCredential API Methods This section provides information about TruCredential APIs, which you can integrate with thetrucredential software SOAP services.the TruCredential API sample application uses the printqueue web service that is exposed by TruCredential software. Specifically, the TruCredential API sample application uses these methods. personalizewithdata() The following code creates a print request: Parameters: Long personalizewithdata(string[][] enrollmentdata, String credentialdesignname, String printername) throws PrintQueueException enrollmentdata credentialdesignname printername Enrollment data in the form of a key-value pair, for example, [credential_field_id: credential_field_ value] The name of the card design to print. The name of the printer to print the card. This method does the following: Retrieves the card design with the name matching the credentialdesignname parameter. Retrieves the printer details with the name matching the printername parameter. Creates the print job and returns the print job ID. If an issue occurs while creating the print job, a message to that effect is returned. TruCredential Developer s Guide 5

12 getstatus() Parameter: String getstatus(long id) throws PrintQueueException id The ID of the print job status to retrieve. If there are no errors, the print status is one of the following values: Completed Personalizing Stopped Stopping Waiting Paused Pausing SentToPrinter If a non-valid print job ID is returned in the parameter, a message to that effect displays. If any issue occurs while retrieving the print status, a message to that effect displays. 6 TruCredential API Methods

13 executeworkflowwithdata() Long executeworkflowwithdata (BatchExecutionDataView batchexecutiondataview) throws BatchExecutionException where the BatchExecutionDataView object is: class BatchExecutionDataView { private List<String[][]> persodata; private String workflowname; private String printername; private Integer hopper = 1; private Integer copies = 1; private String clientip; This method does the following: Verifies that the persodata value was sent in the batchexecutiondataview parameter. If not, it returns a message indicating that the persodata value is required. Checks for the workflowname value sent in the batchexecutiondataview. If the request did not include workflowname, or if it was not valid, a message is returned indicating that. Checks for printername value sent in the batchexecutiondataview. If printername is not included in the request, or if it is not valid, then a message is returned indicating the applicable case. Checks the hopper number sent in the batchexecutiondataview. If it is 0 or a negative number, a message is returned indicating that the hopper number must be at least 1. If all values in the request are correct, then a batch history ID for the print job is returned. Data for executeworkflowwithdata() If a workflow has a Composite element in it, values cannot be provided for it. If you attempt to do so, a response indicates the issue. If a workflow has a Check Box in it, the values provided must be either true or false ; any other value results in a response indicating the issue. TruCredential Developer s Guide 7

14 8 TruCredential API Methods

15 Chapter 4: API Sample Application This section provides information about the TruCredential software API application samples, which integrate with its SOAP services. About the Samples The API samples are designed for use in a Java integrated development environment (IDE). Changes to the Samples The following changes from TruCredential v7.2.1 software apply to the API samples. The TruCredentialConfig.properties file is not used and is not included in the API package. Batch scripts to compile the samples are not included. Refer to Run a Sample on page 9 for more information. A workflow named EMPLOYEE is used with the samples. The EMPLOYEE.tru file and data files are included in the src\main\resources folder. Refer to Resources on page 10 for more information. Classes for COM and.net technologies are included. Web Service Details Apache CXF generates client classes for the SOAP service. Several TruCredential web service endpoints are provided. To add additional support, copy a WSDL file to the resources\wsdl folder, then run the gradlew wsdl2java task to generate a web service client. Run a Sample The samples can be run in one of the following ways: From the command line, using the Gradle task associated with each of the samples. For example: gradlew printwithdata. Refer to Resources on page 10 for information about customizing runtime values for the Gradle task. Directly from a Java IDE. TruCredential Developer s Guide 9

16 Resources The samples are configured to use a workflow named EMPLOYEE. The EMPLOYEE.tru file in the src\main\resources folder can be imported into TruCredential software to provide you with a preconfigured workflow and credential design. Several of the samples are configured to read from CSV files that contain test personnel data. The files are located in the src\main\resources folder. The CSV file must use line 1 for column headings or field UIDs, and all other columns for enrollment data. The EnrollmentData.csv file uses the field UID in line 1, and other enrollment data files must use the field UID. The PrintData.csv file uses the Field name in line 1. Each of the samples has an associated Gradle task to run the sample. Open the Gradle task in the IDE and provide values for the input parameters, such as the workflow name, printer name, CSV file path, number of rows to read from the CSV file, TruCredential server URL, username, and password. Samples The section names the sample classes and provides information about using them. Refer to TruCredential API Prerequisites on page 3 before you begin. BatchExecuteWithData This sample reads a defined number of personnel records and submits them to TruCredential to be run in a batch workflow. The final step in the batch workflow is to print a card. CreatePrinters This sample creates a defined number of printers in TruCredential software. LoadAndDeleteRecords This sample reads a defined number of personnel records and creates enrollments for them in TruCredential. Afterward, it removes the enrollments from the database. PrintAndTrackRecords This sample reads a defined number of personnel records and prints a card for each. It monitors the printer queue and sends the next print job after the current print job has completed. PrintWithData This sample reads a defined number of personnel records and prints a card for each. 10 API Sample Application

17 Create a Request to Print a Batch of Cards Use the following code to print a batch of cards. public Long executeworkflowwithdata(batchexecutiondataview batchexecutiondataview) throws BatchExecutionException where batchexecutiondataview is the DataView required for batch printing. It has the following variables: where: private List<String[][]> persodata; private String workflowname; private String printername; private Integer hopper = 1; persodata workflowname printername A data listed in a key-value pair [workflowfieldname:workflowfieldvalue]. The name of the workflow to batch print. The name of a configured printer. hopper The number of hoppers in the printer. By default, it is 1. clientip The IP address of the computer on which the TruCredential API software is installed. Batch Printing Example Below is a sample batch printing request. These settings are used in this example: hopper: The number of the hopper to use for printing. By default, it is 1. persodata: A list of perso data specified in a key/value pair [workflow field id: workflow field value] printername: The name of a printer configured for use by TruCredential software. workflowname: The name of the workflow to use for batch printing cards. <soapenv:envelope xmlns:soapenv=" xmlns:ser=" trucredential.datacard.com/"> <soapenv:header/> <soapenv:body> <ser:executeworkflowwithdata> <arg0> <hopper></hopper> <persodata> TruCredential Developer s Guide 11

18 <item> <item>fieldname1</item> <item>fieldvalue1</item> </item> <item> <item>fieldname2</item> <item>fieldvalue2</item> </item> </persodata> <persodata> <item> <item>fieldname3</item> <item>fieldvalue3</item> </item> <item> <item>fieldname4</item> <item>fieldvalue4</item> </item> </persodata> <printername></printername> <workflowname></workflowname> </arg0> </ser:executeworkflowwithdata> </soapenv:body> </soapenv:envelope> 12 API Sample Application

19 Chapter 5: Custom Processes This section provides information about the Custom Process option available with TruCredential software. Overview A custom process includes actions that are outside of TruCredential software, but that are triggered by an occurrence within TruCredential software. A custom process uses a custom JavaScript file to perform an action as part of a workflow. You set up the event trigger to run the process, based on an event and the action to take. All actions in a custom process must occur within the TruCredential environment. The following examples show how a custom process can be used: Change a field to readonly when you load an enrollment. Select the available values for a list field when a value for another field is selected, such as populating a list with State or Province names when a country is selected. Hide a field when the operator transitions from one workflow step to another. Act on a field before or after you print the card. Transform the data read during a smart card process, before you save the data. Refer to the Online Help system for information about the customization toolkit and configuring an event. The events, such as On enrollment load, or Save credential before, that can be configured are explained in the WorkFlow Properties Help topic. The JavaScript file uses a JSON key-value pair collection, looks at the values for a workflow field, and then takes action on the field. The result is returned to the workflow as part of the configured event. The JSON key-value pair collection is realized as an object, record, struct, dictionary, hash table, keyed list, or associative array, depending on the language used. You are responsible for creating the JavaScript file. TruCredential Developer s Guide 13

20 Steps Follow these suggested steps to use a custom process: 1. Plan the workflow and custom action. Identify the inputs and outputs. Print count, autosequence, and composite fields are not allowed as output fields. 2. Write the custom process. Refer to Sample Script 1 on page 19, Sample Script 2 on page 19, Sample Script 3 on page 20, and Messages on page 21 for samples. 3. In TruCredential software, import the script for the custom process using the Settings > Settings > Customization Toolkit page. 4. Set up the workflow, including field connections. 5. Configure the custom process in the workflow. 6. Verify that the workflow performs the planned action. JavaScript Notes Use a text editor or IDE to edit or create the JavaScript file. Alert statements cannot be used in custom process scripts. You cannot connect to an external database using a custom process. Use the External DB Operation workflow step instead. Print statements can be used to print to TruCredential stdout logs. In the JavaScript file, use the TC_Event variable to receive the value passed when the custom process is triggered. The variable name is case sensitive. Use the tc_event variable to pass the changed value to TruCredential software when the custom process is complete. The variable name is case sensitive. Use the errormessage variable, defined inside the function, to display a message to the operator. The variable name is case sensitive. TruCredential Notes Scripts are stored in the TruCredential default database. Every time a script is changed, register the script using the TruCredential Settings > Settings > Customization Toolkit page. Print count, auto-sequence, and composite elements cannot be sent to TruCredential software from the custom process. 14 Custom Processes

21 All workflow fields, with their properties and values, are available to the custom process, except the Operator Prompt properties. The TruCredential Workflow Designer provide elements used with in the workflow. For example, you can use a Capture a Photograph step, select the preview image, and set properties for the photograph. The check boxes for the Mandatory, Read only, and Hidden properties indicate that the each of the properties have a data type of Boolean. TruCredential software does not allow read-only fields to be saved to the database. You can save a value but prevent the operator from changing the value by doing the following: In the Workflow Designer, set the Read Only property to false. Link the field to a database table, along with other workflow fields. Load the value when the operator runs the workflow. Use a custom process to set the Read Only property to true when the enrollment is loaded. Save the enrollment, including the value with the temporary Read Only = true setting. TruCredential Developer s Guide 15

22 Common Field Properties The following table describes common field types and the properties associated with each of them. The field types correspond with the icons available in the Workflow Designer toolbar. Field Type Text Date Composite Checkbox AutoSequence Properties name inputlength enforceinputformat dataentrytype mandatory enforcemask name inputlength enforceinputformat dataentrytype name readonly hiddenfield name readonly hiddenfield checkbox_new_record checkbox_null_value name readonly hiddenfield modifyvalue 16 Custom Processes

23 Field Type Photo, Signature, and Document Print Count Properties name readonly hiddenfield mandatory enablecapturefromfile enablecapturefromdevice storageoptions automaticfield name readonly hiddenfield If the above table does not include a property that you intend to use, you can list the properties by defining a custom process and running an enrollment with a print statement in the JavaScript function. The fields and their properties are sent to TruCredential stdout logs in the <TC_HOM<\logs folder. Radio Buttons For elements defined by TruCredential software, such as radio buttons, refer to the Workflow Designer to see the descriptions for each item. This section describes some of the radio buttons in the Workflow Designer. Text Field: In the workflow, text elements have the Input Format property, which displays as a set of radio buttons in the workflow designer. Each radio button for Input Format is represented by an id appended with _InputFormatOption<number>, where: enforceinputformat is a property of the text field. 8b9b3085-6a d8-7c8eb21bce78 is a TruCredential ID to uniquely identify the field properties. InputFormatOption<Number> is the option (radio button) to set for the Input Format property. Example: enforceinputformat_8b9b3085-6a d8-7c8eb21bce78_inputformatoption1, enforceinputformat_8b9b3085-6a d8-7c8eb21bce78_inputformatoption2, enforceinputformat_8b9b3085-6a d8-7c8eb21bce78_inputformatoption3 TruCredential Developer s Guide 17

24 Compression: Image elements, including the Document, Photograph, and Signature elements, have the Compression property. Each radio button for Storage > Compression is represented by the id appended with _CompressionRadioOption<Number> Example: compressionradio_143fd443-05b4-4df3-ad3b-b a392 CompressionRadioOption1 compressionradio_143fd443-05b4-4df3-ad3b-b a392 CompressionRadioOption2 Cropping: The Photograph element includes the Capture Options > Cropping property, which sets how to crop the photograph. Refer to the Workflow Designer to see the descriptions for the Cropping radio buttons. Each radio button is represented by the field is appended with _CropOption<Number> Example: crop_6b53de7e-02c7-48a8-b668-ebfc d_cropoption1 crop_6b53de7e-02c7-48a8-b668-ebfc d_cropoption2 crop_6b53de7e-02c7-48a8-b668-ebfc d_cropoption2 Sizing a Static Graphic: The Static graphic element includes the Advanced > Sizing Options property. Each sizing option is represented by the id appended with _ScaleOption<Number> Example: scaleoption_770a89fa-9b61-40ed-b4fe-950dca2194fe_scaleoption1 scaleoption_770a89fa-9b61-40ed-b4fe-950dca2194fe_scaleoption2 scaleoption_770a89fa-9b61-40ed-b4fe-950dca2194fe_scaleoption3 Custom Process Examples The input to the script is a JSON string that is an array of key-value pairs.each field is identified by a unique name key. Each array includes field properties, where the key is the field property name and the value is the value in the field property. Along with field properties, the id and value are included in the array. Script Input Sample The following JSON sample array uses a workflow field called name which is a List field. It has properties including name, inputlength, hiddenfield, and fontfamily. [{"type":"workflowfieldlist","name":"list field 1", "inputlength":"20","width":"91","positionleft":"287","positiontop":"332", "mandatory":false,"readonly":false,"hiddenfield":false, "listvalueinput":"","fontfamily":"arial","listvalueokbutton":"","fontweight":"normal", "list-value-default":"abc","list-values":["abc","123","one","two"], "fontstyle":"normal", "importokbutton":"","fontcolor":"#000000","fontsize":"12", "id":"d19a a89a-e58fd5dd55b7","value":"abc"] 18 Custom Processes

25 Input Sample Notes List field: When you add a List element to a workflow, you define the values in the list. They are represented by the key list-values in the JavaScript file, for example: "list-values":["value1","value2","value3","value4"]," The default value, if any, is represented by list-value-default, for example: list-value-default : value1 Sample Script 1 This script appends data to the existing value in a text field. var tc_event; changevalue(tc_event); function changevalue(tc_event) { //Parse the JSON string var tcdata = JSON.parse(TC_Event); //Iterate through parsed json for (var index in tcdata) { //Fetch each field i.e each key value pair var field = tcdata [index]; //Change value for the field with name 'Text Field 1' or 'First name' if (field['name'] == 'Text Field 1' field['name'] == 'First Name ) { field['value'] = field['value']+ 'append data'; tc_event = JSON.stringify(tcData); return tc_event; Sample Script 2 This script parses the Full Name field, and sets it to read only. var tc_event; changevalue(tc_event); function changevalue(tc_event) { //Parse the JSON string var tcdata = JSON.parse(TC_Event); //Iterate through parsed json for (var index in tcdata) { //Fetch each field i.e each key value pair var field = tcdata [index]; TruCredential Developer s Guide 19

26 //Change value for the field with name 'Full Name' if (field['name'] == 'Full Name') { field['readonly'] = true; tc_event = JSON.stringify(tcData); return tc_event; Sample Script 3 This script sample limits enrollment to applicants who are 18 years of age or older. /* AgeCheck script: Calculate Age from DOB and set fields based upon under 18 age or not */ /* Note: When this file is updated, it must be reloaded into TruCredential. Use Settings > Settings > Customization Toolkit */ var input; var tc_event; /* do not change this variable name */ /* Function to change values and field properties in the designated workflow */ function changevalue(input) { /* print("input to script: "+input); */ /* the print command is used for debugging the script by sending input to the TruCredential log file: trucredentialstdout.yyyy-mm-dd.log*/ var inputparsed = JSON.parse(input); /* Get the Index to each field once here. Note the 3rd parameter (DOB, AGE, etc.) is the workflow field name that you need to access. These fields must be in the workflow using this function */ var indexdob = getfieldindex(inputparsed, 'name', 'DOB'); var indexage = getfieldindex(inputparsed, 'name', 'AGE'); var indexagepass = getfieldindex(inputparsed, 'name', 'AGEPASS'); var indexphoto = getfieldindex(inputparsed, 'name', 'PHOTOFIELD'); var indexstudentname = getfieldindex(inputparsed, 'name', 'STUDENTNAME'); /* Get DOB field from TruCredential input file and calculate age */ var dobvalue = inputparsed[indexdob]['value']; var agetoday = getage(dobvalue); inputparsed[indexage]['value'] = agetoday; inputparsed[indexagepass]['readonly'] = true; /* if age is 18 or over, then show YES in field and make photo and name writable */ /* print("agetoday="+agetoday);*/ if ((agetoday >= 18)) { inputparsed[indexagepass]['value'] = "YES"; inputparsed[indexphoto]['readonly'] = false; inputparsed[indexstudentname]['readonly'] = false; else { /* if age under 18, then show NO in field and make photo and name readonly */ inputparsed[indexagepass]['value'] = "NO"; inputparsed[indexphoto]['readonly'] = true; inputparsed[indexstudentname]['readonly'] = true; /* print("script output: "+tc_event); */ return JSON.stringify(inputParsed); tc_event = changevalue(tc_event); 20 Custom Processes

27 /* Returns the index of a field based on its property and value, usually name */ /* Example: var indextextfield1 = getfieldindex(inputparsed, 'name', 'DOB'); */ function getfieldindex(fields, prop, value) { for (var i in fields) { if (fields[i][prop] === value) return i; return -1; /* Returns the age based on the input datestring date of birth */ function getage(datestring) { var today = new Date(); var birthdate = new Date(dateString); var age = today.getfullyear() - birthdate.getfullyear(); var m = today.getmonth() - birthdate.getmonth(); if (m < 0 (m === 0 && today.getdate() < birthdate.getdate())) age--; return age; Messages You can display a custom message to users. Return the message using the errormessage variable name. The message you define is displayed to an operator if the Stop on Failure option is selected on the Event Configuration tab in the Workflow Designer. Otherwise, developers can observe the message in an error log. Maintain the following variables while running the message script: Input variable: TC_Event Output variable: tc_event Message: errormessage Script with Message Display This script is similar to the other scripts in the section, with message handling added. var tc_event; var errormessage; changevalue(tc_event); function changevalue(tc_event) { //Parse the JSON string var tcdata = JSON.parse(TC_Event); //Iterate through parsed json for (var index in tcdata) { TruCredential Developer s Guide 21

28 //Fetch each field i.e each key value pair var field = tcdata[index]; if (field['name'] == 'Text Field 1' field['name'] == 'First Name') { if (field['value'] == "Invalid value") { errormessage = "The value for the field is not allowed."; else { field['value'] = 'new value'; tc_event = JSON.stringify(tcData); return tc_event; 22 Custom Processes