<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>WebUI Archive - Pixelfriedhof</title>
	<atom:link href="https://pixelfriedhof.com/en/tag/webui-en/feed/" rel="self" type="application/rss+xml" />
	<link>https://pixelfriedhof.com/en/tag/webui-en/</link>
	<description>IT-Blog, Fotoblog, Travelblog, Nerdstuff</description>
	<lastBuildDate>Tue, 04 Feb 2020 13:18:43 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.8.3</generator>

<image>
	<url>https://pixelfriedhof.com/wp-content/uploads/2022/02/cropped-My-project-3-32x32.png</url>
	<title>WebUI Archive - Pixelfriedhof</title>
	<link>https://pixelfriedhof.com/en/tag/webui-en/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Name of the component for alternative Delivery address</title>
		<link>https://pixelfriedhof.com/en/name-of-the-component-for-alternative-delivery-address/</link>
					<comments>https://pixelfriedhof.com/en/name-of-the-component-for-alternative-delivery-address/#respond</comments>
		
		<dc:creator><![CDATA[megaadmin]]></dc:creator>
		<pubDate>Wed, 22 Mar 2017 15:35:19 +0000</pubDate>
				<category><![CDATA[Tutorials]]></category>
		<category><![CDATA[CRM]]></category>
		<category><![CDATA[SAP]]></category>
		<category><![CDATA[SAP CRM]]></category>
		<category><![CDATA[WebUI]]></category>
		<guid isPermaLink="false">http://pixelfriedhof.com/?p=140</guid>

					<description><![CDATA[<p><span lang="EN-US">The WebUI dialog-window for choosing an alternate delivery address doesn&#8217;t allow us to have a look at the technical details. So it is hard to find out which component is responsible for the configuration of that dialog.</span></p>
<p>Der Beitrag <a href="https://pixelfriedhof.com/en/name-of-the-component-for-alternative-delivery-address/">Name of the component for alternative Delivery address</a> erschien zuerst auf <a href="https://pixelfriedhof.com/en">Pixelfriedhof</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><span lang="EN-US">The WebUI dialog-window for choosing an alternate delivery address doesn’t allow us to have a look at the technical details. So it is hard to find out which component is responsible for the configuration of that dialog.</span></p>
<p>&nbsp;</p>
<p><img fetchpriority="high" decoding="async" class=" size-full wp-image-576" src="http://pixelfriedhof.com/wp-content/uploads/2017/03/image001.png" alt="image001" width="600" height="293"></p>
<p style="margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">The component „GS_SIMPLE_ADDR“ is responsible for the configuration of that dialog window with its views like “POSTALVIEW”.</p>
<p style="margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">Besides being used for the alternative shipping address, the component is also used in the view for involved companies within the opportunity-management.</p>
<p style="margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">Before customizing the component it should be copied to avoid interference with other system functions.</p>
<p>&nbsp;</p>
<p>Der Beitrag <a href="https://pixelfriedhof.com/en/name-of-the-component-for-alternative-delivery-address/">Name of the component for alternative Delivery address</a> erschien zuerst auf <a href="https://pixelfriedhof.com/en">Pixelfriedhof</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://pixelfriedhof.com/en/name-of-the-component-for-alternative-delivery-address/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>SAP CRM: Message &#8216;- CONTENT GENERATED AT RENDERING TIME -&#8216; when creating notes and invoking the editor</title>
		<link>https://pixelfriedhof.com/en/sap-crm-message-content-generated-at-rendering-time-when-creating-notes-and-invoking-the-editor/</link>
					<comments>https://pixelfriedhof.com/en/sap-crm-message-content-generated-at-rendering-time-when-creating-notes-and-invoking-the-editor/#respond</comments>
		
		<dc:creator><![CDATA[megaadmin]]></dc:creator>
		<pubDate>Wed, 22 Mar 2017 15:35:19 +0000</pubDate>
				<category><![CDATA[Tutorials]]></category>
		<category><![CDATA[CRM]]></category>
		<category><![CDATA[Interaction Center]]></category>
		<category><![CDATA[SAP]]></category>
		<category><![CDATA[SAP CRM]]></category>
		<category><![CDATA[WebUI]]></category>
		<guid isPermaLink="false">http://pixelfriedhof.com/?p=150</guid>

					<description><![CDATA[<p>If the message '- CONTENT GENERATED AT RENDERING TIME -' appears instead of the usual editor input field when creating texts, for example as a note underneath a support ticket, check the following facts.</p>
<p>Der Beitrag <a href="https://pixelfriedhof.com/en/sap-crm-message-content-generated-at-rendering-time-when-creating-notes-and-invoking-the-editor/">SAP CRM: Message &#8216;- CONTENT GENERATED AT RENDERING TIME -&#8216; when creating notes and invoking the editor</a> erschien zuerst auf <a href="https://pixelfriedhof.com/en">Pixelfriedhof</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>If the message &#8216;- CONTENT GENERATED AT RENDERING TIME -&#8216; appears instead of the usual editor input field when creating texts, for example as a note underneath a support ticket, check the following facts.</p>
<p>&nbsp;</p>
<ul>
<li>Transaction SU01 &#8211; Has the user defined a language? If not, enter language.</li>
<li>Reset personalization of the Assignment Block in the WebUI, in which the notes or texts are displayed in tabular form.</li>
<li>Subsequently, log off the user system-wide and then log on again.</li>
</ul>
<p>The problem should now be fixed in new cases. Old cases (e. g. support tickets which were created or edited before the above mentioned correction) may continue to suffer from the problem.</p>
<p>&nbsp;</p>
<p>Der Beitrag <a href="https://pixelfriedhof.com/en/sap-crm-message-content-generated-at-rendering-time-when-creating-notes-and-invoking-the-editor/">SAP CRM: Message &#8216;- CONTENT GENERATED AT RENDERING TIME -&#8216; when creating notes and invoking the editor</a> erschien zuerst auf <a href="https://pixelfriedhof.com/en">Pixelfriedhof</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://pixelfriedhof.com/en/sap-crm-message-content-generated-at-rendering-time-when-creating-notes-and-invoking-the-editor/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>How to find out affected Component name of a transport  via GUID</title>
		<link>https://pixelfriedhof.com/en/how-to-find-out-affected-component-name-of-a-transport-via-guid/</link>
					<comments>https://pixelfriedhof.com/en/how-to-find-out-affected-component-name-of-a-transport-via-guid/#respond</comments>
		
		<dc:creator><![CDATA[megaadmin]]></dc:creator>
		<pubDate>Wed, 22 Mar 2017 15:19:06 +0000</pubDate>
				<category><![CDATA[Tutorials]]></category>
		<category><![CDATA[CRM]]></category>
		<category><![CDATA[SAP]]></category>
		<category><![CDATA[SAP CRM]]></category>
		<category><![CDATA[WebUI]]></category>
		<guid isPermaLink="false">http://pixelfriedhof.com/?p=138</guid>

					<description><![CDATA[<p>Sometimes there are situations when you know that there was a change on a special Component, but you do not quite know which component specifically was affected.&#160;Such a situation can happen especially when a dialog window in WebUI doesn&#8217;t show technical information about itself. We can find out the affected component when using the transport GUIDs.</p>
<p>Der Beitrag <a href="https://pixelfriedhof.com/en/how-to-find-out-affected-component-name-of-a-transport-via-guid/">How to find out affected Component name of a transport  via GUID</a> erschien zuerst auf <a href="https://pixelfriedhof.com/en">Pixelfriedhof</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Sometimes there are situations when you know that there was a change on a special Component, but you do not quite know which component specifically was affected.&nbsp;Such a situation can happen especially when a dialog window in WebUI doesn’t show technical information about itself. We can find out the affected component when using the transport GUIDs.</p>
<p>&nbsp;</p>
<p>First we have a look in our Transport-Organization (Transaction SE10) and we open all nodes of our Customizing-Transport to which we want to find out the affected components.</p>
<p>On the bottom-most level of our tree we find the linked GUIDs. We copy them for later research:</p>
<p>&nbsp;</p>
<p><img decoding="async" class=" size-full wp-image-576" src="http://pixelfriedhof.com/wp-content/uploads/2017/03/image001.png" alt="image001" width="600" height="139" srcset="https://pixelfriedhof.com/wp-content/uploads/2017/03/image001.png 734w, https://pixelfriedhof.com/wp-content/uploads/2017/03/image001-300x69.png 300w" sizes="(max-width: 600px) 100vw, 600px" /></p>
<p>&nbsp;</p>
<p>Now we change to Table-View (Transaction SE16) of the table „BSPC_DL_XMLSTRX2“ an enter one of our GUIDs in field “CONTEXT_ID” and start the query:</p>
<p><img decoding="async" class=" size-full wp-image-577" src="http://pixelfriedhof.com/wp-content/uploads/2017/03/image002.png" alt="image002" width="433" height="323" srcset="https://pixelfriedhof.com/wp-content/uploads/2017/03/image002.png 577w, https://pixelfriedhof.com/wp-content/uploads/2017/03/image002-300x224.png 300w" sizes="(max-width: 433px) 100vw, 433px" /></p>
<p>&nbsp;</p>
<p>The following view shows information about all the affected components of that GUID:</p>
<p><img loading="lazy" decoding="async" class=" size-full wp-image-578" src="http://pixelfriedhof.com/wp-content/uploads/2017/03/image003.png" alt="image003" width="545" height="169" srcset="https://pixelfriedhof.com/wp-content/uploads/2017/03/image003.png 663w, https://pixelfriedhof.com/wp-content/uploads/2017/03/image003-300x93.png 300w" sizes="auto, (max-width: 545px) 100vw, 545px" /></p>
<p>Der Beitrag <a href="https://pixelfriedhof.com/en/how-to-find-out-affected-component-name-of-a-transport-via-guid/">How to find out affected Component name of a transport  via GUID</a> erschien zuerst auf <a href="https://pixelfriedhof.com/en">Pixelfriedhof</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://pixelfriedhof.com/en/how-to-find-out-affected-component-name-of-a-transport-via-guid/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
