Create a document remark from an issue

Modified on Mon, 13 Jul at 2:41 PM

While working with technical file requests, ensure the communication with your supplier about progress remains tied directly to a document. Create document remarks from an issue to connect the issue and the document.


Feature access

These features are available to all ProductIP users who work with technical file request. 


Before you begin

  • Create a pre-draft file
  • Send out a technical file request
  • The receiver has shared their technical file with you
  • You have sent issues and the receiver has responded to them


Video instructions 

A short step-by-step guide will follow soon! 


Steps 

  1. Go to the Requests tab > Pending view & clone shares tab and open the shared technical file.
  2. Navigate to the Issues tab.
  3. Click the Add document remarks icon for the issue you want to store with your document.
  4. Select the document you want to add a remark to
  5. Set the Status of the document. Note: If you set the status to rejected this will also remove the document as evidence from the requirements list. 
  6. (Optional) Add the remark to the timeline if you want to have an extra note of it by selecting the box.
  7. Write your remark. You could copy paste the message in the issue or write additional text.
  8. (Optional) Unselect the last box to notify the uploader about the remark. This will generate a platform email containing your remark.
  9. Click Save.


Tips and best practices 

  • Added document remarks are visible for you in the shared technical file, but not for the sharing party. They can see the added remark in the related issue as long as the share was not declined or accepted.  
  • After you Accept & Clone the shared technical file the document remarks are only visible to you and colleagues who can access the cloned technical file.

 

Related articles

Review received technical files

Manage your open issues

Use document remark or issue and the differences

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article