Updating selected record(s) from Pick one or more

rbross

We currently use a process that allows users to pick one or more records from “QueryName”. These records represent a customer’s available cash coupon discounts for a trip.

The selection works like a standard pick list, except that the selected Cash Coupon records must also be updated to indicate that they have been redeemed. However, AwareIM appears to update the selected records inconsistently—sometimes only some records are updated, and other times none are updated.

Can records selected through a standard pick list be reliably updated as part of the process?

Alternatively, should we replace the standard pick list with a query that has a Panel Operation configured as follows?

Type: Start Process
Applicable to multiple items: Yes

The query would be displayed from the process in place of the standard pick list. Users would select the required Cash Coupon records and then click the button in the upper-left corner of the query.

The Panel Operation would start a process that:

Updates the necessary attributes on each selected Cash Coupon record to indicate that it has been redeemed.
Creates one Discount record from each selected Cash Coupon record.

Thoughts/Suggestions?

nhofkes

I think the alternative with the query and panel operation (applicable to multiple items) is indeed the best approach. Using PICK FROM should also work if you feed the selected records into their own subprocess (do not update the selected records in the same process that has the PICK action, but call a subprocess instead that has the record as input). But if you create a query with the panel operation, you have more control over the user interface. For example, you could add filters to the query which the user can use to first filter the records and then select items from the filtered list.

rbross

nhofkes

That’s what I was thinking I would have to do.

I do have a subprocess that the selected records are passed into, but the update(s) still do not hold all the time.
I think it might be an issue with AwareiM losing context sometimes as well.
There are quite a few other rules in the pick process, nd other subprocesses called, so maybe that has something to do with it. It’s not just a simple pick process.

rbross

nhofkes While this method does work. It changes the UI/UX compared with how a Pick List works. By default, the multi-select query opens in a new tab and doesn’t automatically close after you click Continue. Button locations are different from a standard pick list, and there is no Cancel button. So users will ask why it looks different.

If the display is set to a pop-up window, the pop-up window doesn’t close either, so the user has to close it before returning to the previous form.

I decided to create a stored procedure to update the selected record(s). The SP is one of the last rules to be executed as part of the Pick List process. I pass the necessary parameters, and the record(s) now hold the updates, and the form refreshes as expected.