Saves the data from a json string created from an HTML table into a Remedy form for future reporting and/or processing. To see how to create the data to feed into this handler, please see the community article here.
Note that the table name is a value you assign when using this handler to save the data.
Each row in the table will be saved as one record in the form CUSTOM:KS_SRV_TableData_base. This form is provided in the download section. Note that this form is a customized example. This form stores a table name (identifier for the table), Associated Request GUID (Originating ID), the originating Request Template name, the originating Request Template ID, the column labels and the values for each value in the row. In the provided form, up to 20 columns per row can be stored, the labels can be up to 254 characters, and the values can be up to 4000 characters (the out of the box size of the full answer field). If database storage space is a concern, the size of the value fields can be made smaller. If this is done, it is very important that the questions used to fill in the table have a character limit that matches the limit being put in place. Also, it is important to realize that hidden columns (columns not shown to the user) still are stored in the table. If you need more than 20 columns, you'll want to update not only the form with the new label and value fields (note that the field numbers are critical) but the find and retrieve handlers that go with it. Also, if you update the form name to match your naming schema, you'll want to be sure to update each of the handlers to reference your new form name.
One result of the create handler is the row count of the rows of data saved. The other is the instance IDs of the record for each row. This allows for looping through the rows without having to do a find handler if you want to loop through every row in the table.
The format of the XML of request IDs returned is:
The format of the XML of instance IDs returned is:
This handler can be used to store data for reporting. The Associated Request GUID (Originating ID) is a required field, but the Template Name and Instance ID are not. Note that this data may be required by your reporting process if yowant to report on data by template, rather than just by individual record. Reporting most efficiently from this form may require joining this form with the service item or service item template forms, depending on what is desired.
|JSON String||Serialized table data in JSON format|
|Table Name||Identifier for the table|
|Originating ID||Associated Request GUID|
|Template Name||The originating Request Template name|
|Template Instance ID||The originating Request Template ID|
|Table Name||Contact Table|
|Originating ID||<%=@dataset['Originating ID']%>|
|Template Name||<%=@dataset['Survey Template Name']%>|
|Template Instance ID||<%=@dataset['Survey Instance ID']%>|
Sample Configuration 2
|JSON String||[ |
|Table Name||Contact Table|
|Template Name||Contact Updates|
|Template Instance ID||KSfb02da8bec9b1ca832597c3562a6e124b|
|Table Data Request Id List||An XML list of the data rows/records created.|
|Table Data Instance Id List||An XML list of the data rows/records created.|
|Table Data Row Count||The count of the number of data rows saved/records created.|
|2||2013-06-17||Updated the returned request ID list to be XML, added XML list of Instancd IDs to results|
|2||2017-06-21||Only load JSON in Task 3 and below to make it compatible with Task 4 and above.|