Known issues

Known issues are defined as low or medium priority defects which have been identified and reviewed, and deemed to have a low impact on users. They may be resolved in future releases, if viable, when other development work is taking place in that area of AVEVA Contract Risk Management.

• Tender messages:

  • When a tender message is sent to a bidder, one or more of its contacts are explicitly specified as recipients. If a contact who was not a recipient marks a message as read, they are added to its recipients list.

• Contract currencies:

  • Changes made in the Contract Configuration to a contract currency rate are not applied to line items in any draft communications. To account for this, it is recommended that the base currency for any communication which uses line items and is not in Draft state is temporarily changed to a different currency once the contract currency rate change has been made, and then changed back to the original currency to enforce the use of the correct rate.

• Contract setup:

  • If there are errors during the import of contract setup data, an annotated version of the imported spreadsheet can be downloaded which highlights the invalid values. Sorting this spreadsheet causes the error tooltips to no longer be displayed for the relevant invalid values.

• Contract communications:

  • When a communication which contains a line item is rejected, the contract line item and any associated rates continue to be shown as in use.

• Custom fields:

  • When creating a tender, contract or contractor custom field, the name of the custom field cannot contain only Cyrillic characters.

• Communication workflows:

  • Communication custom fields which have the Visible in Contractor Portal option set to No should not be used in routing and notification workflow templates, because this will cause errors in the workflow.

  • If a communication workflow is paused while the Contract Owner user has a disabled login account, the workflow becomes frozen in a state of Pause Requested. This can be resolved by ensuring the Contract Owner user has an enabled login account and then rejecting and creating a revision of the communication to restart the workflow.

• Rich Text Editor:

  When entering text into fields which support the rich text editor, the following should be noted:

  • If text is pasted from Office documents, blank lines will be lost and must be manually re-entered.

  • Hyperlinks cannot be edited; they must be removed and re-added.

  • Text which is encoded, such as apostrophes, will appear in some grids as the codes instead of the correct characters.

    Applies when creating and editing tender messages, editing a communication, and creating and editing contract obligations.

• Audit report:

  • When you close a project/dept, any open contracts within that project/dept are automatically closed, but the audit report for the contract does not tell you both that the contract is closed and who closed the contract.

  • The first time a submission file is downloaded from the tender library, the Downloaded Submission File message is recorded twice in the audit log.

• AVEVA Contract Risk Management Analytics:

  • When viewing data from the Analytics API, special characters in custom field names are not shown.

  • The ETL may experience errors when processing large financial values (greater than 19,2 - maximum of 19 digits including a maximum of 2 decimal places).

• UI:

  • In the Project/Dept and Contract Communication Registers, the Communication State and Reporting Category columns cannot be sorted in ascending/descending order.

  • When viewing and editing lookup lists such as product codes, the display grid may exhibit issues for lists with over 1000 items.

  • When modifying dates for a tender schedule, the Tab key should not be used to move between dates if you have chosen to cascade changes.

  • When viewing the Reorder Breakdown Items dialog, a zoom level of 100% is recommended.

• Export of data:

  • When opening a Microsoft Excel file of data exported from AVEVA Contract Risk Management, an error related to the file format and extension may be displayed. The file can be opened safely.

• Temporary delegation of authority:

  • If a user’s delegation is revoked while they are logged in, they will be still be able to access all of the delegator’s working areas until they log out.

• Search:

  • When using the Contractor Search from the navigation bar, the criteria shows ‘Contains’ but actually performs a ‘Begins With’ search. Click Search again to perform a ‘Contains’ search.

• AVEVA Contractor Risk Management REST API:

  • The REST API help incorrectly indicates that multipart file uploads are used for specific areas of AVEVA Contract Risk Managament. However, from 8.2, the multipart file upload is no longer available. A resumable file request should be used instead.