Open topic with navigation

TIBCO Business Studio™ - BPM Edition 5.4.0

# What's Changed?

Some features that were available in pre-version 5.x ActiveMatrix BPM are no longer available in ActiveMatrix BPM version 5.x and newer.

Feature | Description
--- | ---
BPM Projects | There are some changes to BPM projects. Previously, you could create projects for destinations other than for ActiveMatrix BPM, as well as for other add-ons like simulation. This is no longer the case. There are no other destination environments. Therefore, configuration for destination environments is no longer shown. The existing BPM Developer Project now changes to BPM Process Project. You must have separate projects for business object models and organization models. Note: TIBCO Business Studio - BPM Edition provides a quick fix to move business object models or organization models into dedicated projects.
Web Services | ActiveMatrix BPM version 5.x+ does not support: Using web services with WSDL documents. You must convert web-service invocation tasks to REST service tasks that invoke equivalent REST services. Exposing service operations that external clients or other processes can invoke using WSDL documents. Any of your processes that were previously exposed as web services can now be called using the run-time public REST API. Content and configuration relating to WSDL documents is removed on importing pre-version 5.x ActiveMatrix BPM projects to version 5.x+. See WSDL Activities for more information.
Data | Run-time business data internal representation has changed from XML to JSON which means that XML is not supported as a mechanism for creating business object models. Process data fields are now wrapped in a `data` object. See Scripting.
Data mapping | As data internal representation is changing from XML to JSON, data-mappings are being standardized for the data mapper grammar. All JavaScript/XPath mappings for all WSDL related activities; service task, receive task, send tasks, message events, catch WSDL fault events and all JavaScript mapped to non-WSDL related event / task types (sub-process, signals, catch error) are automatically converted to data mapper grammar, Note: You can use pre-version 5.x TIBCO Business Studio - BPM Edition side-by-side with version 5.x TIBCO Business Studio - BPM Edition. This means you can look at your data mappings in your original project to help you re-map your data in a new project. See Data Mapping for more information.
Forms | Some API methods are different between pre-version 5.x and version 5.x. When importing pre-version 5.x projects to TIBCO Business Studio - BPM Edition, the API methods are converted. See the TIBCO Business Studio™ - BPM Edition Forms User's Guide.
Scripts | As data internal representation is changing from XML to JSON there are changes to the JavaScript capabilities. For example, multiple instance data is now represented as arrays rather than specialized list objects. Many JavaScript capabilities have also been standardized between process scripts and form scripts. Factory methods have also changed. See Scripting.
Business Object Models | The following are changes to Business Object Models: Existing Business Object Models that were generated from WSDL (previously in the Generated Business Objects folder) are automatically moved to a Business Objects folder. This is because they might still be used in processes, even if they are not used to invoke WSDL services. A new concept of a terminal state is introduced. All case classes must have a case state attribute and that attribute must nominate the case state enumerations that indicate when a case is complete. You must set a case to one of its terminal states when there is no more work to be done on a case. The Case Identifier attribute has changed. You can choose to generate case identifiers automatically, or enter them manually. If you choose Auto, the Case Identifier can include a prefix and/or a suffix. For example, UK-1234-A. See Case Identifiers. Some BOM primitive types are no longer supported: Attachment, DateTime, Duration, ID, Integer, Object.
Deployment | You no longer export your project as a DAA (Distributed Application Archive). Instead, you generate deployment artifacts (RASC (Runtime Application Shared Concept) files). These files are deployed using the ActiveMatrix BPM Administrator. Generating deployment artifacts is now done using the Deployment menu when right-clicking a project in TIBCO Business Studio - BPM Edition.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO Business Studio™ - BPM Edition

Copyright © 2015-2023. Cloud Software Group, Inc. All Rights Reserved.