Can I keep an item’s change history when exporting?
The simple answer is yes!
I certain scenario’s you may need to export items from one Cradle database and import them into another. Depending on your reasons for this, you may want to retain an items change history. However, this is only possible when using the Standard Cradle Export Format and Change History is enabled for your item types.
Enabling Change History
Each item type can have change history enabled in the Project Schema via the Project Setup dialog. You can see how to enable change history in this Cradle help article. Once enabled you should start to receive a change dialog pop-up when making changes to items of that type.
You can choose to enter a change comment, which can include your reasons for making this change. This can prove useful in situations where there are a large number of users in one database enabling full traceability.
Standard Cradle format
Cradle export format files are unique to Cradle and can store every piece of PDB (Project Database) information which does include an item’s change history. However, the type of information that is stored can be further defined by you in the export interface.
There are the usual operating system shortcuts such as <ctrl> + C and <ctrl> + V to cut and paste text. Users can see and set the additional Cradle keyboard shortcuts in their user preferences.
These preferences are first drawn from the system wide cradle.ini/cradle.rc file. If you alter any of them for your own needs, they are saved in your personal user preferences as a difference between the system setting and you chosen value. Thereby balancing consistency between users, whilst allowing flexibility when needed.
This menu is selected from the tab Home -> Preferences
The Cradle shortcuts are mainly based around diagram drawing operations. This can speed up productivity considerably. For example; you don’t have to keep moving your mouse cursor to a menu, just to switch between say drawing and selecting.
More information about keyboard shortcuts can be found in the Cradle Help . Similarly the reset of the user preference details can also be set in the same dialog.
Cradle Toolsuite is compatible with both 2013 and 2016Office 365. To see all Toolsuite compatibility see this page. Toolsuite should work with Office 365 the same as with a normal Office install. Occasionally there are problems due to issues with Office 365 not always with Toolsuite.
Recently there was an issue with an update to Office 365 which stopped our InstallShield correctly detecting the installed version. This issue has been fixed by changing our detection routine in a patch release. If you are seeing this issue with your original install files, please download the latest files and try again. Unfortunately this could happen again as we have no control over these updates. All 3SL can do is update our routines as and when this comes to our attention.
Occasionally when Office is updated and when newly installed, it requires you to Accept new terms. If you have not done this then you will see an Error when trying to start Toolsuite applications.
Error instartup: Object reference not set to an instance of an object
Windows 10 Updates
Since a Windows 10 update earlier this year everything is running slower on may different Microsoft™ Windows flavours. Word can open slower and this can cause issues if you are trying to publish a document. There is no work around for this except to keep trying to publish. Check this blog for more information but the summary so far is:
With Windows 10 on newer silicon (2016-era PCs with Skylake, Kabylake or newer CPU), benchmarks show single-digit slowdowns, but we don’t expect most users to notice a change because these percentages are reflected in milliseconds.
Aklso on Windows 10 on older silicon (2015-era PCs with Haswell or older CPU), some benchmarks show more significant slowdowns, and we expect that some users will notice a decrease in system performance.
Windows 8 and Windows 7 on older silicon (2015-era PCs with Haswell or older CPU), we expect most users to notice a decrease in system performance.
Windows Server on any silicon, especially in any IO-intensive application, shows a more significant performance impact when you enable the mitigations to isolate untrusted code within a Windows Server instance. This is why you want to be careful to evaluate the risk of untrusted code for each Windows Server instance, and balance the security versus performance trade-off for your environment.
Connection or Server Issues
Occasionally the Microsoft server or the connection is down (DownDetector) and this can also cause issues with the Office and Toolsuite. There is no work around for this except patience. Once the connection/server is fixed and up and running you should have no issues with Toolsuite.
Subscription and MSI installs
Having a mix of subscription and Microsoft Installer based MS Office installs can cause detection issues during a Toolsuite install. For example the user has a click-to-run Office 2013 installed but a Microsoft Installer version of MS Project or Visio™. This has been fixed by altering how we detect the architecture of the Office applications.
Mixed Office Versions
It is recommended in our install guides not to have mixed Office environments. For example you may have MS Office 2010 but Project 2016. These type of environments can cause install issues. Even once an install is successful there can be application issues including the loading and publishing documents.
Many of us spend long periods of time working at our computer screens. Consequently, eye strain can become a serious problem. Also, we can sometimes be more productive if we can maximise the amount of information shown. Hence, changing the text size used in the Cradle UI can help in both of these cases, and in several other situations as well.
Maximised Data Display Area
Read articles covering how to maximise the screen area available to display information or drawings.
For comparison, if you use all of the tips described in that other blog post, the UI will have a maximised data display area and will appear like this:
Increase Text Size
You can increase the size of text used in the UI by setting the Text size user preference to Large:
You must re-start WorkBench after making this change.
Using the larger text, the above query and view will be shown like this:
Decrease Text Size
You can decrease the size of text used in the UI by setting the Text size user preference to Small:
You must re-start WorkBench after making this change.
Using the smaller text, the above query and view will be shown like this:
Cradle provides several options to maximise the screen area used to display information. You can change a user preference to change the size of text used throughout the UI.
You can use these in combination to:
Simply see bigger text and reduce the risk of eye strain
Reduce the risk of eye strain and also maximise the display area so you do not reduce the amount of information shown in the UI
Use smaller text because you are using a low display resolution and Cradle is using text that is needlessly large for your display
Reduce the size of text and also maximise the display area because you have a large screen and good eyesight and you must have the maximum possible data visible, particularly when you are using multiple panes to display multiple sets of information at the same time
In the case of a standard hierarchy in a book, it is unlikely you’d see duplicates. Chapter 1 may contain paragraph 1 and sub paragraph 1.1. (A complete reference of 1.1.1). Paragraph 1 in chapter 2 would be 2.1 and therefore, even though paragraph 1 is a duplicate number the full identity is unique. However, in an engineering context, it is much more likely that information will be referenced in more than one place. Hierarchy duplicates are not unusual for referenced information. After all, it is much better to store the information once and use it many times. This is one of the major benefits of a Requirements Management tool. Imagine each component that has to meet a certain design standard. It makes complete sense to relate each part to the standard, rather than copying the standard numerous times. In this regard the hierarchy contains duplicates. For each part that is drilled down many components will end up with the same standard at a lower level of the hierarchy.
Linked Hierarchical Information
The following example shows the expansion of a component (Pump) into the sub components (we’ve followed a link type of SUB-PART). The diagram shows that two of the components have to comply with specific flammability requirements. Both Pump Housing and Pump Electrical Control are linked to REF-13 for Flammability. In turn this has lower elements of Smoke generation for plastics and flammability of Cables.
The diagram illustrates that REF-1.3 is a duplicate by the small square in it’s NE corner.
Controlling Expansion of Hierarchy Duplicates
The Hierarchy Diagram Properties dialog has an option to control whether items seen as duplicates are expanded to further levels. Here the Expand Duplicates option is unticked which is why the user does not see REF-12 and REF-14 expanded below it.
There are a number of different storage types in Cradle. These relate to where the data is held and how it is accessed. This article outlines the different storage in Cradle and explains when and where you may consider using it. Whilst there are some compelling reasons to hold certain data in certain ways, others can be a matter of choice.
For example if you want to add a URL to your item, there is no point trying to store the data inside Cradle this is, by its very nature, an As Reference storage type. On the other hand a binary word processor document could easily be stored inside the Cradle Database or as a reference to an external file on the rest of the company’s network. In this case it could depend whether the file needed to be accessed from outside Cradle or whether it was shared by multiple Cradle projects
Within an item data is either held in the main indexed database fields, such as ID, name, key or a category, or in associated frames. These frames are defined as part of the project’s schema to hold different types of data. There are a large number of predefined types and the ability to define your own.
These are the fundamental type of data we expect to see in the frame. They may be presented in different ways to the user. For example a plain text based frame can be shown in Forms and Views and read directly on the screen. The same is true for basic images. However, a word processor document is held as a binary frame and viewed within whichever application your company uses. A CAD sketch would not be directly visible in Cradle, but could still be stored in the item and viewed with an external program.
These are the fundamental and abstract data types offered in Cradle
Category Multiple Picklist
Each of the above types can be stored in Cradle in one or more ways. Some storage in Cradle, such as a date, make no real sense to store in more than one manner, the URL as mentioned or a date would not make sense to be stored in a file!
Referenced File from Item
This shows the combinations of base type and storage in Cradle that are possible. More information in Cradle help.
Referenced File from Item
Category Multiple Picklist
Benefits and Usage
In PDB (Project DataBase)
✔ Frame data stored in the database is inherently linked to the database item that owns it. It is controlled in the same way as all the other fields of data (name, category, group, description, etc.). This means it can be imported and exported as part of the item. Text frames can form part of a query. Images, text and RTF can be displayed in-line. They move through the CM (configuration management) system with the item. Different revisions of the frame form part of the item’s history, and can be rewound. ✗Not ideal for very large data, e.g. video. Not externally accessible.
✔ Frame data stored in a file is loosely linked to the item that owns it. Date and access times are remembered by Cradle so changes to the file can be highlighted. Great for large files. Other users can access the information externally to Cradle if they have access to a common file directory. Can be accessed through Cradle and item is locked while file is being edited as if it were part of the item. ✗Not directly controlled within Cradle, nothing to prevent the external file being removed or deleted. Can’t be rewound.
✔ Frame data is held in an external environment under an identity, the item stores this identity, and uses Get and Set commands to move the data between the environment and a temporary file where it can be operated on. ✗Not directly controlled within Cradle, nothing to prevent the external file being removed or deleted. Can’t be rewound.
✔ Frame data stored anywhere and only loosely linked to the database item. Ideal for large resources such as Intranet pages. Ideal for information that is expected to change outside Cradle and be accessed by others. Cradle does not wait when viewing or editing. ✗ This is not considered storage in Cradle so there is no CM or rewind available. No control over alterations.
Referenced File from Item
✔ Frame data is held in a frame of a different item whose identity (PDUID and frame name) is stored in the current item. When the frame is accessed via a View the user is editing the common shared data held by the referenced item. This provides a method of reuse, allowing multiple items to directly access a data component of a different item. The ‘host’ item and the frame data follow normal CM operations. ✗Not ideal storage in Cradle for very large data, e.g. video. Not externally accessible.
Setting Up a Frame Storage in Cradle
In this example of storage in Cradle, a frame will be set up to hold a word processor document, internally (in pdb), in a file (as file), and in another item (referenced file from item).
First set up a set of frames for each storage type and set commands on how to view and edit the file.
Ensure the items you want have these frames assigned. In this example the Feature has all three types and the Reference item has just the stored in pdb.
When the file types are set up the data can be imported into the item using the frame button and import Content… this brings the document into the item and it can be stored in the database. It can then be viewed and edited from the same button. In this illustration the Design Notes and Legal Requirements and have been stored in in this way.
The Company Design Standards are held in one directory for every project to access. The illustration links to this as file from where it can be viewed or edited.
Finally the Reference item holds the Legal Requirements document so that it is under formal control. However, other linked items can access this file directly, without having to open the holding item. Their frame is an alias for the data held by the other item.
In a sanitised export the following attributes will be sanitised using the method described above:
All item names (except for data definition names – data definitions in models)
The comment and description attributes
All text frames contents
Every symbol name
All change history contents
All binary frames (such as embedded Word documents) do not appear in the export file at all (as they cannot be sanitised they are simple removed)
Sanitisation option essentially allows a customer to produce a sanitised export file that can be sent to another organisation (3SL). This allows the recipient to reproduce the sender’s Cradle database in ALL respects EXCEPT for the critical (and therefore sensitive) data content. Sanitising your data via an export only effect the contents of the export file and DOES NOT effect your live project.
How do I export my data from Cradle so it is sanitised?
Sanitising you data during export is quite simple all if you are exporting via the WorkBench there is a check box called “Sanitise Data” in the export dialog which you just need to enable.
You can also sanitise your data when exporting via c_io all you need to do is add a -sanitise flag to your command for example:
c_io -login MANAGER,MANAGER,DEMO -export myfile.exp -type all -sanitise
After you export you will be able to open the export file in an editor. You can then see that your data has been replaced with x’s
Or you can import the export file into a test project and look at the data in WorkBench.
For further information on sanitising your data in Cradle please see the following section in our online help.
You can show a hierarchy diagram in Web Access, but first of all it needs to be set up.
You can create dynamic and static HIDs in WorkBench. By right clicking the item of interest and then following Links->Hierarchy Diagram (HID) . Once displayed the properties for the diagram and the item types on it can be set.
If you want to return to these display settings, this ‘template’ can be saved.
The diagram will expand as defined in the settings and show in the item tab. The ‘Save’ option will now be available for the diagram itself. At the top of the HID Sidebar there is the option to make the HID static this results in the entire diagram being saved as a frozen snap shot. Leaving it un-ticked the diagram will remain dynamic. Next time you open the diagram all the links will be checked and redrawn. This is most useful when tracking how your project items and their links are growing.
Running Saved HIDs
Now that the named HID exists, it can be run from the Project Sidebar under the Hierarchy (HID) node in the project tree . You can run a query to return HIDs in the same way you can any other item type. If you write a query that returns only one HID item, it can be added to a phase with a run query and open item action. This makes it easy to control what users see and use from the project phases.
Once you have a named HID available in Cradle it can be run from the sidebar in Web Access. The main item form will show a hierarchy diagram in Web Access. Additionally the ‘expand diagram’ icon allows the user to see the diagram in a separate scrollable window.