I have created the workflow and subsciribed to finishactivity event, in the finishactivity event i am just writing logs.
when the item enters into the workflow, the item got suspended after finishing the first activity. what could be the reason?
As stated by #Quirijn, this is the normal state that a workflow item enters if the code in an automated activity throws an error. In order to diagnose this, please post any automated activity code in your question. It is often also worth inspecting your Windows event logs for hints on what has gone wrong.
Related
The actions worked properly before Google changed the UI and probably some more things at the assistant console. Now the action some times works and some times does not work.
Error messages at the simulator ar for instance:
We're sorry, but something went wrong. Please try again.
No output at all (with intent next / previous)
Sorry, this action is not available in simulation
In this link, #4.49sec speaker talks about some stats. He mentions 'event'.
What exactly event here means in programming terms?
An event in this case basically means a message with some data in it. Later in the video he mentions examples like session data, tracing data etc.
You can put e.g. a user id in it, and an action that the user did, when the event was created. Consumers can then create statistics and react on those events (you could for example create a new movie recommendation, when the user finished watching a movie, and you have ingested that event).
Despite knowing AX enough to get around, it's still thoroughly confusing to me. I have a background in Visual Studio C#, and I could always figure out where a particular segment of code was performing the unexpected behavior, but after a year and a half of AX 2012, it's still a mystery.
There's a legacy system that is not getting POs sent from AX whenever a PO Line is cancelled; my objective is to change AX to guarantee that cancelled lines are sent back to this legacy system.
I need to modify the behavior after PO lines are canceled. I know that users cancel the line by going to Procurement and Sourcing => Common -> Purchase orders => All purchase orders. They Request Change on a PO, then under the Purchase Order Lines section, they navigate to Update Line => Deliver Remainder; doing a Personalize on this form shows that the form is called PurchUpdateRemain, a Foundation form. I hit the Cancel Line button, then confirm the change.
I know that a workflow is triggered on this, and I've completed the whole process of approving the change, but no AIF service is called according to the trace I ran on it, so I'm confused as to what AIF service should handle it.
My question is: How do I find where a file should be sent out in AX? AX does not seem to give any indication as to what logic should be called after a line is cancelled. If I could just see the whole flow of the code like I could in Visual Studio, I could determine where I need to make my change in AX, but I've not yet figured out how I can possibly do that. Any tips? I'm at my wits end here.
A lot of it is just knowledge gained from experience. Pretty much figuring out where to look. Putting a breakpoint in and tracing the code and stepping into methods is often the best way.
Here's a stack trace that shows where the status is changing so you can figure out where to put your code. I cut off line #'s because my code is customized and they wouldn't line up.
Hopefully this won't be too late.
Check the class PurchCancel, in the run method you can see the process of how a purchase order is being cancelled.
Full explanation. I currently have a Listen Activity with 3 branches. First branch is if the document is returned on time. Second is if after X days has passed the user gets an email warning them not to be late. Third branch is after Y days the document is late and the user gets an email stating that the document is late. The listen activity is within a while loop. Now the way I have it set up, I know that the workflow is going to execute the second branch every X days. I'm not quite sure how to set up the workflow so it execute the second branch, then if the document is still not returned, it will execute the third branch.
Any ideas?
Check out the Windows Server AppFabric / Workflow Services Demo - Contoso HR sample application. It does exactly what you are looking for.
Use a Pick activity as it will only execute one of the branches when its condition is matched and cancel the other branches. You can then use a delay to wait the period of time appropriate for the branch action.
I'm developing ASP.NET applications and stuck with a "problem" relating to resubmit behaviour.
I'm controling the re-submit using a counter in form submit event which disables the submit if it's already been posted.
My application is a 3 step workflow and when the 3rd step is shown the transaction was submited from step2 to step 3.
What's my problem? Well... i want to avoid the user to resubmit the data by pressing the F5 or all other possibility. I don't want to disable the key because may be workarounds.
I'm wondering if i can remove the post data in a HTTP module that runs after the render was completed and right before the response is sent to the user.
You can use Post/Redirect/Get "pattern", where when user post data, you redirect it (after processing submitted data) to another page that will response to get. Just like stackoverflow and another sites are doing.
Here's is the Wikipedia page that explains the Post/Redirect/Get Pattern.
Maybe I misunderstood your question/issue but it sounds like you may be making things harder than they have to be. If you are already keeping track of whether or not the form has been submitted before, why cant you just check that flag on the code behind before performing whatever logic you execute on the submit? If it has already been submitted before, just ignore the resubmit event and maybe set an error message.