The table view does not have the ability to select all processes, but the list view does.
Is this by design or is it a flaw in the system?
[file]9538[/file]
[file]9539[/file]
The table view does not have the ability to select all processes, but the list view does. Is this by design or is it a flaw in the system?
. OneBox production wrote: The table has a checkmark that itself marks all processes on the page, it is located in the table header
Yes, but still there is no way to select on ALL pages from the table?
[quote]
.
OneBox production wrote:
The table has a checkmark that itself marks all processes on the page, it is located in the table header
[/quote]
Yes, but still there is no way to select on ALL pages from the table?
on the first screen, I see only 30 orders, most likely they are all displayed in the table and pages are not needed. If you drop links it will be a little clearer
on the first screen, I see only 30 orders, most likely they are all displayed in the table and pages are not needed. If you drop links it will be a little clearer
. OneBox production wrote: If you drop links it will be a little clearer
above sent links to the table and the list. Pages are not visible in the table and there is no option to select "on all pages"
[quote]
.
OneBox production wrote:
If you drop links it will be a little clearer
[/quote]
above sent links to the table and the list. Pages are not visible in the table and there is no option to select "on all pages"
Yes, I see that it works differently. But I don't understand why the ticket should be closed. The issue is resolved - closed the ticket, do not sieve - do not close.
Yes, I see that it works differently. But I don't understand why the ticket should be closed. The issue is resolved - closed the ticket, do not sieve - do not close.
. OneBox production wrote: Yes, I see that it works differently. But I don't understand why the ticket should be closed. The issue is resolved - closed the ticket, do not sieve - do not close.
so I can't open other tickets))) I have to close the existing ones, because there is still a lot of curvature in the system.
[quote]
.
OneBox production wrote:
Yes, I see that it works differently. But I don't understand why the ticket should be closed. The issue is resolved - closed the ticket, do not sieve - do not close.
[/quote]
so I can't open other tickets))) I have to close the existing ones, because there is still a lot of curvature in the system.
I took this problem for corrections, but just keep in mind that a closed ticket is considered resolved / closed, regardless of what comments are inside. Those. if you closed the task, it may never be viewed later, including the person who communicated with you in the task. It's closed, so everything is ok.
I took this problem for corrections, but just keep in mind that a closed ticket is considered resolved / closed, regardless of what comments are inside. Those. if you closed the task, it may never be viewed later, including the person who communicated with you in the task. It's closed, so everything is ok.
. OneBox production wrote: I took this problem for corrections, but just keep in mind that a closed ticket is considered resolved / closed, regardless of what comments are inside. Those. if you closed the task, it may never be viewed later, including the person who communicated with you in the task. It's closed, so everything is ok.
ok, i'll keep that in mind
[quote]
.
OneBox production wrote:
I took this problem for corrections, but just keep in mind that a closed ticket is considered resolved / closed, regardless of what comments are inside. Those. if you closed the task, it may never be viewed later, including the person who communicated with you in the task. It's closed, so everything is ok.
[/quote]
ok, i'll keep that in mind
Please join the conversation. If you have something to say - please write a comment. You will need a mobile phone and an SMS code for identification to enter.
Log in and comment
Donate
You don't have enough funds in your account Top up