From the ORCL New Features Doc -
The Process Asset Manager (PAM) is BPM’s business process repository used to provide seamless collaboration across BPM Process Composer and BPM Studio clients. Both these clients publish projects to PAM which interfaces with source control for versioning and management of BPM assets. Key attributes of the Process Asset Manager are:
» BPM Project lifecycle management
» Integrated source control and versioning
Let's debug the fault handling demo process, from the previous post - in that scenario
process A (callingProcess) called process B (calledProcess) via the Validate activity.
Here is the calling process
Time flies and here is the third edition of the new podcast/screencast cross-over series "Developer Interviews". I had the chance to talk to Christian Posta (@christianposta) last week. He is a Principal Middleware Specialist/Architect at Red Hat and well known for being an open-source enthusiast and committer on Apache ActiveMQ and Apache Camel.
These are used for setting business specific constants and can be overridden for an Organization Unit.
If there is no override value for Org Unit, the returned value will be the default value.
So how do these work?