BPM Method Directive Timeout?

Epicor ERP 10
, , ,
1

Hi All,

Is there a way to extend the BPM timeout?

We have a method directive that executes a service connect workflow synchronously.

However when the workflow has been executing for 1 minute we get a timeout message:

BPM runtime caught an unexpected exception of ‘TimeoutException’ type.
See more info in the Inner Exception section of Exception Details.

The inner exception states:

The HTTP request to ‘https://servername/BPMIntegrationWcfService/SCIntegrationWcfService.svc’ has exceeded the allotted timeout of 00:01:00. The time allotted to this operation may have been a portion of a longer timeout.

I have checked the web.config to see if there’s a way to change this timeout but cannot see one?

Does anyone know how to change this?

2

You should ALWAYS execute SC asynchronous. Do you expect your users would be ok to sit and wait for over a minute every time they hit this BO?
What does it do? Is this something that could be rewritten in a BPM directly?

José C Gomez
Senior Software Engineer

3

Hi Jose,

We have various conditions that need to be met prior to the SC executing.

We want a message box to pop up with the status of the SC workflow (Operation Completed etc.). This is a “one click ship” workflow that checks various other things within epicor before proceeding. This is so we can effectively “one click ship” standard orders.

I have attempted to create this in custom code/business object calls within the method directive but the sheer amount of calls are unbelievable and this method does not work half as well as SC does.

Thanks,
Luke

4

Putting on academic architect hat so forgive me

What will the user do if something fails?
I ask myself that when making design decisions on whether something is blocking or async with a log and status somewhere.

If the user is the one resolving the issue then I guess they could sit and wait for this to process. A horrible user experience but sort of functional.
If they are not the one resolving issues from that process then why torture the poor user?

Ignorant and viewing from outside…

1 Like
5

Hi Bart,

The service connect routine outputs error messages etc. so the user can act on those with a log also as the service connect routine goes through.

The user would sit and wait for this to process as it would be an all in one solution and save them time overall, they would also be correcting any issues (packs not being created) etc as they arise.

Thanks,Luke

1 Like
6

Man this still seems like a really really awful solution :frowning:
I understand what you are saying… but eeek…
You said you tried doing it in a BPM / Code and it didn’t work?
What about having SC write to a UDXX table as it goes and have the user look at a dashboard to see the status / fix errors etc?

7

Yes, we tried it in BPM and it was far too complicated for all the business object calls to work properly.

We currently log to a UD table, i am going to output this on a dashboard, make the SC asynchronous and put something in place to stop the end user messing with the order whilst it is being processed.

Thanks for your help guys!