Working with SalesLogix Style Schemas

In the Application Architect many quick form control types have a Style Schema attribute.  If you select from the drop down you can see two defaults “NegativeNumber” and “Bevel”.

If you look at the Application Help file it talks about the Style Schema as:

Select a value from the drop-down list.

This property can be set at design time from a predefined list that can be modified in the configuration located at: ConfigurationGlobalStyleSchemeTypes.xml.

This property can also be set at run time using expression binding logic. For example, the expression mapped to the StyleScheme property will set the property to ‘NegativeNumber’ if the Account.Type is ‘customer’.


The StyleScheme names defined in the configuration file are mapped to the CSS class names in the Web deployment

Looking in the Virtual File System explorer in the specified location you will notice this file does not exist.  The options available for this Style Scheme drop down are actually stored in an external file XML on the local computer running Application Architect.  The location of this file is in C:Documents and SettingsAll UsersApplication DataSagePlatformConfigurationGlobal.  The file is called StyleSchemaTypes.xml.  If you want to add a custom style drop down option you would need to modify this file like shown here:

<?xml version=”1.0″?>
<styleSchemeTypeConfiguration xmlns:xsi=”” xmlns:xsd=””>

After you modify the XML file you will need to close and re-open Application Architect in order for this new option to be visible.

So once you have the Style Scheme drop down option populated what does this do?  Well it will apply the custom style scheme class with the name specified from the sage-styles.css file in the deployment the form is for.  The sage-styles.css file is located under Portal Manager…Support Files…CSS in the Application Architect.  Once you define a Style Scheme for a control, once the quickform is deployed it will inherit those style attributes as defined in the sage-styles.css file.

Of course you could always type in the style scheme instead of modifying the external XML file to have the option in the drop down list. However, since the name specified must match exactly it is much more convenient to have pre-defined options you can simply choose from.  Just be aware that since this file is stored locally on each computer running Application Architect it would need to be updated on any computer that will use the Application Architect.  Also be aware that executable updates in service packs or hot fixes can overwrite this file and you may loose your custom options.



Kris Halsrud

Kris Halsrud is a Senior Analyst / Developer for Customer FX Corporation.

Submit a Comment

Your email address will not be published. Required fields are marked *

Subscribe To Our Newsletter

Join our mailing list to receive the latest Infor CRM (Saleslogix) and Creatio (bpm'online) news and product updates!

You have Successfully Subscribed!