8000 ideas/concerns selection screen and logging · Issue #31 · tricktresor/cute · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

ideas/concerns selection screen and logging #31

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
OberstVonGatow opened this issue Sep 3, 2020 · 1 comment
Open

ideas/concerns selection screen and logging #31

OberstVonGatow opened this issue Sep 3, 2020 · 1 comment
Labels
design design related discussion discussion and ideas

Comments

@OberstVonGatow
Copy link

I really like the idea of a new sm30 application.
i tried cute but got some dumps and concerns

Bugs:

  • "show" is not working (issue Shortdump CX_SY_REF_IS_INITIAL #30) because selection screen is not called
  • in ZCL_CUTE_AUTHORIZATION S_TABU_NAM is checked on activities that don´t exists (display and delete)

Selection Screen ideas/concerns:

  • because of selected entries, duplicate check is not working
  • why do we need a selection screen anyway?
  • 99% of the time i never used selection in sm30
  • you can use filter and search in alv

Idea:

  • get rid of the selection screen
  • add parameter "Filter" in the program and "Hide Filter in Toolbar" checkbox
  • use DB Table to save Filterdata like LVC_T_FILT (for SET_TABLE_FOR_FIRST_DISPLAY)
  • now you could create transaction codes with parameters use skip first screen and filterparameters to build transactions only for specific data but duplicates would still be checked (because they are only filtered)
  • i know if you use big tables it could be a problem but does anyone really edit such big tables? maybe a separate edit class could be used

Also SLG1 Log would be nice and if fields for logging are in the DB Table to use it ("AEDAT","AENAM" ...)

I think of building a fork with the above mentioned adjustmens but wanted to make a discussion out of my ideas. (and maybe a pull request if i'm successfull)

Regards
Fabian
@tricktresor
Copy link
Collaborator

Hey Fabian!
thanks for your feedback and suggestions.

The idea for having a selection before editing data is to only lock the data for this selection. at least lock only entries not the complete table.

You are right: getting rid of the selection screen might make things easier.

Cheers
~Enno

@tricktresor tricktresor added design design related discussion discussion and ideas labels Sep 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
design design related discussion discussion and ideas
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@OberstVonGatow
0