contract: ContractRequestMessage
should be handled also on an existing negotiation
#3380
Labels
Milestone
ContractRequestMessage
should be handled also on an existing negotiation
#3380
Feature Request
Currently,
ContractRequestMessage
is always causing a newContractNegotiation
to be created, but in fact, according to the state machine, it could happen also an already existing negotiation.The behavior should be:
processId
already exists, applynotifyRequested
on itWhich Areas Would Be Affected?
ContractNegotiationProtocolService
Why Is the Feature Desired?
dsp completion
The text was updated successfully, but these errors were encountered: