TITAN CMS VERSION 6.3

Version 6.3

The new features for TitanCMS include many enhancements to make your job easier in managing your content.  

Range Filters are now available!  There is a system configured Date Range, along with being able to set up your own Range.  A new column type was also added for use in Range Filter called "Input for Whole Numbers".   A new Titan Property is the URL Aliases.  The URL Aliases field provides a place to enter different URLS that resolve to the existing Page URL.  There are changes to the Data List block that allows users to now configure their filters in desired order including the keyword search field and option to add a title.  The Filter & Data List blocks now have a caching option.  If block does not change often and there is no security, the results may be cached to improve performance.  The Data Editor block can be configured to allow Author type users to submit data records on display without a login *There are exceptions to which column types are allowed on display for submission without login.   To save time, the Where Used job can now be configured to run per a file folder so that process does not need to run against a full default folder and its subfolders.  The SEO field inputs may now be uploaded for all item types.  There are new counters under SEO property fields.  There is a new system defined Browse View called "SEO Properties" for each content type.  And, finally, there is now Full Text Search queries for inflectional forms of words, example Written, Write or Wrote.  

Range Filters

Benefit:  Saves you time so you do not have to tag all your content.  Ranges can filter based on text, dates and numbers stored in different column types.

Ranges are a special type of Tag that allows filtering based on custom Data Fields.

Valid Column types that may be configured to use in Range Filtering:

  • Basic Text input (1 line).  *Range set as Textual.
  • Input for Date *System defined Date Range calculated relative to the current date and time of SQL Server.
  • Input for a Date and Time *System defined Date Range; no "time-specific" range (*customize). Calculated relative to the current date and time of SQL Server.
  • Input for Decimal / Currency.  *Range set as Numerical.
  • Radio buttons *custom display  (Textual, Numeric, *Customize).
  • NEW column type Input for Whole Numbers (No decimal).  *Range set as Numerical.

Rules for Range Filtering:

  • Range set as Textual Values or Numerical Values.
  • Range Attribute Min/Max values cannot both be blank.
  • Range Attribute Min/Max values require to be number if set as Number.
  • In Data List Block filter section, unable to select Data field twice to configure as range.
  • Range is added in the Titan Administration module.
  • Valid column type fields may be checked to allow Range Filtering. *Range filtering is not supported for columns linked to Titan properties, use the Own Column option.

Range Filters Example *Create in Titan Administration module:

Range - Numerical with Attribute Min/Max Example:

Range - Numerical with Attribute Group Subset Example:

Data List Block - Filter Configuration

Benefit:  You get to decide titles and placement of your filters!

Data List Block - Filter Configuration Example:

Keyword Dialog Example:

  • Keyword = Use field to preset a keyword search term.
  • Permit Keyword Filtering on Display = Check to allow keyword search in block.
  • Use Search Box value for keyword, when available = Enter value in Keyword field and check to preset.
  • Title (Optional - "Keyword" by default) =  Enter your desired title.
  • Keyword Hint (Placeholder) = Enter help text in field. User will type over it when performing their own search.

System Defined Date Ranges Example:

  • Data Field =  Is the field configured in Schema/Table that is either a Date or Date/Time column type with option Range checked.  *Data Fields may be used one time per a Range.
  • Title = Add the title you desire for this Date Range filter.
  • Subset = Is the Range Attribute Group. The default is Alphabetical, but if you configured another group this is where you make selection.
  • Display As = Select from options for desired display.  *Dynamic Checkbox will provide count.  Lookup type will have different options.
  • Server = Doesn't show the Range in display, but selects data record if applicable.
  • Display and Server = Displays Range in Data List for user to make selection.
  • Filter by Attribute Name = If long list of Available Attributes, use field to search for Attribute by name.
  • Selected Value = preselect a Attribute Value to limit results in List.

Data Column Type Example:

Small Number Range Example:

 

New Column Type - Input for Whole Numbers

Benefit:  You may now build a field that uses whole numbers and not decimals.

Data Column Type Example: *New column "Input for Whole Numbers"

New Column Linking - Properties

Benefit:  Able to connect to 4 additional properties!  When building your column types for data fields, you may now connect to these properties: 

  • End Date
  • Show in What's New
  • What's New End Date
  • Teaser Image Alt Text

View Full Chart for Column Linking

Filter Block & Data List Block New Caching Option

Benefit:   Save on page display load time!  If your blocks don't change often and security is not in place, use this option to cache results and save on page load time.

Public view only, doesn't cache if logged in!

Changes that don’t take effect until after Refresh:

  • Different root selections in tree
  • What’s New filter (*optional filter)
  • Items published in last X days (*optional filter)
  • Default Sort Order
  • N/A  Filter Ranges configuration
    • *Exception Keyword
  • Pagination
  • Limit to X items (*optional filter)
  • Excluded docs
  • Set manual priorities  *over-rides sort option
  • Tags, Lookups, Ranges
  • Audit count

Changes that take effect right away:

  • Caching checkbox
  • Filter Area Title
  • Keyword field filter
  • Filter Zone
  • Adv Tag Options
  • Everything in Configure Your Results display except pagination

Data List Block:

Filter Block:

Page URL Aliases

Benefit:  No more broken links!  If you add, update and delete carefully, you can have old URLs associated to your new Page URL.

A new field has been added to the Properties' tab to support creating more than one URL for a content item.  URLs added in the URL Aliases list will all resolve to the Page URL defined for that item.  If you change a Item's Page URL, the *old version gets automatically put in the Alias list so that it links to that old URL and doesn't break (*This occurs when the change is published and the new version is activated).  To add URL Aliases, select green + and NOTE: takes affect immediately on save. 

There is not a limit or recommended number for URL Aliases, but note that processes might get bogged down if you were to save several hundred aliases.

URL Rules for special characters, the only ones allowed are ?, & and =.  However, neither the & nor the = should appear before a ?.  Further, there should be at most one ?

Validation:

  • At most, one ? is allowed (it signals the beginning of the query string)
  • No & or = before the query string delimiter (?)
  • If defining a query string (?) you have to have parameters.  In other words, you can't just end with ? and have nothing after it.
  • ? signals the beginning of the query string
  • & separates the individual parameters
  • Allows 259 inputs

Options:  Add, Delete, Update & Scroll bar  *Be careful on what you update or delete.

 

If URL Alias conflicts as duplicate to another item's Page URL or URL Alias, a message will display as to path where duplicate exists.  This message is similar to using the "Check Availability" for a Page URL.  If restoring an item that would have a duplicate URL Alias, the duplicate would need to be deleted before save will occur.

 

 

Examples of Invalid URL Alias format and message:

Search and Replace - message if duplicate URL, URL Alias:

Recycle Bin Rule for Page URL & URL Alias:

  • An active page cannot have an Alias URL that is already an Alias URL on a recycled page.
  • There isn't anything preventing an active page from having an Alias URL that is also the Page URL of a recycled page.

Data Editor Block - Submit Record Without Display Login

Benefit:  One less Login to remember!  Use a new Data site for your form submissions!  Allow display side submission of data records!

New Options:  "Allow public access to create, but not edit data"

Checkbox provides the ability to let site visitors fill out an empty form and the data be submitted to a data site.  This will be similar to Forms but submissions will be saved in a data site.  This functionality only allows to create records.  The create requires to give the public user Author rights to the data site folder where the new items are being created.

*User is not able to edit data records through Data List or Data Detail unless logged in.

*The Page with the Data Editor block should allow everyone to view.  If Everyone isn't configured for page security, they won't see the page.

*The Data Editor block should be configured to allow Public Access by checking the checkbox.

 

In the Web Content Management module, the Workflow for Database should be set with Author Public or desired group to allow submission of data records.

 

The Page URL for the Data Editor should be added in Titan Administration module for Database "Default Edit Page".

Where Used Job may be configured per a specific File Folder

Benefit:  Save time by only processing the files in desired folder and not all folders!

Instructions:

  • Existing Titan Clients - Client with past version jobs in place, need to update existing XML.  Examples are below, XML needs the FolderID.  If xml is not updated, existing jobs will error out if you try to run them without a FolderID.
  • New Clients - When you create a new job task, the new xml will be there.  All you need to do is add FolderID.  The Default File folder can be used but then job runs against all folders under it.
    • In Web Content Management module, expand the File folders in left nav tree
    • Mouse-over the desired folder and view DocID # (*This is used for FolderID #).

New XML:

<ConfigArgs><IndexType>Create</IndexType><FolderID>#</FolderID></ConfigArgs>

 

<ConfigArgs><IndexType>Update</IndexType><FolderID>#</FolderID></ConfigArgs>

 

In-Progress XML Report View

Completed XML Report View

 

Full Text Search queries match Inflectional forms of word

Benefit:  Helps find more items by also including ed, s, ing type of term searched.

  1. The column type field doesn't have to be connected to a property. It is automatically connected to Keywords and the other standard SEO fields.
  2. It searches against all the SEO fields and the ones marked for Keyword filtering.
  3. Search was tweaked no for partial searches, it is more like natural language searching on terms and their inflectional forms (-ed, -s, -ing)
  4. There is no searching against Decimal or Whole Numbers.
  5. Example:  Written, write, wrote

New System defined Browse View "SEO Properties"

Benefit:  Saves you time so you don't have to configure the view!  This view can be used to both view existing SEO inputs and to download excel to add SEO inputs in upload.

There is a new system defined browse view called "SEO Properties" for pages, files, events & data.  The order of where the new view lands in list is based on an order value stored in the database.  With the exception for Files, the new view has been set to appear third.

Pages

 Files

Events

Data

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Property fields in SEO Properties View:

  • Page
  • Page URL
  • Page Title
  • Metatag Description
  • Metatag Keywords

SEO Property Fields now have Counters

Benefit:  If you know your display parameters, counter assists you in not exceeding it!

  • Page Name  (255 User Interface Limit / Data Base Limit 255)
  • Page Title  (100 UI Limit / No DB Limit)
  • Metatag Description (No UI Limit / No DB Limit)
  • Long Teaser (No UI Limit / No DB Limit)
  • Short Teaser (No UI Limit / No DB Limit)

Examples:

 

SEO Inputs may be uploaded/updated - Pages, Files, Events (*Not create new)

Benefit:  Saves time and energy on updating all those SEO properties by adding SEO in a spreadsheet and upload at once!  The Page URL is required in excel for upload.

  • Page Name
  • Page Title
  • Metatag Description
  • Long Teaser
  • Short Teaser

Steps:

  1. Select Web Content Management module.
  2. Select existing items - Pages, Events or Files you wish to update the SEO inputs.
  3. Select to include children if you want.
  4. Select the browse view SEO Properties.
  5. Download Excel and save, use this file to enter SEO inputs.

Example of Excel downloaded:

6. Use the Upload option:

a). Upload Content - Pages, Files, Events Example:  *File requires URL for update.

 

b). Upload Data Example:

 

7.  Content Upload Example: *? Instruction - review display. 

  1. Browse to find file.  *File must have the Titan URL for each item.  There are different requirements for Data Upload.
  2. Parent Folder shows section where upload will occur.
  3. List of records with inputs to upload.
  4. Upload Options to select for Upload.  *There are Different options for the Data Upload.
  5. Test Only is available to use to view results before actual Upload.
  6. Upload button to process the upload.

 

Data Upload Example:  *Use the ? to view help Instructions, see link for online documentation for Data upload help.

  1. Browse to find file.  *File must have URL.  There are different requirements for Data Upload.
  2. Parent Folder shows section where upload will occur.
  3. List of records with inputs to upload.
  4. Upload Options to select for Upload.  *There are Different options for the Data Upload.
  5. Test Only is available to use to view results before actual Upload.
  6. Upload button to process the upload.

Upload New URL and/ or Alias URL for a Page URL *Columns have to be in the exact order!

Benefit:  Makes changing multiple Page URL's and or URL Aliases easier by updating in a spreadsheet and changing with one upload!

Rules & Validation:

  • URL Rules for special characters, the only ones allowed are ?, & and = 
  • At most, one ? is allowed (it signals the beginning of the query string)
  • No & or = before the query string delimiter (?)
  • If defining a query string (?) you have to have parameters.  In other words, you can't just end with ? and have nothing after it.
  • ? signals the beginning of the query string
  • & separates the individual parameters
  • The imported item’s URL is created per parent Path (not updated). You won’t see a new Alias URL for the same reason you don’t see one when you change the first version’s Page URL before it has been published for the first time.

  • With an upload of new page URL, if “Skip Workflow” is selected, the update should occur to same version.  The Page URL should just be updated and will not be retained as a URL Alias.

  • Because we allow Data Uploads to create and update items, when you upload to a folder it wants to only process the Page URLs that look like they belong in that folder. That means the Page URLs need to look like they belong in that folder.

  • If more than one URL Aliases in file they need to be separated by semicolon.  The Browse view file should also use semicolon to separate.  You could use separate line in file and add same Page URL for each.

Data Rules:  To change URL in a Data Upload, you have to do one of the following:

  1. Only provide “Page URL” and “New URL”, or
  2. Only provide “Page URL”, “New URL”, and “Alias URL”, or
  3. Provide any number of real columns for that data definition (with the correct headings), and the Page URL column (using the correct heading for column if you linked it) and “New URL”.
    1. If you want to update Alias URL, you can include it too.

 

Upload Alias URL Example:

Upload New URL Example:

 

Upload New URL and Alias URL Example:

 

The Preview Different Size Options Removed

Benefit:  Preview is still available!  Size options were only removed.

The browsers support what Different Size Options did by using tools in their respective Developer Tools.