What happens if the review due date for a role runs overdue?
What happens is that the user is going to see that document on their dashboard highlighted in red. They will also receive an email notification stating that the due date for the review of that specific document has run overdue.
This improvement intends to promote the culture of accountability, enabling the user to be aware that they are delaying the process, impacting everyone that comes after them.
Is it also possible to have, for instance, turnaround times for approving and publishing only?
This is not possible right now, you need to configure turnaround times with a full timeline for all the tasks. You can set a specific date for setting documents to the “published” status, when you reach “approval not published”; you would simply make use of these turnaround times for scheduling the publication. But you would need to have configured the previous ones too.
The fields for “Products & Services” and “Contacts” are part of the document settings, is there a way to exclude those fields?
There is no way to exclude these fields, they have become standard in Scilife. All documents will have those 2 fields. Although they are not mandatory, you can choose not to input data. If you do not input data, the text “Non applicable” will be shown in the field.
If you use Products & Services to link to documents associated with a particular product, is it possible to apply security to that so that only users associated with that product can see those documents?
In this case, you would need to make use of the groups. The only way to ensure within the system that only a specific set of users have access to a specific set of documents, events, CAPAs, or other items you create within the system, is blocking their access by using specific groups.
You would need to create a group, and only add that group to those documents or any other items which you want those users to see. In doing so, they will only be able to see the documents that also have that one group assigned to them.
The email notification regarding action due date, is it only sent when the due date is already past? Or for example, will the reviewer receive an email a day before the action due date?
That's one to be confirmed? We will check that out. I think they receive a notification a few days before, and then they receive a notification when it's overdue. But this is something we will check up on, just to make sure.
In the Release Note for Document Control 3.0, a lot of new variables are available related to Linked documents and Linked change requests. Where can we use those variables?
Okay, what I propose is related to the 'link documents' variable, which is one of the most frequently used variables in document control. Everyone always wants to ensure that information or metadata travels directly with the linked documents.
What I suggest to make it more user-friendly is that we work on some knowledge-based articles that will provide updates on the use of each specific variable.
Once we have completed this, we'll share it with a couple of teams. Let's aim to have it ready before we send out the recap next Thursday, so you can see what each individual variable does, how it works, and where you can make use of it.
