#PROJECT HEARTBEAT UPDATE#
#PROJECT HEARTBEAT REGISTRATION#

Members will interact with the reporting functionality of the heartbeat feature, generating Openbravo usage reports. Openbravo Strategic Board member – A member of the Openbravo Strategic Board. The System Administrator is the person responsible for enabling, disabling and configuring the heartbeat functionality. System Administrator – The Administrator of the customer's Openbravo instance.

#PROJECT HEARTBEAT REGISTRATION#

Registration information – Contact information and Company description provided by an Openbravo customer to enable communication between the customer and Openbravo Support Services.įunctional Requirements User roles & profiles

#PROJECT HEARTBEAT UPDATE#

Update information – The information sent back to a customer identifying any system updates that may be available for the customer's Openbravo instance. System information – The environment and installation specific information of a customer's Openbravo instance that is to be collected and transmitted to Openbravo. Heartbeat – The name given to the process periodically collecting Openbravo instance information and sending the information to Openbravo for analysis.

References Design Considerations Assumptions Dependencies Constraints Glossary System information is stored in a database, and update information is returned to the client. The information is then stored in a database.Ĥ. Periodically collects and securely sends the system information to the Openbravo servers. The user is prompted with a configuration window asking to enable, disable or postpone the heartbeat process.Ģ. This client registration, whilst occurring in the same initialisation process (as the heartbeat initialisation), is not considered part of the heartbeat process.īelow is a diagram outlining the scope of phase 1 of the heartbeat project:ġ.

The information gathered by this feature will never be used for commercial purposes.Ĭustomers may also register for Openbravo Support Services by providing contact information. Available updates might may include, for example, Operating System updates, Database updates and Openbravo code. To entice customers to enable the heartbeat feature, Openbravo will offer, for heartbeat enabled Openbravo installations, system specific configuration and component update information, sent automatically to the customer. This data will then be used to generate detailed reports clearly identifying where and how the Openbravo product is being utilised. The Openbravo heartbeat will periodically gather and send data about the Openbravo installation back to a service on Openbravo's infrastructure. The intention of the heartbeat project is to gather information from installed Openbravo instances in order to more accurately analyse in what capacity it is actually being utilised worldwide. This is not a true indication of project activity, as the number of downloads does not accurately reflect in what capacity Openbravo is actually being used. Heartbeat - Functional Specifications OverviewĬurrently the only means available to track the activity of Openbravo is by Pop-up window to launch Registration configuration Pop-up window to launch Heartbeat configuration 1.4.4 Functional requirements based on business processes.

1 Heartbeat - Functional Specifications.

Project heartbeat