Aloha Scheduling

[blurngr]

Hi all,

We are attempting to interface with the Aloha scheduling files, but are having a difficult time.

It appears (please let me know if I'm wrong) that we can read / write to the schdshift.dbf file to accomplish the insertion of a work schedule into the Aloha system.

A few questions about this process ...

1. This DBF file has a number of columns which are self-explanatory, and some that aren't. What are the columns usernumber, storeacc, parentacc, storeid, priority, emplocked, laboradd, instruct, and splitid used for? Does anyone have a sample of this file that we could take a look at?

2. Would we need to insert the data into DBF file in the NEWDATA or the DATA directory? I assume if it's in the NEWDATA directory, we'd need to do a db upgrade to get it to take affect?

3. I've seen a sch.dbf file in a few places, but it's not on our Aloha 5.3 QS system. What is this file for, and is it necessary? Any other files that we're missing?

4. What needs to be done to enforce the schedule? I assume there's a configuration flag that needs to be thrown, just not sure where.

Thanks very much!

 

[alohahello]

to run labor shceduler you need to be licensed for it.
Its one of the backoffice products that aloha offers.

 

[blurngr]

alohahello,

Thanks ... I know that the labor scheduler needs a license, but my clients don't want to use the labor scheduler from Aloha - they'd prefer to use our product. However, they want to enforce the schedule in Aloha.

In other POS systems (which are more open), like Dinerware, Micros, RMS, POSitouch, this isn't a problem. In Aloha, it is a bit of a pain.

Was looking for some help for users who want to use the schdshift.dbf file and enforcement without the aloha labor scheduler product.


--
Anthony

 

[DTSMAN]

Yep, there is a configuration flag. It is under job code maintenance. The flag is too ignore labor scheduler. Obviously there to work with Aloh's scheduler, but that is the only flag.

Bo

Remember,
If the women don't find you handsome,
they should at least find you handy.
(Red Green)

http://www.redgreen.com

 

[blurngr]

Bo,

Thanks for your help! That was easy enough. Can you help at all with the field definitions in the schdshift.dbf file?

usernumber,
storeacc,
parentacc,
storeid,
priority,
emplocked,
laboradd,
instruct,
splitid

Thanks!

 

[DTSMAN]

I am not at all familiar with this area, but will help you guess if noone else knows.

It looks like you may not need all these fields and may only need place holders for them. It is solely designed to work with their labor scheduler, they don't care about yours; it is the competition.

Good ol' car analogy;
You are putting a Ford engine into a Dodge and possibly trying to adapt a Toyota computer to control it all.
Have fun!

If I had to make a guess at some;
Store id may be for multistore environments, just use a 1 if that is all there is. User number may be the line number in the DB and not the employee number. Storeacc and Parentacc may again be for multistore environments. Emplocked probably looks for the marker that an employee is logged on to a terminal and will not let the scheduler do something.

Call Radiant and ask for SDKs or this guy at the following web site has been granted access to create add-ons and may or may not help you. Throw some money at him and maybe he will.

http://www.lonetreetechnology.com/aloha/index.php

Bo

Remember,
If the women don't find you handsome,
they should at least find you handy.
(Red Green)

http://www.redgreen.com

 

[blurngr]

Bo,

Thanks again for your help.

I'm not sure what the status of LoneTree is, I've tried pinging them a few times for various projects over the past three years ... haven't heard back.

I have called Radiant. They want $25,000 for the SDK's, and an annual $500 per store to use their Connect platform.

Which is an interesting number, because that's slightly more, per year, than the ongoing support for the labor scheduling product. Of course, our customers don't want anything to do with the Aloha labor scheduling product.

 

[alohahello]

yea lonetree is pretty good. we have one client using them integrated with aloha, for billiards and food.