| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| UPES/Web Client problem |
« View previous topic :: View next topic » |
| Author |
Message
|
| JKehoe |
 Posted: Fri Dec 02, 2005 10:05 am Post subject: UPES/Web Client problem |
 |
|
Novice
Joined: 10 Aug 2005
Posts: 20
|
Hello,
We are having a problem with a UPES activity that must be something very small that I am overlooking.
We have a UPES activity that is configured to start Manually, so that when a user checks it out, it launches the UPES application. However, instead of launching the UPES application, it brings the data container up in the Web Client with the option of modifiying the data container and either checking in the item, or cancelling the check out. It's basically what would happen if you checked out a manual activity work item without a .jsp configured for the activity.
We have several other UPES activities that are configured exactly like this one that are working fine. Does anyone know what we might be doing wrong?
Here is the activity from the fdl
| Code: |
PROGRAM_ACTIVITY 'ImagesCreateDocsRetry' ( 'Agribusiness_Data', 'Agribusiness_Data' )
START MANUAL WHEN AT_LEAST_ONE CONNECTOR TRUE
EXIT AUTOMATIC WHEN "_RC=0" XPOS 500 YPOS -650
LAYOUT XPOS 500 YPOS -500
ICON "EXMWMIPA"
NAME_POSITION XPOS 500 YPOS -575
PRIORITY DEFINED_IN INPUT_CONTAINER
DONE_BY PERSON 'RHLLC'
NO CHECKOUT_POSSIBLE
PROGRAM 'AGRI_ImagesCreateDocs'
PROGRAM_EXECUTION_UNIT 'SPTUPES.FMCSYS.FMCGRP'
SYNCHRONIZATION NESTED
END 'ImagesCreateDocsRetry'
|
thanks,
josh |
|
| Back to top |
|
 |
| kotha |
| Posted: Fri Dec 02, 2005 12:29 pm Post subject: |
|
|
Partisan
Joined: 12 Mar 2005
Posts: 333
|
START MANUAL WHEN AT_LEAST_ONE CONNECTOR TRUE
that is in your FDL. I think it is working as manual activity. Change the properties of the UPES at action level. |
|
| Back to top |
|
|
| JKehoe |
| Posted: Fri Dec 02, 2005 2:18 pm Post subject: |
|
|
Novice
Joined: 10 Aug 2005
Posts: 20
|
I think I have this figured out. The fdl block that I included was newly imported into runtime (unknown to me at the time that I originally posted). I'm pretty sure that the old fdl did not have the "NO CHECKOUT POSSIBLE" line within this program definition. From what I have been reading, if checkout is possible, the WebClient will check it out. Now that this change is in place, I'll have to wait and see if new process instances work correctly.
thanks for your response |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
