There are many ways to return multiple values from a cfc. Typically we return a query object, a json string, an array, or a structure, but one of my favorite ways to return multiple bits of data is using a shorthand structure. It is much easier and intuitive to use on both the back and front end than using an array. Here is a simple example: Cfc:

<!--- There are two types of routing titles. The original design used an routing title that was used to populate a contract and this title was not the official title, but something more generic that was easily identifiable on a written contract. The other title is the official title that is coming from the workday database We will use the original routing title if the user was assigned a routing title that is found in the routing database, otherwise, we will use the official workday title. --->
<cffunction name="getTitleByEmail" access="remote" returntype="struct"  hint="Determines the approver title. This will be either the routing title that was used in previous contracts, or the official title found in workday. We need to return multiple values, so this returns a one dimension array instead of a string.">
	<cfargument name="email" type="string" required="yes" hint="Supply the email.">
                    
      <cfparam name="title" default="">
                    
      <!---Format the email--->
      <cfinvoke component="#WorkdayUsersObj#" method="formatUwEmail" returnvariable="uwEmail">
      	<cfinvokeargument name="email" value="#arguments.email#">
	</cfinvoke>
                    
      <!--- Query the Approval database to see if the title exists. --->
      <cfquery name="approvalTitle" datasource="Contracts">
      	SELECT TOP (1)     
		ApproverTitle
		FROM dbo.Approval
		WHERE  (Email = <cfqueryparam value="#uwEmail#" cfsqltype="cf_sql_varchar">) 
      </cfquery>
      <!---Set the ApproverTitle--->
      <cfset ApproverTitle = approvalTitle.ApproverTitle>
	<!---Get the workday job title. --->
	<cfinvoke component="#WorkdayUsersObj#" method="getEmployeeJobTitle" returnvariable="workdayTitle">
		<cfinvokeargument name="email" value="#email#">
	</cfinvoke>
                    
      <!---Build the shorthand struct --->
      <cfset titleStruct = {workdayTitle = #workdayTitle#, ApproverTitle = #ApproverTitle#}>
                    
   <cfreturn titleStruct>
                
</cffunction>

On the client side, simply use the following to output the value:

<cfset thisRoutingTitle = getTitleByEmail(thisApproverEmail).ApproverTitle>
<cfset thisWorkdayTitle = getTitleByEmail(thisApproverEmail).WorkdayTitle>

I am going to forgo using Raymond's localization support for this version. To incorporate a few languages, Raymond uses the resourceBundle.cfc template that was originally coded by Paul Hastings. I believe that it supports two variants Dutch and German languages, along with English of course. Raymond labels his buttons and text messages in the different languages in 4 different .properties files, and uses the 'rb('message var') function to display the text and messages. I have decided not to incorporate the localization as I can't translate between English and the other languages, and this blog is also intended to be a living example how to use Kendo with ColdFusion. Using 'rb('pleaseWait') in my code will be confusing to the reader wanting to know how I am using ColdFusion and Kendo. It is much easier to read:

'$.when(kendo.ui.ExtWaitDialog.show({ title: "Please wait...", message: "Searching.", icon: "k-ext-information" }));'

than

'$.when(kendo.ui.ExtWaitDialog.show({ title: "
<cfoutput>
 #rb(pleaseWait)#
</cfoutput>", message: "
<cfoutput>
 #rb(searching)#
</cfoutput>", icon: "k-ext-information" }));'

for example. In one of the next versions, if someone wants to assist me in translating the English into the supported languages, I may revisit this decision and incorporate localization into the code.