This is an extension to my previous post regarding Hierarchy Extraction which compares different ways to extract property sets. I have quoted in the earlier post regarding the length limitation(75 characters) of Workflow Utilities echo method using dot notation. But Siebel never run out of altervatives and each one gives me something different.
In order to overcome the length limitation of the dot notation one can make use of "Aliases" which lasts upto 255 characters. Workflow Processes can have Process Properties of type "Alias" (ignorant me). Basically this data type acts as a pointer to a specific attribute inside a Property Set. So in order to fetch Sr Number or Account Id, mentioned in previous post, we have to define two process properties of data type "Alias" with Default value as below
SR Number: SiebelMessage/ListOfService/Service Request/@SR Number
Activity Id: SiebelMessage/ListOfService/Service Request/ListOfAction/Action/@Activity Id
In the workflow in order to get the values from siebel message we need to pass input/Output variables as shown below:
Input Arguments
Output Arguments
The other advantage of using Aliases is that it doesn't error out reading a non-existing attribute from a Property Set.
Happy Extracting!!
5 comments:
Hello,
I was wondering, what business service and method are you using in the Set Property step? Also, I am unable to see the screen shots very well. Is it possible you could tell me the values you are using?
Thank you so much!
Hello,
Apologies for poor screen shot visibility. I am still using the Echo method only but with process property of type Alias which overcomes length limitation.
We are passing three input properties as
ActivityId, SR Number and Siebel Message where ActivityId and SR Number are set to predefault as mentioned in post.
In the output are fetching output of these two properties in different process properties as sActivityId and sSR Number.
Let me know if you know anything else
Regards,
-Rahul-
I am getting an error at the echo step
SBL-BPR-00217: The call to fetch process property is invalid as no such process property is defined.
Could you please let me know what could be wrong?
The siebelmessage is being created using XMLDocToIntObjHier of EAI XML Converter
Thanks,
mnbv
Hi Mnbv,
Can you check the propertyset you are trying to fetch from message exists and have a valid alias property defined for the same. The above error states that you are trying to fetch a property which doesn't exist.
Regards,
-Rahul-
Nicely written. I love succinct posts that actually impart usable information.Hierarchy Structure
Post a Comment