@NavneetPanpaliya I do not see any issue in the workflow it looks okay. Just verify that in_TransactionNumber is getting incremented after every transaction. Also @phyogananda Repeat Forever is property of On Element Appear not of Element Exists. I think you wrote it by mistake never mind.
@phyogananda I verified, Repeat Forever is set to false in Process.xaml and @PrankurJoshi it seems in_TransactionNumber is not getting increment and it always showing 1, may be it is due to, workflow is not moving to next page.
After running Dispatcher workflow I am facing one issue that workflow does’t exist after getting all the queue items. I guess this is because there is no data in queue which I verified in orchestrator. I used highlighted queue name as in Config file as well as in Orchestrator. It seems I need to use InHouse_Process4 in both the places as well as in config file (Name/Value). Please correct me if my understanding is wrong.
@NavneetPanpaliya, I’m probably misinterpreting your idea but the Performer part is a separate program. You should have two main programs. After the dispatcher did its work, you run the performer. It’s not being invoked or run automatically. You run it manually
Hey @MGMKLML, I understood this part hence updated my above post but by that time you replied it. Please see my above post and suggest the resolution if you can.
@NavneetPanpaliya, The Name column made so you could address it. It’s like a name of a variable. The Value column is what will be substituted. You have use the Queuename “InHouse_Process4” in both Orchestrator and config because this will allow you to use something like config(“OrchestratorQueueName”).ToString and it will substitute the value.
I also don’t get what you mean by “workflow doesn’t exist”.
Sorry I did typo mistake… I mean to say that “workflow doesn’t exit”, it keep log in to System1 site and moving through work item pages…
Also I am using same config statement which you mentioned above but I understood now that I need to change my queue name to InHouse_Process4 in orchestrator which will resolve my issue…
Clear your queue before you run dispatcher every time. Log message in the start and end of workflow so that you can see where the script is failing in output pane
Hello @PrankurJoshi, @MGMKLML, @phyogananda, @Mahesh_Lakshmipathy, @ClaytonM I am able to get the queue items but still facing one issue where Dispatcher workflow not getting stopped/exit after getting all work items in first run for all pages. Dispatcher workflow running 2 more times for 2nd and 3rd page in my case to get all the 8 work items but it should stop after 1st run as all 8 work items it added to queue in first run itself. Below is the final output I am getting.
I suspect issue should be either in "GetTransactionData’ or “Process” workflow but I believe it should be in “GetTransactionData” workflow. Please correct me if I am wrong. Attached below both the workflows for your reference. Please help let me to resolve this issue.
@PrankurJoshi and @phyogananda, Yes I always clearing queue before running dispatcher but still facing the same issue. Can you please verify my workflows attached in this post and let me know if anything is working in that?
i checked your workflow, but not able to find any problems in that.
Better you start with new Reframework template, and as you already have all the xaml files it wont take much time. this time follow Walkthrough with each details so incase if you made mistake last time you can rectify it.