Here is what’s new on the site since our last blog update:
Kinetic Request Answers All Retrieve (October 14, 2014)
Retrieves a specific submission’s answers. This is useful for inside subtrees/routines because it allows you, after this handler is run, to have the equivalent of the @answers references available.
Kinetic Request Base Submission Retrieve (October 13, 2014)
Returns an XML string of the base submission (KS_SRV_CustomerSurvey_base) name and value pairs. This is useful for inside subtrees/routines because it allows you, after this handler is run, to have the equivalent of the old @base references available. Note that values here are referenced by their names of the base form, not the “friendly” names defined in the dataset.
Kinetic Request Submission Dataset Retrieve (October 13, 2014)
Returns an XML string of the dataset name and value pairs. This is useful for inside subtrees because it allows you, after this handler is run, to have the equivalent of the @dataset references available.
Utility JSON to Results (October 13, 2014)
This handler is useful for converting JSON array declarations to XML strings. At right is an example of the type of conversion from JSON to XML.
Using a Bridge Search to Populate Questions using a YUI Table (October 10, 2014)
This solution describes how to use bridging to do a people search, populating fields on the service item using a bridge request based on criteria the user provides. If there is more than one response to the search, a table is displayed for the user to select the correct individual from. This table uses a version of YUI tables.
Using a Bridge Search to Populate Questions using a Mobile Friendly Table (October 10, 2014)
This solution describes how to use bridging to do a people search, populating fields on the service item using a bridge request based on criteria the user provides. If there is more than one response to the search, a table is displayed for the user to select the correct individual from. This table uses a mobile friendly version of datatables called FooTables.
Chef Node Bootstrap (October 8, 2014)
This handler bootstraps a node in chef by using an external ruby instance to call chef. Before uploading this handler, make sure to include a chef repository containing a knife.rb file on the task engine server, either in the resources directory of the handler file or in a directory that the handler can access on the server.
How to Leverage Subtrees/Routines for Approval Delegation (October 8, 2014)
This solution describes how to use a subtree (routine in Task 4) recursively to process approval delegation (re-assigning of the approval). The subtree/routine built here is an individual approval flow that could then be called by a group approval process if necessary.
Calculating the Cost of a Requested Service Item (September 26, 2014)
At times Service Items require the calculation of a total cost based upon the items selected. Ordering computer accessories is an example of this scenario. The user can select from several different computer accessories, each of which has an associated cost.
New Task Handler Page on Kinetic Community (September 23, 2014)
Browse and download existing Kinetic Task Handlers to use out of the box or customize them. All Kinetic Task Handlers are validated by Kinetic Data Task experts.
Pardot Prospect Create Handler (September 19, 2014)
This handler uses the Pardot REST API to create a new prospect. To configure the info values, you’ll need your email, password, and a user key. This key can be found in your account settings under the description of API User Key. After configuring the handler, all the information can then be used to send and API call to Pardot to create a new prospect.
To learn more, check out all recent updates and resource additions on Kinetic Community.
Cassy Lueneburg