Lock a master acquisition method in a project -

Hello, 

We are starting to use OpenLAB 2.3. The way to quantify for some products is the same.  How can we introduce an intelligent report within each of the projects without having to create it from 0 in each of them?

Regarding the acquisition method, as a supervisor can leave a method blocked so that the analyst/technician at the time of launching the sequence can not change the injection parameters (flow, volume,...). The option that we have been told from a near company is to create a "ghost" folder where the method is created, it is saved and locked in the ECM by administrator and then an administrator transfers it to the project folder. Is this true? 

Thanks a lot!

Òscar 

Parents
  • Oscar,

    It is possible with CDS projects to point the report templates path to another project path. This means that all your project could point to the same path for report templates. This is the easiest way to make sure all projects have access to the same report templates. There is no way to lock methods in a project without removing the user access to change and save methods in the roles. In CDS 2.6 they added a method approval workflow that does allow locking of methods for the end users. 

    Marty Adams

Reply
  • Oscar,

    It is possible with CDS projects to point the report templates path to another project path. This means that all your project could point to the same path for report templates. This is the easiest way to make sure all projects have access to the same report templates. There is no way to lock methods in a project without removing the user access to change and save methods in the roles. In CDS 2.6 they added a method approval workflow that does allow locking of methods for the end users. 

    Marty Adams

Children
No Data
Was this helpful?