<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Your feedback on the new request screen</title>
	<atom:link href="http://blogs.exact.com/products/2009/10/your-feedback-on-the-new-request-screen/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.exact.com/products/2009/10/your-feedback-on-the-new-request-screen/</link>
	<description></description>
	<lastBuildDate>Fri, 10 Feb 2012 16:00:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Edgar Wieringa</title>
		<link>http://blogs.exact.com/products/2009/10/your-feedback-on-the-new-request-screen/comment-page-1/#comment-1278</link>
		<dc:creator>Edgar Wieringa</dc:creator>
		<pubDate>Tue, 26 Jan 2010 09:33:50 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.exact.com/products/?p=625#comment-1278</guid>
		<description>Hi Deepthy,

Thanks for your reply. I noticed your issue as well, you however touch an interesting topic here. A hidden request has always been a bit typical to me, so I would like to understand for what kind of situations you use it. Hidden request are not shown - they do not occur in the long list of request type at the bottom of the page for instance - but for thosew who know them, they can create them. In the past these happy few, could just create there request by entering the ID.

Only allowing a group of people to create a certain request can be done by other means (attach a role or use security level). Based on your reply I would like to learn when you guys use it.

Fixing the situation is relatively easy, however hiding it from the auto-complete would however result in the auto-complete list giving you a &#039;No data found&#039; whilst you can create the request, this I would not find great.

So you are right that this occurs, jsut help me know in solving this.

Thanks again for your post and in this way engaging with us,


Edgar

BTW. We also had an issue that inactive requests where shown, this has been fixed along the way in 242.</description>
		<content:encoded><![CDATA[<p>Hi Deepthy,</p>
<p>Thanks for your reply. I noticed your issue as well, you however touch an interesting topic here. A hidden request has always been a bit typical to me, so I would like to understand for what kind of situations you use it. Hidden request are not shown &#8211; they do not occur in the long list of request type at the bottom of the page for instance &#8211; but for thosew who know them, they can create them. In the past these happy few, could just create there request by entering the ID.</p>
<p>Only allowing a group of people to create a certain request can be done by other means (attach a role or use security level). Based on your reply I would like to learn when you guys use it.</p>
<p>Fixing the situation is relatively easy, however hiding it from the auto-complete would however result in the auto-complete list giving you a &#8216;No data found&#8217; whilst you can create the request, this I would not find great.</p>
<p>So you are right that this occurs, jsut help me know in solving this.</p>
<p>Thanks again for your post and in this way engaging with us,</p>
<p>Edgar</p>
<p>BTW. We also had an issue that inactive requests where shown, this has been fixed along the way in 242.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Deepthy</title>
		<link>http://blogs.exact.com/products/2009/10/your-feedback-on-the-new-request-screen/comment-page-1/#comment-1263</link>
		<dc:creator>Deepthy</dc:creator>
		<pubDate>Sun, 24 Jan 2010 11:21:59 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.exact.com/products/?p=625#comment-1263</guid>
		<description>Hi Edgar,

From the release 242, when we are creating requests from the new search text box, its listing the hidden requests as well. Users are able to create a new request even if it is actually hidden.</description>
		<content:encoded><![CDATA[<p>Hi Edgar,</p>
<p>From the release 242, when we are creating requests from the new search text box, its listing the hidden requests as well. Users are able to create a new request even if it is actually hidden.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob</title>
		<link>http://blogs.exact.com/products/2009/10/your-feedback-on-the-new-request-screen/comment-page-1/#comment-704</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Fri, 13 Nov 2009 12:59:11 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.exact.com/products/?p=625#comment-704</guid>
		<description>Hi Edgar, 
As a user, the ID of a request is not often used. 
However, in copying requests (for sales or consultancy) it is handy to have the possibility to show them, or get an overview of them. 

Further, the use of one column with all requests is absolutely not user friendly. With an extensive range of request types, it is not working for me. 
I would prefer the possibility to make multiple (2 or 3) columns and arrange the categories in my own way (pretty much like a search screen or account card.</description>
		<content:encoded><![CDATA[<p>Hi Edgar,<br />
As a user, the ID of a request is not often used.<br />
However, in copying requests (for sales or consultancy) it is handy to have the possibility to show them, or get an overview of them. </p>
<p>Further, the use of one column with all requests is absolutely not user friendly. With an extensive range of request types, it is not working for me.<br />
I would prefer the possibility to make multiple (2 or 3) columns and arrange the categories in my own way (pretty much like a search screen or account card.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ronaldo</title>
		<link>http://blogs.exact.com/products/2009/10/your-feedback-on-the-new-request-screen/comment-page-1/#comment-662</link>
		<dc:creator>Ronaldo</dc:creator>
		<pubDate>Thu, 05 Nov 2009 20:30:44 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.exact.com/products/?p=625#comment-662</guid>
		<description>Ronald, 
great news. It might be a really competitive adventage and a strong tool to get enterprise customers worlwide. 

If I can continiue my customers wishes, please thnik also about supporting Firefox or Mozilla. Unfortunetely many people want to be &quot;independent&quot; and use Apple products, etc. We loose many prospects by this constreain. I finished my wishes :)

Regards.</description>
		<content:encoded><![CDATA[<p>Ronald,<br />
great news. It might be a really competitive adventage and a strong tool to get enterprise customers worlwide. </p>
<p>If I can continiue my customers wishes, please thnik also about supporting Firefox or Mozilla. Unfortunetely many people want to be &#8220;independent&#8221; and use Apple products, etc. We loose many prospects by this constreain. I finished my wishes <img src='http://blogs.exact.com/products/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Regards.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Edgar Wieringa</title>
		<link>http://blogs.exact.com/products/2009/10/your-feedback-on-the-new-request-screen/comment-page-1/#comment-661</link>
		<dc:creator>Edgar Wieringa</dc:creator>
		<pubDate>Thu, 05 Nov 2009 19:50:35 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.exact.com/products/?p=625#comment-661</guid>
		<description>@Martin,

You are right about showing the ID. This is one of the losses you sometimes have to take as a product manager. Due to technical constraints we currently can&#039;t show the description over the ID in the input field.

Or you can also read it as I could not give the technical team the time to build it as we ideally wanted it to be. So we had to make the choice to deliver it as is.

Thanks for your input and investing the time to explore this.</description>
		<content:encoded><![CDATA[<p>@Martin,</p>
<p>You are right about showing the ID. This is one of the losses you sometimes have to take as a product manager. Due to technical constraints we currently can&#8217;t show the description over the ID in the input field.</p>
<p>Or you can also read it as I could not give the technical team the time to build it as we ideally wanted it to be. So we had to make the choice to deliver it as is.</p>
<p>Thanks for your input and investing the time to explore this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin</title>
		<link>http://blogs.exact.com/products/2009/10/your-feedback-on-the-new-request-screen/comment-page-1/#comment-659</link>
		<dc:creator>Martin</dc:creator>
		<pubDate>Thu, 05 Nov 2009 18:04:48 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.exact.com/products/?p=625#comment-659</guid>
		<description>Today I had a nice talk with one of the persons how strongly believes that the numbers should be back. After a short discussion the conclusion is that we don&#039;t need the numbers, but...
- If you don&#039;t provide them, be consistent; when i select to create a task and use the search in the new request screen, the system gives me back the ID instead of the description. When i select to report on a request, in the filter field in shows me the ID instead of description.
- In the new request screen, give the option to sort the request groups. this functionality is removed. 

when these two are back, the numbers indeed are no longer needed</description>
		<content:encoded><![CDATA[<p>Today I had a nice talk with one of the persons how strongly believes that the numbers should be back. After a short discussion the conclusion is that we don&#8217;t need the numbers, but&#8230;<br />
- If you don&#8217;t provide them, be consistent; when i select to create a task and use the search in the new request screen, the system gives me back the ID instead of the description. When i select to report on a request, in the filter field in shows me the ID instead of description.<br />
- In the new request screen, give the option to sort the request groups. this functionality is removed. </p>
<p>when these two are back, the numbers indeed are no longer needed</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ronald Voets</title>
		<link>http://blogs.exact.com/products/2009/10/your-feedback-on-the-new-request-screen/comment-page-1/#comment-657</link>
		<dc:creator>Ronald Voets</dc:creator>
		<pubDate>Thu, 05 Nov 2009 11:25:18 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.exact.com/products/?p=625#comment-657</guid>
		<description>@Ronaldo Thanks for your response. Translation of requests is something we&#039;ve heard from more customers using Synergy across multiple countries (or have users from various nationalities). It&#039;s on our product planning to offer translation possiblities for the (free) fields, labels and sections that users see on a request,</description>
		<content:encoded><![CDATA[<p>@Ronaldo Thanks for your response. Translation of requests is something we&#8217;ve heard from more customers using Synergy across multiple countries (or have users from various nationalities). It&#8217;s on our product planning to offer translation possiblities for the (free) fields, labels and sections that users see on a request,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ronaldo</title>
		<link>http://blogs.exact.com/products/2009/10/your-feedback-on-the-new-request-screen/comment-page-1/#comment-652</link>
		<dc:creator>Ronaldo</dc:creator>
		<pubDate>Wed, 04 Nov 2009 21:51:06 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.exact.com/products/?p=625#comment-652</guid>
		<description>Edgar,
I fully agree with Steffan. If you have many request types, than you have to scroll. This isn&#039;t ergonomic. I showed this &quot;new&quot; screen a few customers and they have mixed feelings, especially with top section - nobody remembers ID of each request and lack of two columns as in previous versions.  
Please take into consideration developing possibility of translating tittles of request categories , tittles of request types and particular fields of request for different languages. This is real problem for international customers. Currently, you can choose interface&#039;s language but crucial functionality doesn’t support it.</description>
		<content:encoded><![CDATA[<p>Edgar,<br />
I fully agree with Steffan. If you have many request types, than you have to scroll. This isn&#8217;t ergonomic. I showed this &#8220;new&#8221; screen a few customers and they have mixed feelings, especially with top section &#8211; nobody remembers ID of each request and lack of two columns as in previous versions.<br />
Please take into consideration developing possibility of translating tittles of request categories , tittles of request types and particular fields of request for different languages. This is real problem for international customers. Currently, you can choose interface&#8217;s language but crucial functionality doesn’t support it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steffan Hoeke</title>
		<link>http://blogs.exact.com/products/2009/10/your-feedback-on-the-new-request-screen/comment-page-1/#comment-602</link>
		<dc:creator>Steffan Hoeke</dc:creator>
		<pubDate>Mon, 26 Oct 2009 08:10:49 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.exact.com/products/?p=625#comment-602</guid>
		<description>Edgar,

Even though (from our perspective) part of the redesign of the &#039;new request&#039; screen is an improvement, we would like to see the list of requests presented in two columns (as with the asp version) instead of one.

The main reason for this is that in the asp version we have *all* available requests on one screen without scrolling, where -with the new screen- we now lose that overview and have to scroll to see the entire list.</description>
		<content:encoded><![CDATA[<p>Edgar,</p>
<p>Even though (from our perspective) part of the redesign of the &#8216;new request&#8217; screen is an improvement, we would like to see the list of requests presented in two columns (as with the asp version) instead of one.</p>
<p>The main reason for this is that in the asp version we have *all* available requests on one screen without scrolling, where -with the new screen- we now lose that overview and have to scroll to see the entire list.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

