#Openbravo web pos update#

The update process is very intrusive because it basically drops the whole database and recreates it again. This is an unreliable method for the Web POS as this version is not automatically updated each release, and doesn't work in case extension modules add tables to the database The Web POS only considers that the database needs to be updated when the database version is changed. Right now there are several different problems in the way Web POS handles updates of both the main module and other extension modules: If applying the solution provided in the original ticket has caused a new issue, you could also create a follow-up ticket.Openbravo Issue Tracking System - Retail ModulesĠ029055: Web POS doesn't handle update of local database tables correctly You should create a follow-up ticket when the solution provided did not solve the problem reported in the ticket, that is, the problem happened again after applying the solution. Once a solved ticket is closed it will include the following line at the end: The ticket status will change to Open again. If you want to add an answer to the request, you should use Add to conversation button, add the required text and Submit. It will be at the end of the conversation. You could enter the ticket to analyze the provided answer. Once Openbravo provides you with a final answer, its status will change to Solved. When you submit a ticket, you will see it in Open status:

Solved : Final answer has been provided by Openbravo.

Awaiting your reply : Openbravo needs your action for following the ticket management.

Open : Openbravo is currently working on it.You could filter the requests by its status and order them by the Last activity column in order to have the newer tickets first.

You will get a success message after submitting the ticket.Īll the requests will be listed in My activities menu entry.

Finally, submit the request by the Submit button.

In case you need to attach any file to the ticket, you can directly drop to attachments section.

In case the ticket is related with a doubt during a training, please select the training name in the Training Course field.

In case we should launch a process or modify data to reproduce an issue, it would be very important to have access to a TEST environment.

If the problem is happening on a POS terminal, remote desktop access will also be required.

It is very important to have both web and ssh access to the environment in which the problem is happening, the configuration should be checked and so on.

Add private data such as accesses in Confidential Information section:.

Critical: production system is severely impacted or business-critical applications are completely down causing that the customer cannot reasonably continue to work.

Major: A business-critical process is impaired, causing serious impact on daily operations, and there is no acceptable workaround.

Medium: a problem causing partial, non-critical functionality loss.

Minor: an inquiry and/or low system impact issue which does not require immediate attention.

Set the severity based on the request type:.

Adding an example, the business case of the customer and so on will help us speeding up the resolution.

Use the description field to explain your request in deep.

You could take a look to it in order to find a clue for solving your issue.

When adding the title to the request, some Knowledge Base entries will be proposed.

Note: it could be a good option to add the customer name on the request title in order to ease looking for it among all the tickets of your organization.

Add other email addresses in CC field in case it is needed.

Select the customer that is having the issue.

When submitting a request it is very important to provide us with as much information as possible. In case you need to raise an issue or doubt to Openbravo Support Team you should sign in first by adding your email and password.

Openbravo web pos