Projects:Extend Navigation Model/Functional Specifications
Contents |
Overview
This project implements to customize the window where a records has to be shown when Open in tab options is opened in a tab where it is used.
Purpose
Currently when Open in tab option is used, or the field label is clicked on a entity field the window defined in the table definition of the entity is used. This means that it is only possible to define a window for the sales flow and another for the Purchase flow. Currently there are several entities that are created from different windows. For example, the Order entity can have entities that are created in the Sales Order window or the Return From Customer. It should be possible that when navigating to an Order be able to define whether it is a Sales Order or a Return to open it on the correct window.
Scope
The scope of this project is to extend the configuration of a table to define the navigation model based on rules. Core entities that are edited on more than one core windows are also updated to define the needed rules to open them on the correct window.
References
Design Considerations
Assumptions
Dependencies
Constraints
Glossary
Functional Requirements
Business process definition
- Ability to define different navigation window for each table
- Navigation rules are ordered by a sequence number.
- Each rule defines the destination window, an HQL whereclause and its expected value.
- It should be possible to define specific rules for a field.
User stories
Functional requirements based on business processes
| Id | Requirement | Importance |
| 1 | Tab Navigation Rules under Field tab. Fields:
| Must have |