Passing variables directly from iApps to TMSH.

iapp::conf is a wrapper for tmsh::create/modify/delete that automatically logs the command in /var/tmp/scriptd.out to cut down on the need for debugging "puts" statements like the one you used. iapp::conf also prevents command duplication, which you may or may not be interested in. In order for iapp::conf to return the object name, however, it depends on the convention that the object name contains an underscore character ("_"). Since zscaler-wcf-gre-source-nonfloat-lb01-dbb-12345 contains no underscores, the proc runs but returns a null string. I do not see anything in your example that would require escaping. The use of [format] is harmless but probably unnecessary. Either of the following should work in implementation:

tmsh::create $::NONFLOAT$::GRESourceLoopback__lb-$::GRESourceLoopback__diocese-$::GRESourceLoopback__orgid$::IPADDRESS$::GRESourceLoopback__loopback/32$::TRAFFICGROUP$::VLANLOOPBACK
or
iapp::conf create $::NONFLOAT$::GRESourceLoopback__lb-$::GRESourceLoopback__diocese-$::GRESourceLoopback__orgid$::IPADDRESS$::GRESourceLoopback__loopback/32$::TRAFFICGROUP$::VLANLOOPBACK

BTW, if you want to be more explicit with the boundaries of your variable names, use curlies, like this:

tmsh::create 
${::NONFLOAT}${::GRESourceLoopback__lb}-${::GRESourceLoopback__diocese}- \
${::GRESourceLoopback__orgid}${::IPADDRESS}${::GRESourceLoopback__loopback}/32 \
${::TRAFFICGROUP}${::VLANLOOPBACK}

Excellent. Thank you Gentlemen. I will try these suggestion and report back.

That did the trick.... With another check of my code, I found the issue: I had used the tmsh::create before however it kept giving me errors, so moved to iapps::conf and still the same issue.... Upon review of my code, I noticed my variable $::NONFLOAT had the "create" command already set. I simply needed to remove the "create" in my variable, as the create is passed by the tmsh::create command. Obvious now I look at it! Thank you so much. I was going mad!