| Author |
Message
|
| sureshpattaje |
 Posted: Mon Nov 03, 2003 5:42 am Post subject: [KNOWN BUG with 3.4.0.3] Notification/Expiration in Blocks |
 |
|
Newbie
Joined: 13 Aug 2003
Posts: 8
Location: Bangalore
|
In my flow, i have a block actvity that contains two program activities. I have set the expiration and notification features for the program activities within the block activity. When i test it using the workflow runtime client, it is not working (it is not giving notification and also not expiring after the time i specified). I have started the Scheduling server and configured it properly.
But for the activity that is outside the block activity, the notification and expiration works fine.
Is there anything else i will have to do for the scheduling server to pickup the notifications from the block activities? |
|
| Back to top |
|
 |
| Ratan |
| Posted: Mon Nov 03, 2003 10:51 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
It should work. Probably there is something wrong with your FDL. Post your FDL here and somebody can help.
_________________
-Ratan |
|
| Back to top |
|
|
| sureshpattaje |
| Posted: Mon Nov 03, 2003 10:59 am Post subject: |
|
|
Newbie
Joined: 13 Aug 2003
Posts: 8
Location: Bangalore
|
The FDL of the process is:
/*
* PROCESS test
*/
PROCESS 'test' ( 'DS_GpsisA1', 'DS_GpsisA1' )
DO NOT PROMPT_AT_PROCESS_START
PROCESS_ADMINISTRATOR 'ADMIN'
WINDOW VIEW_REFERENCE_POINT XPOS 0 YPOS 250
WINDOW SHOW ALL CONNECTORS
WINDOW SHOW EXIT_CONDITIONS
SOURCE 1 XPOS -800 YPOS 600
SINK 1 XPOS 600 YPOS 0
BLOCK 'Block' ( 'DS_GpsisA1', 'DS_GpsisA1' )
START WHEN AT_LEAST_ONE CONNECTOR TRUE
EXIT WHEN "(_State() = _Expired) OR (CLStatus = ""A"")" XPOS -200 YPOS 50
LAYOUT XPOS -200 YPOS 200
NAME_POSITION XPOS -200 YPOS 125
WINDOW VIEW_REFERENCE_POINT XPOS 0 YPOS 400
WINDOW SHOW ALL CONNECTORS
WINDOW SHOW ALL CONDITIONS
SOURCE 1 XPOS -600 YPOS 500
SINK 1 XPOS 600 YPOS 0
PROGRAM_ACTIVITY 'Program' ( 'DS_GpsisA1', 'DS_GpsisA1' )
DESCRIPTION "Test activity"
START MANUAL WHEN AT_LEAST_ONE CONNECTOR TRUE
EXIT MANUAL
LAYOUT XPOS -200 YPOS 200
NAME_POSITION XPOS -200 YPOS 125
PRIORITY DEFINED_IN INPUT_CONTAINER
EXPIRATION AFTER 120 SECONDS
DONE_BY PERSON 'ADMIN'
PROGRAM 'Dummy'
SYNCHRONIZATION NESTED
END 'Program'
DATA
FROM SOURCE 1 TO 'Program'
MAP '_STRUCT' TO '_STRUCT'
LAYOUT
XPOS -600 YPOS 200
DATA
DEFAULT 'Program'
MAP '_STRUCT' TO '_STRUCT'
LAYOUT
XPOS -300 YPOS 400
XPOS -100 YPOS 400
DATA
FROM 'Program' TO SINK 1
MAP '_STRUCT' TO '_STRUCT'
END 'Block'
DATA
FROM SOURCE 1 TO 'Block'
MAP '_STRUCT' TO '_STRUCT'
LAYOUT
XPOS -800 YPOS 200
DATA
FROM 'Block' TO SINK 1
MAP '_STRUCT' TO '_STRUCT'
LAYOUT
XPOS 600 YPOS 200
DATA
LOOP 'Block'
MAP '_STRUCT' TO '_STRUCT'
LAYOUT
XPOS -100 YPOS 400
XPOS -300 YPOS 400
END 'test' |
|
| Back to top |
|
|
| jmac |
| Posted: Mon Nov 03, 2003 11:11 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Is the scheduling server running?
What is the Notification Check Interval?
You can find these out with the Admin utility
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| sureshpattaje |
| Posted: Mon Nov 03, 2003 11:13 am Post subject: |
|
|
Newbie
Joined: 13 Aug 2003
Posts: 8
Location: Bangalore
|
| Scheduling server is running with notification check interval 1 min. |
|
| Back to top |
|
|
| jmac |
| Posted: Mon Nov 03, 2003 11:19 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Have you restarted the Admin server since you modified the notification check interval?
If not give that a try
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| vennela |
| Posted: Mon Nov 03, 2003 11:19 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| If the check interval is too long, sometimes to test it (on a test box) I restart the scheduling server and I get the notifications instantly. |
|
| Back to top |
|
|
| sureshpattaje |
| Posted: Mon Nov 03, 2003 11:44 am Post subject: |
|
|
Newbie
Joined: 13 Aug 2003
Posts: 8
Location: Bangalore
|
Yes. I tried all these options, but couldnt get thro 
Looks like some problem with the configuration of scheduling server. The scheduling server properties are :
- Scheduling server settings
- Check interval PT1M
- Start mode Immediate
- Notification check interval PT1M
- Create notification items threshold 10
- Delete notification items threshold 100
Is there any differnce between the activities that are within block activity and that are outside?
Bcos, for the activities that i have outside the block activity generates notification properly. |
|
| Back to top |
|
|
| jmac |
| Posted: Mon Nov 03, 2003 12:00 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
There is absolutely no difference between activities in a block and not for measuring purposes.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| Ratan |
| Posted: Mon Nov 03, 2003 1:07 pm Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
AFAIK a Block does not Expire. Activities expire. Your FDL suggests you are using _State() = _Expired for the Block exit condition.
Do you have expiration for activities inside the block?
_________________
-Ratan |
|
| Back to top |
|
|
| jmac |
| Posted: Mon Nov 03, 2003 1:22 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Ratan:
Good catch... I think that this exit condition on the block is fine, but it would have to use the state function to test the activity within the block that has an expiration. I have never tried this, but I don't see why it wouldn't work as long as you specified the fully qualified name of the activity.
As to why the expiration/notifications are not working, I still don't have a clue.
Suresh: Send me an email with the FDL exported deep so that I can have a look
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| Ratan |
| Posted: Mon Nov 03, 2003 2:02 pm Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
John,
So should his block exit condition be something like <ActivityName>._State() = _Expired.
_________________
-Ratan |
|
| Back to top |
|
|
| jmac |
| Posted: Mon Nov 03, 2003 5:18 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Ratan:
It would look something like this I think:
_State(BlockName.ActivityName)= _Expired
Realize that I have never done this using The _State function... but I believe it should work
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| sureshpattaje |
| Posted: Mon Nov 03, 2003 9:06 pm Post subject: |
|
|
Newbie
Joined: 13 Aug 2003
Posts: 8
Location: Bangalore
|
Thanks for the replies.
But the problem i am facing is that the Scheduling server is not picking up the notifications. If i see the activity properties from the workflow runtime client, it shows the notification time in the History tab properly. But the notification is not generated by the sceduling server. Same case with the expiration also.
The reason why i am telling the activities are not getting expired/notified is, if at all the activity gets expired and not exiting the block, the last modified date will be changed when i see the activity properties. And also, it should have generated notification, at least. Its not doing both, means there is something wrong with the scheduling server picking up the notifications.
Note that this is happening to the activities that are inside the block only. For the activities that are outside the block, notifications and expiry works fine. |
|
| Back to top |
|
|
| sureshpattaje |
| Posted: Mon Nov 03, 2003 11:41 pm Post subject: |
|
|
Newbie
Joined: 13 Aug 2003
Posts: 8
Location: Bangalore
|
Update:
My system has Workflow 3.4 with CSD3 that is facing the above problem.
But same flow works fine in another system with Workflow 3.4 and [b]without any CSD[/b]. Both are Windows NT workstations with SP6a.
Workflow configuration is same in both systems. Will a CSD cause this problem? Or am i missing something ??? |
|
| Back to top |
|
|
|
|
