| |
Results |
|
Importing a blueprint allows database name to be changed
|
Per the SBM Composer Guide - The following list describes the items that are locked after a process app is published:
|
|
|
|
Composer: allow underscores in DB names
|
Composer: allow underscores in DB names
|
|
|
|
Underscores not allowed in DB names for fields and tables
|
Underscores not allowed in DB names for fields and tables
|
|
|
|
File-Attributes have a strange dbName in WebService, e.g. "File: nnn", and not the DB-Name as defined in the composer.
|
File-Attributes have a strange dbName in WebService, e.g. "File: nnn", and not the DB - Name as defined in the composer.
|
|
|
|
After upgrade Composer fails to validate if table database name >24 characters. Worked in previous version.
|
Composer will not fail to validate if there is a table db name with length of greater than 24 characters, but it will not allow users to type in new table db names greater than 24 characters.
|
|
|
|
SBM 10.1.5.2 loses spaces in database names
|
If one or more of the SBM Databases are configured to use a name, which contains spaces then upgrading this configuration to 10.1.5.2 will strip the space characters from the database names rendering them unusable. For example if the Common Log database is named "CL DB " it will be renamed to "CLDB" after applying the configuration which then in turn means the DB connection will fail.
|
|
|
|
Process app does not list incident type values for restricting a transition by type
|
An incidents process app upgraded to SBM that uses the Incident Type system field does not list the incident type values when trying to restrict a transition by type. Also, when clicking the "Edit item types" link at the bottom of the Restrict By Type tab on a transition, you are taken to the primary table, but the Incident Type field is not selected. This is caused by Composer not recognizing the Incident Type field ( database field name of "INCIDENTTYPE") as being the field that is storing item types.
|
|
|
|
How can I find the name of the report associated with a "Reference Name" and the project it resides in to troubleshoot the Embedded Report Widget?
|
Running the following sql query against the application database will give a list of all reports along with their "Reference Name " and "Report Name " SELECT TS_PROJECTS.TS_NAME AS Project_Name, TS_REPORTS.TS_NAME AS Report_Name, TS_REPORTS.TS_REFERENCENAME AS Reference_Name, TS_PROJECTS.TS_INTERNALNAME AS Internal_Name
|
|
|
|
The specified schema name either does not exist or you do not have permission to use it
|
The specified schema name either does not exist or you do not have permission to use it
|
|
|
|
Mashup: special characters in field database name cause Publish to fail
|
Mashup: special characters in field database name cause Publish to fail
|
|
|
