The CSC Key fields are used:

key1 = keyword is the record selection or linkage field
key2 = The sku for the suggestive selling BuyButton item to be included

notes:

• The SKU used for retrieving suggestive sell items will be the first matching SKU returned from the showcase items query.
• The buy buttons will be seperated into sections delimited by the AttributeList.
• The title and suggestive selling text for these items is defined in the CSC Suggestive Selling Content Record (ContentType = 1)
• The CSC system will use all SQL matching BuyButtons. All matching items are sorted by the FullName
• The keys must be listed in order of significance.
• The SQL 'LIKE' operator is used on keywords so substring matching will occur if the term is a sub-string.
• You must specify at the minimum key1 and key2.
• In the e-store framework the configuration keyword cscShowCaseSuggestiveSell = true
• If you are using Hidden Sort Characters then those hidden characters must also be present in the keys.

One select query per showcase page is performed to retrieve suggestive sell items for display. The query can match an unlimited number of suggestive selling items records.

Select * from items, itemsExt
where sku in (Select rtrim(key2)
from ContextSensitiveContent, items
where ContentType = 8
and keywords like '%contents of key1%'
and sku = the first SKU retrieved for the showcase product
and enabled = 1)
and items.itemcodeId = itemsExt.itemcodeid
order by fullname

SEARCH ENGINE CONTENT

This content is displayed on any website page as merged or replaced content. This CSC function requires custom ASP webpage development on the site. The key purpose of this Search Engine CSC is to dynamically display different webpage content based on the search engine terms which were entered into the such engine (such as Google or Yahoo).

The CSC record for this content is ContentType = 2.

The CSC system will first attempt to match all four keys (key1,2,3,4), then three keys (key1,2,3), then two keys (key1,2), with one key matches discarded.

The CSC Key fields are used in an SQL select clause to match incoming HTTP Referral information as follows:

key1 = Search Phrase 1
key2 = Search Phrase 2
key3 = Search Phrase 3
key4 = Search Phrase 4

notes:

• The CSC system will use only the content from the first SQL match. Additional content from additional matches will be discarded.
• The keys must be listed in order of significance.
• The SQL 'LIKE' operator is used on all three keys so substring matching will occur.

The CSC ContentLocation field must match root the webpage being loaded.

E-MAIL BROADCAST

This content is used for creating content for e-mail broadcasts or for I-CRM e-mails. The CSC subsystem can be used to create standard set of reusable e-mails or a one time e-mail. Using CSC is the typical way e-blast are authored and sent.

There are two different kinds of CSC E-Mails:

• A CSC e-mail blast which is sent from the CSC admin page uses the normal broadcast system and sends the same email to everyone.
• An I-CRM CRC e-mail blast which is run by an I-CRM job and uses a CSC record as a template, sends personalized emails.

In the case of I-CRM e-mails the CSC content can contain I-CRM mail-merge variables which are replaced with values taken from DB records.

The CSC record for this content is ContentType = 3.

These entries for e-mail broadcasts are:

• Key1 = title/name of record (this is not used in the email, this is only for record keeping purposes).
• Key2 = the Type for an advertisement which will be the header. This value is typically = 100 (the universal header advertisement).
• Key3 = the Type for an advertisement which will be the footer. This value is typically = 101 (the universal footer advertisement).

Make sure all records (CSC and Advertisements) are enabled.

The format of the e-mail:

From: sales@mybiz.com
To: mycustomer@theirbiz.com
Subject: You have left un-purchased items in your shopping cart

VERY IMPORTANT Do not change the record being sent until the e-mail blast has completed. Do not run more than one broadcast job at time. Changing the record before the e-mail blast has begun or running multiple jobs at the same time can result in unexpected results such as mixed subject lines or duplicate emails beging sent out. To check status on an I-CRM job load either the CSC Admin page or Job Queue. When an I-CRM job completes, an email will be sent to the return address set for the message AND to the CC Mail list configured for the storefront.

CATEGORY DRILLDOWN DESCRIPTIONS

This content is used solely as a means of adding a description for category icons when in Matrix product browsing mode. The content of each CSC will be displayed next to the category icon in a similar format as seen in the product display level of drilldown browsing.

The CSC record is related to a category by key1.

E-store framework the configuration keyword catDrilldownLabeling = true OR listingCatDrilldownLabeling = true

The CSC record for this content is ContentType = 5 for products and 6 for listings.

These entries for category labels are:

• Key1 = category name - This must be the same entry as found in items.category or listing.category record.
• Key2 = n/a
• Key3 = n/a

Note: Categories flagged with an "@" in the category name must use the full category name including the "@" in the category name field of the CSC record.

BRAND DRILLDOWN DESCRIPTIONS

This content is used solely as a means of adding a description for brand icons when in Matrix browsing mode. The content of each CSC will be displayed next to the brand logo (icon) in a similar format as seen in the product display level of drilldown browsing.

The CSC record is related to a brand by key1.

E-store framework the configuration keyword brandDrilldownLabeling = true

The CSC record for this content is ContentType = 7.

These entries for brands labels are:

• Key1 = brand name - This must be the same entry as found in itemsext.brands record.
• Key2 = n/a
• Key3 = n/a

SUBCOMPONENT HTML CONTENT MANAGEMENT

CSC can be used to manage the static SUBCOMPONENT HTML content on any webpage (see Dynamic Content Management for more details). Using the CSC admin page is user friendly means of accomplishing the same type of static content management which is done via FTP and an off-line editor.

KNOWLEDGE-BASE OR MESSAGE BOARD

CSC can be used to create newsletters, mini-blogs, message boards, bulletin boards, announcement, or other collections of articles and factoids.

This content can be used for e-mail broadcasts.

The CSC record for this content is ContentType = 1000 - 2000; where each numeric value is a separate knowledge-base

These entries for are:

• Key1 = title/name of record.
• Key2 = the Type for an advertisement which will be the header.
• Key3 = the Type for an advertisement which will be the footer.
• Key4 = searchable key word(s).

The system is linked into the e-mail broadcasting system, so with the push of button you can send an article in an e-mail blast to all customers who have signed up (think e-mailed newsletter). In an e-mailed newsletter, up to three type 10 ads will be included at the end of all broadcasts.

SendSafe comes with a Knowledge-base reader. This webpage is designed to index and display a set of articles. To use the Knowledge-base reader, open the webpage: Store.kbreader.asp?Ctype=1000 (where Ctype = the set of records defined by ContentType).

• Store.KBReader.asp - Top level display tool which handles listing and viewing of records.
  This file contains includes for both: SendSafe.KBLister.inc.asp and SendSafe.kbreader.inc.asp

• SendSafe.KBLister.inc.asp - Tool which displays a list of Knowledge base articles with hyperlinks to the article itself (with a target=_parent)

• SendSafe.kbreader.inc.asp - Tool displays a single article formatted within a box (parameter KBIDX=)

The reader displays a dated list of articles chronologically at the top of the webpage. Clicking on any article will open the article in the "viewer pane" located directly below the list. In the example below, someone has clicked on the "Electric cars of the Future" link.

Set of articles are managed with a very easy to use Admin page. Articles can have any kind of HTML, pictures and text. There is a built in HTML editor on the admin page OR you can use some other editor and then copy & paste.

BLOGS

CSC can be used to create full featured blogs.

This content can be used for e-mail broadcasts.

The CSC record for this content is ContentType = 3000 - 10000; where each numeric value is a separate blog

These entries for are:

• Key1 = title for article
• Key2 = the Type for an advertisement which will be the header during email blasts.
• Key3 = the Type for an advertisement which will be the footer during email blasts.
• Key4 = used internally for customer editing of blog entries (contains the parent IndexKey for a temporary record)
• ContentType = blog ID (3000 - 10000)
• Content = HTML Content of article
• Enabled = This blog entry is approved and can be displayed
• CSCheadlineFormatCode = A code which controls how each entry is displayed on the headline page
• CSCArticleFormatCode = A code which controls how the article is displayed
• CSCLastShown = This is the last time this article was shown
• CSCImpressionCnt = This is the number of times this article has been shown
• CSCClickCnt = reserved
• CustomerID = This is the customerId of the person how added the article
• CSCRanking = reserved for future control of the order of display of headlines
• CSCVotes = reserved for reader voting
• CSCImpressionBalancer = reverved for fuyre use to control balancing of displays of headlines
• CSCLastRevised = This is the last time this article was revised
• RevisionCount = This is the number of times this artcile has been revised
• CSCLinkageCode = This is record linkages from comments to a parent article
• CSCPublicationProcessingStep = This is the publication processing Step
• CSCProcessingStatusMessage = This is the last status message regarding publication
• CSCAuthor = Author's name.
• CSCAltSummary = If present this summary name superceeds the automated summary.
• CSCReadMoreLink = Text used for the read more link. The link can also be a site relative link to a file to open in a separate browser window. Enter the relative location + "#" + text to display for link i.e. "en/images/mypic.jpg#my link text.
• CSCBoBackLink = Text used for the go back link.

Review and approval for Publication (blog moderation) is required before a blog entry is displayed on the site. An entry will be displayed when the following fields are set:

• Enabled = 1
• CSCPublicationProcessingStep = 3

Records with a CSCPublicationProcessingStep=>1 are canidates for publication. Records with a CSCPublicationProcessingStep=0 are being edited by the visitor. You can find all records in CSCPublicationProcessingStep1 or 2 by performing a FIND operation then going through each record in the list selecting or rejecting publication.

Rejecting publication can be done manually or by using the [Reject for Publication] button. It is recommend that the [Reject for Publication] button be used. This button will set Enabled=0 and CSCPublicationProcessingStep=3 (i.e. moderation tasks are complete for this record). Automated notication of blog entry status changes are not provided to the author in any way.

Formatting of headlines is controlled by each record by the CSCheadlineFormatCode. Each headline is display in a separate content box arranged one after the other vertically on a page. Beyond the verticial orientation, all other fortmat is controlled by the code.

Headlines:

• Headline code 1 = Standard vertical layout with picture CSCpicturefileB, title, and summary one below the other. The read more link is at the end of the summary. Horizontal lines seperate each headline. BlogFmt1
• Headline code 2 = Abbreviated horizontal layout with picture CSCpicturefileB on the left and a text block on the right consiting of: date,author, & title (no summary). The read more link is at the end of the the content block. BlogFmt2
• Headline code 3 = Press Release layout with date on the left and the title (no summary) on the right. The read more link is at the end of the the title block. BlogFmt3

Articles:

• Article code 1 = Standard vertical layout with picture CSCpicturefileB, title, and article one below the other. The go back link is at the end of the article. BlogArticleFmt1
• Article code 10 = Same as #1, standard vertical layout with picture, title, and article one below the other. The difference is the picture is CSCpicturefileB. The go back link is at the end of the article. BlogArticleFmt1
• Article code 2 = This is 100% Free-form content except for the return (goback) link. All content other than the link it derrived from the ContextSensitiveContent.Content DB field.
• Article code 3 = Press Release layout title, date and release one below the other. CSCpicturefileA will be displayed if present. The go back link is at the end of the release. BlogArticleFmt3
• Article code 4 = Same as #1, standard vertical layout with picture (the first 7), title, and article one below the other. The go back link is at the end of the article. BlogArticleFmt1

Each headline box is not placed in a table row. Each line is a paragraph break or some other height controlled break. Entire groups of headlines can therefore be easily placed within a table cell (column) as part of top level page layout.

Formatting headlines and articles using CSS is accomplished with the following selectors. Each selection is the same name for each format code (except the number is different i.e. BlogFmt1, BlogFmt2, etc.). There are two sets of CSS selectors; one for headlines and one for articles.

• BlogFmt1HR
• BlogFmt1Title
• BlogFmt1Author
• BlogFmt1Dateline
• BlogFmt1Revision
• BlogFmt1bart
• BlogFmt1Goback

• BlogArticleFmt1HR
• BlogArticleFmt1Title
• BlogArticleFmt1Author
• BlogArticleFmt1Dateline
• BlogArticleFmt1Revision
• BlogArticleFmt1bart
• BlogArticleFmt1Goback

The system is linked into the e-mail broadcasting system, so with the push of button you can send a blog article in an e-mail blast to all customers who have signed up (think e-mailed newsletter). In an e-mailed blog article, up to three type 10 ads will be included at the end of all broadcasts.

Basic Article navigation is accomplished with bart codes. The same ASP page which displays the headlines MUST ALSO display the full articles. This dual purpose is accomplished with URL parameters to select an operating mode for the ASP page.

To display a full article a URL parameter is added to the URL the current page. This parameter is called bart code. The bart code is it indexkey for the article to display. These URL links and parameters are automatically generated by the headling listing functions.

Public Posting is enabled by setting "allowBlogPosts = true" and "blogEditPage = "file.asp" must equal the page which performs editing; both these params are set in the pageconfig.inc.asp e-store framework config file. You must also set up a "post label" in the CSCReadMoreLink db column if you want a label other than "post new blog." If the CSCReadMoreLink contains two strings delimited by an "=" then the first string will be the read more of this article link and the second string will be the post a new blog string.

If this functionality is enabled an "Post New Thread" link will be displayed next to each "Read More" link on the headline page. Clicking this link will open a new article in the editor.

Editing blogs after posting is easy. If this functionality is enabled an "Edit" link will be displayed below the article if you are logged in as the author. Clicking this link will open the article in the editor.

To enable editing, make sure the editAllowed parameter is set TRUE in the advancedBlogArticle() function.

SendSafe comes with tools to display blogs:

• blogHeadlineIndex() - Displays headlines
  • blogHeadlineIndexRenderer() - headling primative
  • openBlogHeadlineRecordSet() - open headling list primative
• blogArticle() - Displays articles
  • advancedBlogArticle() - advanced function with more options

E-Store framework setup: