Most Powerful Open Source ERP

Latest ERP5 Documents

OfficeJS Iodide: Ubiquitous Data Science Notebooks for Business and Education

Iodide and Pyodide have brought a standard notebook application to OfficeJS that can be used for business reporting, research and education. They support data science libraries such as NumPy, Pandas, Matplotlib, Plotly, etc. and soon scikit-learn. OfficeJS Iodide notebooks can be used offline or online on any modern HTML5 web browser such as Firefox or Chrome. Thanks to JIO, notebooks can be synchronised with Dropbox, WebDAV, ERP5 and any other storage supported by a JIO plugin. Iodide notebooks can also be embedded through RenderJS into any business application. The dream of ubiquitous data sciences at no infrastructure cost has come to a reality.
0 comment | Share: Facebook logo Twitter Logo |

HowToBuildPyodide

0 comment | Share: Facebook logo Twitter Logo |

HowTo Upload OfficeJS Application

How to showing step to upload application on officejs server type.
0 comment | Share: Facebook logo Twitter Logo |

Business Template Specification

ERP5 Design Specification of Business Template and Commit Tool and how they interact with each other.
0 comment | Share: Facebook logo Twitter Logo |

Guideline Include Module Base Categories In Business Template

They will not be created automatically.
0 comment | Share: Facebook logo Twitter Logo |

How To Update ERP5 Instance

How to showing steps to update an existing erp5 instance
0 comment | Share: Facebook logo Twitter Logo |

How To Use Commit From ERP5

Document showing how to work with business templates using git from inside ERP5.
0 comment | Share: Facebook logo Twitter Logo |

Guideline Semantic Field Should Be Used In Favor Of Technical Field

Semantic fields are more specific and descriptive.
0 comment | Share: Facebook logo Twitter Logo |

Guideline Use Glossary Defined Prefix For Specific Semantics

Field libraries should be consistent within.
0 comment | Share: Facebook logo Twitter Logo |

Guideline Proxy Fields Should Share Semantics

To keep consistency across fields.
0 comment | Share: Facebook logo Twitter Logo |

Guideline Only Use Proxy Fields In Non Field Library Forms

To prevent excessive customisation.
0 comment | Share: Facebook logo Twitter Logo |

Guideline Semantic Field Is Named Using My Prefix, Technical Context And Semantic Name

Differentiate between semantic and technical template fields.
0 comment | Share: Facebook logo Twitter Logo |

Guideline Use My Prefix and Class Name For Template Field Name

To prevent creating multiple technical template fields.
0 comment | Share: Facebook logo Twitter Logo |

Guideline Technical Template Fields Are Defined In Base_viewFieldLibrary

Non semantic fields should not be duplicated.
0 comment | Share: Facebook logo Twitter Logo |

Guideline A Proxy Field Never Links To An External Field Library

Business templates must work standalone.
0 comment | Share: Facebook logo Twitter Logo |

Guideline A Business Template Has Only One Field Library

Field libraries share semantic configuration.
0 comment | Share: Facebook logo Twitter Logo |

Guideline Unset Acquire Local Roles On Document Portal Type Configuration If Applicable

sub and parent document security may differ.
0 comment | Share: Facebook logo Twitter Logo |

Guideline Inside The Roles Tab, Assignor, Assignee, Associate And Auditor Must Be Defined

Follow 5A security model.
0 comment | Share: Facebook logo Twitter Logo |

Guideline Include Module Local Roles In Business Template

They will not be created automatically.
0 comment | Share: Facebook logo Twitter Logo |

Guideline Modify Correct Changelog On Business Template Commits

Differentiate major changes and purpose changelog.
0 comment | Share: Facebook logo Twitter Logo |