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 Improve garbage collection for orchestration workflows
When orchestration engine consumes a lot of memory the whole installation slows down and the memory is not released in the next half hour or so. Often user is forced to reset JBoss in order to get the SBM running to satisfaction. SBM should release the memory occupied by orphaned objects as soon as the orchestration workflow finishes executing.
CMS-XML A big obstructing white box can appear on certain pages of the Application Administrator under certain versions of SBM and Internet Explorer
A user running 10.1.4 or 10.1.4.1 of SBM may have a big white box appear on certain pages of the Application Administrator (aka Admin Portal) that blocks their view of the webpage's content behind the box, namely under the details section of any workflow or project.
CMS-XML A big obstructing white (or sometimes transparent) box can appear on certain pages of the Application Administrator under certain versions of SBM and Internet Explorer
A user running 10.1.4 or 10.1.4.1 of SBM may have a big white or invisible box appear on certain pages of the Application Administrator (aka Admin Portal) that blocks their view or ability to click the content behind the box, namely under the details section of any workflow or project or on a default fields page
PDF Performance Improvements in SBM
• Improved Diagnostics ‐ Diagnostics now run at server startup and detect whether the SBM Orchestration Engine is able to execute orchestration workflows . Results are reported in the
PDF Orchestration Scaling and Design in SBM
Well-designed orchestration workflows are concise, well-annotated, and partitioned in logical groups. Each such group in these workflows should represent a business function in a process and handle Orchestration Scaling and Design in SBM 7
PDF Best Practices for Concurrent Development with SBM 10.x
We do this by prohibiting those design components that have a runtime presence (i.e. to which this requirement applies) from being created directly in a patch context. For example, the following items cannot be created new when operating in a patch context: • Tables • Fields • Selections • Application Workflows • States • Report Definitions
CMS-XML SBM Composer Field Mappings Ignore Field Ordering in Locked Event
When an event definition is locked, all defining characteristics of the event are saved and should be used anywhere the event is used, such as in other process apps. However, transition actions generate the event using a different field order than that defined by the locked event definition. After the orchestration workflow runs , in SBM Application Repository, an ERROR message with text “Error mapping data with field ‘fieldname
PDF SOO Upgrade Guide
(It is recommended that you upgrade the SDM solution to take advantage of the latest features.) If you want to preserve your current workflows and data (forgoing the latest versions of the SRC and SSM process apps), simply run the SOO installer and configure your installation using SBM Configurator as described in Chapter 3: Upgrading the Installation [page 11]. This upgrades just the framework files and completes the installation upgrade phase.
CMS-XML Item Type not checked before running a transition
1. In SBM Composer, go to Workflow Design > select a transition (e.g. Assign) and click the “Restrict by Type” tab in the Properties editor. ... 3. Now, go to SBM User Workspace and login as User Ethan. ... 5. Meanwhile, User Claire logs into SBM User Workspace and updates Item 001. ... SBM should prevent the “Assign” transition from being run since the Item Type is now set to B
CMS-XML How does the December 31, 2020 end-of-life for Adobe Flash effect SBM (Solutions Business Manager) and SSM (Service Support Manager) and RLC (Release Control)?
If you are running an SBM version older than 11.4, you need to upgrade as soon as possible. Once Flash is disabled, you will no longer be able to render Rich Graphical Reports, add/update users or permissions, make workflow or project level updates, add/update notifications, etc. SBM versions 2009 R1 through SBM 11.3.1 ... Micro Focus removed Flash from these areas beginning with SBM 11.4, but we recommend upgrading to SBM 11.4.2.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs