The commit is actually done by the Perform-Action-Apply,
along with the window close. but again this is just from
observation. The save button, it turns out, fires off an active link
called RSH:GenericSave which ONLY calls the Perform-Action-Apply. which
just runs that command. This is probablly shipped with remedy's change
app. Will the active link still fire if I add a new active link to execute
right after the RSH:GenericSave on the same form? Even if the form
closes? Just seems like a sloppy way to get around this, but if I can't
just replace the RSH:GenericSave with a commit command it will have to
do.
Bob Halstead
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of McKenzie, James J C-E LCMC HQISEC/L3
Sent: Monday, October 02, 2006 2:37 PM
To: arslist@ARSLIST.ORG
Subject: Re: Perform-Action-Apply
Robert:
I would suggest
trying to do the following:
Commit the action
(this maybe caused by the Perform-Action-Apply) and then immediately open the
window in Modify mode where the current user can input more. I'm assuming
one of two things: 1. The user has the ability through either a
Fixed or Float license to modify or 2. The summitter mode is locked so
that users with read licenses can modify only their own summitted actions.
If neither is true, you will have to figure out how to do this.
James
McKenzie
L-3
GSI
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Halstead, Robert
Sent: Monday, October 02, 2006 1:27 PM
To: arslist@ARSLIST.ORG
Subject: Re: Perform-Action-Apply
Well I would like
to keep the window open for one. Basically he's my process. A user
starts to enter a new change request. They can create tasks for that
change request. In that task they can create an outage which is another
form. They first have to save the task before they can create an
outage.The outage form is passed the taskID. The prcess in question
is assigned to the save button on the task form. The problem is, and it's a
small problem, I would like the keep the task form open after they save
it. Currently this only happens when they are modifing an existing
task. On a new task it automatically closes the form. I was just
wondering if I could replace this process with just a commit command instead,
which is why I would like to know what exactly this process does and the
code/actions behind it. In the end, if it's too much work to just replace
the command I won't do it. But I would like to know for future reference
as it could be a viable command to use in future development.
Bob
Halstead
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of McKenzie, James J C-E LCMC HQISEC/L3
Sent: Monday, October 02, 2006 2:07 PM
To: arslist@ARSLIST.ORG
Subject: Re: Perform-Action-Apply
Robert:
I agree with
Carey, do not remove this workflow. However, you may add workflow before
this Active Link. I would look very closely at all of the active links for
this particular form and see if I could move it to a larger sequence number or
bundle your additional workflow into an Active Link Guide and trigger it from
one Active Link.
James
McKenzie
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Halstead, Robert
Sent: Monday, October 02, 2006 12:31 PM
To: arslist@ARSLIST.ORG
Subject: Perform-Action-Apply
From the Documentation:
PERFORM-ACTION-APPLY
Performs the Apply or Save operation on the current window. For Search windows, the search is performed.
Is this the same as just doing a commit? It seems to do a little bit more, like open a message box and close the window. Anyone know what exactly this process does? I am wondering if I can remove this from our Change Request piece so that I may add more workflow afterwards while the window is open.
Bob
Halstead
