In a lot of organizations the preferred method of managing multiple tickets is to close them and then wait to see if the users open a new one.
Beyond that I am afraid that James is right. You need to explain a lot more about your problem and get specific about what needs to be solved. A short code sample that illustrates your problem is an excellent starting place.
I want to make several tickets waiting by covered or by table number.
the concept as follows:
cash register for tea room
manage tables that are waiting for each table there are several command lines
then the validation of the tickets did to the regulation
So it's a web based Tab system? And it's a conceptual design stage? What OE version? I'm guessing you'll be looking at PASOE, with a REST API and things like that. But you really haven't given us much to go on. Therefore the advice will also be poor.
I want to make several tickets waiting by covered or by table number.
the concept as follows:
cash register for tea room
manage tables that are waiting for each table there are several command lines
then the validation of the tickets did to the regulation
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.