optional applications called "plugins" that extend basic functionality and is the main way to add custom logic to OFBiz. 1.2. Components The basic unit in OFBiz is called "component". A component is at control servlet for each OFBiz component is defined in controller.xml under the webapp folder. The main configuration for routing happens in controller.xml. The purpose of this file is to map requests to loadJWT() Ajax function which in turn calls the CommonEvents::loadJWT method through the common controller. 4. The CommonEvents::loadJWT method uses the calling webapp name to retrieve the userLoginId

optional applications called "plugins" that extend basic functionality and is the main way to add custom logic to OFBiz. 1.2. Components The basic unit in OFBiz is called "component". A component is at control servlet for each OFBiz component is defined in controller.xml under the webapp folder. The main configuration for routing happens in controller.xml. The purpose of this file is to map requests to

optional applications called "plugins" that extend basic functionality and is the main way to add custom logic to OFBiz. 1.2. Components The basic unit in OFBiz is called "component". A component is at control servlet for each OFBiz component is defined in controller.xml under the webapp folder. The main configuration for routing happens in controller.xml. The purpose of this file is to map requests to loadJWT() Ajax function which in turn calls the CommonEvents::loadJWT method through the common controller. 4. The CommonEvents::loadJWT method uses the calling webapp name to retrieve the userLoginId

optional applications called "plugins" that extend basic functionality and is the main way to add custom logic to OFBiz. 1.2. Components The basic unit in OFBiz is called "component". A component is at control servlet for each OFBiz component is defined in controller.xml under the webapp folder. The main configuration for routing happens in controller.xml. The purpose of this file is to map requests to loadJWT() Ajax function which in turn calls the CommonEvents::loadJWT method through the common controller. 4. The CommonEvents::loadJWT method uses the calling webapp name to retrieve the userLoginId

optional applications called "plugins" that extend basic functionality and is the main way to add custom logic to OFBiz. 1.2. Components The basic unit in OFBiz is called "component". A component is at control servlet for each OFBiz component is defined in controller.xml under the webapp folder. The main configuration for routing happens in controller.xml. The purpose of this file is to map requests to loadJWT() Ajax function which in turn calls the CommonEvents::loadJWT method through the common controller. 4. The CommonEvents::loadJWT method uses the calling webapp name to retrieve the userLoginId

optional applications called "plugins" that extend basic functionality and is the main way to add custom logic to OFBiz. 1.2. Components The basic unit in OFBiz is called "component". A component is at control servlet for each OFBiz component is defined in controller.xml under the webapp folder. The main configuration for routing happens in controller.xml. The purpose of this file is to map requests to loadJWT() Ajax function which in turn calls the CommonEvents::loadJWT method through the common controller. 4. The CommonEvents::loadJWT method uses the calling webapp name to retrieve the userLoginId

Framework The lowest or most foundational part of Apache OFBiz is a classical web MVC (Model View Controller) framework. This part of the system is designed for basic routing of web requests and may be considered Settings: • Chart of Accounts - a comprehensive master template for a complete chart of accounts. • Custom Time Periods - a master list to display or setup financial periods • Costs - a master list of any global template before they can be assigned to be used at the organisation level (e.g. Company) Custom Time Periods Time periods are a defined period of time (usually a month, quarter or year) that is

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 9.9.2. Custom Time Periods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Framework The lowest or most foundational part of Apache OFBiz is a classical web MVC (Model View Controller) framework. This part of the system is designed for basic routing of web requests and may be considered emails which the store would send to customers. The actual email services are either mounted in the controller, such as the order confirmation email, or from scheduled services, such as back order notifications

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 8.9.2. Custom Time Periods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Framework The lowest or most foundational part of Apache OFBiz is a classical web MVC (Model View Controller) framework. This part of the system is designed for basic routing of web requests and may be considered emails which the store would send to customers. The actual email services are either mounted in the controller, such as the order confirmation email, or from scheduled services, such as back order notifications

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 8.9.2. Custom Time Periods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Framework The lowest or most foundational part of Apache OFBiz is a classical web MVC (Model View Controller) framework. This part of the system is designed for basic routing of web requests and may be considered emails which the store would send to customers. The actual email services are either mounted in the controller, such as the order confirmation email, or from scheduled services, such as back order notifications