Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Contract Risk Management - Company Portal

Internal Correspondence

  • Last UpdatedJan 26, 2024
  • 2 minute read

Company to Company (Internal Correspondence) communications can be created in the Company Portal only. Users with the following contract roles can create this type of communication:

  • Contract Owner

  • Contract Administrator

  • Company Representative

When creating a Company to Company communication, you can select whether to specify recipients. Recipients can be select contract roles, business process roles in the contract, and company users who have a contract role for the contract. Any recipients will be sent an email notification when the communication is published/sent. See Create a communication for more information. The sender of a Company to Company communication is always the user who created the communication.

A typical lifecycle of a Company to Company communication is:

  1. The communication is created in the Company Portal by a company user.

  2. The communication is saved as Draft.

  3. The workflow can be started for the communication, which can include internal reviews.

  4. The communication is published/sent, so that it is visible on the Company Portal only.

The following diagrams show more detailed workflows.

Communication requires agreement

Example: A company user creates an internal communication which requires agreement, so that a formal record can be held in the contract and will be included in reports.

The Required Response option of the communication template is set to Agreement Only or Agreement and Reply.

Tip It is recommended that a workflow is used for internal reviews rather than using the Required Response option for the communication template.

The possible communication states of an internal communication which requires agreement are:

  • Draft

  • Awaiting Agreement from Company

  • Agreed

  • Not Agreed

  • Rejected

Communication does not require agreement

Example: A company user creates an internal communication so that a formal record can be held in the contract and will be included in reports.

The Required Response option of the communication template is set to None or Reply Only.

The possible communication states of an internal communication which does not require agreement are:

  • Draft

  • Approved

  • Rejected

In This Topic
TitleResults for “How to create a CRG?”Also Available in