Hi,

In v2006, we have a screen called Send Msg to RF User. I've been trying to dig into it to figure out how it works in the background, because I'd like to be able to re-purpose some of the functionality if possible. I'm wondering if it can be used to send a message to a Vocollect user - if so, I was considering writing a database trigger to do stuff like:

• When a picker picks up a task, have Vocollect tell them something like “This task has 2 emergency picks”.
• When a picker completes a pick (not the whole task – just a single pick on a task), have Vocollect check the next pick and potentially say “The next pick is for an emergency order”.
• Also when a picker completes a pick, have Vocollect check the status of the carton the pick was for. If it’s stat code 20 (packed), have Vocollect say “close container”.

Using the database trigger method, I can write the code myself without needing Manhattan. I just did that for a different piece of functionality, which saved us the $100K that Manhattan quoted for the mod. 

Also, I was looking in the documentation we have for Vocollect messages, specifically prTaskLUTGetPicks – apparently in the response to that, there’s a field “PICKMESSAGE”, which is always blank, at least according to our document. I’m trying to figure out how to populate it so that when it directs a user to a location, and finally says “pick 1”, it would end up saying “pick 1 – emergency” instead. We'd like to have the "close container" command working as well - apparently Vocollect does have the command, but it's turned off in our Voice Console because our task package doesn't handle it.

Finally, does anyone have any documentation about how to create a Vocollect task package? Or modify one? I was able to successfully modify our existing task package, basically through some dumb luck. Here's a snippet of our task package:

Does anyone have any documentation about what any of that means?

Hah! Thanks, I'll take that as a compliment. :)

I'm kind of forced into thinking about strange ways to do things, since we're way beyond end-of-life with our version, and there's a big push in the company I work for to reduce costs so it's difficult to get approval for a mod. We generally try to figure out a way to do things ourselves before approaching Manhattan for a quote, mainly because the quote is often much higher than expected. For example, they recently quoted us $100K for a mod; I ended up coding the desired functionality myself using a database trigger and a couple of system codes within about a week.

Anyway, thanks for your continued input. Having others to bounce ideas off of is always helpful, and could potentially save us all some mod-money. I'm going to pursue the PICKMESSAGE thing and see if I can figure out how it gets populated.