Joe, My personal experience is that you can utilize the field in the run-process, without the field existing on the form because it's implicitly already there, on a regular form at least....try it on a display only form, or something similar, you are likely to have a problem.
On Mon, Feb 23, 2015 at 10:57 AM, Joe D'Souza <jdso...@shyle.net> wrote: > ** > > In the past (way back a few versions during the AR Admin Tool days) in > order to use that run process in conjunction with the results list field > (or any other AR workflow action for that matter) you had to create a > hidden table field with a 1020 ID to allow you to associate workflow to > that ID. It was like a place holder field for 1020 to use it in workflow. > > > > I’m not sure if they have changed that now and allow you to do so without > the developer studio complaining that the field does not exist. > > > > Just thought I would throw that out in case you get a similar error with > the Dev Studio with the recent versions too. > > > > Cheers > > > > Joe > > > ------------------------------ > > *From:* Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] *On Behalf Of *LJ LongWing > *Sent:* Monday, February 23, 2015 10:58 AM > *To:* arslist@ARSLIST.ORG > *Subject:* Re: F5 equivalent via workflow > > > > ** > > Dave, do a PERFORM-ACTION-TABLE-REFRESH (or equivalent actual run-process > name) on field 1020, which is the field for 'Result List', this effectively > performs an 'F5' action. > > > > On Mon, Feb 23, 2015 at 8:40 AM, Dave Barber <daddy.bar...@gmail.com> > wrote: > > ** > > This was a query sent over to me from a colleague. Personally not sure > how to handle it (I gave up when I saw macro - we're moving to 8.1 at some > point, ain't no client side macros no more). > > ====================================================== > > User Tool Version: 7.6.04 SP4 > > Server Version: 7.6.04 SP4 > > > > Bespoke Incident Application. > > > > I want to be able to refresh an incident from the Incident form itself, > using workflow, in the same way that hitting F5 refreshes the incident. > > > > The form is in *Modify* mode. > > > > *Commit Changes* is not suitable since it does not appear to have the > same effect as simply clicking F5. > > > > Opening a new window for the same entryID and closing the old one is not > suitable due to problematic interaction with a macro query and rsults list > handling. > > > > From an *Active Link* attached to a button, I have tried using *Run > Process* with PERFORM-ACTION-GET-ENTRY (Record ID is the entryID, field > ID 1). PERFORM-ACTION-GET-ENTRY returns no value and merely returns an > anonymous failure if used it with Set Fields and $PROCESS$. It is also only > run on an AL in the client, so requires no “@@:” token. I have tried these > variants : > > > > PERFORM-ACTION-GET-ENTRY “$Record ID$” > > PERFORM-ACTION-GET-ENTRY $Record ID$ > > PERFORM-ACTION-GET-ENTRY <hard coded entry ID> > > PERFORM-ACTION-GET-ENTRY “<hard coded entry ID>” > > > > In all cases, I get an error window: > > > > ====================================================== > > Problem: > > > > The following specific error(s) occurred when executing > > PERFORM-ACTION-GET-ENTRY “$1$” *(or $1$, <hard coded entry ID>, “<hard > coded entry ID>”* *depending on the call I am trying)* > > > > Hint: > > > > Press Details to display the error message > > > > Details: > > The system cannot find the file specified. > > ====================================================== > > > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > > > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > _ARSlist: "Where the Answers Are" and have been for 20 years_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
