In ebXML CPA, a trading partner is designated as a party to the agreement, and identified with a party Id. The generated CPA template always includes two parties. Each party can play more than one role defined by the BPSS document on the Binary Collaborations. To define the characteristics of the two parties and some shared parameters (CPA Id, Start and End time, Status, conversation constraints), you can use the following extended attributes available from the model property sheet:
|
Name |
Description |
|---|---|
|
Identifier |
Specifies the identifier of the party Scripting name: PartyInfo1ID, PartyInfo2ID |
|
Name |
Specifies the name of the party Scripting name: PartyInfo1Name, PartyInfo2Name |
|
Reference to more details |
Specifies a reference to more detailed information on the party. Scripting name: PartyRef1, PartyRef2 |
|
Default delivery channel |
Specifies the default delivery channel used by the party to exchange the messages Scripting name: PartyInfo1defaultMshChannelId, PartyInfo2defaultMshChannelId |
|
Default message packaging |
Specifies the default message packaging used by the party Scripting name: PartyInfo1defaultMshPackageId, PartyInfo2defaultMshPackageId |
|
CPA ID |
Specifies the ID of the CPA document Scripting name: cpaid |
|
BPSS document reference |
Specifies a reference to the BPSS document Scripting name: hrefBPSS |
|
Start time, End time |
The Start and End time define how long the agreement is valid Scripting name: Start, End |
|
Status |
Specifies the status of agreement. By default it is proposed. It can be agreed or signed. Scripting name: Status |
|
Invocation limit, Concurrent conversations |
Specifies limits on the number of conversations under the CPA. Scripting name: ConversationConstraints_invocationLimit, ConversationConstraints_concurrentConversations |