. RE: UWL Bypass Gui Connection
Dart, Jocelyn
jocelyn.dart at sap.com
Thu Nov 10 21:12:34 EST 2011
Thanks Florin - very good explanation.
Dale, given that ... If you redefine the display method of IMAGE to call SCMS_URL_GENERATE that will probably be enough.
Alternatively, if you want to leave the business object alone and create a webdynpro app or iview to handle the call to SCMS_URL_GENERATE, then use SWFVISU > Object Visualization with business object IMAGE and method <NONE>, then reregister the system in the UWLAdmin iview.
Regards,
Jocelyn
-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Florin Wach
Sent: Friday, 11 November 2011 1:22 AM
To: SAP Workflow Users' Group
Subject: Re: RE: . RE: UWL Bypass Gui Connection
Hello Dan,
I can add some information on the business object type IMAGE, which is in use here and as I know the TravelExpense-Workflow from the R/3-side:
What's called on a method-before execution of the workitem is IMAGE.Display (the default method), which displays the ArchiveLink document instance in a new window.
In order to have that working, an URL needs to be generated "on-the-fly" (anticipating the the archive system is connected via HTTP content server interface 4.5), as it becomes encoded, signed and stuffed out with an expiration of 2 hours. For that matter, the private key of the SAP R/3 system is used, and for that, the GUI is used as the middleware to get hold of that URL (including proper authorization checks and so forth).
If you could integrate a hyperlink in the UWL display, where the backend function is executed, you could probably avoid the GUI here. You would need to frame a call to SCMS_URL_GENERATE.
Alternatively one could make a special URL generation with a longer expiration.
With kind regards,
Florin
-------- Original-Nachricht --------
> Datum: Thu, 10 Nov 2011 13:51:16 +0000
> Von: Dale Brown <dale.brown at duke.edu>
> An: "sap-wug at mit.edu" <sap-wug at mit.edu>
> Betreff: RE: . RE: UWL Bypass Gui Connection
> Hi Jocelyn,
> I made need to clarify when I say attachment. It is actually an archived
> document link. When creating a travel trip expense workflow on portal
> (BUS2089), one is allowed to attach/upload receipts etc.
> This works fine and when viewing the attachment (archive doc link) during
> this time it works fine also. But when an approver goes to uwl to approve
> and tries to view the attachment(archive doc link),
> then the first screen (Launch SAP transaction) appears, then the archive
> document link (attachment) will appear in another screen. I'm not real
> familiar with the xml code or the SWFVISU transaction as the
> user is making those changes. I know an entry was added for object
> visualization for BUS2089 that seemed to stopped work item from going to SAP when
> clicking on the actual trip document link. If an entry is needed for
> the work item task, (which the task itself does not seem launch SAP as it
> stays in portal uwl view, only the archive doc link seems to launch SAP),
> which visualization type should I tell him to select? I did try another
> work item
> in UWL for another business object, that also had an archive document link
> associated with it, and it too launched the SAP transaction screen before
> actually displaying the image of the archived doc link. Also the archived
> document
> link for both of these business objects were using the BO IMAGE. I
> believe the user tried to put an entry in object visualization in SWFVISU for
> IMAGE, but that did not seem to resolve the issue. Thus we were thinking it
> might
> be something like a parameter, etc. for launching in xml code that we
> overlooked. Thanks for your help. Should he still add a task entry in
> SWFVISU and with what type ?
>
>
> Dale Brown
> Duke University
> OIT Application and Database Services
> (919) 684-5341
>
>
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of sap-wug-request at mit.edu
> Sent: Wednesday, November 09, 2011 8:09 PM
> To: sap-wug at mit.edu
> Subject: SAP-WUG Digest, Vol 84, Issue 17
>
> Send SAP-WUG mailing list submissions to
> sap-wug at mit.edu
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://mailman.mit.edu/mailman/listinfo/sap-wug
> or, via email, send a message with subject or body 'help' to
> sap-wug-request at mit.edu
>
> You can reach the person managing the list at
> sap-wug-owner at mit.edu
>
> When replying, please edit your Subject line so it is more specific than
> "Re: Contents of SAP-WUG digest..."
>
>
> Today's Topics:
>
> 1. UWL Bypass Gui Connection (Dale Brown)
> 2. RE: UWL Bypass Gui Connection (Dart, Jocelyn)
> 3. RE: WF-BATCH - System or Service user? (Dart, Jocelyn)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 9 Nov 2011 22:12:50 +0000
> From: Dale Brown <dale.brown at duke.edu>
> Subject: UWL Bypass Gui Connection
> To: "sap-wug at mit.edu" <sap-wug at mit.edu>
> Message-ID:
> <1311B5D8F69C1E4A9FD4F302EC6A0314D221B6 at ex-mbg-05.win.duke.edu>
> Content-Type: text/plain; charset="us-ascii"
>
> Is there a section in some xml code where when you are in the UWL that it
> can be changed to bypass the SAPGUI connection (Launch SAP Transaction)
> prior to a pdf attachment screen appearing?
> Configuration has been done in SWFVISU on the business object for the
> travel workflow that keeps the work item itself from going to SAPGUI, but when
> clicking on an attachment for the work item, it launches a sapgui
> connection, then proceeds to bring up the attachment in another screen. This seems
> to be standard UWL, as a work item for another business object behaves the
> same way. We are just wanting to bypass the connection screen if
> possible, prior to the attachment appearing.
> Would only want when clicking on the attachment, that, that will be the
> only screen to come up. Is this possible or is ut just something that is
> standard uwl and must live with it that way? Thanks .
>
>
> Dale Brown
> Duke University
> OIT Application and Database Services
> (919) 684-5341
>
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 10 Nov 2011 02:06:39 +0100
> From: "Dart, Jocelyn" <jocelyn.dart at sap.com>
> Subject: RE: UWL Bypass Gui Connection
> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> Message-ID:
> <8C507B5E0BA5114E933C3C6E2E9729E0076128E1E7 at DEWDFECCR01.wdf.sap.corp>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi Dale,
> That doesn't sound right... you shouldn't be seeing a SAPGUI screen and no
> that's not standard UWL.
>
> You would have done a Task Visualization in SWFVISU for your travel task.
> You might also need a Object Visualization in SWFVISU for the display of
> the attachment ... I'm assuming that it's called via some sort of secondary
> method?
> Regards,
> Jocelyn
>
>
>
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Dale Brown
> Sent: Thursday, 10 November 2011 9:13 AM
> To: sap-wug at mit.edu
> Subject: UWL Bypass Gui Connection
>
> Is there a section in some xml code where when you are in the UWL that it
> can be changed to bypass the SAPGUI connection (Launch SAP Transaction)
> prior to a pdf attachment screen appearing?
> Configuration has been done in SWFVISU on the business object for the
> travel workflow that keeps the work item itself from going to SAPGUI, but when
> clicking on an attachment for the work item, it launches a sapgui
> connection, then proceeds to
> bring up the attachment in another screen. This seems to be standard UWL,
> as a work item for another business object behaves the same way. We are
> just wanting to bypass the connection screen if possible, prior to the
> attachment appearing.
> Would only want when clicking on the attachment, that, that will be the
> only screen to come up. Is this possible or is ut just something that is
> standard uwl and must live with it that way? Thanks .
>
>
> Dale Brown
> Duke University
> OIT Application and Database Services
> (919) 684-5341
>
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 10 Nov 2011 02:08:43 +0100
> From: "Dart, Jocelyn" <jocelyn.dart at sap.com>
> Subject: RE: WF-BATCH - System or Service user?
> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> Message-ID:
> <8C507B5E0BA5114E933C3C6E2E9729E0076128E1EC at DEWDFECCR01.wdf.sap.corp>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi Sue,
> No that's not it ... the SUPER user group is required either way just to
> create WF-BATCH.
> Looks like whoever was using RFCUSER perhaps changed it directly..?
> In any case you should be safe to just change it back to System.
> Regards,
> Jocelyn
>
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Sue Doughty
> Sent: Thursday, 10 November 2011 2:56 AM
> To: 'SAP Workflow Users' Group'
> Subject: RE: WF-BATCH - System or Service user?
>
> We have it set to Service User.
> [cid:image001.jpg at 01CC9FA1.7DC97ED0]
>
> In the documentation in SWU3 for the Configure RFC Destination action it
> states:
>
>
> If you carry out this activity automatically, the logical RFC destination
> WORKFLOW_LOCAL_xxx is created (if it does not already exist). The user
> WF-BATCH (system user) is assigned to this destination.
>
> If you belong to the SUPER user group, and the WF-BATCH user does not
> exist, it is created and automatically gets the maximum authorization of the
> current user (SY-UNAME). This function is to be performed once by a user who
> belongs to the SUPER user group.
> It looks like we followed the SUPER user group....this was done before I
> got here, so I don't know why it was done that way.
>
> Regards,
> Sue Doughty
> Old Dominion Freight Line, Inc.
> Thomasville, NC
>
> ________________________________
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Cathy
> Sent: Wednesday, November 09, 2011 10:37 AM
> To: SAP Workflow Users' Group
> Subject: Re: WF-BATCH - System or Service user?
>
> We have it set to system.
>
> From: George Caramaliu <george_caramaliu at yahoo.com>
> To: SAP Workflow Users' Group <sap-wug at mit.edu>
> Sent: Wednesday, November 9, 2011 1:40 AM
> Subject: Re: WF-BATCH - System or Service user?
> Same here, WF-BATCH defined as System user.
> Did you checked the change documents for user WF-BATCH?
>
> George Caramaliu
> Metro Systems Romania
> From: Florin Wach <florin.wach at gmx.net>
> To: SAP Workflow Users' Group <sap-wug at mit.edu>
> Sent: Wednesday, November 9, 2011 9:03 AM
> Subject: Re: WF-BATCH - System or Service user?
>
> We have the WF-Batch users of type B = System, which seemed to be the
> default value, as there're no change documents available for that particular
> field, since creation of the record.
> >From what I read from the SAP documentation on that field, "System" is
> the type, which should be assigned to such a user anyways.
>
>
>
> -------- Original-Nachricht --------
> > Datum: Wed, 9 Nov 2011 15:34:09 +1100
> > Von: Rick Bakker <rbakker at gmail.com<mailto:rbakker at gmail.com>>
> > An: "SAP Workflow Users\' Group"
> <sap-wug at mit.edu<mailto:sap-wug at mit.edu>>
> > Betreff: Re: WF-BATCH - System or Service user?
>
> > Hi Jocelyn,
> >
> > That's good to know. No, nobody's been naughty!
> > Does anyone out there have a production system with WF-BATCH as a
> Service
> > user?
> >
> > regards
> > Rick Bakker
> > hanabi technology
> >
> > On Wed, Nov 9, 2011 at 3:16 PM, Dart, Jocelyn
> <jocelyn.dart at sap.com<mailto:jocelyn.dart at sap.com>>
> > wrote:
> > > Hi Rick
> > > Default user type of WF-BATCH is "System"
> > > Someone's been a little naughty perhaps?
> > > Cheers,
> > > Jocelyn
> > >
> > > -----Original Message-----
> > > From: sap-wug-bounces at mit.edu<mailto:sap-wug-bounces at mit.edu>
> [mailto:sap-wug-bounces at mit.edu<mailto:sap-wug-bounces at mit.edu>] On Behalf
> > Of Rick Bakker
> > > Sent: Wednesday, 9 November 2011 2:48 PM
> > > To: SAP Workflow Users' Group
> > > Subject: WF-BATCH - System or Service user?
> > >
> > > Hello Wuggles,
> > >
> > > Basic question here: what sort of user should WF-BATCH be?
> > >
> > > In SU01D tab 'Logon data' field 'User Type' we have the value
> 'Service'.
> > > Nobody is sure why. The Security people want this changed to 'System'
> > > (so nobody can log on with that user).
> > >
> > > Practical Workflow for SAP, 2nd Edition page 88 says:
> > > "WF-BATCH is set as a system user, which means no dialog login is
> > > possible via the SAP GUI."
> > >
> > > Is 'Service' possibly the default for WF-BATCH when it is created via
> > > SWU3? If so, why?
> > >
> > > Opinions welcome.
> > >
> > > regards
> > > Rick Bakker
> > > hanabi technology
> > > _______________________________________________
> > > SAP-WUG mailing list
> > > SAP-WUG at mit.edu<mailto:SAP-WUG at mit.edu>
> > > http://mailman.mit.edu/mailman/listinfo/sap-wug
> > >
> > > _______________________________________________
> > > SAP-WUG mailing list
> > > SAP-WUG at mit.edu<mailto:SAP-WUG at mit.edu>
> > > http://mailman.mit.edu/mailman/listinfo/sap-wug
> > >
> > _______________________________________________
> > SAP-WUG mailing list
> > SAP-WUG at mit.edu<mailto:SAP-WUG at mit.edu>
> > http://mailman.mit.edu/mailman/listinfo/sap-wug
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu<mailto:SAP-WUG at mit.edu>
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu<mailto:SAP-WUG at mit.edu>
> http://mailman.mit.edu/mailman/listinfo/sap-wug
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://mailman.mit.edu/pipermail/sap-wug/attachments/20111110/0d0a5ef2/attachment.htm
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: image001.jpg
> Type: image/jpeg
> Size: 26717 bytes
> Desc: image001.jpg
> Url :
> http://mailman.mit.edu/pipermail/sap-wug/attachments/20111110/0d0a5ef2/attachment.jpg
>
> ------------------------------
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
> End of SAP-WUG Digest, Vol 84, Issue 17
> ***************************************
>
> _______________________________________________
> 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