home

ACST Content Standards

RealmMinistryPlatformPDSACSAccountingGivingConnectShepherdGrowth MethodGo MethodMissionInsiteGatherHeadMaster ChildcareTrust CenterData Governance and Business DocsACST Content Standards
RealmMinistryPlatformPDSACSAccountingGivingConnectShepherdGrowth MethodGo MethodMissionInsiteGatherHeadMaster ChildcareTrust CenterData Governance and Business DocsACST Content Standards

What would you like to know more about?

Show Contents

thumbnailACST Content Standards

Publishing

Conditional Processing Rules

ACST has a very complex product offering. It is complex because of product versions (Realm I, C,M, O), myriads of brands, integration between products, and additional personalization under discussion. This reference topic lists our personalization strategy, for filtering content in our ecosystem.

Table 1. Current Filters Used for Personalization
Filter Where Used
Product (any product)
  • Standard DITA attribute that specifies the specific product the content is related to.
  • Use within sitesections and subsections of the sitemap, maps, articles, or elements that contain global content or content used across multiple products. The Privacy Policy is an example of where we use this attribute to filter for each product.
  • There's a value for each product. To view the product taxonomy, in the upper left corner of the CCMS, click the Administration Menu > Taxonomy > Product.
Audience (any product)
  • Standard DITA attribute that specifies the intended audience of the content.
  • Use within sitesections and subsections of the sitemap, maps, articles, or elements that contain global content or content used across multiple products.
  • Approved values in use:
    • Administrator
    • Employee
    • Leader
    • End User
Custom Product Version (Realm & Giving)
  • Custom filter built on the props attribute to differentiate features in different versions of Realm.
  • Use within sitesections and subsections of the sitemap, maps, articles, or elements that contain global content or content used across multiple products.
  • These values can be used in combination with accountingpackage, giving, and product version. Example: giving1_accounting1
  • Approved values in use:
    • inform
    • connect
    • multiply
    • office
    • giving1 (realm giving)
    • giving2 (eGiving
Accounting Package (Realm)
  • Custom filter built on the props attribute to differentiate features in different versions of Realm.
  • Use within sitesections and subsections of the sitemap, maps, articles, or elements that contain global content or content used across multiple products.
  • Approved values in use:
    • accounting1
Network Version (Realm)
  • This is a custom field built on the props attribute.
  • Currently deprecated.
deliveryTarget
  • The deliveryTarget attribute is used to specify the intended delivery target of content, such as "html", "pdf", or "helpdrawer". It is a replacement for the now deprecated @print attribute and is specialized from the @props attribute. This filtering attribute is new in DITA 1.3 and is intended for use with a set of hierarchical, controlled values.
  • Approved values in use:
    • PDF
    • helpdrawer
    • portal
    • Note: There are other values in the taxonomy that will be moved to a new internal use taxonomy.
Platform
  • Not currently in use.

Guidelines for Using Conditional Taxonomy to Personalize

The values for conditional processing are stored in the Taxonomy and "bound" to the user interface in the attributes panel. Note that there are also taxonomies used for faceted search, such as media type, content type, etc.

Employee Filter (Part of the Audience Taxonomy)
  • When the filter is applied in the sitemap on the map or section to be excluded, this requires merging the sitemap or applying the same filter from master to production.
  • You can test employee filters in the testing portal or production, but not staging. The reason for this is that Heretto does not apply the full login to the staging portal.
Ditavals
Ditavals are small files that contain the rules the DITA OT uses to filter content in or out. Ditavals are stored in the CCMS at master > acst-global-reuse > _Ditaval_Files. The ditaval in the following codeblock will deliver to the reader Realm Iinform + Realm Accounting content + and only the content targeted at the helpdrawer. 
<val>
    <prop action="exclude"/>
    <prop action="exclude" att="product"/>
    <prop action="exclude" att="realmplan"/>
    <prop action="exclude" att="accountingpackage"/>
    <prop action="exclude" att="deliveryTarget"/>
    <prop action="exclude" att="deliveryTarget" val="portal"/>
    <prop action="exclude" att="deliveryTarget" val="PDF"/>
    <prop action="include" att="product" val="realm"/>
    <prop action="include" att="realmplan" val="inform"/>
    <prop action="include" att="product" val="Realm_Accounting"/>
    <prop action="include" att="accountingpackage" val="accounting1"/>
    <prop action="include" att="deliveryTarget" val="helpdrawer"/>
</val>
portal_content-audiences map
This map is located at the bottom of the sitemap. Any new audience profiled by Realm or future oAuth must be contained in this map as a data reference. The values are passed from the software product or oAuth to the portal for filtering.

Last updated: March 3, 2026

Related Articles: