Monday Apr 01, 2013
Wednesday Sep 19, 2012
By Christopher Karl Chan on Sep 19, 2012
So this blog will focus on BPM Swimlane roles and users from a ADF context.
So we have an ADF Task Details Form
and we are in the process of making it richer and dynamic in
functionality. A common requirement could be to dynamically show
different areas based on the user logged into the workspace. Perhaps
even we want to know even what swim-lane role the user belongs to.
It is is a little bit harder to achieve then one thinks unless you know the trick.
Monday Jul 23, 2012
By Christopher Karl Chan on Jul 23, 2012
Lately customers have been asking a lot about how to version ADF Task Forms in a BPM context.
In BPM 11g (from PS4 Feature Pack onwards) version handling is fairly
flexible and it is now possible to migrate in flight process instances
of the same version to the new version. My colleague Mark Foster has a
great blog article that walks through these concepts.
In addition to migrating the same version of processes we might in some
instances want to have more than one version of the process running at
the same time, for example so that each will finish on their own process
However what happens if these processes contain human
tasks and there is a requirement that the task forms be different for
each version of the process?
Saturday Feb 04, 2012
By Christopher Karl Chan on Feb 04, 2012
There may be many reasons why it might be beneficial or necessary to configure a separate LDAP for your BPM/SOA suite implementation. Corporate LDAPs are often huge, slow, ill maintained, restricted to change and even full of circular references.
One of my customers were setting up their environments for current latest version of Oracle BPM 11g. One of the steps was to configure a directory to handle both authentication and user groups. The chosen LDAP of choice was a poor sister of Active Directory called LDS. I say poor because it is not exactly the same and the AD weblogic providers are designed to work with the elder brother. Therefore the standard procedure of setting up a AD provider just didn't work with LDS, because of some missing attributes in LDS. But I made it work anyway. This is how I did it.