Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML 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:
CMS-XML 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.
CMS-XML 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
CMS-XML Database Table Name editable after deploy.
Database Table Name editable after deploy.
CMS-XML Cannot connect to Application Repository is database name contains & symbol
Cannot connect to Application Repository is database name contains & symbol
CMS-XML AppScript method IsFieldEqual always returns False when using Database Field Name
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..
CMS-XML Deployment fails for database field name of TS_ID or TS_TS_ID
Deployment fails if the database name of a field in the table editor in SBM Composer is TS_ID, or if the database name of a field in a blueprint file is TS_TS_ID.
CMS-XML Cannot promote Global Process App if it contains a user with an apostrophe in name e.g. John O'Neil - ERROR -- An exception occurred while attempting to fetch a record count or a record integer value from the database.
record integer value from the database . [(|TTexcIDS_EXC_RETRIEVE_DATA|)]
CMS-XML Long ts_internalname and/or ts_name doesn't work with AppScript with Oracle db
When referencing ts_name or ts_internalname in ts_states with an app script, if either is over 30 characters, it fails with "ORA-00972:Identifier is too long" which is due to an Oracle limitation. It appears we accommodate this limitation in other areas in Composer when creating names /internal names , States can still be created with long names /internal names .
CMS-XML Notification Templates - Brackets in file name cause duplicate database entries
Notification Templates - Brackets in file name cause duplicate database entries
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs