If you have two actions on a transition, one calling a Mashupscript and another one following that calling an Orchestration (async). If the scripts modifies a value in another item (e.g. an aux table) and the Orchestration reads that modified value sometimes the orchestration will get the pre-change.
Many javascript functions can now be accomplished with form actions. If there are too many they can cause a performance issue. In IE there can be a timeout that occurs.
When there is a pre-transition script on a transition and that transition is run from a web service call, not all field vales that should be set by the script get set.
The relate scripts are correctly created but they never seem to be executed by the migration utility. When running those scripts manually the relationships are created correctly.
The web services authentication user setting that controls the user used for running scripts and web services from notifications is available under the Mail Client tab for Mail Services in the Configurator. NOTE: This only applies to SBM 10.1 This setting was moved to the Notification Server tab under the Common Options section in 10.1.1.1
With MVS deployment, if you write a pre-deployment script in JCL, then when the script is run , all that is returned is whether or not the job got submitted correctly - it is simply a 'fire-and-forget' process. There is no return code from the job, which in turn means that there is no return code sent from any sub-routines run from within the pre-deployment script.
