| Topics | Notes | AI SIG status | JIRA ticket |
|---|
| Modals: movable | - Modals or other popups need to move
- should not be fixed in place on the screen
- In various Apps functional Modals be moved out of the way while in use but at the same time cover over information that is needed while using the Modal.
- Modals need to be able to be moved.
- Not all modals are "Look-up" modals, some are "Fill-out" modals and so info is on the screen now hidden
- e.g.: in the Receiving App, the Receiving Note.
- Additionally, I often want to copy and then paste into the pop-up modal info from the screen behind, but no longer can.
- I would hope that if I can move it out of the way, I then would also be able to copy off it to pate into fields in the popup
- my demo example would get be when I am creating a piece in the Receiving App.
| |
|
|---|
| Modals: size | - Ability to change size of modal
- it would be helpful to be able to change the size of the popup
- e.g. enlarge to view more lines / more information
|
|
|
|---|
| Modals: Warning modals | - Warning Modals needed when deleting any record in any App when it is the source of truth for other records
- To avoid dead links, or even disappearing records and information, when deleting a record to which other Apps link or connect or downstream display information regarding, a warning modal should appear informing the user that if they confirm the deletion then the following other records in such-and-such apps will be unlinked or deleted as well
|
|
|
|---|
| Modals: Shortcut for ENTER key | - In the User Management SIG today (6/29/2022) it was discussed that it would be convenient to have the ENTER key perform the Primary button function on a modal.
| | | Jira Legacy |
|---|
| server | System JIRA |
|---|
| columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | STCOM-1041 |
|---|
|
|
|---|
Wildcards: standardized | - Wildcards (truncation marks) need to be standardized across all Apps
- Currently depending on what App either % or * is the truncation mark to use.
|
|
|
|---|
Date formatting | - How Dates are formatted and entered
|
|
|
|---|
Spaces handling | - Example: In Inventory 'extra' spaces are eliminated,
- while in Orders they can exist and impact search & retrieval:
- From Orders: Newspaper of extra spaces becomes Newspaper of extra spaces in Inventory.
- If you copy Newspaper of extra spaces from Inventory to search in Orders by Orders Lines, you retrieve nothing, until you add the spaces back
|
|
|
|---|
| Search: lowercase vs. cap | - Use of lowercase vs CAP re: searching not consistent,
- barcode example (in my case, B891369-MHC vs. B891369-mhc) or
- KW in Inventory searching for something that is an Identifier for example, in my case (MHeb* works but not (MHEB* ... ... different in other apps
|
|
|
|---|