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 SBM 10.1.5, in an orchestration workflow rename an app script crashes composer - Error in Main()
SBM 10.1.5, in an orchestration workflow rename an app script crashes composer - Error in Main()
CMS-XML "Publish" Task Plan should be renamed to "Unlock" or something more descriptive
"Publish" Task Plan should be renamed to "Unlock" or something more descriptive
CMS-XML Renaming view in task plan doesn't hold after reloading applet.
In the 2009 R1 task plan you can right click in the top left corner to see a list of pre-defined views with specific columns selected. If you rename one of the views to something meaningful to you it appears to let you and hold onto your new name but if you reload the applet the name will go back to the default label or project name.
CMS-XML An orchestration is no longer run after renaming it
If you look at the Alfeventmanager.log, you will see the event being received, but it will not match to a workflow . This is because the event type name is defined using a combination of the transition name and the orchestration name.
CMS-XML Linked field text is not updated when field is renamed
This is only a problem for forms created directly from the mashup explorer tree. If the form is created from a workflow /state/transition form property, the change is propagated as expected.
CMS-XML Importing blueprint breaks the event maps as workflow name truncated
To workaround this you must rename the workflow in Composer rather than taking the automatically truncated value. This will ripple the change through to the event maps. You will then need to remap the events correctly.
CMS-XML Workflow diagram opens to blank window
When a user clicks on the workflow diagram inside an item, it opens to a blank window. This is due to an ampersand (&) in the Application Workflow name. You can work around the problem by renaming the Application Workflow name in Composer and redeploying the application.
CMS-XML Unable to add sub-workflow if name would exceed 32 characters in length
To workaround this you need to rename your application to have less characters.
CMS-XML Renaming orchestration causes orchestration to run twice
Renaming an orchestration will cause the orchestration workflow to run twice after the renamed orchestration is deployed. This can be verified by the orchestration workflow showing as running twice in the common log.
CMS-XML After upgrade to SBM 10.1.3+ orchestration workflow may get error "Invalid item id 0 for table 0."
For standalone Process Applications, the fix is self-contained and there are no issues. However, a problem arises if the field, any of "Item Id", or "Project", have been renamed and exported events are being used in process applications that were created prior to SBM 10.1.3.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs