Expense management tutorial error

Question

I have completed all the steps of expense management tutorial. but when I try to run the process using the start engine, I am getting the following error.
Error: The project publication has failed. Reason:'_ConfirmReceipts' is not a member of 'Feugo_AutoGen_Screenflows_'..
I have redone this example 3,4 times from the scratch.still this same error persists. What am I missing . Please help.

Answer 1

There were two errors in your project that showed up in the Problems tab. I put out the fixed version of your project on http://www.4shared.com/file/xPCET82f/ExpenseManagementFix.html
You followed the instructions in the tutorial and were bitten by a very poor practice that it recommends. I thought I'd corrected this in the errata that I sent you, but I'm must be mistaken. Both errors were caused by the argument mapping you did in the "Confirm Receipts" task in the "Confirm Receipts" Screenflow. One of the errors was
"Expressions can only be used on the right side of an assignment in argument mappings. The current invalid expression is: action located in Activity ConfirmReceipts"I first double clicked the description of the error. This took me to the Confirm Receipts screenflow. I right mouse clicked the "Confirm Receipts" task -> "Main Task" -> "Argument Mappings". Note that on the left of this dialog there are two mapping ("ConfirmReceiptsIn" and "ConfirmReceiptsOut"). Click the outgoing argument mapping called "ConfirmReceiptsOut". Once this was clicked, I saw the two mappings that the tutorial has you enter. What the tutorial recommends is a disasterously poor practice so I removed both of these and the errors in your project went away.
Your Confirm Receipts screenflow is now enhanced to work the way the way it should work with a cancel button. Added is a new Cancel task where the action variable is set to CANCEL. Note the new conditional transition going to it with the transition name of "cancel" the name of the button on your presentation.
Bottom line, ignore the screenflow argument mapping the tutorial has you doing for the Interactive Component Call. Argument mapping is done in Begin, End and where Interactive activities invoke screenflows and where processes invoke subprocesses. Do not change the default argument mapping in Interactive activities.
Dan