• 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.

• 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.

• 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).

• Phase 2 in new Process with new UI architecture. Parameter Windows are defined in the AD and used for generating a GUI, usually a pop-up window, to ask the user the values of process parameters. In the current implementation, parameters are associated only to a Process or Report. The definition of the Processes and Reports is made in the same table AD_Process table, and this definition is bloated with too many columns (flags at user level) that is hard to maintain and understand .The goal of this project is to provide a new infrastructure for OB3.

• When filtering by a drop-down list, in case the field has a validation, it should be applied to restrict the possible options

• Named filters (eg. Not complete or recently touched documents)

• Modules should be allowed to add new trees in a clean manner. A table could have more than one tree.

• Improve the ease of editing and visualization of Openbravo trees (menu, chart of accounts, etc.).

• Replace the 2.50 implementation of these references by a new implementation using Openbravo 3 technology

• Openbravo display-logic is a platform mechanism to show/hide fields in a tab depending on a boolean expression. This behaviour applies only to the form view, this project is about to apply it to the grid view (the content should be shown/hidden, but the column will be always present)

• Allow definition of rules at different levels (column, field, others...) for foreign key entity navigation.

• Implement a new reference used for dynamic links. This reference is readonly and composed by two fields (entity and record ID), depending on entity value navigation is done to different entity table. It takes it into account also for identifier display in UI.

• This advanced parameter types are: sorted lists, multiple selection in a list, multiple selection in a selector, option buttons

• Now we still use interstitial popups before process execution which do not serve a purpose. The idea is to get rid of them and execute a process directly when pressing an orange process button. In order to do so, we need also to build the multi-action button type where multiple processes sit beneath the button in a fly-out.

• Ability to define in the Applicaiton Dictionary the buttons shown in a particular tab. This way it will be easy to add or remove buttons in the toolbar

• Sorting by more than one column is very useful. For example: Sorting a sales order grid primarily by business partners, and secondarily you want all the sales order from each partner to be ordered chronologically.

• Filter expressions are very powerful but hard to learn or discover by the user. We need to provide a visual expression builder that does the same but also adds multiple selection and conditions. The Filter Builder is launched from the column header.

• Possibility to view the average or sum of a column.

• Ability to see the content of a collapsed section without the need of expanding in (as one liner with the information, similar to the status bar)

• Ability to bookmark specific documents/records

• Info messages might become annoying for power users so it must be able to dismiss them forever (with a possibility to reset in admin settings). You should also be able just to click on the big icon on the left hand side in the colored message to make it disappear instead of having to reach for the little x close button.

• Highlighting based on conditions set by the user or the system. We can also think of "pinning" rows so they are not affected by column filters.

• At the moment only one document can be processed at a time. It should be possible to select multiple documents and process them at a time, providing that they all have the same document status.

• To assist the user in quickly accessing related windows and learning about the sequence of steps to be taken in order to complete a task, it would be beneficial to define a set of links to related windows (or even external URLs) in certain places in the application. As every company is different, these links must be configurable.

• Similar to what some browsers offer, it should be possible to keep the current tab state. Additionally we can think of more advanced tab functionality such as: Close all tabs/close other tabs/new thread or Drag and drop to re-order them.

• Contextual menus are invoked by a right mouse click on selected cells. Currently "use as filter" and "open on tab"is offered but this can be extended to more admin-like functionality such as linking to translation or related Application Dictionary items.

• 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.

• 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.

• 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

• The xml webservices can be used as a datasource in Excel, the xml should be simplified

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

• Several enhancements: make it easier the maintenance of user accounts, direct login, Google docs as attachments

• Ability to overwrite column properties: default value, is Mandatory field, reference (UI) implementation, validation.

• Note can be a security risk authorization checking on free format HQL can be difficult. Corresponding to the direct link functionality

• Refactor CreateFrom functionality so it is easier to extend/adapt to specific customer needs in a modular manner

• Ability to define ownership of each row/property (so new versions of the same dataset do not overwrite my changes), define dependency between datasets, define expressions instead of static data.

• Ability to execute off-line (eg. scheduled) reports/processes with parameters. The result of the process/report should be sent to the user once it is ready

• Ability to edit (add, modifiy, remove) values by end users. Lists of values used in business logic implementation are not editable. Validation rules (to reuse the same list in different windows) should be easily applicable at user level (for example, rules for return are different for return from customer and return to vendor).

• Enable Export/Import Client utility to deal with large volumes (split the xml files into chunks, support partial loads, etc.)

• Ability to define a list of users to be emailed in case a background process execution fails.

• 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.

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

Contributed by SAIC

• Move the backup functionality from Appliance into the ERP as a module. Appliance also backs up stack files. If we are moving this functionality to ERP then we should be stack agnostic? So we only should talk about owned by ERP files and data? If to take stack into account then it might be better to use OS oriented tools - http://goo.gl/dBLw.

• For professional instances, ability to directly open a ticket from an Openbravo instance. Tickets reported directly from an instance will get all the "instance information" preloaded (version, stack, license, etc.)

• Avoid the local changes issue by allowing the user to export or ignore changes. Ideally the user does not have to worry about local changes, and if exporting is needed, the system will carry this out automatically.

• Visibility on status (validation flow, etc.). Ability to execute ant tasks from the UI. Ability to manage Openbravo db objects through Openbravo UI. Include a diagnostic tool for performance issues in Openbravo that is easy to use. It should include at least a JavaScript benchmark, a disk speed test and a bandwidth test.

• Implement replicate production to testing and vice versa functionality in the ERP. Integrated flow to promote code through the different environments (development, test, production) in a safe and efficient manner

• 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.

• Refactor most of Openbravo business processes so they are by default implemented by the BPM/Workflow engine definition and this way make it easier for consultants to adapt business logic to specific customer requirements.

• Define security settings to move data up and down

• Current Query list widgets only show grids. In order to impress a provide our customers the KPI overview they need, we must offer charts to visualize that data.

• Ability to do changes in the translations provided by a localization pack and package them as part of a module, so updates to the localization pack can be applied without overwritting those changes

• On-line service to translate Openbravo in an efficient manner

• Ability to define, for business information, the original language of the information and translate this information to other languages. Based on this information, provide out-of-the-box functionality to get business information in a language that depends on the context (eg. language of the customer, language of the organization, language of the vendor, etc.)

• 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"

• Ability to modify an existing payment plan for outstanding amounts.

• 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.

• The term analytical accounting is very broad and generally refers to the practice of exploiting accounting information for the purpose of supporting managerial decisions, as opposite as financial, legal or fiscal reporting.

At Openbravo, we prefer to use the term managerial accounting instead of analytical accounting. Openbravo supports managerial accounting thanks to its embedded multi-dimensional accounting store that allows to analyze accounting information based on a number of pre-defined dimensions. Accounting Date Period Natural account Organization Business Partner Product Project Sales Region User Defined Dimension 1 User Defined Dimension 1 Some of these existing dimensions are not fully implemented in openbravo. This project as well aims to fully implement existing dimensions and add new ones as cost centers.

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

• Migrate invoices and orders selector to "Pick & Execute" pattern

• Enhance APRM to support negative credit payments (generation and consumption)

• The "Fiscal Calendar" window should be split into two as "Fiscal Calendar" creation and "Closing Fiscal Year" are two different processes.

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

• Review existing modules and make the necessary changes to port them and get them work

• Refactoring of manual forms ito take advantage of OB3 new platform capabilities.

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

• Review current functionality related to the credit memo invoices as this kind of invoices use positive numbers which makes that reporting need to be always adjusted

• Enhance document sequence engine to ensure that unique and correlative document numbers are used

• Ability to load an initial balance sheet using Initial data load.

• Enhancement of existing reports or development of new ones to allows analytics by taking advantage of:# new OB3 technology (OB3 SmartClient)#OB3 widget capabilities for monitoring purposes#xls and pdf format capabilities. All the reports should also be refactor to ensure they are all exported to xls and pdf format.

• Create a new type of Financial Account together with the required fields associated to this new financial account type. All of the above mean a set of tools related to Credit Card management

• 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.

• This project aims to extend new cost calculation engine to support manufacturing module.

• This project aims to extend new cost calculation engine to support cost adjustments, for example landed costs or invoice price differences.

• LIFO costing method. This project takes advantage of the infrastructure provided by Cost Calculation Engine.

• Specific idetification is a costing method which determines a cost for a particular lot of a product. This project takes advantage of the infrastructure provided by Cost Calculation Engine.

• "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.

• 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

• Reservations feature must be improved as described below:#Orders can reserve material in the warehouse as a way of deliver guarantee#Orders coming later won't be able to use the reserved material#This behaviour will apply to material/items quantity on hand as well as material//items quantity coming from a purchase order or a production request.

• It should be possible to pick goods following:#different rules such as FIFO,LIFO,FEFO#a logic path within the warehouse and besides#It should be possible to pack goods following logistic rules (Localizations, routes)

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

• Stock report should allow filtering by warehouse by taking into account:#existing, reserved and available stock in every warehouses. In fact, it should be possible to choose any attribute to filter on.

• Purchase orders could be created based on sales orders requirements. This process should fulfil the corresponding purchase orders based on the booked sales orders

• Ability to know when I can commit a date to a customer for a specific product depending on the incoming materials, reservations, stock, etc..

• A three way matching should be implemented within procurement/sales management processes, therefore order, receipt/shipment, invoice are always matched against each other.

• The ability to manage different UOMs for a particular produc must be implemented. UOM current functionality must be extended.

• Widgets creation for Whosale distribution

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