The Role allocation view for Users/Groups may not provide visual cues upon role allocation and the checkboxes may not have description labels. This happens mostly with databases containing user/group names with diacritics.
If your MS SQL Server is setup with the Force Encryption value set to yes then you will have to make the following changes for SBM to communicate with it. If your SQL server is setup this way then the Application Engine components will work fine because they connect via ODBC but the JBOSS components will fail to connect via JDBC and need the following changes made to the JDBC connection string in order to connect to the SQL Server database.
If your MS SQL Server is setup with the Force Encryption value set to yes then you will have to make the following changes for SBM to communicate with it. If your SQL server is setup this way then the Application Engine components will work fine because they connect via ODBC but the Tomcat components will fail to connect via JDBC and need the following changes made to the JDBC connection string in order to connect to the SQL Server database.
When the results of a listing report are displayed every other row is slightly farther to the right than the row above it. But values in the Item Id and any other displayed column appear to line up properly
When using the Mashup2009 driver and "import from another SBM database ", you can map the source and destination fields. However, get error "Number of bound columns exceeds the number of result columns" when trying to map the specific values for a single select field. (For example, when trying to map the "new" state in the source to be the "waiting" state in the destination.) State field is just an example.
The doc says that IsFieldEqual will accept a field name or a field ID. However, when you use database field name, it always returns False. The correct value is returned when using the ts_id of the field or you use the field name ( not the database field name ), however the field ID changes between environments and the field name could be changed later in composer and inadvertantly breaking your scripts..
