Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML How To: - Version Manager and/or System Administrator wants to setup archive directories so that user do not have delete rights on an NT Server
This policy should result in a minimal amount of data loss and/or down-time.
CMS-XML How to modify the subject line of an outgoing item email
The resulting email a user receives when you send one out from an item is composed by two different template files which both construct your email's subject line. ... This line is what pre-populates the subject field that you see when you go to send an email from an item . ... The resulting auto-generated subject line you should see would resemble something like this: ... No matter what templates you change, be sure to backup your existing ones and perform a "Put files into Database" in the System Administrator after saving the changes.
CMS-XML Change the Text Color of Inactive Items
The example below demonstrates how to change the color of inactive items to red. ... 4. From SBM System Administrator , select ... 5. Stop and start your Web server and clear your browser cache for the change to take effect .
CMS-XML Exception thrown while trying to restore record from archive in SBM 10.1 and newer
Attempting to restore an item from archive in SBM 10.1 and newer after upgrading from a previous version can result in the following error message: "Exception thrown while trying to restore record from archive Insert Error: Column name or number of supplied values does not match table definition."
CMS-XML After making an archive update, user gets: Serena PVCS Version Manager could not read the information stored in the archive ""
As a result the actual archive was not changed, so there is no permanent damage, but the archive change the user tried to make has been lost.
CMS-XML "The item could not be found" error when trying to view item due to data truncated error
"We're sorry, but the last operation caused an error. The last operation resulted in an error, but the following unrecognized error code was received: The item could not be found."
CMS-XML Mashup Script may cause unexpected results when using UpdateWithLock() in a Shell.Item context
If you are using Mashup Scripts where you have a Shell.Item, invoking the Ext.UpdateWithLock() function may cause unexpected results to the current item. For example, if you are using Mashp Script to write to a field on the current item in a Pre- or Post-Transition context, in one case, trying to UpdateWithLock causes the PROJECTID field to be set to zero (" 0 "). That makes the item unaccessable by anybody.
CMS-XML KM-Dim9: File Get hangs on the Results dialog; Add Item Results dialog flashes but fails.
When trying to Get File through Web Client, the results dialog hangs. When trying to Add Item through Web Client, the Results dialog flashes and disappears, but item is not added.
CMS-XML PBrowse/PVIEW of VSAM data set results in PDS961E VSAM POINT error at RBA=00000000; Feedback=D708009C
CMS-XML KM-Build6: Evaluation of Builder results in directory listing of files being displayed when trying to connect to Builder
The license must be pasted into the License Manager GUI and the license.ini file, located in the installation directory tomcat\webapps\openmake.ear\openmake.war\license, must be modified to point to the license server.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Working with items, part 1 (demonstration)
This Dimensions CM demonstration shows you how to perform impact analysis to determine which files are affected by specific changes

Additional Assistance

  • Submit a Case Online
  • FAQs