PartyActivatedEvent not firing as expected

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Set up a package rule to fire when a subsequent party is activated.
2. Run the transaction so the rule should fire (the package party was activated)

What is the expected output? What do you see instead?
The rule should fire, but it is not fired.

Seems to happen for Party created, Party activated and Party transferred.

Original issue reported on code.google.com by yoz...@gmail.com on 29 Jul 2014 at 12:27

[GoogleCodeExporter]

The event logic is not quite correct for the party-specific events as these can 
fire when the current state of the workflow is still "ahead" of these.

EXAMPLE: If on the FirstParty completing the LastDocument in the package, the 
rule to create/activate the next party, SecondParty, takes place while still on 
FirstParty and LastDocument, so the rules to create/activate SecondParty don't 
fire.

Will need to change the runtime to not use the current party, but the event's 
configured party to see if it matches the rules.  This way the actions 
assocated with the rule for PartyCreated on SecondParty will fire when the 
PartyCreatedEvent for SecondParty occurs regardless of the current party in the 
workflow.

For all other events, the current party and current document make sense, but 
the party-specific events needs to fire based on what will be future parties, 
not the current party.  This is true for created, activated and transferred.

Original comment by yoz...@gmail.com on 29 Jul 2014 at 12:33

• Changed state: Started

[GoogleCodeExporter]

Fire the PartyCreatedEvent, PartyActivatedEvent and PartyTransferredEvent when 
the party defined in the event matches the custom logic rule party name rather 
than using the current party which is generally not the correct party (as these 
tend to fire when another is the party and the process flow is moving ahead or 
changing).

In the 14.8.23 release.

Original comment by yoz...@gmail.com on 31 Jul 2014 at 1:28

• Changed state: Fixed