Project Manager is a utility that is used to manage your Cradle projects. It provides access to all Cradle systems that are accessible to the user (usually only one) and all projects defined in the Project Register(s) of these Cradle system(s).
*If you will have the same users in the new project that are in the existing project.
To avoid the Personal and/or User definition files being part of this import, we would suggest the following:
Log in to the existing project as MANAGER
Select Project > Export
In the Export dialog set Owner to Everything and Info Type to ProjectSchema and User Profiles (if users are required, see comment above)
Press Export to create the export file and close the Export Status dialog but do NOT close the Export Information dialog:
In the Export Information dialog, change the Info Type to ONLY show Definition Files:
You will see that some new options appear – Definition Type and Location:
The Definition Type option allows you to specify the types of definition file to be included in the export. For this example, we will leave this as All:
The Location option defines which location you are exporting the definition files from.
Users may have created Personal or User definition files that might not be relevant to the new project. Personal and/or User definitions might only have been useful to an individual person rather than the project so could be omitted.
In this case, we would only need to select Team*, User Type* and Project
* It may only be necessary to select Project
Press the Export button again. This will present you with the option to Overwrite, Append or Cancel. Select Append:
Select Project > Import and set Owner to As in File and Overwrite to On:
You will see that your new project contains:
All the Project Setup information including the phase hierarchy and all supporting definition files
If you had NOT chosen to append the definition files, it is highly likely that the phase hierarchy from the existing project would not work in the new project and would produce errors.
These definition files are important to define the WorkBench environment.
Also, if you had chosen to export all the definition files, this may have resulted in numerous views, forms, queries, documents etc., that are not particularly relevant or accepted into project definitions.
Using Project Manager with Multiple Projects and Passwords
In an environment where you have numerous projects that you switch between, using Project Manager to Login can save retyping your Cradle password.
If you have many projects that you need to switch between and don’t have a limitless desktop to open multiple copies of Cradle or don’t want to lock multiple licences, use Project Manager to look after switching.
Once you Login to a project through Project Manager your Cradle password is cached for that session. You can then access the project through WorkBench, Web Access, or the Toolsuite applications; Document Loader, Document Publisher or Spell Checker. When you exit a tool, you can open another project through Project Manager as you work through your day. When you need to re-enter any previous projects, you’ll only need to use the Open command as your login details will be cached.
If you need to clear the cache (for security reasons) then simply use the Clear User Cache option. Alternatively close Project Manager.
Another option to change to a different user is to use the “Switch Identity” option, this can be enabled in the “User Setup” A User Profile’s switch identity can only be set if you have read-write access to the User Profile. If you have no access to a User Profile, you cannot see any part of it, including the switch identity. If you have read-only access to a User Profile, the switch identity is disguised in the same manner as the User Profile’s password.
Users can be disconnected and their licences released by another user from Project Manager without the need of restarting the CDS.
This could be useful in the following circumstances:
A user has left a login dialog open locking a RW connection
A user has locked a licence and cannot manually release it
You have locked a project for maintenance and need to remove users while the maintenance is carried out
Disconnect your users through Cradle’s Project Manager. To disconnect a user select User Management… from the System pulldown menu which produces a User Management dialog, from here you can see details of all connections to the CDS, select a user and then choose Log Off. This will kill the connection and free up any licences they had in use.
It is easy to see who, using what, where from the Users report in Project Manager. This details the host system user name, their Cradle login name and the project they are connected to.
Why is there an Executing Client and Display Client shown?
These would show different values if your system is set to have the executable running on one machine with the UI redirected to another. For example a Windows® user may remotely log on to a Linux® machine, and start WorkBench, viewing the output on a Windows X terminal emulation. The machine running the Cradle Database Server may be a third machine.
Additional brief information detailing which module licences they currently have in use is also given. For full details on the licence usage users would run the Licence Usage report.
If you need to check your new installation is running IPv6, then you can use Project Manager, or the Help->About screen in WorkBench, Document Publisher etc.
There’s a whole host of other information on these screens which will tell you; how your client found the CDS (Cradle Database Server), which language variant is active and which licences you are currently using.
If you need to ensure no-one can log into your project, in order that you can:
Back-up the hard disk while no data can change
Perform maintenance on Cradle items assured that none can be locked by others
Prevent users you are adding to a project can’t start until an official go-live point
Then locking the project to a selected user can ensure a data manager has the appropriate control.
Lock your projects to a selected user through Cradle’s Project Manager. Only MANAGER and the optional named user can login to the project. They are also the only users who can unlock the project once again.
When you have a large number of projects and users it can get difficult to track them all. Project Manager, part of the Cradle suite, provides a method to hierarchically organise, categorise and sort your projects.
Classification / Categorisation
A Project may belong to more than one sub category, “Mechanical Department” and “Current Project”, you can place a link to the project in each of these folders. In the future the link may be in the “Mechanical Department” and “Completed” folders, its up to you. Project manager can also add a host of user defined categorisations and references. This will help identify a project and its associated contracts or references, now and in years to come.
You can set attributes for each project. These can provide extra details about the project’s purpose, status, dates and so on. Project Manager ships with nine default attributes, however, you can add your own or change those supplied.
Alias ‘Alias ID for the project, such as an alternative project ID number’
Division ‘General Description such as the company division doing the project’
Branch ‘General description such as the company branch doing the project’
Customer ‘General description such as the name of the customer for the project’
Reference ‘General Description such as the RFP or ITT reference number’
‘Inception Date’ ‘General description such as the start date of the project’
Purpose ‘General project description, used in any manner found to be useful’
Summary ‘General project description, used in any manner found to be useful’
Description ‘General project description, used in any manner found to be useful’