There are seven main groups into which Cradle definitions can be filed. These are common for each type of definition, say a view or a query.
Personal – These are available to the Operating System User whichever project they are logged into – ‘Peter’ may be the ‘admin‘ on one project and the ‘design manager‘ on another but will be able to see this definition whichever he logs into. This only makes sense if the item types are the same in both or the definition is very generic showing say ID and Status, common to all.
User – These are based on the Cradle User name and are available to that role name on every project. On three different projects the role QA manager may be held by three different people. Definitions here would be available to anyone logging in as QA manager.
Team – Definitions here are available to anyone in the same Cradle team on a particular project.
User Type – Users can be grouped by type within a project and this allows definitions to be shown to users of a matching type.
Project – These are queries available to anyone on that particular project
Automatic – Each time a new item type is added, Cradle generates a set of useful definitions to help you get started. These are idea to open tweak and ‘Save As’ to match your personal preferences. They are also useful if you want to write a phase or reference a view in a query as these standard definitions will exist without you having to create them.
System – Some hard wired definitions covering the minimum shipped functionality in Cradle.
Last month saw the start of the Summer and also National Sunglasses day. We still hear the odd story that engineers are using ‘Spreadsheets‘ and ‘Word-processor documents‘ to manage their requirements. We can only sympathise with their misguided ways and revel in the fact that we (and you our dear newsletter readers) have seen the light. So the only thing you should need your rose tinted spectacles for is to eat your Cream tea while watching Wimbledon!
National Cream Tea day – eFFBD
Non Graphic Interfaces
This month (July 2017 Newsletter) we’re highlighting c_io and how it can be used to complement the functionality we’re more used to in WorkBench and Web Access.
c_io
Using c_io.exe in a batch file means you can do many things whilst you are away from your desk or in the background while you continue to work. You can then add this batch file to be run by a task application during times you are away from your desk or work. This can be handy when needing to do backups of a single or many large databases.
The executable can import and export everything in a project from single items to the whole project. It can use queries or different options to whittle down the required export. So a user can export all items of a specific type or just one to several items based on a query and or other set options.
We continue to welcome new followers each month and would encourage any Cradle users who would like regular ‘Hints & Tips’ to follow us @threesl
Reviews
Thanks to those who responded adding reviews of Cradle to Capterra. If you have not yet and are able to add a few words, please reply using Yes I’m happy to consider writing a review
Hints of the Month
Here are some links to helpful topics since our last newsletter, they should improve your Cradle experience:
Using c_io.exe allows a user to do many things within a project without using the interface and is usually faster.
Using c_io.exe in a batch file means you can do many things while you are actually away from your desk or in the background. You can then add this batch file to be run by a task application during times you are away from you desk or work. This can be handy when needing to do backups of a single or many large databases.
The executable can import and export everything in a project from single items to the whole project. It can use queries or different options to whittle down the required export. So a user can export all items of a specific type or just one to several items based on a query and or other set options.
The user can use also use the import to update or create a new Project schema, items, cross references and definitions.
Import and Export can use the Format Types already saved into the database.
It can also export just a single frame from a single item into a file of the right type and print diagrams to specific print types.
How to use c_io.exe
The only real difference between using a command prompt and a batch file is the user will need to have a path for the executable. At the beginning of each command line the user will need “%CRADLEHOME%\bin\exe\windows\c_io.exe”
As in commandline code, a user will require the correct login information and the project being logged into. -login <username>,<password>,<projectcode>
For example:
-login admin.ADMIN.demo
As long as the -login user has the correct privileges, they can use c_io.
Different Options in c_io.exe
Required options are:
-export
Export Options for c_io.exe
-import
Import options for c_io.exe
-getframe
The options for getframe in c_io.exe
-printdiag
The printdiag options in c_io.exe
Without any of the previous options, c_io.exe will put up the Information page or an error.
Helpful other c_io options
There are several helpful options especially when using in a batch file.
-log allows a user to specify a name for a log. This is the log that will have the details of the actions performed during the import.
-noldap allows users to bypass using LDAP when running a command line or batch file. -errorstack option is for logging any issues with the import
A few of the options are not used in a batch file but are in a command prompt. The reason is that they are only used in a command prompt is that they show pop ups with information on them.
-verbose lets the user know that c_io.exe has finished -ver lets the user see what the version number, date and time of the build they are using. -help is used to see all the command line options.
Batch Files from Project Phase
Batch files can be added into the Project Phases, this is done by going to “Project Setup”, and in Options selecting “Project Phases”. Inside here if you create a new Process and change the type to command, in Command navigate to your .bat file.
Command phase node to run batch filesArticle Updated 04/02/2019 – Added infor on running batch file from phase sidebar
