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 Deployment from Composer with 11.4 breaks Rest Grids if either no results or 1 result (e.g. no array) - browser hangs and CPU spikes towards 99% - 'long running script' error
Deployment from Composer with 11.4 breaks Rest Grids if either no results or 1 result (e.g. no array) - browser hangs and CPU spikes towards 99% - ' long running script ' error
CMS-XML Some listing reports take longer to render and causes unresponsive script error
The data appears to be returned and then the browser runs a javascript to format the results. The formatting process takes so long that the browser may think the script is unresponsive and display an " long running script " error. The error indicates that the issue is not with the database, but with browser rendering.
CMS-XML Pre-filling a journal field (with append) via a pre-transition script no longer works
Pre-filling a journal field (with append) via a pre-transition script no longer works
CMS-XML CreateObject("scripting.dictionary") is no longer creating objects in SBM 11.3
CreateObject("scripting.dictionary") is no longer creating objects in SBM 11.3 in SBM 11.3 due to it becoming case sensitive. This may be seen as an "Object required -- ERR #9" error when executing the script .
CMS-XML UGBase Member function should return a Long Integer
What are the steps to reproduce the problem? Use sample script as an action to a transition
CMS-XML P4DTI operation refresh.py may take an extremely long time on some systems.
This is because currently, the refresh.py Python script re-synchronizes ALL TeamTrack (Business Mashups) items with ALL Perforce Changelists since the inception of the integration. If this integration has been in place, it may be trying to syncrhonize hundreds of thousands of records.
CMS-XML IsBlank(), IsDbBlank(), IsSelected() should say they return Boolean instead of Long Integer
The following three methods in the SBM Script Guide say that the return value for all of these is a Long Integer but in my testing it looks like these all return a Boolean value. The customer wants to know for sure because in their code they are trying to use the actual value without using an If statement. At the end is the appscript I used to test this and the value displayed in the event viewer was always "True" rather than a 0 or Non Zero.
CMS-XML Long ts_internalname and/or ts_name doesn't work with AppScript with Oracle db
The workaround is to not use the ts_internalname in the script (can't be modified after deploy), but to shorten the ts_name in Composer and use that in the script (this can be modified after a deploy).
CMS-XML "select all" on promote when choosing reports takes a long time return the screen
(3) Can take a large amount of time e.g. 1.2 hour to complete - meanwhile you may get lots of the following message from IE that you need to respond "No" to. "A script on this page is causing internet explorer to run slowly. If it continues to run it may become unresponsive.
CMS-XML Long redo messages and "Log On as Another User"
Workarounds: Refrain from using the "Log On as Another User" when testing long redo messages Shorten the Shell.RedoMessage in the script or test with fewer unfilled required fields
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs