ijc
Well Known Member
Dear All,
I'm having an intermittent problem with workflow that I can't track down. Basically we have modified our purchasing functions so that a message will be sent every time a requisition has been approved. This then allows the purchase order to be generated.
Because we're on SP17.1 I1 and a lot of our users are using the HTML client we have the setting below in our JDE.INI on both the Fat Clients and the Enterprise Servers
ClientType=HTML
[JAS PREFERENCE]
JasServer=IFSJAS01
Port=80
Servlet=/jde/servlet/html.login
This means that when the message is sent the link should point back to the Jas server. This works beautifully 99% of the time but occasionaly a JAS user will get a message with a Fat Client attachment pointing them back to the work centre. The message reads
A workflow process has generated an action item. You may enter the
Work Center by opening the attached shortcut.
I then check the message on the workflow tables (F98860/5) and on the message tables (F0113*) and all seems fine (the correct message exists)
Does anyone have an idea why this message is being sent instead of the HTML link. I suspect a timeout or somethiing.....
Any ideas,
Ian
I'm having an intermittent problem with workflow that I can't track down. Basically we have modified our purchasing functions so that a message will be sent every time a requisition has been approved. This then allows the purchase order to be generated.
Because we're on SP17.1 I1 and a lot of our users are using the HTML client we have the setting below in our JDE.INI on both the Fat Clients and the Enterprise Servers
ClientType=HTML
[JAS PREFERENCE]
JasServer=IFSJAS01
Port=80
Servlet=/jde/servlet/html.login
This means that when the message is sent the link should point back to the Jas server. This works beautifully 99% of the time but occasionaly a JAS user will get a message with a Fat Client attachment pointing them back to the work centre. The message reads
A workflow process has generated an action item. You may enter the
Work Center by opening the attached shortcut.
I then check the message on the workflow tables (F98860/5) and on the message tables (F0113*) and all seems fine (the correct message exists)
Does anyone have an idea why this message is being sent instead of the HTML link. I suspect a timeout or somethiing.....
Any ideas,
Ian