Changes to HTTP Send configuration not updating

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Inside HTTP Send definition, make a change (ie: change the NameLast field to 
LastName) and save, then make your package production
2. Complete an employee application through the work flow (Applicant -> 
HRManager -> I9Witness -> PayrollSystem) (where the HTTP Send custom logic is 
on the event of I9Witness party completes document).
3.the HTTP Send fires, but changes you made does not come through in the data 
mapping.
4. Return to custom logic screen, and the change shows that it was made.

What is the expected output? What do you see instead?
above

What version of the product are you using? On what operating system?
Hosted eSign-HR.

Upon Request I can provide what I received (I save a copy of the full set of 
pairs received i my system).

Please provide any additional information below.
Example transaction id: 16916092-017f-4f48-b8c4-c72a39f1d2ca

Original issue reported on code.google.com by guyinho...@gmail.com on 10 Sep 2013 at 11:58

[GoogleCodeExporter]

You might want to ask questions in the forums (or contact Yozons support 
directly) before you create an issue to see if there's a resolution of some 
sort.

We checked the transaction you show and "tran details" shows that this was 
started under Package version 4 (old), not version 5, which is your latest 
version at the Production level.

In general, it's tricky to make changes that will reflect in existing 
transactions because you don't want to mess up running transactions. However, 
if nobody is using your system, you can make such a change by REVERTING 
production back to test, updating things, and then putting it back into 
production. This is okay for quick and easy changes, but of course all testing 
should have taken place before it went into production, perhaps with one final 
"test like production" run after putting into production to ensure it's as 
expected.

So in this case, you started the transaction under version 4, so it won't use 
the configuration for version 5.  Only transactions started using version 5 
will make use of that configuration.

Original comment by yoz...@gmail.com on 11 Sep 2013 at 12:17

• Changed state: Invalid