• This module provides the common infrastructure to develop mobile applications on top of Openbravo.

• Openbravo 3 must offer a world class user experience on mobile/touch devices (such as iPhone, Android and tablets). A mobile enterprise is generally accepted to confer benefits in the areas of higher workforce productivity and employee satisfaction. With a mobile offering, Openbravo 3 will be truly accessible anwhere, anytime.

• Define and publish the technical architecture and vision of Openbravo Mobile

• Openbravo Mobile infrastructure should be able to detect a mobile browser and redirect to a mobile login page. After a successful login, the user should be able to get an initial Workspace from which operations are launched (open windows, recent documents, etc)

• Support for Standard Windows defined in the Application Dictionary. This implies code generation, reference implementation, etc

• Support for launching Processes and Reports from a Mobile device

• Support for opening manually coded windows

• Fine-tune all functional flows and usability in a mobile device

• Ability to register purchase orders from mobile devices. Includes configuration option that allows to control weight of the order.

• Mobile application that allows to do goods movements and supports scanner based input for fast operations

• Image reference allows developers to embed images into the Openbravo windows. They can be uploaded and associated with any record.

• Put your favorite widgets inside standard Openbravo forms. These widgets can contain anything such as charts and grids and can be configured to be filtered for the active window only.

• Modify the layout of forms to suit personal preferences. Position, visibility, first focus, width and height of fields can be defined on user level. The order in which the fields appear and the section they appear in can be modified though an easy drag & drop interface.

• Saving Views stores grid and form settings, column filters and even the entire layout of the screen. You can access Saved Views through a pull down menu that sits underneath the Saved Views button in the toolbar.

• Filter expressions at column level that are typed by the user (eg. >5, !, etc.)

• P&E aims to replace all process popups with a generic design pattern. The essence of P&E lies in reusing objects that are picked from a larger collection. Sometimes this collection needs to be filtered in steps while picked objects need to be kept. Sometimes the picked objects need to be edited. The final set is eventually submitted as a process and adds or replaces existing sets.

• Phase 1 in new Process with new UI architecture. Implement manual processes that can be invoked from generated windows executing a JavaScript function.

• New UI pattern defined in the AD that generates dialog that requests user to enter parameters of a process / report. It makes use of SmartClient references for parameters aiming to be a replacement of the existing generated UI Process and Reports which still uses Openbravo 2.50 style forcing to generate code through WAD.

• Completion of Parameter Windows

• Ability to define fields that require entering text/string values in the correct format

• Ability to add a rich text field (that supports text formatting) to Openbravo

• Log in to Openbravo using a Google account

• Now if you try to delete a client from the UI, you get an error. It has to be re-implemented using DAL.

• Onchange functions can be executed completely in the client, implemented in javascript, which brings benefits of simplicity and performance

• Usually users want to continue creating another header after having completed a document. Now, the focus remains in the child level after completion, resulting in creating an additional line (in the completed document!) where in fact she wanted to create a new header

• Openbravo allows user to specify a number of company logos. Each logo is expected to be in a specific size. However, finding the size is difficult and requiring users to resize logos is just unpractical and not what users expect (most applications resize images automatically)

• Ability to define fields that are not backed by a physical column but by a javascript expression that is computed in the front-end

• Support for languages that are written right-to-left, such as Hebrew and Arabic.

• Ability to define fields that are not backed by a physical column but by a property path, in the same way that can be defined within selectors

• Ability to define fields that are not backed by a physical column but by a sql expression that is computed in the back-end

• Reduce build time by not generating unneeded 2.50 generated windows

• DropDown lists can be filtered by selecting multiple of the available values. When multiple values are selected all records matching any of them are shown in the grid.

• Records in grid can be grouped by a certain value/column.

• The grid allows you to set summary functions for a column. These summary values are shown in a separate row in the bottom of the grid. The summary functions are executed on the server so they operate on the complete dataset which fits into the current filter.

• Extend background process definition by making possible to define them as "Single Instance". A Single Instance background process checks before running if there is another instance of the same process, in this case execution is prevented.

• Tabs can be hidden depending on expressions

• Extension of Query List Widget to support Java implementation of the datasource providing data instead of creating this data from a HQL.

• New capability of the Process Definition process to execute different actions after completion (such as open a new window, display message, etc). It is extensible by modules, being possible them to define new actions.

• New reference based on Selector, that allows user to select multiple items from a list. To be used within Standard UI Process Definitions

• Platform capability that allows to send emails based on programmatically defined events.

• Add capability for Tabs to be based on arbitrary datasources instead of just in tables. This feature allows to programatically define the source of data that will be shown in a tab.

• Integrate Mondrian Online Analytical Processing (OLAP) server with Openbravo. Use Smartclient Cube / Charts to renders an OLAP table and chart.

• Ability to define which are the securizable elements used by each manual component

• Currently 2.50 drop down list references (table and tableDir) are implemented as they were in 2.50. This is, the complete list of possible values is returned on load. This affects performance in case of big volumes. This project aims to implement these references in 3.0 style, not returning the whole set of values but dynamically request to backend for them.

• Fix following issues

• Ability to print/email any document from any window

• Improve URL entries in menu to allow to make them secure by role, open in application tab/browser tab...

• Differentiate basic components (included by default. eg. invoice complete) from advanced ones (excluded by default. eg. edit payment plan)

• Eg. It is too difficult for developers to preview / understand the result of their work (clearly developers do not understand that the "Reference Data Description" field will be used to enable users to select the right data set")

• Ability to open a query/list widget from any tab in any window in which the tab information can be queried (child tabs will join with its parents and information won't be filtered by a specific header).

• This is a brand new demo data set but it is built to preserve consistency with the previous one. Customers, vendors and products remain the same. Structure organizations is kept but the consolidation now happens in USD. P&L and Balance sheet is fully configured in the US org. Other several incorrect configurations have been corrected

• It must be possible to define Openbravo business processes through a BPM/Workflow engine. The web console of the BPM/Workflow engine will be embedded into the Openbravo UI so it is possible for Openbravo users to interact with runtime tasks generated by the BPM/Workflow engine and administer/monitor runtime instances.

• Ability to define role access at tab and field level (write).

Contributed by SAIC

• New deployment mode of Openbravo Professional, only available for Openbravo Partners. On-line service to provision an Openbravo instance on-demand, and bill the service monthly based on named users.
  • Phase 1: Service working in a semi-automated mode available for partners on request.

• New deployment mode of Openbravo Professional, only available for Openbravo Partners. On-line service to provision an Openbravo instance on-demand, and bill the service monthly based on named users.
  • Phase 2: Service working in a fully-automated mode activated by default for all existing and new partners.

• Create Openbravo package for the Ubuntu 12.04 which is the latest LTS. Package will use PostgreSQL 9.1.

• Define & deliver new Openbravo Appliance based on Ubuntu Server LTS

• Update release scripts to build new appliance instead for rPath

• New On Demand instances should be provisioned with the latest Openbravo CS release - MP20.

• Create Openbravo package for the Ubuntu 13.04. Research Java7, Tomcat7 topics

• Publish Openbravo Retail distribution

• Publish Openbravo for CoWorking distribution (code repository, testing, appliances)

• In case an instance has background processes that are very demanding java resources, Openbravo can be deployed in a configuration with two Tomcat contexts pointing to the same database. One of these contexts is used for regular operations whereas the other one is used solely to execute background processes.

• Some fields should be editable in processed "awaiting execution" payments

• It should be possible to void payments in "awaiting execution status"

• It should be possible not to post a remittance if needed

• OB should find a credit payment if any, with a generated credit amount equal to invoice's grand total amount. Invoice and Payment description must be properly adjusted

• It should be possible to generate a unique payment out from a remittance of that type

• Creation of an "Accounting" view under Financial Account transactions tab, including 2 new columns "Bank Statement" and "Bank Statement Line"

• GL entries must allow entering accounting dimensions

• It should be possible to undo settle and protested remittance lines, in order to get that a remittance can be reactivated

• Write off amounts should be properly accounted regardless positive/negative write off amounts

• It should be possible to generate a unique payment in from a remittance of that type

• It should be possible to add accounting dimensions to the GL item type payments created in the Financial Account (Add Transactions)

• Ability to split a bank statement line in order to allow partial matching

• OB should allow to add several GL items during reconciliation process

• It should be possible to mix invoices, orders and GL item while adding a payment

• Exchange Rate at document type level

• IDL must support accounting dimensions import

• It should be possible to link accounting dimensions to each GL item entered while creating a payment

• Allow to generate a unique payment in/out from the corresponding remittance when that remittance also includes payment and not just invoices or orders

• Presents the position of a financial account in a given date taking into account expected cash inflows and outflows

• The performance of the "Reconciliation" tab of the Financial Account window needs to be improved.

• APR Payment monitor process should update paid and outstanding amounts

• Settle/Protest remittance process should improve as described below:# When protesting a remittance end-user should be able to filter by remittance dates, remittance (optional), business partner and payment description (doc.number)#Besides, It should be possible to protest and void in one shot

• It should be possible to replace GL items as well as its corresponding dimensions in "GL Item" transaction types, after being reconcilied.

• Make a relationship between the credit payment (the one reconciled) and the later on created invoice payment

• Some additional info such as BP balance needs to be added to payment report.

• Some additional info will be included when exporting to excel, such as payment method, payment date...

• Add payment details form should display the information grouped by invoice or order depending on filtering criteria

• Enhancement in remittance module to allow new option when processing: "Group by invoice"

• Report which displays the expected incomes or payments in a user defined range of dates

• Ability to print checks (individually or by batches) in an automated manner and to browse historical data in order to print a check again if required. It also provides an easy way for other modules to implement different check printing formats.

• Definition of different statuses in dunning cycle and events to trigger when getting a specific status or when transition from a given status to another given status. Warning for new documents when the BP is in dunning cycle in any of the expected payments. Process which triggers notifications both for OB users (alerts) and BP (email)

• Adds a new configuration flag (Reverse Permanent Account Balances) to the Accounting Schema. In some countries (for example, in Spain) reversing permanent accounts in the end year closing process is mandatory while in others (ex. USA, Canada) it is not required.

• Adds new processing option which is reverse payment. This process should create a new payment which reverses original. It will create a negative payment that will on one side mark invoices as unpaid again, and will create lines for each GL Item contained in original payment with a negative amount, so credit will be debited and debit credited.

• The purpose of this project is to enhance reactivate action for payments. Current functionality erases lines and header amount when a payment is reactivated. This project aims to enhance the process to support editing lines after reactivating a payment.

• Return of material posting: Use different accounts for sales transactions. COGS, Revenue accounts can now be different for this documents.

• in terms of the expected date of a payment and outstanding amounts.

• Improved performance and filtering capabilities of the Select Expected Payments pop-up.

• This project adds tree support for product category so that hierarchy can be defined

• This project adds tree support for assets so that hierarchy can be defined

• Reactivate and Remove Lines (Payment Deletion) Simplifies the deletion of payments reduces the manual steps required of the user

• Provide a new selector using new technology to replace existing manually coded one. Provides auto suggest feature for fast entry as well as filters for each column of the project selector.

• Import bank statement lines from a generic CSV format. It also provides the framework to import custom CSV formats

• Imports bank statement lines from the official WePay CSV file format

• Bank Account section of the Financial account is unified with the Bank Account tab of the Business Partner window exposing fields that allow entry of the account in the international format. There is a new field called Bank Account Format where a user can set the preferred method for generating the Displayed Account Number, which is later on used by other reports or processes to get the account identifier. This list can be later on extended by other modules that add more bank account formats, like for example country-specific formats with bank account number validation.

• Trial Balance Report need to be revisited to improve output format. Current formats are not optimized which leads into a problem when printing large amounts of data. As well some of the current filters will be hidden in a collapsible section to make them easier to use for the end user.

• General Ledger Journal Report (renamed to Journal Entries Report) need to be revisited to improve output format. Current formats are not optimized which leads into a problem when printing large amounts of data. As well some of the current filters will be hidden in a collapsible section to make them easier to use for the end user.

• When creating an account, system will automatically place it in its proper place in the account tree. This feature will just be enabled for accounts which search key is a number.

• Existing valid combination selector is complex. The name of the account is not present once a valid combination is fulfilled and that kills the user experience. In this project a new selector for valid combination will be provided so that it maps accounts. When creating an account, system will also create the related valid combination, so the full concept of valid combination and its complexity will be hidden to the end user.

• Include an Accruals & Deferrals plan in the Product window so that Invoices use it to modify invoice accounting to book revenue / expense in different periods

• Accounting Schema term is not self explanatory. It should be renamed to General Ledger. Multi-accounting schema is an advanced feature that as well should be at first hidden. An additional property will be added to organization which will allow Accounting schema tab of that window to be hidden by default

• Accounting of payments: When a payment is done against an invoice but in a date prior to invoice accounting date it should book things as a prepayment

• Exceptions can be added to an existing bank file import format, so that those are not being taken into account by the import process when trying to match an existing Business Partner or GL Item.

• Now imported bank statement lines are matched against GL Item transactions. By adding some parsing rules for the description of a bank statement, system recognizes lines which were previously related to a GL Item. This match is done using historical info from previously imported Bank statement.

• Current Matching algorithms do not support GL Items Transaction recognition. When most of the imported bank statement lines are matched against GL Item transactions, current logic provided by this module is not helpful enough. The algorithm could provide much more value doing automatic creation of transactions in the financial account (Advance matching Algorithm) or matching existing transactions linked to this GL Item (Standard matching Algorithm).

• New accounting dimension implementation for new entities such as Cost Center, User 1 and User 2 defined dimensions.

User 1 and User 2 are new dimensions which can be customized for each Openbravo instance.

• New dialog to configure dimensions in existing documents (orders, invoices, etc)

• Fiscal calendar supports 13th period. 13th period is an adjustment period, created in the last day of a fiscal year to be used for creation of manual journal entries to do required adjustments before end year closing.

• A button which allows to generate a payment from GL Journal line. This option is available for instances which have only one General Ledger.

• Configuration option at a product level that allows to book goods receipt using its purchase order price

• Ability to deposit to the financial account payments created (Deposit To field) for other financial accounts

• Ability to provide a date for the purchase invoice when voiding an existing one. Up to this point the date used was "now".

• Ability to provide a date for the goods receipt when voiding an existing one. Up to this point the date used was "now".

• Flag to be able to block a customer or a vendor so that specified documents (orders, invoices, shipments / receipts and payments) cannot be fulfilled for them.

• Adds support for doubtful debts management. When a doubtful debt is recognized a provision is booked in the ledger. The provision is cancelled if the debt is satisfied.

• Moves the logic from PLSQL to Java and adds several new features like ability to configure number of the days in a month for the depreciation (regular calendar days or 30 days in each month).

• Improves performance working with big volumes of data.

• Allows to edit description of accounting entries both in Acccounting tab for transactions and in Accounting Transactions window. Once a description has been updated, record is flagged to require a confirmation before unposting the document.

• Adds Date From and Date To filters in GL Posting by DB Tables window.

• Redesigned Open/Close Periods and a new End Year Closing windows improve usability of the Open/Close Periods and Year Closing processes.

• Shows invoice and payment information for a selected customer in a defined period

• Replaces underlying view with a table to enable easy extensibility of this component

• Report which analyzes an account by periods allowing filters to be applied and dimensions grouping

• Avoid closing a year if there are documents which are not yet posted or in draft status. Add a force option to skip this validation.

• When closing a year cretae final sequence for transactions in Accounting (entry sequence).

• Modify output to make it scrollable and standarize to show any document (including not core documents coming from modules such as remittances).

• Reset and delete are two different processes. User most of the times frgets reseting accounting after deletion. Reset should always be run while deleting to make sure everything is computed again.

• Ability to flag a business partner contact as a billing contact and a default billing contact. When sending an invoice through email, an email will be sent to each billing contact.

• Report which shows how changes in balance sheet accounts and income affect cash and cash equivalents, and breaks the analysis down to operating, investing, and financing activities

• Managerial Accounting refers to accounting and financial information aimed at internal audiences. This initiative will address needs such as division, cost center, profit center analysis and will be both separate from the external accounting reporting infrastruacture while reconciling fully with those reports

• Process which calculates actual amount for each of the lines in a budget

• Flag in the BP Customer (default set at organizational level) to automatically control the logic of locking BP (see Business Partner Locking above)

• Rename Accounting Schema as General Ledger in Modules

• General Ledger Report need to be revisited to improve output format. Current formats are not optimized which leads into a problem when printing large amounts of data. As well some of the current filters will be hidden in a collapsible section to make them easier to use for the end user.

• Kind of "accounting dimension", in this case the user can modify the account to be used when posting a goodReceipt/shipment/salesInvoce/purchaseInvoice by providing a GL item to be used instead of the common account

• Accounts in OB have an attribute level. This attribute maps with Spanish COA structure but it does not with other COAs. As accounts are defined in a hierarchical structure, there is no need to use that attribute as level can be retrieved from the tree structure. This project aims to remove that property and the complexity added by it.

• This project aims to revisit all accounting reports defining new structure output formats etc.

• Creation of a cube with accounting information together with the rest of dimensions to do analytic.

• New subledger concept and reporting related.

• Process to move funds between different financial accounts

• Add approvals flow support to Expense reports

• Add approvals flow support to purchase orders and invoices

• The Inventory Count List should be printable in order to allow a proper inventory counting

• It is needed to include the general ledger definition as part of a dataset to get that the Balance sheet and P&L reports definition can be packaged together with Loc Pack

• Report which explains the root cause of any incoming or outgoing fund (cash flow)

• Price including taxes feature lets you define prices including taxes in a price list. This is a critical functionality, especially in the retail industry, where prices ( include taxes) needs to be published.

Contributed by Promantia

• The manufacturer sells to the distributor several products and this to the end customer. One of these products comes damaged and the customer instead of returning the item to the distributor sends it back to the manufacturer. The manufacturer does not have the original order shipped to the customer in his system but wants to register the entry as a return material anyway. Sponsor by Transitional data

• Ability to calculate the pricing based on the cost plus margin. Sponsor by Frontier Solutions

• Ability to group by Invoice and Due date.

Contributed by Praktics

• Enhancements to allow computation of commisions semi-monthy, based on margin, paid invoices, and complex commission calculations. Sponsor by Transitional data

• The ability of not allowing to edit the exchange rate and the amount is defined by preferences. Sponsor by Frontier Solutions

• Ability to define a write-off limit by amount per financial account. Sponsor by Frontier Solutions

• Ability to show the supplier reference in some manual windows

• Price including taxes feature lets you define prices including taxes in a price list. This is a critical functionality, especially in the retail industry, where prices ( include taxes) needs to be published. Contributed by Promantia

• Ability to group by financial account and sort by due date or financial account. Contributed by Praktics

• Enhancement to be able to configure the report with more options and ability to select Breakdowns, Accounts, Subaccounts. Contributed by Xpand-it

• Ability to import projects

• Ability to create procurement contracts and define an invoice plan. Based on this plan ability to create purchase invoices

• Now depreciation can be indicated in asset group.

• An asset can be defined as static, preventing from moving it into the asset tree.

• Costing engine that supports organization and warehouse based costing. It incorporates Average as a first costing method. It also allows to include different costing algorithms as modules. Later it will be enriched with LIFO and FIFO support among other costing methods.

• Ability to calculate the average cost of a product using the invoice price. Sponsor by Frontier Solutions

• FIFO costing method. This project takes advantage of the infrastructure provided by Cost Calculation Engine. Sponsor by Transitional data

• "Invoice Register Books" improved as a way of getting 340 tax report information in a more straightforward way

• The "Spanish Chart of Accounts" needs to be adjusted to reflect 2009/2010 and 2011 new legal requirements

• These new VAT legislation changes imply that the Invoice Register Books setup must be adjusted

• It should be possible to setup few "input" type data as constant values

• 340 tax report submission as a txt file according to Spanish AEAT requirements

• 349 tax report new version includes "Bienes de Inversión" tax rates

• 303 tax report new version includes "Bienes de Inversión" tax rates

• Tax Report 190 submission as a txt file generated according to Spanish AEAT legal requirements

• Tax Report 390 submission as an xml file according to Spanish AEAT legal requirements.

• This version of the tax report supports new legal requirements of Spanish authorities.

• This version of the tax report supports new legal requirements of Spanish authorities and is now compatible with Openbravo 3.

• SPLP modules to change due to VAT rates increase are:

Spanish Taxes (FR 21037), Configuración de Libros de Factura - Modelo340 (FR 21075) Changes in the VAT reports will be implemented as they are known.

• Spanish VAT tax report needs to be delivered to comply with the new VAT rates. Same module version will work for OB3, OB 2.50 with APRM and OB 2.5 without APRM

• Spanish VAT tax report needs to be delivered to comply with the new VAT rates. Same module version will work for OB3, OB 2.50 with APRM and OB 2.5 without APRM

• Includes 2012 fiscal year requirements that are new withholding rates valid from 1st of September 2012. Submission date is 20th of January 2013, the latest.

• Includes 2012 fiscal year requirements that are new VAT and RE rates. Submission date is 30th of January 2013, the latest.

• Includes 2012 fiscal year requirements related to new VAT and RE rates valid from September 1st, 2012. Last submission date is February 28th, 2013.

• New version of the module which supports voiding checks once they have been printed and extensible number to text functions for different languages.

• New version of the module which allows to include in the remittance payments in the status "Payment Received". This is required to complete the support of promisory notes flow.

• Module which deploys an infraestructure to define Number to Word conversion modules so that different logics for different languages can be deployed

• English language module for number to word conversion. Translates number to words in english

• Spanish language module for number to word conversion. Translates number to words in spanish language

• New Accounting tab in transactional data windows that displays accounting information. This functionality was available in a Commercial module that now is no longer required as this feature is embeded in the core.

• Includes Check Printing and Number to Words modules

• Its copies the business partner's, product's and asset's accounts with the corresponding category's accounts in batch mode.

• Return of Materials feature includes two different flows:
  • RMC: Return material from customer. This flow manages customer returns orders, the physical inbound of returned materials and the financial settlement for customer refunds
  • RMV: Return material to vendor. This flow manages vendor returns orders, the physical outbound of returned materials and the financial settlement for vendor refunds

• Allows to manage packs in an easy manner starting from the Sales Order till the Sales Invoice

• Refactor the module to avoid having duplicate PL's

• Thanks to this ext. point you are allowed to sort the retrieved query as you wish. For example FIFO, LIFO, etc.

• Ability to display delivery and invoicing status percentage in sales documents. Contributed by Cleardrop

• Ability to create picking list and complete it once all items have been verified. Sponsored by Massada

• Improved reservations process:
  • Orders can reserve products in a warehouse as a way of a delivery guarantee
  • Orders coming later are not able to use the reserved products
  • This behavior applies to the materials/items with a quantity on hand as well as to the materials/items with a quantity coming from purchase orders. Sponsored by Transitional Data Services.

• Ability to export to Excel. Contributed by Praktics

• Ability to export to Excel. Contributed by Praktics

• Ability to pack a goods shipment. Sponsored by Massada

• Ability to pack items grouping goods shipments per business partner and address and to calculate the weight per box

• Ability to create picking lists grouping by sales order

• Prototype of the WEB based POS window for demostration purposes.

• The WEB based POS window for demostration purposes. Including new Login window and taxes calculation.

• User Guide for the Web based POS window.

• WEB based POS window using HTML5 technologies. Sales window agile, flow oriented, for tablets and touchscreen systems. With wide support of POS hardware. Fully integrated with most recent card payment options. Modular. And capable to work offline.

• Openbravo for Retail version 1.3.1

• Add support for Element PS.

• Wiki documentation for Openbravo retail developers to help building new features, on top of Openbravo's technology. This documentation includes a section for Openbravo for retail concepts and a section of How to documents.

• Ability to log in into Web POS without connectivity to the backend. This will only be possible if the user logged in in the terminal in the past successfully and for instance the terminal has the user session locally stored.

• Support of several user sessions in the same terminal, allowing to switch from one user to another without losing the local session data.

• By configuration, when cashing up, the application will generate an invoice for all the orders created in the cash up period or one invoice per order.

• Configure by permissions the possibility to print or not the order before the receipt is done

• Configure by permissions the possibility to print the cash up report and cash management report.

• Master data is stored locally in the terminal. This master data is refreshed in order to load changes made in the central backend. The refresh of master data is done only when needed, and is configurable.

• Web POS orders are created in the store currency. This functionality allows to perform payments in different currencies. For payments in currencies different than the store currency a change will be applied.

• Ability to check in the client side during the edition of a receipt whether there is available stock for each line of the receipt or not. This functionality will be only available when online. It will be created in an independent module

• Openbravo On Demand will be able to support Openbravo for Retail licensing: billing based on the backend Named Users and POS Terminals.

• Protect user interface from blocking when there is a large list of data to display like products, custmers, ... Implementing a limit of records that can be shown.

• Ability to edit the description field of the order in the Web POS terminal.

• Closed tickets are possible lo find, load and printed in Web POS. This functionality is only available if the terminal is online.

• POS terminal option that adds a confirmation step when closing a receipt that allows the cashier to open the cash drawer and give the change to the customer.

• Functionality to create new and edit customers from the Web POS terminal.

• Ability to edit the description field of order lines.

• Ability to define Discounts and Promotions. This functionality extends existent Price Adjustments by enabling external modules to provide new rules for discounts and promotions.

• Web POS now supports Discounts and Promotions defined in backend, so it is possible to apply them to tickets generated in POS.

• This module implements some rules for discounts and promotions, such as "buy X products and pay Y", "fixed percentage discount", etc. It is included in the Retail distribution.

• Ability to assign a default warehouse & a rule for each store

• Ability to search products in other store warehouses. This functionality will be available only when online.

• Quotation and orders are a separate documents with a separate document type and numbering. When converted to a sales order, persist in the system but the quotation is not be overwritten.

• Functionalty to create quotations, find created quotations and convert to receipts from the Web POS terminal

• Ability to sell on credit, without paying completely the receipt.

• Ability to use from POS Pack Promotions as products. When one of these products is selected, lines for all products in the pack are included in the ticket

• Ability to add discretionary discounts to receipt lines. Percentage discounted can be manually edited.

• Gift Cards include a monetary credit. Gift Vouchers include credit in terms of a list of products or services.

• Filter products, customers while the user is typing the filter

• In addition to the price list including taxes Web POS supports a price list excluding taxes. In this case net prices are shown in the receipt lines and an additional line with a total tax is shown both in the main Web POS screen and in the printed ticket.

• Main Web POS screen shows tax amounts grouped by the tax type.

• New Tab of the Web POS Terminal window that allows to see information about all Cash Ups and print the Cash Up report.

• Model properly in dictionary payment method searchkeys: OBPOS_ prefix, OBPOS_cash.payment method, ...

• In a multi-currency environment the system accepts cash in different currencies displaying the pending amount and the change in the currency selected.

• Ability to specify the customer category when creating a new customer using Web POS.

• Now can be configured at store level more than one waherhouse so the old warehouse selector at store level must be removed and move this value using a config script to the warehouses tab.

• Includes translation of the latest versions of all Retail modules

• Security configuration option (at role level) that allows to revoke access to the backend for corresponding users (by default access to the backend is granted). It for example enables to have Web POS users that do not have access to Openbravo backend.

• Module passed Element PS certification tests

• Allow / disallow users to access particular POS terminals

• Functionality in which the seller reserves an item for a consumer until the consumer completes all the payments necessary to pay for that item

• Ability to work with fiscal printers

• Ability to enter payment amount as a percentage (% key) of a total

• Show payments made and thier dates in the ticket area of the Web POS

• Ability to run Web POS on smartphones

• Ability to select sales representative who has done the order

• Manage all the cycle since work order is

         created in Web POS with prescription data, then work received
         and being done in the lab or third party, including purchase
         order when necessary, and sent back to the store for delivery
         to customer

• Ability to import products with specific characteristics

• Ability to enter the prescription in the SO

• Ability to select several open tickets and pay them at once

• Ability to have several pictures per product

• Ability to define charactheristics for products

• Ability to search and edit

• Ability to search by product characteristics

• Functionality to access terminal configurations only in selected physical devices.

• When returning goods in a retail store. It must be an option to generate a credit note to give to the customer. This credit note can be used by the customer to buy goods in the future.

• Integration with new payment provider companies. Focus in ability to integrate with mobile devices and worldwide operations.

• Funtionality to display the customer purchase history for a selected customer. This functionality will be available only when online.

• User interface help for counting coins and notes during the cash up process

• Functionality to manage products with different attributes, size, color, ... with different prices, barcode, ... by attribute.

• Implementation of replenishment strategies by store.

• Implementation of replenishment strategies by warehouse.

• Reporting, charts, and balanced score cards, retail oriented

• Functionalty to sell products from warehouses following a FIFO strategy

• Ability to send tickets created in the Web POS.

• Workspaces for POS terminals, including widgets, reports, charts, ...

• Ability to define the maximum stock of a product for the purchasing plan

• Main are:
  • User interface in the Work Requirement window
  • Ability to create intermediate products on the fly
  • Ability to inherit attributes.

• When a new member is signed up, a contract is created including the spaces that the member will occupy and/or the services the member will consume.

This contract will be used to create invoices according to the regular billing schedule.

• We define a resource as any bookable item in the system. In a coworking space scenario, examples of resources are conference rooms, meeting rooms, desks, etc...

Managing resources in the system, and making reservations, is a must functionality in a coworking space.

• Coworking User Guide - Documentation

• CWS v1.0 package

• Simplified worspace to host widgets for portal members and a new configuration in the Role window to create portal member roles

• A front end portal for Members where there can be general information, news, events and calendars and where the user is able to register and manage their own information, book any available asset, register to an event or buy products that are sold.

• Authorize.Net payment gateway is integrated in backend (pull ACH, not present dredit card) and portal (push ACH, present credit card)

• Members, employees and staff are granted access to the coworking space facilities through either physical keys or other types of access cards (FOBs). The system will permit the management of those items as returnable products (including purchase, traking and returning).

• Members Portal will allow members in coworking spaces to manage their own data, and perform some othe operations, such book resources.

• The application will enable full lead lifecycle management. The completion of a lead qualification process should allow users to automatically initiate the creation of new member contract.

• Pricing for rental spaces is typically offered on a scale basis where the price is determined not only by the type of space (the service being rented) but also the quantity rented and the notice period.

• Different kind of events take place in coworking spaces. These events require coordination, planning, communication and a ticket selling platform.

• Reach and maintain number of the defects at the level of <100

• Deliver a set of How To articles

• This part of the user guide needs to be improved: the overall concept, how payment configuration impacts on payment managment and payment accounting. Put examples.

• Process should be explained in the Financial Management Introduction.

Details in the corresponding windows.

• Document Accruals and Deferrals for products

• General Setup documentation improvement in the Quick Config. Guide and in the User Guide. For additional details, visit the Documentation Backlog. Rows 27 and 28

Ready for review 15 Oct 2012

• Accounting Config documentation improvement in the Quick Config. Guide and in the User Guide. For additional details visit the Documenation Backlog. Rows 31 and 32

Ready for review 5 Nov 2012

• Review and improve the Quick Config. Guide content. For additional details visit the Documentation Backlog Row 34

Ready for review 13 Nov 2012

• Rename Accounting Schema as General Ledger

Ready for review 19 Nov 2012

• Review the payables and receivables section, mainly the Financial Account window. Review also the Quick Config. Guide. For additional details visit the Documentation Backlog. Rows 36 and 37

Ready for review 4 Dec 2012

• Enable fiscal calendar to support 13th period. 13th period is an adjustment period, created in the last day of a fiscal year, to be used for creation of manual journal entries to the required adjustments before end year closing.

• 2013 Documentation Plan

• Partner portal review and clean-up.

There is nothing about the new user guide and quick guide (refer to wiki). Comunication of the changes to the Partners in collaboration with Josep

• How to document “Vertical” solutions such as Openbravo for Retail or Openbravo CoWorking spaces

- Research - Implementation as a How To article - Update wiki and partner portal.

Ready for review

Ready for review April 18th, 2013

Would like to add a "real" example. To be planned as it depends on GPS input

• How to initilize the financial balances in Openbravo.

How to article document to create in collaboration with the suport/GPS/functional teams

• Fine tune wiki search

• How to edit the wiki? How to document in the Release Notes new features implemented across OB