Step Based on Multi line element

[Bibby, David]

Mike
You're right, it was getting confused.
I created the container element in the task initially as a multiline
element.
When I realised my error I unchecked the multiline flag on the element
to make it a single line element.
I deleted the bindings, re-bound everything and it still didn't work.
Then I remembered a problem I'd previously had where the only solution
was to delete the element in the task container and re-create it.

I did this and it now works. The Plant value now displays in the WI
header description.

Many Thanks
David

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Mike Pokraka
Sent: 22 February 2006 12:48
To: SAP Workflow Users' Group
Subject: Re: Step Based on Multi line element

Hi David,
Shouldn't be the case, but it does sound like it's getting confused
between your multiline and single element.

This is not really an answer to your problem either, but I always make a
habit of naming elements according to their multilineness (another new
entry for the English dictionary). Having elements named PLANTS and
PLANT is clearer, will avoid such confusion or at least point you in the
direction of the error.

Cheers
Mike

Bibby, David wrote:
>
> Hi All,
> I have a workflow that creates multiple steps based on a multi-line 
> element.
> The header line description of the work item text is the same for each

> item of the multi line element.
>
> What I would like to do is distinguish between each work item by 
> putting a value in the work item text e.g. WERKS.
>
> I have bound from the WF container to the task container using the 
> structure 'OfficeProfit' and selected the index so &OFFICEPROFIT()& is

> bound to OfficeProfit in the task container.
> OfficeProfit in the task container is defined as a single line element

> and of the same structure as &OFFICEPROFIT()&.
>
> I pass this multi line element to the task and place it in the work 
> item text header.
> However I get an error message in the workflow log and only the 
> variable &OFFICEPROFIT.ZWF_STRUC1-WERKS& is displayed in the work item

> header, not the value.
> The error message is: Access to field WERKS is not possible for 
> multiline element OFFICEPROFIT
>
> I have NOT defined the element in the task container as multi line.
>
> The same thing is done in another workflow using the same structure, I

> cannot see any differences yet the other workflow works.
>
> Can anyone give any pointers as to what might be the problem?
>
> Many Thanks
> David
>
>
> _______________________________________________
> This message is confidential. It may also be privileged or otherwise 
> protected by work product immunity or other legal rules. If you have 
> received it by mistake please let us know by reply and then delete it 
> from your system; you should not copy it or disclose its contents to
anyone.
> All messages sent to and from Linklaters may be monitored to ensure 
> compliance with internal policies and to protect our business. Emails 
> are not secure and cannot be guaranteed to be error free as they can 
> be intercepted, amended, lost or destroyed, or contain viruses. Anyone

> who communicates with us by email is taken to accept these risks.
>
> The contents of any email addressed to our clients are subject to our 
> usual terms of business; anything which does not relate to the 
> official business of the firm is neither given nor endorsed by it.
>
> The registered address of the UK partnership of Linklaters is One Silk

> Street, London, EC2Y 8HQ. Please refer to 
> http://www.linklaters.com/regulation for important information on the 
> regulatory position of the firm.
>
>
> _______________________________________________
> 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