Can some body guide me how to execute policies programatically from Orchestr
ation.
The code supplied by MS is not usable.
If I import the code I'm not getting the reference for the imported code.
Pl. give me a live example code with explanation

Thanks,
--------------------------------
From: Srinivasan N

-----------------------
Posted by a user from AdminLife (http://www.adminlife.com/)

<Id>hZ7tYoSI5kytiIVo7UeEGw==</Id>

[ Post a follow-up to this message ]

You use the call rules shape to choose the policy and the parameters.  One
thing you might run into if you use XML documents is you will need to make
sure you use the full type name in the business rules composer when you
create your vocabulary.

Matt


"Srinivasan N via AdminLife" <anonymous@adminlife.com> wrote in message
news:%23XbB4LiMEHA.1468@TK2MSFTNGP12.phx.gbl...
> Can some body guide me how to execute policies programatically from
Orchestration.
> The code supplied by MS is not usable.
> If I import the code I'm not getting the reference for the imported code.
> Pl. give me a live example code with explanation
>
> Thanks,
> --------------------------------
> From: Srinivasan N
>
> -----------------------
> Posted by a user from AdminLife (http://www.adminlife.com/)
>
> <Id>hZ7tYoSI5kytiIVo7UeEGw==</Id>

[ Post a follow-up to this message ]

I am having problems configuring an xml document parameter.  I have altered 
the document type in my business rules to include the project name (e.g NWMe
ssaging.CustomerOrder from the default of just CustomerOrder).  I have an or
chestration parameter of th
e same type (NWMessaging.CustomerOrder) in my orchestration however it doesn
't show up in the parameters list of the CallRules shape.

One other parameter (a .NET object) does show up correctly.

Any suggestions?

Larry Guger
lguger at online-can dot com

[ Post a follow-up to this message ]

Do you have more than one root in the xml document? If you do, in the vocabu
lary definition, please specify the document type as the concatenation of th
e following three parts: 

1. Namespace of the project (e.g. MyCompany.MyProject)
2. Type of the document (e.g. CustomerOrder)
3. Type of the root element where the facts belong to. (e.g. Reply). 

You should use the fully qualified name "MyCompany.MyProject.CustomerOrder.R
eply" as the document type. 

For more information, check out my webblog: 
http://biztalkshow.blogspot.com

[ Post a follow-up to this message ]