How do you transfer a project from the Non-Regulated folder to the Regulated folder in a MassLynx Security environment? - WKB55081

OBJECTIVE or GOAL

Transfer a project from the Non-Regulated folder to the Regulated folder in a MassLynx Security environment.

ENVIRONMENT

• MassLynx 4.1
• MassLynx 4.2
• MassLynx Security

PROCEDURE

1. In order to perform this transfer, two things must first be configured within the MassLynx Security manager.
   
   a) The user must have the right to import projects, which is what creates the checksum. In Group Rights, for this user, enable General: Import legacy projects.
   
   b) In the Directory Policy, the Regulated user group must have Import enable on the folder for Non-Regulated projects. (Allowed should NOT be enabled for Regulated Users on the Non-Regulated projects.)
    
2. After the User Rights and Directory Policy are set up correctly, you can move the Non-Regulated project to the folder for Regulated projects using the following steps.
   
   a) Log in to MassLynx as a user with the right to Import Legacy Projects. (Note: This must be a user; it cannot be someone in the Administrator group.)
   
   b) From the menus at the top of the Main MassLynx page (sample list page), go to Security > Import Project.
   
   c) Browse to the folder for Non-Regulated projects and select the project folder (*.pro folder), which is going to be moved to the Regulated projects folder.
   
   d) Click OK and type the appropriate user credentials.
   
   e) Open Windows Explorer (not Internet Explorer). Browse to the Non-Regulated projects folder.
   
   f) Locate and highlight the project for which the Import Project was performed in Steps c and d.
   
   g) Right-click on the highlighted project. Select Copy from the menu that appears.
   
   h) Browse to the Regulated Projects folder. Right-click in the panel and select Paste from the menu that appears.
   
   To open this project in the Regulated environment, log in to MassLynx as a Regulated user. Go to File > Open project. Browse to the project and click Open.
   
    

ADDITIONAL INFORMATION

When the project is in non-regulated mode and a calibration file is linked to the tune, you will like get a checksum error when trying to access the tune file. This is because the calibration file to which the tune file is linked is from the non-regulated mode and does not have a checksum. After moving the project to the regulated mode, a new lnk must be set in the tune file to a calibration file that was created in regulated mode or has had a checksum created.