Form step - 'Back' arrow completes step

Nigel Thurgood Nigel.Thurgood at sanitarium.com.au
Sat Oct 8 00:13:46 EDT 2005


Hi Tom.
 
Thanks for your response - the 'confirm end of processing' is a step in the right direction, but as you state, is not foolproof (nor particularly elegant, but hey!). At first I wasn't sure whether I'd screwed something up by changing the SAP standard task - I added a container variable based on 50 char SGTXT and redefined the work item header text, to allow a more meaningful description than 'Change form'. I initially tried to copy the task and create my own, but this obviously doesn't bond with the forms wizard (unless, again, I'm missing something here - still in my formative days as far as workflow goes).
 
I know I've read that an 'edit' form is not completed until the save button is selected - not absolutely sure if this was one of our Jocelyn's articles or whether it was SAP help. The approve step certainly stays open until either approve or reject is selected - backing out of the form leaves the item in the workbox. Is the fact that the edit form 'completes without saving' a fault, would you think? If so I'll harass SAP via OSS.
 
One other question if I may. This particular workflow is a very simple one which collects specific EAN data when a field in the material master changes, and goes on to update a 'Z' table as well as the material master itself. Works fine except for the edit form 'fault', and the data collection is minimal. Another workflow I am persevering with, however, is completely based on simple forms, and creates a material. Each form (structure) is pretty big and when split into several plants / warehouses / sales orgs. &etc., the form data is stored in multi-line container elements until calling a sub-workflow for each BAPI_MATERIAL_SAVEDATA step. Works fine and the users are OK with it, but my question is whether it is OK to have so much data being stored in the workflow container (performance / resource wise) rather than writing data out to 'Z' tables and suchlike. Haven't managed to find any doco on this and am hoping it's alright.     
 
All the best.
 
Nigel.

________________________________

From: PEOU Tom T [mailto:Tom_PEOU at rta.nsw.gov.au]
Sent: Fri 7/10/2005 10:37 AM
To: sap-wug at mit.edu
Subject: Form step - 'Back' arrow completes step



Hi Nigel,

 

If you wish to keep the work item in the user's inbox, then you will need to turn on the "Confirm End of Processing" under task properties for the change form step (task).

Activating this option will force a popup box to confirm if this is the end of processing - They will have the option to say 'Complete' or 'Cancel and Keep Work Item in Inbox'. However, this is not fool proof and will not acknowledge whether the save button has been clicked or not - it is simply a way to keep the work item after the change step is exited (whether saved or otherwise).

 

There are a number of other ways to perform what you want - but this is the simplest method without any programming changes.

 

Cheers,

T

 

Tom Peou

Workflow & ESS Administration

Roads and Traffic Authority

Centennial Plaza

260 Elizabeth Street

Surry Hills, NSW

P: (02) 9218 6601

E: Tom_PEOU at rta.nsw.gov.au

 

 

 

 

 

________________________________

I have a simple 'change' form step as part of my workflow. I thought that the step would only be complete if the save button was selected, but it is completed when the back arrow is pressed (and the user selects 'no' to 'do you wish to save your data first'). I want to ensure that the work item remains in the user's inbox unless the form step is saved. What am I doing wrong?

 

Thanks.

 

Nigel Thurgood

 

 

This is an email from Australian Health & Nutrition Association Limited,

ABN 63 096 452 872 trading as Sanitarium Health Food Company.

 

 

IMPORTANT NOTICE: This e-mail and any attachment to it are intended only to be read or used by the named addressee. It is confidential and may contain legally privileged information. No confidentiality or privilege is waived or lost by any mistaken transmission to you. The RTA is not responsible for any unauthorised alterations to this e-mail or attachment to it. Views expressed in this message are those of the individual sender, and are not necessarily the views of the RTA. If you receive this e-mail in error, please immediately delete it from your system and notify the sender. You must not disclose, copy or use any part of this e-mail if you are not the intended recipient.

This is an email from Australian Health & Nutrition Association Limited,
ABN 63 096 452 872 trading as Sanitarium Health Food Company.

THIS E-MAIL IS CONFIDENTIAL.
Any recipient who is not the intended recipient is requested to
notify the sender by return e-mail and erase all copies of the message
and attachments. The sender cannot guarantee that this email or any
attachment to it is free of computer viruses or other conditions which may
damage or interfere with data, hardware or software with which it might be used.

If you do not wish to receive commercial email messages from Sanitarium Health Food
Company, please send an unsubscribe message to the sender of this email, or contact
unsubscribe at sanitarium.com.au.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 12744 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20051008/a47cec48/attachment.bin


More information about the SAP-WUG mailing list