Sorting similar workitems into different folders
Dart, Jocelyn
jocelyn.dart at sap.com
Tue Feb 15 20:17:32 EST 2005
Hi Paul,
Glad you got it working.
Expression = read it from a container element
in this case - similar to use of "Expression" when determining agetns.
The sort of "expression" you are thinking about would be called a
"condition" in workflow.
Hope that's clear.
Regards,
Jocelyn
-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Paul.Bakker at osr.treasury.qld.gov.au
Sent: Tuesday,15 February 2005 3:19 PM
To: SAP Workflow Users' Group
Subject: RE: Sorting similar workitems into different folders
Jocelyn,
Thanks for that - I tried the 'Task determined by Expression' feature
(on
the Control tab of the Step)
and it works a treat! A very powerful feature. It allows me to easily
split
workitems from the same workflow
into different folders/tabs of the UWL.
But I wonder if I am using it the right way - is it possible to write an
Expression
that evaluates to a task id (eg 'TS9000008') without simply reading that
actual id string from
a container element? As far as I can tell, the only Expressions allowed
are
Constants
or Container Elements....
In any case, this seems a much more elegant way to group workitems, in
contrast to (e.g.) _WI_GROUP_ID
(which, to be fair, wasn't really intended for this particular purpose).
_WI_GROUP_ID is more for grouping
heterogeneous workflows that are linked to the same object instance.
thanks again for all your help,
Paul
(Brisbane)
"Dart, Jocelyn"
<jocelyn.dart at sap To: "SAP Workflow
Users' Group" <sap-wug at mit.edu>
.com> cc:
Sent by: Subject: RE: Sorting
similar workitems into different folders
sap-wug-bounces at m
it.edu
14/02/2005 16:46
Please respond to
"SAP Workflow
Users' Group"
Hi Paul,
I've been away so apologies if you've already been told this....
You can create different views in the XML configuration files for the
UWL - e.g. a "bulk" view and a "individual" view.
It's easier to do this if bulk/individual are on separate task ids -
i.e. one for bulk and one for individual. If you want to stop the
workflow getting too complex, you could always copy the task, and use
the "task by expression" option to swap in the correct task at runtime.
The views automatically appear as possible subviews in the UWL if the
user has any of the items currently in his UWL worklist.
You need to use the <View> tag to create the view and the <ItemType> tag
to make the view the "default view" of the tasks.
You can then add additional columns to the view if you want your users
to see extra info as well.
Regards,
Jocelyn
-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Paul.Bakker at osr.treasury.qld.gov.au
Sent: Friday,11 February 2005 9:14 AM
To: SAP Workflow Users' Group
Subject: Re: Sorting similar workitems into different folders
Mike,
Thanks for that. We are using Enterprise Portal 6.0 and are now
investigating the use of dynamic columns there.
It's not just sorting we're after, however - we want different folders!
Hopefully we can use the EP columns to split workitems into different
folders. The idea is to have
one folder each for 'Individual' and 'Bulk' approvals. I think the
folders
will actually both contain all
approval workitems, but will be pre-filtered to display only those with
the
'B' or 'I' attribute respectively.
The reason we want to split them into separate folders, is so that we
can
enable 'multiple execution'
(via an IView?) for the 'Bulk' approvals.
NB There's no particular reason for using the same task for both -
except
that they perform the same function :-)
I just wanted to keep a lid on the number of custom tasks and the
complexity of the workflow.
cheers,
Paul
Michael Pokraka
<workflow at quirky. To: "SAP Workflow
Users' Group" <sap-wug at mit.edu>
me.uk> cc:
Sent by: Subject: Re: Sorting
similar workitems into different folders
sap-wug-bounces at m
it.edu
10/02/2005 19:13
Please respond to
"SAP Workflow
Users' Group"
Hi Paul,
Three ideas:
- In EP6 it is possible to do the equivalent of dynamic columns, so your
users
could then sort it themselves.
- Any particular reason to use the same task for both? There is no real
drawback to splitting it into two.
- If it's a small group of users, they may be very amenable to the idea
of
putting a code into text. e.g. prefix your text with I or B. I've got
one
task
which starts with a one-letter code followed by a date followed by a
description.
Cheers
Mike
--- Paul.Bakker at osr.treasury.qld.gov.au wrote:
> WUG-meisters,
>
> We have a custom workflow that generates approval workitems for FI-CA
> refunds. Some refunds are straightforward (eg for small amounts)
> and have been marked internally with a 'B' (for Bulk approval). Other
> refunds (eg for large amounts) are marked with an 'I' (Individual
> Approval).
>
> My problem is this:
>
> **** How can I make the distinction between 'Bulk' and 'Individual'
> approval workitems clear in the user's worklist? ****
>
> They are internally labelled with a 'B' and an 'I' in a container
element,
> but how can the Business Workplace make use of this difference?
> Ideally, I would like to get the workitems to appear in different
folders.
>
> This problem is complicated by the fact that we are using the *same*
> workflow template, step and task for both 'Bulk' and 'Individual'
> approval workitems.
>
> Therefore, in SBWP, you can't 'Group According to task' because the
tasks
> are the same. You also can't 'Group According to content'
> because the FI-CA documents are all different. They all have the same
> 'content type' as well.
>
> I've investigated using 'Group According to sort key', but it seems
> perversely complex. _WI_GROUP_ID can only hold objects, not
> a simple 'B' or 'I' marker. And it groups according to object
instance,
not
> object type. If I understand it right, I would have
> to create a custom table and object for the approval types, and add a
step
> to the workflow to instantiate the object and store
> it in _WI_GROUP_ID. Then I have to change all existing workflows to
assign
> a Group Id..
>
> Am I missing something obvious here? We're in 4.7 and (will be) using
the
> Universal Worklist.
>
> thanks in advance,
> Paul
> (Brisbane)
>
>
>
>
>
>
> We have the following problem. I have set up a workflow task to allow
> 'multiple execution of workitems' - in this case, to allow the 'Bulk
> Approval' of small refund amounts. The user selects a bunch of
workitems,
> approves the first one, and is then prompted by a popup to approve
> ALL selected workitems in one go.
>
> This works fine. However, we also want to label some workitems (eg
those
> for large amounts, or where the customer is dodgy) as unsuitable for
> bulk approval - these require individual attention. We call these
workitems
> 'Individual Approvals'.
>
> ******The problem is this: how can I make the distinction between
'Bulk'
> and 'Individual' approval workitems clear in the user's
worklist?*******
> They are labelled with a 'B' and an 'I' in a container element, but
how
can
> the Business Workplace make use of this difference?
> Ideally, I would like to get them to appear in different folders.
>
> This problem is complicated by the fact that we are using the *same*
> workflow template, step and task for both 'Bulk' and 'Individual'
> approval workitems.
>
> Therefore, in SBWP, you can't 'Group According to task' because the
tasks
> are the same. You also can't 'Group According to content'
> (or content type), because these are the same.
>
> I've investigated using 'Group According to sort key', but it seems
> horrendously complex. _WI_GROUP_ID can only hold objects, not
> a simple 'B' or 'I' marker. And it groups according to object
instance,
not
> object type. If I understand it right, I would have
> to create a custom table and object for the approval types, and add a
step
> to the workflow to instantiate the object and store
> it in _WI_GROUP_ID.
>
> Am I missing something obvious here? We're in 4.7 and are (will be)
using
> the Universal Worklist.
>
> thanks in advance,
> Paul
>
>
> *************************************************
>
> Only an individual or entity who is intended to be
> a recipient of this e-mail may access or use the
> information contained in this e-mail or any of its
> attachments. Opinions contained in this e-mail or
> any of its attachments do not necessarily reflect
> the opinions of Queensland Treasury.
>
> The contents of this e-mail and any attachments
> are confidential and may be legally privileged and
> the subject of copyright. If you have received
> this e-mail in error, please notify Queensland
> Treasury immediately and erase all copies of the
> e-mail and the attachments. Queensland Treasury
> uses virus scanning software. However, it is not
> liable for viruses present in this e-mail or in
> any attachment.
>
> **************************************************
>
>
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug
More information about the SAP-WUG
mailing list