<?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: Feedback on new request screen</title>
	<atom:link href="http://blogs.exact.com/products/2009/06/feedback-on-new-request-screen/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.exact.com/products/2009/06/feedback-on-new-request-screen/</link>
	<description></description>
	<lastBuildDate>Wed, 16 May 2012 09:36:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Sunil Girdhari</title>
		<link>http://blogs.exact.com/products/2009/06/feedback-on-new-request-screen/comment-page-1/#comment-27162</link>
		<dc:creator>Sunil Girdhari</dc:creator>
		<pubDate>Fri, 11 May 2012 13:38:39 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.exact.com/products/?p=224#comment-27162</guid>
		<description>Hi John and Gary, 

Thank you for your valuable feedback.
We will definitely take this into consideration as a feature to be added in the near future.</description>
		<content:encoded><![CDATA[<p>Hi John and Gary, </p>
<p>Thank you for your valuable feedback.<br />
We will definitely take this into consideration as a feature to be added in the near future.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gary@VCD</title>
		<link>http://blogs.exact.com/products/2009/06/feedback-on-new-request-screen/comment-page-1/#comment-27111</link>
		<dc:creator>Gary@VCD</dc:creator>
		<pubDate>Thu, 10 May 2012 21:20:27 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.exact.com/products/?p=224#comment-27111</guid>
		<description>I fully agree with John&#039;s idea. Make it so... ;-)</description>
		<content:encoded><![CDATA[<p>I fully agree with John&#8217;s idea. Make it so&#8230; <img src='http://blogs.exact.com/products/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Clark</title>
		<link>http://blogs.exact.com/products/2009/06/feedback-on-new-request-screen/comment-page-1/#comment-26938</link>
		<dc:creator>John Clark</dc:creator>
		<pubDate>Tue, 08 May 2012 20:54:22 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.exact.com/products/?p=224#comment-26938</guid>
		<description>I woud suggest the feature for the recent requests and the drop down capability also be added to the create a new document page.  Right now it is horrible to create a document you have to find it in the list and then click on it instead of just typing it like in the request.  Also would be nice to have the frequently used documents post at the top.</description>
		<content:encoded><![CDATA[<p>I woud suggest the feature for the recent requests and the drop down capability also be added to the create a new document page.  Right now it is horrible to create a document you have to find it in the list and then click on it instead of just typing it like in the request.  Also would be nice to have the frequently used documents post at the top.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bean bag chairs for adults</title>
		<link>http://blogs.exact.com/products/2009/06/feedback-on-new-request-screen/comment-page-1/#comment-21016</link>
		<dc:creator>bean bag chairs for adults</dc:creator>
		<pubDate>Fri, 24 Feb 2012 01:54:45 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.exact.com/products/?p=224#comment-21016</guid>
		<description>hey :) what theme are you utilizing for this 1? (this actual site) I kinda enjoy this and I was wanting to know if this is offered.</description>
		<content:encoded><![CDATA[<p>hey <img src='http://blogs.exact.com/products/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  what theme are you utilizing for this 1? (this actual site) I kinda enjoy this and I was wanting to know if this is offered.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Petr</title>
		<link>http://blogs.exact.com/products/2009/06/feedback-on-new-request-screen/comment-page-1/#comment-16687</link>
		<dc:creator>Petr</dc:creator>
		<pubDate>Mon, 14 Nov 2011 13:24:06 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.exact.com/products/?p=224#comment-16687</guid>
		<description>I find this screen (Request: New) very confusing, even for experienced user. In my opinion, it does have the right elements (features) - but they are implemented in user &quot;unfriendly&quot; way.

Example 1: I am about to enter a new request, for which I do not remeber name, nor ID - therefore I start typing some name, which I think is right - a promissing shortlist displays but suddenly, a number shows up and jumps in the &#039;Regest type&#039; field and I do not know whether it corresponds with the name ...

Example 2: I decide to scroll down trough the list of available processes to find THE ONE - I see categories and within each category I see requests sorted by alphabet - fine. However, I cannot sort it by alphabet regardless of the category - uff.

Here is what is suggest:

1/ List of recent / most used on top (req ID in the brackets)
2/ Searching by name
3/ Show more options control (something, which just shows hidden part of the screen, so nothing like a link to search screen, which is contacting server and waits for response
In this section: multiple search criteria (name, category, security level, role, color, manager, mail merge, etc.)
4/ Results set / section with option to sort by any column

What do you think?</description>
		<content:encoded><![CDATA[<p>I find this screen (Request: New) very confusing, even for experienced user. In my opinion, it does have the right elements (features) &#8211; but they are implemented in user &#8220;unfriendly&#8221; way.</p>
<p>Example 1: I am about to enter a new request, for which I do not remeber name, nor ID &#8211; therefore I start typing some name, which I think is right &#8211; a promissing shortlist displays but suddenly, a number shows up and jumps in the &#8216;Regest type&#8217; field and I do not know whether it corresponds with the name &#8230;</p>
<p>Example 2: I decide to scroll down trough the list of available processes to find THE ONE &#8211; I see categories and within each category I see requests sorted by alphabet &#8211; fine. However, I cannot sort it by alphabet regardless of the category &#8211; uff.</p>
<p>Here is what is suggest:</p>
<p>1/ List of recent / most used on top (req ID in the brackets)<br />
2/ Searching by name<br />
3/ Show more options control (something, which just shows hidden part of the screen, so nothing like a link to search screen, which is contacting server and waits for response<br />
In this section: multiple search criteria (name, category, security level, role, color, manager, mail merge, etc.)<br />
4/ Results set / section with option to sort by any column</p>
<p>What do you think?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Maarten Tigchelaar</title>
		<link>http://blogs.exact.com/products/2009/06/feedback-on-new-request-screen/comment-page-1/#comment-2736</link>
		<dc:creator>Maarten Tigchelaar</dc:creator>
		<pubDate>Tue, 22 Jun 2010 14:31:37 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.exact.com/products/?p=224#comment-2736</guid>
		<description>Additional note. The start of a procesflow should be integrated into this screen as well. Now users have to click on a button to see the available procesflow options. Most users don&#039;t know the difference between a single request or a proces flow.</description>
		<content:encoded><![CDATA[<p>Additional note. The start of a procesflow should be integrated into this screen as well. Now users have to click on a button to see the available procesflow options. Most users don&#8217;t know the difference between a single request or a proces flow.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shawn Gamble</title>
		<link>http://blogs.exact.com/products/2009/06/feedback-on-new-request-screen/comment-page-1/#comment-2414</link>
		<dc:creator>Shawn Gamble</dc:creator>
		<pubDate>Tue, 25 May 2010 13:36:06 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.exact.com/products/?p=224#comment-2414</guid>
		<description>I agree With Christian about being able to Expand and Collapse the workflow groups. Infact I have Enhancement request 34.517.085 created for this specific task.
In my Environment I have some groups that have 200 plus Workflow it is a pain in the butt to scroll through pages of workflow to get to the one your want. some people just would like to collapse Large groups that they know they have no interest in using.</description>
		<content:encoded><![CDATA[<p>I agree With Christian about being able to Expand and Collapse the workflow groups. Infact I have Enhancement request 34.517.085 created for this specific task.<br />
In my Environment I have some groups that have 200 plus Workflow it is a pain in the butt to scroll through pages of workflow to get to the one your want. some people just would like to collapse Large groups that they know they have no interest in using.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christian Ibetsberger</title>
		<link>http://blogs.exact.com/products/2009/06/feedback-on-new-request-screen/comment-page-1/#comment-1672</link>
		<dc:creator>Christian Ibetsberger</dc:creator>
		<pubDate>Wed, 17 Mar 2010 18:48:47 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.exact.com/products/?p=224#comment-1672</guid>
		<description>Additional note to my idea above: It a certain (&gt;10) number of requests is shown it would be more efficient to be able to &#039;expand&#039; a specific request group to show all requests. It is not neccessary to to show all requests of all categories. 
So I would see all requests groups and all f.e. 30 recently used requests and I could expand the 1 group I m interested in to pick a request that was not recently used.</description>
		<content:encoded><![CDATA[<p>Additional note to my idea above: It a certain (&gt;10) number of requests is shown it would be more efficient to be able to &#8216;expand&#8217; a specific request group to show all requests. It is not neccessary to to show all requests of all categories.<br />
So I would see all requests groups and all f.e. 30 recently used requests and I could expand the 1 group I m interested in to pick a request that was not recently used.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christian Ibetsberger</title>
		<link>http://blogs.exact.com/products/2009/06/feedback-on-new-request-screen/comment-page-1/#comment-1671</link>
		<dc:creator>Christian Ibetsberger</dc:creator>
		<pubDate>Wed, 17 Mar 2010 18:29:13 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.exact.com/products/?p=224#comment-1671</guid>
		<description>We also used the IDs to create a sort order other than alphabetical. Requests for general purposes are always on top, those for specific purposes are on bottom of each category. Sometimes the sort order also follows phases, for example in the HR application prozess.

We do not miss the IDs other than for that purpose, since it is always possible to create a request by entering the ID if it is known or noted on a document.

The request screen would look &#039;nicer&#039; if the colours would be shown again (I m a visual user) - even if its of no use otherwise. by different colours it would be easier to distinguish the categories when scrolling. 

In the recent used pane there is no reference to the category and the order of the entries changes according to the used requests. Again a color &#039;code&#039; might help spotting right request or be a &#039;reference&#039; the color of a category.

For customers with less than 50 requests, two columns would be way easier (no scrolling). For customers with more than 50 requests I wonder how they manage with the short request descriptions. The description field should be longer.

If I had to programm this I guess would simply have made a setting for the number of recently used request you wanna see, for example 20. And then show those 20 in two columns with categories, and a button to show all instead in the same layout. That way, users can choose to see recent 10, 20, 50 (what fits on one screen or even all). The more recently used requests you choose, the less will the position/order of the requests change.</description>
		<content:encoded><![CDATA[<p>We also used the IDs to create a sort order other than alphabetical. Requests for general purposes are always on top, those for specific purposes are on bottom of each category. Sometimes the sort order also follows phases, for example in the HR application prozess.</p>
<p>We do not miss the IDs other than for that purpose, since it is always possible to create a request by entering the ID if it is known or noted on a document.</p>
<p>The request screen would look &#8216;nicer&#8217; if the colours would be shown again (I m a visual user) &#8211; even if its of no use otherwise. by different colours it would be easier to distinguish the categories when scrolling. </p>
<p>In the recent used pane there is no reference to the category and the order of the entries changes according to the used requests. Again a color &#8216;code&#8217; might help spotting right request or be a &#8216;reference&#8217; the color of a category.</p>
<p>For customers with less than 50 requests, two columns would be way easier (no scrolling). For customers with more than 50 requests I wonder how they manage with the short request descriptions. The description field should be longer.</p>
<p>If I had to programm this I guess would simply have made a setting for the number of recently used request you wanna see, for example 20. And then show those 20 in two columns with categories, and a button to show all instead in the same layout. That way, users can choose to see recent 10, 20, 50 (what fits on one screen or even all). The more recently used requests you choose, the less will the position/order of the requests change.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Danny Bonthuis</title>
		<link>http://blogs.exact.com/products/2009/06/feedback-on-new-request-screen/comment-page-1/#comment-771</link>
		<dc:creator>Danny Bonthuis</dc:creator>
		<pubDate>Mon, 23 Nov 2009 14:07:57 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.exact.com/products/?p=224#comment-771</guid>
		<description>The only thing that I really like about the request screen is the top ten, that is a big improvement...but I miss the ID&#039;s. and the list of requests is now really long so a lot of scrolling and searching....

After 6 hours of working actively in 242 I can still stand by my innitial thoughts and the feedback given by customers during the Controlled Release faze of release 241 where this screen was introduced.</description>
		<content:encoded><![CDATA[<p>The only thing that I really like about the request screen is the top ten, that is a big improvement&#8230;but I miss the ID&#8217;s. and the list of requests is now really long so a lot of scrolling and searching&#8230;.</p>
<p>After 6 hours of working actively in 242 I can still stand by my innitial thoughts and the feedback given by customers during the Controlled Release faze of release 241 where this screen was introduced.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

