PICK FROM problem

ask180

I have a query which uses a search parameter form.

I execute the query using PICK.

The application displays a list of matching search results.

All good.

However, the business scenario is that none of the search results may be appropriate, so the user has to create a new row in the business object.

PICK insists that you pick one. DISPLAY doesn't seem to let the user pick any. I can't test SEARCH COUNT, because there are matches, but none of them are appropriate.

Any thoughts on how to resolve this scenario?

RocketRod

How about storing a record in the BO that says something like:

"Add new value"

Make the description something so that it always appears at the top of the pick list. Change your pick query to always include this record. Then in your process check value of picked item and if it is add new value then do something.

Cheers Rod

ask180

Rod, thanks for the suggestion. I'll give it a go. My main concern will be to ensure the user can't filter out the 'Add new value' option.

Back to the original issue, I'm wondering whether I'm looking at the problem the wrong way. Surely it would be a common scenario in most applications that (a) you run a search (b) get no results back, so you want to do an add.

Why doesn't AwareIM let you configure operations from a PICK list?

RocketRod

Mmm, in the back of my mind I remember reading somewhere that there is now a function or command that tells you the count of the number of records in context. If you know this then its quite straight forward. Maybe someone knows of this or support can help?

Cheers Rod

ask180

I'll have a look through the functions in the back of the user guide to seen if I can find the one you are referring to.

Powerm

Try to put it the other way: first have the system look if there is no appropriate results according to your criteria, than propose to the user to pick something .

An other easier way if to display a form launched from a Process displaying :

a query showing the pick list
a process for creating a new object

ask180

Thanks for the suggestions. My problem is I can't see in the user guide the method to implement your suggestions.

I do have a query that lists the pick list. In this query, I have configured an operation to start a process to create a new object. The problem is that the button does NOT display anywhere on the picklist form. I have set below the list, above the list etc, but it seems that when you run a query using PICK FROM, the configured operations are disabled.

This is very frustrating. I would appreciate an example of how to get operations configured in a query to show on a PICK FROM list.

Powerm

Processes are disabled when you launch a pop-up. Regarding your query for the PICK FROM you can place on any Business Object you wish and create a process showing that BO. This process option can be placed on a Menu or within a Form of any BO.

ask180

Thanks for the advice that you cannot run processes from pop-ups. Makes sense. I'll follow your tip about displaying the query - that approach should work.

Thanks again.

ask180

I have implemented the scenario using DISPLAY instead of PICK FROM, and it works perfectly, except for one thing. On my home page, I have some standard tabs. As soon as the DISPLAY action runs, these home page tabs disappear (even though I checked 'always show').

Is there any way to direct a DISPLAY into a new tab, rather than trash the home page? Note that I need to run the display from a form, so the RUN QUERY menu approach doesn't apply.

Jaymer

(per my suggestion on your other Q about this, I think you've come to the same result that I said)

sorry... still researching this. i've read this thread about 5 times. it all makes sense EXCEPT one thing:
On your FORM where you put a button that starts the People search, why did you have to Start a Process that did
"DISPLAY queryname"

when the button could have just done "Run a Query queryname"

I've tried both and the resulting query seems equivalent.
On both, there's an option for OUTPUT, so you could select New Tab.

I guess the answer is that in the older version you were on in 2014, something was different than now. Thats one minor annoyance with looking up forum posts that are a version or two out of date.