Configure Extended Notifications in QA/PRD

[Mike Pokraka]

Hi Ravi,

Thanks for your input. SWNCONFIG is the transaction giving me problems. I
have in the meantime found out that SWNADMIN will do the job via the web
interface, but unfortunately HTTP is locked down at this site - no web
stuff whatsoever.

So we're back to the question: is there any way in the backend to maintain
the extended notification parameters? personally I think it's a bit
strange to enable the maintenance via one transaction, but not via the
other.

Cheers,
Mike

PS: Shandra - Thanks for the response but this has nothing to do with UWL.


On Wed, November 14, 2007 10:47 pm, Ravi Dixit wrote:
> Hi Mike
>
> Have you tried the other transaction - SWN_CONFIG? Otherwise check the
> client settings, I was able to modify on a previous project. I agree with
> you, it doesn't make sense to lock it as it needs to point to the
> respective
> portals.
>
> Best Regards
> Ravi Dixit
>
>
>> From: "Mike Pokraka" <asap at workflowconnections.com>
>> Subject: Configure Extended Notifications in QA/PRD
>> To: sap-wug at mit.edu
>> Message-ID:
>>        <
>> 51147.212.157.152.235.1195053192.squirrel at pluto.workflowconnections.com>
>>
>> Content-Type: text/plain;charset=iso-8859-1
>>
>> Hi Wuggers,
>>
>> Quick question: How do I configure extended notifications in non-dev
>> systems?
>>
>> Everything gets transported, including system-specific settings like the
>> sender address and the system to log onto, and I cannot change it.
>>
>> Or am I missing something obvious?
>>
>> TIA,
>> Mike
>>
>>
>>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>


-- 
Mike Pokraka
Senior Consultant
Workflow Connections
Mobile: +44(0)7786 910855