The popup screen type of a table variant is not working as I expect it to in a task.
I have a cases screen for which I created a table variant, named cases_menu. The cases_menu variant serves as a screen where users search for their cases. Since there are a lot of cases, the setting ‘Start empty with filter’ is turned on. This works perfectly when accessing the screen from the menu.
However, when using a task that opens the cases_menu variant as a popup, the variant is opened with data. This defeats the purpose of the start empty with filter checkbox.
Table variant with popupTable variant popup with data
Additionally, the task below should open a form of the cases screen, which is assigned and made available in the cases_menu variant, but doesnt work. Now this could be solved with a form detail, but since the user is used to double clicking a case, I would like it that the double click opens an additional popup/zoom.
Kind regards,
Mark
Best answer by Arie V
@Mark Leunissen Your case (pun intended) intrigued me, so I have been playing around a little too.
First of all, I can confirm your findings:
A (Task) Lookup pop-up is indeed not listening to ‘Start empty with filter’
I don’t get the Process flow to Open document as Modal from a (Task) Lookup pop-up working either. For reference I did try with another Process flow in combination with the Extended Property and for instance Activate detail and Go to next row do work.
Second of all, I can get your desired behavior working when doing the following:
Create Task in the Menu which starts a Process flow to perform ‘Open document as Modal’. This does give me an empty Grid:
Create Double-click task which starts another Process flow to perform ‘Open document as Modal’ to open a Form of the searched Grid record on which I performed the double-click:
But the question is if you could create a similar flow for your use case? As somehow you need to work around the Task look-up pop-up where you’d wanted to do this and use Open Document as Modal instead.
@Mark Leunissen On your first remark, I think that ties in with other topics at the Community and might be similar to what is mentioned in this Idea regarding Detail tabs in which it doesn't work:
On your second remark: I'm lacking a bit of necessary context here, but could you try and test for both the screen from the Menu and the Popup? If it's not working for the Popup, that might be related to the Extended PropertyAllowProcessFlowsInLookupDialogs. Could you give it a try after enabling that setting?
That topic is indeed simalar to the problem that I am facing.
The extended property would solve the problem, however it states the following: By default, process flows cannot be executed in a lookup. With this property, a process flow is allowed access to a lookup, provided all process actions are allowed in a lookup. Forbidden process actions are: Manual, Close document, Open document, Activate document, and Zoom in on detail.
Therefore, the process action that I want to use is forbidden.
Is there a specific reason that this action is forbidden?
@Mark Leunissen Basically a Pop-up screen is an overlay over the entire application and as such ‘blocks’ the underlying screen where regularly a Document would be opened/closed/activated.
I double-checked with our Developers and most likely it is not explicitly forbidden at the moment. Therefore, you could test with performing an Open document as Modal from within the Pop-up: it might just work.
But do note that this Extended Property is generic and as such allows all Process Flows to work from within a Lookup pop-up.
@Arie V I tried it in the pop-up screen. There is a short pause which seems like the task is activated, but the flow is not started. So my guess is that the action is halted because of the pop-up screen.
@Mark Leunissen Your case (pun intended) intrigued me, so I have been playing around a little too.
First of all, I can confirm your findings:
A (Task) Lookup pop-up is indeed not listening to ‘Start empty with filter’
I don’t get the Process flow to Open document as Modal from a (Task) Lookup pop-up working either. For reference I did try with another Process flow in combination with the Extended Property and for instance Activate detail and Go to next row do work.
Second of all, I can get your desired behavior working when doing the following:
Create Task in the Menu which starts a Process flow to perform ‘Open document as Modal’. This does give me an empty Grid:
Create Double-click task which starts another Process flow to perform ‘Open document as Modal’ to open a Form of the searched Grid record on which I performed the double-click:
But the question is if you could create a similar flow for your use case? As somehow you need to work around the Task look-up pop-up where you’d wanted to do this and use Open Document as Modal instead.
@Arie V Nice! While I think this would work in other cases (😉), this unfortunately doesn't resolve the issue in my flow. Thanks for thinking with me on this topic!
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
