Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | ||||||||
| 0051386 | ||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
| feature request | [POS2] POS | major | have not tried | 2023-01-17 12:37 | 2023-02-02 12:20 | |||
| Reporter | meriem_azaf | View Status | public | |||||
| Assigned To | meriem_azaf | |||||||
| Priority | normal | Resolution | fixed | Fixed in Version | ||||
| Status | closed | Fix in branch | Fixed in SCM revision | |||||
| Projection | none | ETA | none | Target Version | ||||
| OS | Any | Database | Any | Java version | ||||
| OS Version | Database version | Ant version | ||||||
| Product Version | SCM revision | |||||||
| Merge Request Status | approved | |||||||
| Review Assigned To | ||||||||
| OBNetwork customer | No | |||||||
| Support ticket | ||||||||
| Regression level | ||||||||
| Regression date | ||||||||
| Regression introduced in release | ||||||||
| Regression introduced by commit | ||||||||
| Triggers an Emergency Pack | No | |||||||
| Summary | 0051386: Touchpoint type availability in Schemas | |||||||
| Description | In this project we will add the ability to restrict the availability of the schemas of an organization depending on the touchpoint type. -> In organization window -> Tab schemas a new field (label: Terminal type availability, Type: combo) will be added with three options: 1- All. 2- Only those defined. 3- All excluding defined. -> Connected with “Schemas” tab a new Tab (3th level) will be added (Name. Terminal type availability). In this tab user will be able to select terminal types which are defined on its organization or in organizations above the current organization. Registers on this tab will mean different things (inclusion or exclusion) based on the value of the combo explained above. Note: if value selected in the combo is ALL → Display logic should be added to hide subtab “Terminal type availability“ when ALL is selected in parent tab | |||||||
| Steps To Reproduce | - | |||||||
| Tags | No tags attached. | |||||||
| Attached Files | ||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
||||||||
|
||||||||
 Relationships |
|
Notes |
|
|
(0145497) hgbot (developer) 2023-01-17 14:24 |
Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/merge_requests/1469 [^] |
|
(0145979) hgbot (developer) 2023-01-29 20:08 |
Repository: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2 [^] Changeset: dc873d1db32ae684c00ef70a299da59071d220de Author: Meriem Azaf <meriem.azaf@openbravo.com> Date: 29-01-2023 20:07:33 URL: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/commit/dc873d1db32ae684c00ef70a299da59071d220de [^] FR-51386: Touchpoint type availability in Schemas In this project we will add the ability to restrict the availability of the schemas of an organization depending on the touchpoint type. - Create a new table "obpos2_org_schema_touchtype". - Create a new column "touchpoint_Type_Selection" in the table "obpos2_org_schema". - Create a new field/element "terminal type availability" on "the Organization -> Schema tab" as a reference list "All/Included/Excluded List". - Create a new tab "touchpoint type" under "Organization -> Schema". - Update the "schema.java" to only the relevant schemas are sent to the frontend according to the terminal type. --- A src-db/database/model/tables/OBPOS2_ORG_SCHEMA_TOUCHTYPE.xml M src-db/database/model/tables/OBPOS2_ORG_SCHEMA.xml M src-db/database/sourcedata/AD_COLUMN.xml M src-db/database/sourcedata/AD_ELEMENT.xml M src-db/database/sourcedata/AD_FIELD.xml M src-db/database/sourcedata/AD_TAB.xml M src-db/database/sourcedata/AD_TABLE.xml M src/org/openbravo/pos2/term/Schema.java --- |
|
(0145980) hgbot (developer) 2023-01-29 20:08 |
Merge request merged: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/merge_requests/1469 [^] |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2023-01-17 12:37 | meriem_azaf | New Issue | |
| 2023-01-17 12:37 | meriem_azaf | Assigned To | => Retail |
| 2023-01-17 12:37 | meriem_azaf | OBNetwork customer | => No |
| 2023-01-17 12:37 | meriem_azaf | Triggers an Emergency Pack | => No |
| 2023-01-17 12:37 | meriem_azaf | Assigned To | Retail => meriem_azaf |
| 2023-01-17 12:37 | meriem_azaf | Status | new => scheduled |
| 2023-01-17 14:24 | hgbot | Merge Request Status | => open |
| 2023-01-17 14:24 | hgbot | Note Added: 0145497 | |
| 2023-01-29 20:03 | hgbot | Merge Request Status | open => approved |
| 2023-01-29 20:08 | hgbot | Note Added: 0145979 | |
| 2023-01-29 20:08 | hgbot | Note Added: 0145980 | |
| 2023-01-30 11:09 | guilleaer | Status | scheduled => acknowledged |
| 2023-01-30 11:09 | guilleaer | Status | acknowledged => scheduled |
| 2023-02-02 12:20 | guilleaer | Status | scheduled => resolved |
| 2023-02-02 12:20 | guilleaer | Resolution | open => fixed |
| 2023-02-02 12:20 | guilleaer | Status | resolved => closed |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |