Hi,

I'm trying to create a c# program that connects to the HWS.

I've used the AddActionToActivityFlow method to activate an action and as a
result a task was created in de file location I specified.

Now, I try to retreive some information with the following statements (the
guid is the guid used when creating the activtityflow):

ActivityFlow flowDetail = hwss.GetActivityFlowInfo(new
Guid("32d8b1d4-34a9-4f94-a400-1653c132a9ca"),
ActivityFlowDetailLevel.TaskLevel, null );
Console.Out.WriteLine(flowDetail.RootActionInstances.Length);
ActionInstance rootInstance = flowDetail.RootActionInstances[0];
Console.Out.WriteLine("RootInstance: " + rootInstance.ActionInstanceTitle);
Console.WriteLine("First task sent: " +
rootInstance.Tasks[0].TaskID.ToString());

The last line however failes, because there are no tasks found.

Checking the HWS Administrator tool, the Activity Flows section is empty,
but I expected my flow to be there.

I'm probably forgetting a step somewhere is creating the action. Someone
know what?

regards, Felix

[ Post a follow-up to this message ]

I found that the activityflows are added to the system, but are all
inactive.... why would this be?


"Felix Planjer" <felix.planjer@yellowred.nl> wrote in message
news:%23t2p8osqEHA.1668@TK2MSFTNGP14.phx.gbl...
> Hi,
>
> I'm trying to create a c# program that connects to the HWS.
>
> I've used the AddActionToActivityFlow method to activate an action and as
a
> result a task was created in de file location I specified.
>
> Now, I try to retreive some information with the following statements (the
> guid is the guid used when creating the activtityflow):
>
> ActivityFlow flowDetail = hwss.GetActivityFlowInfo(new
> Guid("32d8b1d4-34a9-4f94-a400-1653c132a9ca"),
> ActivityFlowDetailLevel.TaskLevel, null );
> Console.Out.WriteLine(flowDetail.RootActionInstances.Length);
> ActionInstance rootInstance = flowDetail.RootActionInstances[0];
> Console.Out.WriteLine("RootInstance: " +
rootInstance.ActionInstanceTitle);
> Console.WriteLine("First task sent: " +
> rootInstance.Tasks[0].TaskID.ToString());
>
> The last line however failes, because there are no tasks found.
>
> Checking the HWS Administrator tool, the Activity Flows section is empty,
> but I expected my flow to be there.
>
> I'm probably forgetting a step somewhere is creating the action. Someone
> know what?
>
> regards, Felix
>
>
>

[ Post a follow-up to this message ]

I've been playing with this some more, but still do not get it.

Can anyone point me to some good examples of HWS sending out tasks and
receiving task responces?

regards,

Felix


Felix Planjer wrote:
> I found that the activityflows are added to the system, but are all
> inactive.... why would this be?
>
>
> "Felix Planjer" <felix.planjer@yellowred.nl> wrote in message
> news:%23t2p8osqEHA.1668@TK2MSFTNGP14.phx.gbl...
> 
>
> a
> 
>
> rootInstance.ActionInstanceTitle);
> 
>
>
>

[ Post a follow-up to this message ]

You may be running into the latency issue that affects HWS tasks.  It's a
rather complicated issue, but the simple version is that HWS relies on
tracking data to know whether or not a task has been sent.  In BizTalk,
tracking data is written after a message is sent by a send shape.  Since
BizTalk itself does not see much importance in tracking that event, it may
not write that tracking data out to the tracking tables immediately.
Unfortunately, as you've seen, that tracking data is very important to HWS,
and since it hasn't been written to the tracking tables, even though you've
received the task message, HWS doesn't know that the task message was sent.

The recommended way to fix this is to make sure that you surround any send
shapes which send HWS task message with an atomic scope.  This will
guarentee that once the send finshes sending the message, a tracking record
of that message will be written to the tracking tables.

As for inactive activity flows, that may in fact be correct behaviour.  An
activity flow is considered active if at least one of the actions in the
activity flow is active.  An action is defined as active if the action
orchestration is currently running.  So, if the only actions you've added
to your activity flow are actions that send out a task message and then
complete, well, those actions will only be active for a very short period
of time, and then they will finish.  Since no actions in the activity flow
would be active at this point, the activity flow would be considered
inactive.

Hope that helps,

--Chris

--------------------[vbcol=seagreen] 
as[vbcol=seagreen] 
(the[vbcol=seagreen] 
empty,[vbcol=seagreen] 

[ Post a follow-up to this message ]