Test yourself in the CMS Console Application Developer track

By doing the assignment below, you can test your knowledge of the CMS Console Application Developer track. Make sure you have studied all the materials suggested in this track.

The assignment consists of 10 tasks. Some of the tasks refer to the data you have to create in some of the previous tasks. So we recommend that you do the tasks in the suggested order.

The actual assignment may include one or more tasks similar to those below. However, you should bear in mind that the actual tasks may be different from the topics covered here and be a bit more complex.

Task 1

1. Create a user group “Editors” that will be allowed to edit pages and media files.
2. Create a user “user1” and assign it to “Editors”.
3. In “Media”, allow “user1” to create media files.
4. In “Content”, allow “Editors” to create and delete pages.

Task 2

1. Create a global data type called “Test.Company” with fields: “Name” (string (64)), “Address” (string (512)), “Phone” (string (32)), and “Website” (string (32).
2. Change the widget of the Address field to TextArea.
3. Add 3 items with arbitrary data.
4. Create a global data type “Test.Contact” with fields: “FirstName” (string (32)), “LastName” (string (32)), “Phone” (string (32)), “Email” (string (32)), “Prospective” (Boolean), “Company” (data reference: Test.Company).
5. Edit the form markup of the “Test.Contact” to split the fields between 2 field groups: “Main” (FirstName, LastName, Company, Prospective), “Additional Information” (Address, Phone, Email).
6. Add 6 items with arbitrary data (at least 1 for each company).

Task 3

1. Create an auto-attaching console application “Contacts” that appears in the Users perspective (bottom).
2. Add a simple element labeled “Contacts” and another simple element labeled "Contact List" as its child.
3. Attach the standard Add action to the “Contact List” element to add items of the Test.Company type (from Task 2).
4. List data elements of the Test.Company type under the “Contact List” element using the Name field for labels.
5. Attach the standard Edit and Delete actions to Test.Company data elements.
6. Sort the elements by Name in ascending order.

Task 4

1. In the “Contacts” console application (from Task 3), list data elements of the Test.Contact type (from Task 2) under each Company element filtering Contact elements by Company ID.
2. Use values separated by a comma from the LastName, FirstName fields for labels.
3. Attach the standard Add action to the Test.Company type elements to add items of the Test.Contact type.
4. Attach the standard Edit and Delete actions to Test.Contact data elements.
5. Sort the Test.Contact elements by LastName in ascending order.

Task 5

1. In the “Contacts” console application (from Task 3), add a simple element labeled “Prospective Customers” as a sibling to “Contact List”.
2. List data elements of the Test.Contact type (Task 2) under the “Prospective Customers” element.
3. Use LastName, FirstName and Company for labels.
4. Filter the elements by Prospective where it is ‘True’.

Task 6

1. Create a static IData type (programmatically) called “Demo.Book” with these fields: “Id” (Guid), “Title” (string), “Author” (string), “Published” (DateTime).
2. Create a form definition for the type.
3. Create a tree definition that auto-attaches in the Content perspective (bottom).
4. Have the tree definition list items of this type (books) and attach standard actions to add, edit and delete books.

Task 7

1. Add another language of your choice to the website.
2. Localize the "Test.Contact" data type (from Task 2).
3. Switch to the second language.
4. Translate and publish a few pages.
5. Translate and publish a few "Test.Contact" data items.

Task 8

1. Create a page meta type called “WelcomeMessage” with a field called “Text” (string (64)).
2. Create a page type called “MyPage”.
3. Specify the default template of your choice.
4. Add the WelcomeMessage metadata field (from Step 1).
5. Set the default child page type to "MyPage".
6. Create a page based on this page type.

Task 9

1. For Visual Editor, create a style class named “allcaps” for <span>.
2. Have it transform the selected text to be all capital letters.
3. Create a format based on this style class for an inline text.
4. Add a button to the toolbar of Visual Editor.
5. Apply the format to the inline text on the Home page.
6. Make sure that it is visible in both Visual Editor and Preview.

Task 10

1. Enable the verbose logging in C1 CMS.
2. Install Log Viewer and connect to C1 CMS.
3. Switch to History mode and view old entries.