| Author |
Message
|
| yworkflow |
 Posted: Mon Jan 12, 2004 10:57 am Post subject: Sorting Work item based on Date Received |
 |
|
Newbie
Joined: 29 Aug 2003
Posts: 4
|
Dear Friends,
I wanted to sort all the workitem based on received date. I tried sorting using sort criteria and it is working fine.
Item take some time (2-5 days) before it gets added to workflow. So received date of workitem is differed by 2-5 days. It differ item to item. If I do sorting by received date it won't be correct (as it represent date when item came to workflow and not the actual date).
Is there any way to set date received for work item?
I have solution ready which keep actual date into container and java code use it and sort based on actual date. Performance result says solution is taking much more time compare to build in SORT Criteria of workflow.
Any help/suggestion is appreciated. |
|
| Back to top |
|
 |
| vennela |
| Posted: Mon Jan 12, 2004 11:12 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
| Item take some time (2-5 days) before it gets added to workflow. |
What do you mean.
Where is it created?
What do you mean by actual date |
|
| Back to top |
|
|
| yworkflow |
| Posted: Mon Jan 12, 2004 11:24 am Post subject: |
|
|
Newbie
Joined: 29 Aug 2003
Posts: 4
|
Initial item came into ORACLE database. It take some time for intial process (2-5 days). Once it is over batch program pick up the rows from ORACLE, generate XML and put it in workflow.
So workitem is coming after 2-5 days it is originally received. As a result received date of workflow is 2-5 days newer. I want to set this received date to original date.
P.S. Original Received Date = Actual date when item received in ORACLE
Workflow Received Date = Original Date + (2-5 Days) |
|
| Back to top |
|
|
| vennela |
| Posted: Mon Jan 12, 2004 11:36 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Looks like you don't have much other choice other than this
| Quote: |
| I have solution ready which keep actual date into container and java code use it and sort based on actual date. Performance result says solution is taking much more time compare to build in SORT Criteria of workflow. |
Yes, it is resource intensive and perfomance may degrade. |
|
| Back to top |
|
|
| sshaker |
| Posted: Mon Jan 12, 2004 1:08 pm Post subject: |
|
|
Disciple
Joined: 20 Sep 2002
Posts: 185
|
hi
try pushing the data container value into description and sort on the description or store the data container value (THE date) into global container and sort in your client application. hope this helps.. !
regards
_________________
shaker |
|
| Back to top |
|
|
| ucbus1 |
| Posted: Tue Jan 13, 2004 8:41 am Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
I agree with sshaker and thats how we do it.
We get applications from users say date 01/01/2004, scanned on 01/02/2004, then loded into database on 01/03/2004, then we trap the date 01/01/2004 in our data container and process them sorting on the date. |
|
| Back to top |
|
|
| sshaker |
| Posted: Tue Jan 13, 2004 9:29 pm Post subject: |
|
|
Disciple
Joined: 20 Sep 2002
Posts: 185
|
Hi
the same is discussed in the best practices document. i highly recommend reading of this document
regards
_________________
shaker |
|
| Back to top |
|
|
|
|
