I want to have the AppSearch action run in both UI and Exec sequence for some searching purposes. So I've placed a condition of '1' in both instances of the action. However, when I look at my logfile I see that the AppSearch action in the Exec sequence won't run because the action was already run on the client side. This used to work in ISWI 2.02.
Just as a test however I put a condition of APPS_TEST on the AppSearch action in the UI sequence.
I would expect the AppSearch action in the UI sequence to be skipped and this would cause the AppSearch action in the Exec sequence to run but when I look in my log file it says: Skipping action: AppSearch (condition is false)
But then further down in the log file, the other AppSearch in the Exec sequence says: Skipping AppSearch action: already done on client side.
What the heck is going on??
Has anyone else experienced this??
My reading of the MSI Help Library page "Custom Action Execution Scheduling Options" suggests to me that AppSearch's having been encountered in the UI sequence was enough to suppress its running in the Execute sequence, even though the condition failed. The Execute sequence version of it would run only if the UI sequence didn't, as in a silent installation.
I did another test where I deleted the AppSearch action from the UI sequence and I still got the same results where the AppSearch action in the Exec sequence would not run because it said that it already ran in the UI sequence.
But regardless, this all used to work in ISWI 2.02, where I was able to force AppSearch to run in both sequences.