This article is a guide to understanding threaded views of workflow relationships within FastDraft.
This guide contains the following:
Related articles:
Introduction
The standard way of viewing relations on FastDraft is to use the Relations tab on any draft/communicated notice. However, the limitation of using the Relations tab is that it will only show you a list of notices directly linked to this specific notice. Users can follow the link to that direct relation, but then see that there are additional relations that have formed a communication chain, not previously shown.
Over time you may find that you build up a chain of related notices. For example, an Early Warning leads to a PM Instruction which leads to a CE Notification, which results in a Contractor's Notification followed by a Project Manager's Notification. Each of those will be directly linked to the communication that went before it but, in many cases, it would be beneficial to be able to see the whole conversation from start to finish.
We have introduced the capability to view a register of all related notices in the chain. This will show all of the relations plus any associated replies, associated quotes and any replies to those quotes, with each entry on a separate row.
Relation Chain
In order to view the end-to-end 'conversation' users can use the View Relation Chain feature within the Relations tab, and a new table will appear showing you the communications history.
Within this register you can search, filter, sort, and export all notices that you are entitled to see (for example, you won't be able to see drafts from the other party as you wouldn't normally have access to those). All notices in the table are directly or indirectly related to one another.
By default, the following columns will be enabled:
- Reference ID
- Notification Title
- Subject
- Description
- Notified By
- Date Notified
- Reply
- Sending Party
- Type
You can, however, use the column chooser to add/remove any additional columns.
The list will, by default, be sorted based on when each notice was communicated so you can see the thread from start to finish.
Note - for contracts with an Asset Register enabled the feature ignores relations and instead finds all communications linked to a particular asset.
Note - for performance reasons, this feature caches results for one hour.
Comments
0 comments
Please sign in to leave a comment.