Items in a database can have many different fields, some or all of which may need their spelling checked. On Cradle installations with Tool Suite the Spellchecker tool can check items that are returned by a query.
Launch Spellchecker, and login. (This can be done by launching the standalone application or selecting it from the Tools menu in WorkBench)
The purpose of Multiple Data Cells in a view is to allow more data to be consolidated in one place. It might me that a reference number is made up from categories storing ‘Part‘, ‘Sub-Part‘ and ‘Version‘. This may need to be formatted in a cell as part:sub-part/version. This can be achieved by setting the format of a multiple data cell in the Cradle view.
This image shows the TEST STATUS:TEST TYPE and Text from the test being combined in one cell.
New Cradle-7.2 View Feature
Initially the cell string was formed by combining the text from single line entries from categories, the group, description and possibly piece of text from a frame. Customers have found the multiple data cell useful and have been combining data from frames with multiple lines. Whilst the drive is still to show as much data in a combined block, those using, say lists as in the example shown, found that the removal of line breaks in the display altered what was being conveyed. It is now, therefore, possible to select the ‘Preserve line breaks’ option in the ‘Multiple Data Cell Setup’, ‘Edit Attribute’ dialog.
Cradle has supported KPIs being shown in the sidebar of WorkBench or Web Access for a number of years. This gives a quick overview of the health of the project. It’s giving a rating for each of the measurements and coloured highlighting to draw attention to those areas that need further input.
Due to its compactness, this table style allows many KPIs to be shown in a small space. However, one of the limitations with this approach is that the scale of the measurement and the relative position of the current value are not immediately obvious.
Bring on the Dials
A dial on the other-hand can display the full range, and the relative position. This allows a much faster assimilation of the data being shown to the user.
New Cradle 7.2 Dashboard Dials Feature
Cradle’s dashboard dials are available in a number of sizes, thus allowing more important dials to be clearly seen. The size is set per dial as:
Large
Medium
Small
Minimal
There are also a number of styles available for the dashboard as a whole:
Round 270°
Round 180°
Round 140°
Text
These can be displayed with the following pointer types:
None
Triangle
Stick
Needle
Coloured
It’s also possible to print these dials to the standard Cradle outputs:
Cradle can import data from external files in different formats. One of the most common formats is CSV / TSV (comma separated value and tab separated value). When data is imported from CSV / TSV files, you can choose different import overwrite options. The option that you choose will control whether your data is imported and, if it is imported, which existing data in your database will be kept, or replaced by data from the import file.
Items and Attributes
To explain these options, let’s use a simple picture to represent an item and the attributes inside it:
Example
Lets say in your Cradle database you have an item with the following attributes:
meaning that the item in the database has values set in the 2nd, 4th, 5th and 6th attributes.
In a spreadsheet you have a row with data in columns corresponding to the 1st, 2nd and 5th attributes of the item in the database:
Import Overwrite Options
Option A – Overwrite On
If Overwrite is On then, for each row in the spreadsheet or each record in the CSV / TSV file, Cradle will find the work-in-progress item (if any) and delete everything inside it, and completely replace the contents of the work-in progress item with the data from that record or spreadsheet row.
You would get the following result:
As you can see, only the data from the file or spreadsheet (the yellow cells) are now in the item, all previous attributes (the blue cells) are now gone.
Option B – Overwrite Off
If Overwrite is Off then if there is an item in the database for the record in the CSV / TSV file, or row in the spreadsheet, no import will occur. If there is no item in the database for the record or row, then the result is the same as Overwrite set to On.
Option C – Overwrite Merge
This is the more interesting case!
If Overwrite is Merge then, for each row in the spreadsheet or record in the CSV / TSV file, Cradle will find the work-in-progress item (if any) and replace the attributes of that item with the columns from that row in the spreadsheet (or field i the CSV / TSV file) so any attributes in the item that have not been mapped to a column in the spreadsheet row (or field in the CSV / TSV file) will be left alone.
So the attributes that already exist in the item in the database and the attributes in the spreadsheet row or file record are merged:
You would get the following result:
Attributes in the spreadsheet row or file record have been loaded into the item. All other attributes in the item have not been changed.
Summary
Setting Overwrite to Merge is useful to add data to database items from an external CSV / TSV file or Excel spreadsheet. Any attributes not in the external file are not affected by the import.
To get more help importing information into Cradle, explore the Cradle help here.
Most people are familiar with a ‘find and replace’ function in a word processor document. However, when you have thousands of items in a database, it’s not very easy to open each one and search through for the replacement term. You could run a query, but then you’d still need to know which attribute of the item the query should match.
Allowing the search to take place at the database level ensures that the items are found that contain the term. Rather than just ‘finding’ in the visible text on the screen.
New Cradle-7.2 Find & Replace Feature
If items are visible as the result of running a query, for example, it is possible to select all those items and perform the find and replace within the attributes of those items.
Clicking each item in the left hand column of the dialog will show the attribute in the right hand part of the dialog that matches.
The user can optionally double click the ‘Yes’ in the ‘Replace’ column to prevent this substitution occurring.
Alternatively users can select a query to run to source the items in which replace will occur. In both cases a report to detail which items were changed can be printed by checking the box at the bottom of the dialog.
Imagine you have a project and teams of people working on it. You can control who sees what by placing staff in different teams (for information watch this video about collaborative teams). You can provide skills based access to individual frames within the item. However, there maybe one type of item which only certain team members can see, maybe a Finance item. The solution is to set a skill for the item type. Ensure those who are allowed to view the item type have the skill. For those assigned the required skill, all the other access controls still get applied, (CM status, security clearance and ownership). For those without the skill, the item type disappears from existence, it is as if the project schema had not defined the item.
Login to WorkBench as a user who can modify the schema
Start Project Setup from the Project tab, set Options to User Settings and select the Skills tab
Select New and define a new skill
Set Options to Item Definitions and select the Item Types tab
Select the item type to be controlled and choose the new skill from the Required skill: drop-down list
Save the schema and close Project Setup
From the Project tab, select User Setup and for each user who is to be able to see the item type, select that user, select Skills, add the new skill to the user’s user profile and save the profile
RO Skill Based Access Feature
New Cradle-7.2
Now imagine the scenario that you want team members to see an item type but you don’t want them to be able to change any aspect of it. The latest version of Cradle allows you to set Read-only access for these item types.
Related Items
To restrict access to categories alone, this article will help.
In the database each item can have a number of categories assigned to it. These are indexes by which you want to sort and retrieve your items. Some values are plainly single, an item’s Customer Approval can’t be Approved and Rejected at the same time. However, Colours could be Red and Blue on the same item. These are multiple value categories. They are used to classify an item when the attribute itself can have multiple non mutually exclusive values.
The values that can be held by the category are defined in the Project Schema. Each value is allocated to a ‘slot’ each item holds a set of flags indicating which slots (values) are ‘selected’ for that item.
When shown in a View or Form, the values for the slots are shown to the user.
New Cradle-7.2 Project Setup Feature
It’s now even easier to set up multiple value categories in Project Setup.
The new options are:
Clear – Clears the value from the list but leaves the slot blank
Copy – Copies the selected value
Paste – Pastes the copied value into the selected slot
Delete – Deletes the value and all values below this value are moved up
Insert – Inserts a slot so you can add a value, all values below this slot are moved down
Up – Exchanges the currently selected slot with the one above it
Down – Exchanges the currently selected slot with the one below it
There is consequence on existing items in the database for all of the operations above so a warning message will be shown when attempting one of these operations.
If slots 1, 2, 3 are Red, Blue and Green and item AA1 has flags set for 1, 2 it will be seen as Red and Blue. If a subsequent change is made to the schema (after items exist as drafts or baseline items), making slot 1, 2, 3 Red, Orange, Blue and Green, will result in item AA1 being defines as Red and Orange. This is because the flags tally with the slot. Users should query on existing data to see which items will be affected and subsequently update those they wish to change individually, or using “Item Properties”.
In an ideal world we would design the project schema first and then run our project from that point on. However, that’s not always how real life pans out, changes post ‘work starting’ can create questionable item integrity.
Cradle’s WorkBench Item Integrity checker allows an authorised user to check the status of items in the database. The thorough check ensures each item’s attributes are consistent with the schema and valid. It highlights areas that need the database administrator’s attention.
These issues may have been created in a number of normal operational ways.
Altering the schema after these items have been created and saved.
Importing items whilst overriding data validation. (In order to get items in to the database, so that they can be edited it is quite logical to want the old value to remain. The user then has a chance to view and edit and save with the new parameters).
Creating, say, a hierarchy of items and subsequently not editing them to fill in all required category fields or filling mandatory frames with content. (It would be most laborious to be forced to fill each one at the time of creation. It is better allowing a hierarchy to be created and then subsequently edited)
Item Integrity Checker
New Cradle-7.2 Item Integrity Fix Feature
A Fix button has been added to the Item Checks section of the Item Integrity Checker. This button only apply to certain checks. These checks are shown below with details of what happens when the Fix button is pressed:
Check
Fix Operation
Category values are defined in project schema
Clear the category values.
Category values match data type in project schema
If it has a default value, set it to this value, otherwise don’t do anything, i.e. this cannot be fixed using the Fix button.
Categories are not empty when predefined values exist
If it has a default value, set it to this value, otherwise don’t do anything, i.e. this cannot be fixed using the Fix button.
All mandatory categories have values
If it has a default value, set it to this value, otherwise don’t do anything, i.e. this cannot be fixed using the Fix button.
In the latest version of Cradle’s Web Access it is possible to show images in a View. In previous versions of Cradle it was only possible to show an item’s images in a Form.
This small but significant enhancement moves the remote Web Access client’s capabilities nearer the WorkBench rich desktop client’s functionality. Therefore, wherever you are located you can get detailed access to your data.