Time To Acknowledge
|
Yes |
The amount of time to wait for a Receipt Acknowledgment
before resending the original request. This attribute works in conjunction
with Retry Count. The units are in minutes.
The default value is taken from the RosettaNet PIP specification
document. |
Limited to package or connection |
120 |
Time
To Perform
|
Yes |
The amount of time to wait for a response
to a request action before sending a failure notification message. |
Limited to package or connection |
|
Retry
count
|
Yes |
The number of times to send a request when
an Receipt Acknowledgment was not received. This attribute works
in conjunction with Time to Acknowledge.
For example, with a setting of 3, the request can potentially
be sent 4 times (the initial time and the three retries).
The default value is taken from the RosettaNet PIP specification
document. |
Limited to package or connection |
3 |
Digital Signature Required
|
No |
Indicates whether the PIP message requires
a digital signature.
The default value is taken from the RosettaNet PIP specification
document. |
Limited to package or connection |
Yes |
Non-Repudiation Required
|
No |
Indicates whether to store the original document in
the non-repudiation store.
The default value is taken from the RosettaNet PIP specification
document. |
Limited to package or connection |
Yes |
Non-Repudiation of Receipt
Required
|
No |
Indicates whether to store the Receipt Acknowledgement
document in the non-repudiation store.
The default value is taken from the RosettaNet PIP specification
document. |
Limited to package or connection |
Yes |
Sync
Supported
|
|
Indicates whether the PIP supports synchronous communication.
The default value is provided based on the PIP specification. |
Limited to package or connection.
This attribute is available for RNIF 2.0 only. |
|
Sync
Ack Required
|
|
Indicates whether the PIP requires a synchronous Receipt
Acknowledgment.
The default value is provided based on the PIP specification. |
Limited to package or connection.
This attribute is available for RNIF 2.0 only. |
|
Global
Supply Chain Code
|
Required for RNIF 1.1 |
The code identifying the supply chain for
the participant's function.
Valid values are:
- Electronic Components
- Information Technology
- Semiconductor Technology
|
Limited to package or connection |
|
Encryption
|
|
This attribute indicates whether encryption should
be performed.
Note: This is not the same as SSL encryption.
For the TO side of an exchange (when you are sending documents
to a partner), this specifies whether to encrypt the document.
For the FROM side of an exchange (when you are receiving documents
from a partner), if the attribute is set to Yes, an RNIF request
sent from the partner must be encrypted. If the attribute is set
to No, the document from the partner can be encrypted or un-encrypted.
Valid values are:
- None
- Encryption is not required.
- Payload
- Encrypt the RosettaNet Service Content only.
- Payload and Container
- Encrypt the RosettaNet service content and the service header
together.
|
Limited to package or connection.
This attribute is available for RNIF 2.0 only. |
None |