Jimmy'sTubeCast Blog

Regardless of the programming language, a looping-statement is a common declaration for iterating through collections of things, such as the items of an array, records selected from a database, elements within an XML file, or the files inside a directory. A recent AutoStore challenge was presented where a script was used to fetch data in a process that returned either one or many items. This was the easy part. However, each return record needed to be specific to an individual Route based on one of those items returned. Example Example1@email.com Example1/URL Example2@email.com Example2/URL Example3@email.com Example3/URL Although the captured document being processed would be common for all in the return, the recipient belonging to one of these unique records should not be aware of  nor  receive any of the information that would belong to a different recipient. Because an unknown number of return records would be expected, this presents a challenge due to the fa

If Runtime Replacement Tags (RRTs) make an AutoStore configuration come to life, then workflows can get a bit more clever when Smart RRT technology is used. The Smart RRT is not a new gadget, but these little wonders can come in handy. What is a Smart RRT? As a placeholder for information, an AutoStore RRT has an RRV, which stands for Runtime Replacement Value. We can take a user-defined RRT, also referred to as a FRTN (Field Replacement Tag Name), and inject VBScript into the RRT to quickly modify that tag's value. The result is a Smart RRT. A Smart RRT is certainly not the only way to modify the value of an RRT. The VB/JScript component allows a custom script to be used to generate a needed value based on a metadata value, and the Data Filter component also provides several filters to do the same. There are cases where implementing a Smart RRT may generally be a quicker approach if a given workflow can benefit from the RRV of its modified RRT. We'll look at some ex