Workflow Process Business Objects

April 12, 2007 at 8:50 am 4 comments

A first contribution from elsewhere! Outstanding. Nathan kindly offered this note in return for ‘getting famous’. Not sure I can help with that, but everyone has to start somewhere…

I did this trying to prototype a problem I had for an interface I was working on. When you setup a Workflow Process you must assign it a Business Object, or else a whole heap of functionality within that Workflow Process does not work i.e. you cannot select Business Components etc.

My Workflow Process was triggered by a Runtime Event, and all was fine for the UI contexts where the business component of the Workflow action matched the primary business component of the UI. However, when I was in a different business object, the Row Id passed was that of a different Business Component and so my workflow did not “flow”.

For example, upon creation of a Contact in “My Contacts”, the Row Id passed in was the Row Id of the Contact. However, when you create a Contact in Account->Contacts, then the Row Id passed in is that of the Account record.

Well, there is a simple way around this, ready for it?

Are you sure you’re ready?

Okay, here it is…

In the Runtime Event, you need to set a Profile Attribute to the current Row Id to pass into the Workflow. You can then put as many Runtime Events on as many business objects as you require, as long as it always sets that Profile Attribute for the Row Id.

Too easy. A gentle warm-up from Nathan, there’s more to come…

Advertisements

Entry filed under: Siebel, Workflow.

Using MVG aggregate functions Client-side DLLs

4 Comments

  • […] 1st, 2007 Nathan’s enthusiatically followed up on his first contribution to eulogise about a couple of new Runtime Events… This one is relatively simple but it is […]

  • 2. Soum  |  June 16, 2007 at 8:54 am

    How do we set the Profile Attribute for Contact Row Id?

  • 3. stuandgravy  |  June 17, 2007 at 8:17 pm

    G’day Soum,

    In the Runtime Event Action Set that executes your workflow process, add in an extra Action Step of type ‘Attribute Set’, set operator ‘Set’. Name the Profile Attribute and fill in an expression to set the correct Value. Make sure you set the sequence of the actions so that the Set Attribute executes before the RunProcess.

  • 4. Graham  |  June 25, 2007 at 7:56 am

    The Object Id that is passed by default is that of the primary BC for the BO which is why you can sometimes struggle to get the right value. You only really need to use this workaround if you’ve got the “wrong” Object Id when you start testing, as when it’s right it’ll stay right (and conversely when it’s wrong it’s dead wrong)!


Feeds


%d bloggers like this: