Submitting to third party application and post back creating refresh issue

Question

Hi,
I am doing a web application in which I need to hit a third party application from a view and come back to the same view if the third party sends a response back.
For this I am getting the adfCtrlState and submitting it as a postbackurl for the third party.
After coming back to the same view from the third party, I need to go to the next activity in the taskflow without any user interaction.
I am using the following code to find the next activity
<af:commandButton text="AutoSubmit" id="cb2"
action="processResponse"
binding="#{pageFlowScope.responseBean.braodCastAction}"
visible="false"/>
In the responseBean : I am using the RichCommandButton to broadcast event
RichCommandButton myEvent;
public RichCommandButton getMyEvent(){
if(conditions satisfied){
myEvent.broadcast(new ActionEvent(myEvent));
The above code is executing the action(processResponse) specified in the commandButton.
But it is not able to find the next activity in the taskflow, if a hit F5(refresh) it is rendering the next view in the taskflow.
My primary requirement is to execute or render the next method call activity or view after coming back from the third party application without user interaction. Is there any other way to go to the next activity without broadcasting the event ?*
Thanks
Mohan.

Answer 1

Hi there
I see some flaws with that.
J41 wrote:
 It would act somewhat like an LMS where users could post their dev files on a network share.
Dev files need to always be local. Placing on a network share for the purposes of using RoboHelp to compile or generate is risky business and may explode in your face. LMS to me means Learning Management System. Those are typically used for eLearning. RoboHelp does help systems. Captivate does eLearning. So you are losing me with your LMS reference.
When ready to review with the customer, the would use the registration tool to push the project to preview.
I'm lost. What "registration tool" are you even referring to here? Or is this what you are planning on creating and that's what you are choosing to call it?
The app would call the RH command prompt using a server side technology, in my case .NET, and supply the necessary arguments and push the generated project to preview.
There is no "preview" of projects. Preview of individual topics, sure. But not for a project. There is only compile or generate to create the final output.
Once it had been reviewed and ready, then the user could push to production.
Sounds like what one might typically accomplish using RoboHelp in a typical development cycle. You edit content on the local hard drive. If a review is needed, you compile or generate the content and place the output on a server. After approval is complete the content is then copied to the production server.
Sure sounds like you are attempting to reinvent the wheel in many situations here.
Cheers... Rick
Helpful and Handy Links
RoboHelp Wish Form/Bug Reporting Form
Begin learning RoboHelp HTML 7 or 8 within the day - $24.95!
Adobe Certified RoboHelp HTML Training
SorcerStone Blog
RoboHelp eBooks