PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 5/5/2006 5:33 PM by  John Henley
Setting up inbasket in portal
 6 Replies
Sort:
You are not authorized to post a reply.
Author Messages
prithwee
Basic Member
(42 points)
Basic Member
Posts:20


Send Message:

--
8/11/2005 7:28 PM
    Hello,

    I am new to Lawson and have a question. How do I make sure that inbasket in displayed in portal? I have set myself up as a administrator, verified LX00, changed WFUSER value on my RD30 -> LX95 to 1, verified with hosting company that inabsket servelet calls are working. I am not seeing the inbasket in my portal still.
    Bill Ianni
    Private
    Private
    Veteran Member
    (330 points)
    Veteran Member
    Posts:110


    Send Message:

    --
    9/14/2005 6:36 PM
    It the end of your url, replace lawson/portal/ with lawson/inbasket/. If you still can't get there, then your WF servers are probably not started; check the em, wf, and wfc server "out" logs in the ccs/lawson/process flow/ directory.
    prithwee
    Basic Member
    (42 points)
    Basic Member
    Posts:20


    Send Message:

    --
    9/27/2005 8:46 PM
    Thanks. I was able to logon to web inbasket but the inbasket was not coming in portal itself. We applied a patch and then it worked and the work units are showing in it. My issue is that I want to show a copy of form RQ10 when the user clicks on display. This is done via putting a xml file in Display Exec field on user action in process flow. My problem is how to generate that file.

    Please help. I am struck in this as Lawson is not ready to help me as they claim that it is custom. They have a document on this : PFlow admin guide page 268 and that doesn't take you anywhere.
    John Henley
    Private
    Private
    Senior Member
    (9908 points)
    Senior Member
    Posts:3320


    Send Message:

    --
    10/4/2005 12:15 PM
    You need to use Design Studio (or get someone to do it who has Design Studio and will give you the .xml file).
    See Lawson KB article 544628.

    http://kmcollections.laws...3S02PROCEDURE02.HTML
    Thanks for using the LawsonGuru.com forums!
    John
    E
    New Member
    (3 points)
    New Member
    Posts:1


    Send Message:

    --
    11/9/2005 8:54 PM
    Do you have any inbasket tasks assigned to your ID in WF12 in logan. If you do not none will show up.
    ridjayc
    Veteran Member
    (493 points)
    Veteran Member
    Posts:191


    Send Message:

    --
    5/5/2006 4:42 PM
    I am not sure you can edit these types of files with the Design Studio tool. The file you need to start with is recsum.htm. It is found in

    "....lawsonweb\wwwroot\lawson\inbasket\execs\recsum.htm"

    I would just copy the file to something like

    my_custom_recsum.htm

    NOTE: I think there is some type of restriction on what name you give this file as it may need to have *recsum.htm in the name to work.

    You also need to go into the user actions in your process flow and point them to use your custom page.

    One of the reason we edited this file was to bypass the issue where we needed to set the access flag to 'Y' on the users RD30 record. Basically we setup some custom views on the req tables and then repointed the the recsum.htm to use are views. This let us keep the access flag set to 'N' for are users. We also added a bunch of fields as well on the page such as account description, the actual part description etc. Custom views in Lawson can make the dme queries much more useful.

    If I have to something like this over again I might just try something like making the recsum.htm a redirect to a custom ".Net" page.
    John Henley
    Private
    Private
    Senior Member
    (9908 points)
    Senior Member
    Posts:3320


    Send Message:

    --
    5/5/2006 5:33 PM
    There are two versions of the inbasket:
    - HTML: the page (recsum.htm) is part of the HTML inbasket, and you modify by editing the HTML
    - Portal: Those you modify with Design Studio
    Thanks for using the LawsonGuru.com forums!
    John
    You are not authorized to post a reply.