eVision - User contributions [en]

Smart Spec

2016-03-26T07:10:14Z

Jshearer: Updated link.

{{Infobox software
| name = Smart Spec
| logo = SmartSpecLogo.png
| logo_size = 250
| logo caption = SmartSpec Logo
| screenshot = SmartSpecScreenshot.png
| caption = SmartSpec running on Windows 8.1
| website = {{URL|http://smartspec.evisionservices.com}}
}}
'''Smart Spec''' is an application developed by [[eVision Services]] for Windows PCs, as well as Android tablet and Apple iPad devices. The purpose of the application is to replace the specification books used by cabinet manufacturers in the kitchen and bath industry by offering their contents in an accessible and interactive digital format. Intended to be used by dealers who sell cabinets, it enables those users to view the contents of the physical specification books used by manufacturers on a PC or tablet device, in a format that is targeted specifically to each platform.

== Features ==

* Search a collection of high quality graphics, charts, and illustrations
* Compare products side by side for easy selection
* Search for a series of Modifications that are validated against the selected product so you never question what is available
* Add your own personal notes to all Products, Styles, and Finishes
* Set Products as Favorites for easy future reference
* Easily enhance the shoppers experience by creating innovative Idea Boards to store your design ideas and even create and share potential project Idea Boards with clients
* Showroom Companion – Capture client wants and needs for qualifying consumers and managing sales leads and projects
* Receive/View important Alerts, Updates, and Sales Promotions right in the program from your sponsoring manufacture so you always know what is going on

== See Also ==
[[Smart Spec - Tips & Tricks]]

[[Category:SmartSpec]]

Nuget Package Repository

2016-03-01T05:32:49Z

Jshearer: Updated feed instructions.

eVision hosts an assortment of code libraries on our locally-hosted NuGet repository. While the packages within our repository were not specifically designed to be consumed by third-parties, we have purposely left them publicly-accessible so that our clients can leverage some of our internal tools in order to interact with the various systems that store and process their data.

It is worth noting that these resources are the exact packages that we use within our internal projects, so these packages get tested fairly thoroughly and are well supported by our internal applications. While most of the packages don't have any documentation, there are some that include some degree of documentation in the format of VS-compatible "xmlcomments", which provide some level of documentation by way of Intellisense within Visual Studio.

== Prerequisites ==
* Visual Studio 2010 users must install the [https://visualstudiogallery.msdn.microsoft.com/27077b70-9dad-4c64-adcf-c7cf6bc9970c NuGet extension for Visual Studio].
* Visual Studio 2012 includes NuGet by default, and thus requires no additional work.

== Adding the eVision NuGet Server ==
In order to consume eVision's NuGet packages, you must add eVision's NuGet server to the list of NuGet package sources in Visual Studio. This will allow the eVision packages to show up in search results so that they can be added to your projects.

# Open Visual Studio and navigate to <code>Tools</code> > <code>Options</code> > <code>NuGet Package Manager</code> > <code>Package Sources</code>.
# Add a new package source by clicking the plus (<code>+</code>) button.
# Enter a name for the package source. For the location, enter <code><nowiki>http://nuget.evisionservices.com/nuget</nowiki></code>
# Click <code>OK</code> to save the changes.

== Related Information ==
* http://docs.nuget.org/docs/start-here/installing-nuget
* http://docs.nuget.org/docs/start-here/managing-nuget-packages-using-the-dialog

Order Express - Advanced Troubleshooting

2016-02-29T18:48:16Z

Jshearer:

__FORCETOC__

== Standalone Version ==
[[File:OrderExpressStandaloneDownload.png|thumbnail|Standalone Version Download]]
[[File:OrderExpressStandaloneExexecutable.png|thumbnail|Locating the Executable]]
In order to debug certain issues, eVision Support may provide you with a link to download a ''Standalone Version'' of Order Express. This version of Order Express does not require installation and is primarily used to identify whether an issue is caused by a broken installation, or with Order Express directly.

<ol>
<li>Open the link that was provided to you by eVision Support</li>
<li>Click the ''Download'' button on the page and save the file to your desktop</li>
<li>Extract the downloaded file to a folder. (Note: Ensure the file is not marked as "Blocked" before you perform the extraction.)</li>
<li>Open the folder and locate the executable file for the application</li>
<li>If the program loads up successfully, the issue is the result of the installation routine. Perform the ''Extended (Full) Uninstall'' on the [[Uninstalling_Order_Express|Uninstalling Order Express]] page.</li>
<li>If the program does '''not''' load successfully, the cause of the issue is within the application.</li>
<li>Ensure that you communicate the results of this test back to eVision Support for additional troubleshooting steps.</li>
</ol>

<div style="clear: both"></div>
== Standalone Version Will Not Connect ==
[[File:OrderExpress_Standalone_Unblock1.png|thumbnail|Opening the "Properties" window]]
[[File:OrderExpress_Standalone_Unblock2.png|thumbnail|Unblocking the file]]
There exists a security feature within Windows that can sometimes prevent Standalone Versions of Order Express from working correctly. Files that are downloaded from an non-trusted web location are marked as "Blocked" by default, preventing them from retrieving content from the internet. The solution for this issue is to "unblock" the downloaded file.

<ol>
<li>Right-click on the file that was downloaded from the internet.</li>
<li>Select <code>Properties</code> from the context menu.</li>
<li>Find the <code>Unblock</code> button at the bottom of the dialog, and click it.</li>
<li>The file can now be opened. If the file is a zip file, it can now be extracted.</li>
</ol>

'''Note:''' If the blocked file is a zip file, it ''must'' be unblocked prior to extracting it, or you will likely encounter issues with the unzipped files.

<div style="clear: both"></div>
== Duplicate DbProviderFactories ==

Due to an issue in certain software, you may receive the following error:
<code>The 'DbProviderFactories' section can only appear once per config file.</code>

This occurs because the [[Machine.config]] file on the computer contains erroneous information and must be fixed by hand.

<ol>
<li>Locate the <code>machine.config</code> file. Refer to the [[Machine.config]] article for instructions on locating it.</li>
<li>Once found, make a backup of the file and put it in a safe location.</li>
<li>Open the original file in a text editor and search for <code><DbProviderFactories></code>. This text should appear more than once.</li>
<li>Compare your file to the block of text below. If the file contains text that matches this, delete the block of text.
<syntaxhighlight lang="xml" enclose="div">
<system.data>
<DbProviderFactories>
<add name="IBM DB2 for i5/OS .NET Provider" invariant="IBM.Data.DB2.iSeries" description=".NET Framework Data Provider for i5/OS" type="IBM.Data.DB2.iSeries.iDB2Factory, IBM.Data.DB2.iSeries, Version=12.0.0.0, Culture=neutral, PublicKeyToken=9cdb2ebfb1f93a26" />
</DbProviderFactories>
</system.data>
</syntaxhighlight></li>
<li>Ensure that the file is saved before exiting the text editor.</li>
<li>The issue should now be resolved.</li>
</ol>

<div style="clear: both"></div>
== Event Log Errors ==
[[File:Order-Express-Has-Stopped-Working.png|thumbnail|Error Dialog]]
Order Express may occasionally crash without allowing the user to describe and submit the error to the support team.

When this occurs, the user will need to retrieve the log files and submit them manually.
=== Instructions ===

<ol>

<li> Press the "Windows" key, or click the "Start" button in the bottom-left corner of the screen.<br />
[[File:Windows-key.png|border|left]]
<div style="clear: both"></div>
<br />
</li>

<li>
Once on the Start screen, type the text <code>Event Logs</code>. A search box should display as you begin typing.<br />
Wait for the search results to appear.<br />
Click the top entry, which should read <code>View event logs</code>.<br />
[[File:Search-event-logs-windows8.png|border|left]]
<div style="clear: both"></div>
<br />
</li>

<li>
In the window that appears, click the arrow to the left of <code>Windows Logs</code><br />
[[File:Event-logs-default.png|border|left]]
<div style="clear: both"></div>
<br />
</li>

<li>
Select the <code>Application</code> entry.<br />
[[File:Event-logs-windows.png|border|left]]
<div style="clear: both"></div>
<br />
</li>

<li>
In the list shown in the middle of the window, locate the most recent entry that meets the following criteria:
<ul>
<li>It uses the <code>Error</code> Icon: [[File:Event-logs-error-icon.png]]</li>
<li>The <code>Source</code> column should contain <code>.NET Runtime</code></li>
</ul>
<div style="clear: both"></div>
<br />
</li>

<li>
Right-click on that entry, select <code>Copy</code>, and then select <code>Copy Details as Text</code>.<br />
[[File:Event-logs-dot-net-runtime-copy.png|border|left]]
<div style="clear: both"></div>
<br />
</li>

<li>
At this point, the contents of the error log are on your clipboard, and can be pasted into any text editor.
</li>

<li>
Open a text editor (such as Notepad), and use the <code>Paste</code> command to insert the error details.
</li>

<li>
Save the text document, and attach it to an email to our support team.
</li>

</ol>

[[Category:Order Express]]

Order Express - Advanced Troubleshooting

2016-02-29T16:47:11Z

Jshearer: Fix filename

__FORCETOC__

== Standalone Version ==
[[File:OrderExpressStandaloneDownload.png|thumbnail|Standalone Version Download]]
[[File:OrderExpressStandaloneExecutable.png|thumbnail|Locating the Executable]]
In order to debug certain issues, eVision Support may provide you with a link to download a ''Standalone Version'' of Order Express. This version of Order Express does not require installation and is primarily used to identify whether an issue is caused by a broken installation, or with Order Express directly.

<ol>
<li>Open the link that was provided to you by eVision Support</li>
<li>Click the ''Download'' button on the page and save the file to your desktop</li>
<li>Extract the downloaded file to a folder. (Note: Ensure the file is not marked as "Blocked" before you perform the extraction.)</li>
<li>Open the folder and locate the executable file for the application</li>
<li>If the program loads up successfully, the issue is the result of the installation routine. Perform the ''Extended (Full) Uninstall'' on the [[Uninstalling_Order_Express|Uninstalling Order Express]] page.</li>
<li>If the program does '''not''' load successfully, the cause of the issue is within the application.</li>
<li>Ensure that you communicate the results of this test back to eVision Support for additional troubleshooting steps.</li>
</ol>

<div style="clear: both"></div>
== Standalone Version Will Not Connect ==
[[File:OrderExpress_Standalone_Unblock1.png|thumbnail|Opening the "Properties" window]]
[[File:OrderExpress_Standalone_Unblock2.png|thumbnail|Unblocking the file]]
There exists a security feature within Windows that can sometimes prevent Standalone Versions of Order Express from working correctly. Files that are downloaded from an non-trusted web location are marked as "Blocked" by default, preventing them from retrieving content from the internet. The solution for this issue is to "unblock" the downloaded file.

<ol>
<li>Right-click on the file that was downloaded from the internet.</li>
<li>Select <code>Properties</code> from the context menu.</li>
<li>Find the <code>Unblock</code> button at the bottom of the dialog, and click it.</li>
<li>The file can now be opened. If the file is a zip file, it can now be extracted.</li>
</ol>

'''Note:''' If the blocked file is a zip file, it ''must'' be unblocked prior to extracting it, or you will likely encounter issues with the unzipped files.

<div style="clear: both"></div>
== Duplicate DbProviderFactories ==

Due to an issue in certain software, you may receive the following error:
<code>The 'DbProviderFactories' section can only appear once per config file.</code>

This occurs because the [[Machine.config]] file on the computer contains erroneous information and must be fixed by hand.

<ol>
<li>Locate the <code>machine.config</code> file. Refer to the [[Machine.config]] article for instructions on locating it.</li>
<li>Once found, make a backup of the file and put it in a safe location.</li>
<li>Open the original file in a text editor and search for <code><DbProviderFactories></code>. This text should appear more than once.</li>
<li>Compare your file to the block of text below. If the file contains text that matches this, delete the block of text.
<syntaxhighlight lang="xml" enclose="div">
<system.data>
<DbProviderFactories>
<add name="IBM DB2 for i5/OS .NET Provider" invariant="IBM.Data.DB2.iSeries" description=".NET Framework Data Provider for i5/OS" type="IBM.Data.DB2.iSeries.iDB2Factory, IBM.Data.DB2.iSeries, Version=12.0.0.0, Culture=neutral, PublicKeyToken=9cdb2ebfb1f93a26" />
</DbProviderFactories>
</system.data>
</syntaxhighlight></li>
<li>Ensure that the file is saved before exiting the text editor.</li>
<li>The issue should now be resolved.</li>
</ol>

<div style="clear: both"></div>
== Event Log Errors ==
[[File:Order-Express-Has-Stopped-Working.png|thumbnail|Error Dialog]]
Order Express may occasionally crash without allowing the user to describe and submit the error to the support team.

When this occurs, the user will need to retrieve the log files and submit them manually.
=== Instructions ===

<ol>

<li> Press the "Windows" key, or click the "Start" button in the bottom-left corner of the screen.<br />
[[File:Windows-key.png|border|left]]
<div style="clear: both"></div>
<br />
</li>

<li>
Once on the Start screen, type the text <code>Event Logs</code>. A search box should display as you begin typing.<br />
Wait for the search results to appear.<br />
Click the top entry, which should read <code>View event logs</code>.<br />
[[File:Search-event-logs-windows8.png|border|left]]
<div style="clear: both"></div>
<br />
</li>

<li>
In the window that appears, click the arrow to the left of <code>Windows Logs</code><br />
[[File:Event-logs-default.png|border|left]]
<div style="clear: both"></div>
<br />
</li>

<li>
Select the <code>Application</code> entry.<br />
[[File:Event-logs-windows.png|border|left]]
<div style="clear: both"></div>
<br />
</li>

<li>
In the list shown in the middle of the window, locate the most recent entry that meets the following criteria:
<ul>
<li>It uses the <code>Error</code> Icon: [[File:Event-logs-error-icon.png]]</li>
<li>The <code>Source</code> column should contain <code>.NET Runtime</code></li>
</ul>
<div style="clear: both"></div>
<br />
</li>

<li>
Right-click on that entry, select <code>Copy</code>, and then select <code>Copy Details as Text</code>.<br />
[[File:Event-logs-dot-net-runtime-copy.png|border|left]]
<div style="clear: both"></div>
<br />
</li>

<li>
At this point, the contents of the error log are on your clipboard, and can be pasted into any text editor.
</li>

<li>
Open a text editor (such as Notepad), and use the <code>Paste</code> command to insert the error details.
</li>

<li>
Save the text document, and attach it to an email to our support team.
</li>

</ol>

[[Category:Order Express]]

File:Windows10-SmartScreen-DialogConfirm.png

2015-07-29T17:47:45Z

Jshearer: Windows SmartScreen may prevent Order Express from installing. Checking the box reveals a hidden "Run Anyway" button. Click that button to continue.

Windows SmartScreen may prevent Order Express from installing. Checking the box reveals a hidden "Run Anyway" button. Click that button to continue.

File:Windows10-SmartScreen Dialog.png

2015-07-29T17:45:55Z

Jshearer: Windows SmartScreen may prevent Order Express from installing. When it does, this screen is displayed.

Windows SmartScreen may prevent Order Express from installing. When it does, this screen is displayed.

Order Express - Advanced Troubleshooting

2015-06-09T18:25:03Z

Jshearer: Added walkthrough for manually submitting error details.

__FORCETOC__

== Standalone Version ==
[[File:OrderExpressStandaloneDownload.png|thumbnail|Standalone Version Download]]
[[File:OrderExpressStandaloneExexecutable.png|thumbnail|Locating the Executable]]
In order to debug certain issues, eVision Support may provide you with a link to download a ''Standalone Version'' of Order Express. This version of Order Express does not require installation and is primarily used to identify whether an issue is caused by a broken installation, or with Order Express directly.

<ol>
<li>Open the link that was provided to you by eVision Support</li>
<li>Click the ''Download'' button on the page and save the file to your desktop</li>
<li>Extract the downloaded file to a folder. (Note: Ensure the file is not marked as "Blocked" before you perform the extraction.)</li>
<li>Open the folder and locate the executable file for the application</li>
<li>If the program loads up successfully, the issue is the result of the installation routine. Perform the ''Extended (Full) Uninstall'' on the [[Uninstalling_Order_Express|Uninstalling Order Express]] page.</li>
<li>If the program does '''not''' load successfully, the cause of the issue is within the application.</li>
<li>Ensure that you communicate the results of this test back to eVision Support for additional troubleshooting steps.</li>
</ol>

<div style="clear: both"></div>
== Standalone Version Will Not Connect ==
[[File:OrderExpress_Standalone_Unblock1.png|thumbnail|Opening the "Properties" window]]
[[File:OrderExpress_Standalone_Unblock2.png|thumbnail|Unblocking the file]]
There exists a security feature within Windows that can sometimes prevent Standalone Versions of Order Express from working correctly. Files that are downloaded from an non-trusted web location are marked as "Blocked" by default, preventing them from retrieving content from the internet. The solution for this issue is to "unblock" the downloaded file.

<ol>
<li>Right-click on the file that was downloaded from the internet.</li>
<li>Select <code>Properties</code> from the context menu.</li>
<li>Find the <code>Unblock</code> button at the bottom of the dialog, and click it.</li>
<li>The file can now be opened. If the file is a zip file, it can now be extracted.</li>
</ol>

'''Note:''' If the blocked file is a zip file, it ''must'' be unblocked prior to extracting it, or you will likely encounter issues with the unzipped files.

<div style="clear: both"></div>
== Duplicate DbProviderFactories ==

Due to an issue in certain software, you may receive the following error:
<code>The 'DbProviderFactories' section can only appear once per config file.</code>

This occurs because the [[Machine.config]] file on the computer contains erroneous information and must be fixed by hand.

<ol>
<li>Locate the <code>machine.config</code> file. Refer to the [[Machine.config]] article for instructions on locating it.</li>
<li>Once found, make a backup of the file and put it in a safe location.</li>
<li>Open the original file in a text editor and search for <code><DbProviderFactories></code>. This text should appear more than once.</li>
<li>Compare your file to the block of text below. If the file contains matching text, delete it.
<syntaxhighlight lang="xml" enclose="div">
<system.data>
<DbProviderFactories>
<add name="IBM DB2 for i5/OS .NET Provider" invariant="IBM.Data.DB2.iSeries" description=".NET Framework Data Provider for i5/OS" type="IBM.Data.DB2.iSeries.iDB2Factory, IBM.Data.DB2.iSeries, Version=12.0.0.0, Culture=neutral, PublicKeyToken=9cdb2ebfb1f93a26" />
</DbProviderFactories>
</system.data>
</syntaxhighlight></li>
<li>Ensure that the file is saved before exiting the text editor.</li>
<li>The issue should now be resolved.</li>
</ol>

<div style="clear: both"></div>
== Event Log Errors ==
[[File:Order-Express-Has-Stopped-Working.png|thumbnail|Error Dialog]]
Order Express may occasionally crash without allowing the user to describe and submit the error to the support team.

When this occurs, the user will need to retrieve the log files and submit them manually.
=== Instructions ===

<ol>

<li> Press the "Windows" key, or click the "Start" button in the bottom-left corner of the screen.<br />
[[File:Windows-key.png|border|left]]
<div style="clear: both"></div>
<br />
</li>

<li>
Once on the Start screen, type the text <code>Event Logs</code>. A search box should display as you begin typing.<br />
Wait for the search results to appear.<br />
Click the top entry, which should read <code>View event logs</code>.<br />
[[File:Search-event-logs-windows8.png|border|left]]
<div style="clear: both"></div>
<br />
</li>

<li>
In the window that appears, click the arrow to the left of <code>Windows Logs</code><br />
[[File:Event-logs-default.png|border|left]]
<div style="clear: both"></div>
<br />
</li>

<li>
Select the <code>Application</code> entry.<br />
[[File:Event-logs-windows.png|border|left]]
<div style="clear: both"></div>
<br />
</li>

<li>
In the list shown in the middle of the window, locate the most recent entry that meets the following criteria:
<ul>
<li>It uses the <code>Error</code> Icon: [[File:Event-logs-error-icon.png]]</li>
<li>The <code>Source</code> column should contain <code>.NET Runtime</code></li>
</ul>
<div style="clear: both"></div>
<br />
</li>

<li>
Right-click on that entry, select <code>Copy</code>, and then select <code>Copy Details as Text</code>.<br />
[[File:Event-logs-dot-net-runtime-copy.png|border|left]]
<div style="clear: both"></div>
<br />
</li>

<li>
At this point, the contents of the error log are on your clipboard, and can be pasted into any text editor.
</li>

<li>
Open a text editor (such as Notepad), and use the <code>Paste</code> command to insert the error details.
</li>

<li>
Save the text document, and attach it to an email to our support team.
</li>

</ol>

[[Category:Order Express]]

File:Event-logs-error-icon.png

2015-06-09T18:01:04Z

Jshearer: Event log error icon

Event log error icon

File:Event-logs-dot-net-runtime-copy.png

2015-06-09T17:53:23Z

Jshearer: Copying the details of a log entry.

Copying the details of a log entry.

File:Event-logs-windows.png

2015-06-09T17:52:12Z

Jshearer: Screenshot of the "Event Logs > Windows" tree-view.

Screenshot of the "Event Logs > Windows" tree-view.

File:Event-logs-default.png

2015-06-09T17:51:36Z

Jshearer: Screenshot of the "Event Logs" tree-view.

Screenshot of the "Event Logs" tree-view.

File:Search-event-logs-windows8.png

2015-06-09T17:50:39Z

Jshearer: Searching for the "Event Logs" application in Windows 8.1.

Searching for the "Event Logs" application in Windows 8.1.

File:Windows-key.png

2015-06-09T17:48:56Z

Jshearer: Screenshot of the "Windows" button on the taskbar within Windows 8.1.

Screenshot of the "Windows" button on the taskbar within Windows 8.1.

File:Order-Express-Has-Stopped-Working.png

2015-06-09T17:44:57Z

Jshearer: Screenshot of the "Order Express Has Stopped Working" dialog.

Screenshot of the "Order Express Has Stopped Working" dialog.

Order Express - Release Notes

2015-03-05T16:26:13Z

Jshearer: Created page with "test"

test

Nuget Package Repository

2014-12-10T16:16:44Z

Jshearer: Adding itemized instructions.

eVision hosts an assortment of code libraries on our locally-hosted NuGet repository. While the packages within our repository were not specifically designed to be consumed by third-parties, we have purposely left them publicly-accessible so that our clients can leverage some of our internal tools in order to interact with the various systems that store and process their data.

It is worth noting that these resources are the exact packages that we use within our internal projects, so these packages get tested fairly thoroughly and are well supported by our internal applications. While most of the packages don't have any documentation, there are some that include some degree of documentation in the format of VS-compatible "xmlcomments", which provide some level of documentation by way of Intellisense within Visual Studio.

== Prerequisites ==
* Visual Studio 2010 users must install the [https://visualstudiogallery.msdn.microsoft.com/27077b70-9dad-4c64-adcf-c7cf6bc9970c NuGet extension for Visual Studio].
* Visual Studio 2012 includes NuGet by default, and thus requires no additional work.

== Adding the eVision NuGet Server ==
In order to consume eVision's NuGet packages, you must add eVision's NuGet server to the list of NuGet package sources in Visual Studio. This will allow the eVision packages to show up in search results so that they can be added to your projects.

# Open Visual Studio and navigate to <code>Tools</code> > <code>Options</code> > <code>NuGet Package Manager</code> > <code>Package Sources</code>.
# Add a new package source by clicking the plus (<code>+</code>) button.
# Enter a name for the package source. For the location, enter <code><nowiki>http://nuget.evisionservices.com/nuget/Ensemble</nowiki></code>
# Click <code>OK</code> to save the changes.

The NuGet package source repository is also accessible via the web, at http://nuget.evisionservices.com/feeds/Ensemble

== Related Information ==
* http://docs.nuget.org/docs/start-here/installing-nuget
* http://docs.nuget.org/docs/start-here/managing-nuget-packages-using-the-dialog

Order Express

2014-11-10T23:45:40Z

Jshearer: Added major version history.

{{Infobox software
| name = Order Express
| logo = OrderExpressLogo.png
| logo_size = 150
| logo caption = Order Express Logo
| screenshot = OrderExpressScreenshot.png
| caption = Order Express running on Windows 8.1
| website = {{URL|http://orderexpress.evisionservices.com}}
}}
'''Order Express''' is an ordering application developed by [[eVision Services]]. It primarily services manufacturers and dealers in the kitchen and bath industry by allowing them to obtain price quotes using up-to-the-minute pricing data directly from the manufacturers.

== Features ==

* Advanced Quoting and Ordering Solution
* Full Specials Manager
* Secure User Login and Catalog Selection
* Cloud Storage of all Quotes and Orders
* Offline Creation and Editing of Projects
* Integrate to ERP, Biz, or Manufacturing System
* Extremely Low Cost Per User
* Automatic Updating of Application
* Automatic Updating of Product Catalog

== System Requirements ==

=== Minimum ===
* 1.3GHz or faster processor
* Microsoft® Windows® XP with Service Pack 3 (32-bit)/ Microsoft® Windows® XP with Service Pack 2 (64-bit)
* 2GB of RAM
* 320MB of available hard-disk space
* 1024x768 screen resolution
* Internet Explorer 8, 9, or 10; Firefox Extended Support Release; Chrome 36.0.1985.125

=== Recommended ===
* 2.0GHz or faster dual-core processor
* Microsoft® Windows® 8.1
* 4GB of RAM
* 10GB of available hard-disk space
* 1920x1080 screen resolution
* Internet Explorer 11; Firefox 30; Chrome 36.0.1985.125

== Network Requirements ==

=== Overview ===

Order Express is deployed to end users as a ClickOnce application requiring a "Full Trust" security zone. Because the Order Express binaries are not digitally signed, it is unfortunately not possible to set a deployment policy to allow Order Express to be installed independently of other ClickOnce applications. Subsequently, it is suggested (although not ''currently'' required) that end-users of Order Express have administrative access of their local machine.

Additional information regarding ClickOnce can be found at the following link: http://msdn.microsoft.com/en-us/library/t71a733d.aspx

In addition to the requirements of the security policy of the local machine, Order Express also has a number of requirements in terms of network connectivity. At its very core, Order Express is an internet application, relying on its ability to synchronize data to and from remote systems to keep both manufacturers and dealers informed throughout the ordering process.

Order Express must be able to access the following ports on remote machines. In the interest of helping network administrators maintain network security during the deployment of Order Express, the information in the list below is granular enough to reliably identify network traffic from Order Express so that it can be allowed.

=== Hosts And Ports ===
* Feature: Status Notifications
** Host: <code>smtp.gmail.com</code>
** Ports: <code>25:TCP</code>, <code>465:TCP</code>, <code>587:TCP</code>

* Feature: ClickOnce Install/Update, Setup & Admin (Accessed via Web-Browser), Database Synchronization
** Host: <code>*.evisionservices.com</code>
** Ports: <code>80:TCP</code>, <code>80:UDP</code>, <code>443:TCP</code>, <code>443:UDP</code>, <code>1433:TCP</code>

* Feature: Catalog Install/Update, Image Install/Update
** Host: <code>s3.amazonaws.com</code>
** Ports: <code>80:TCP</code>, <code>443:TCP</code>

In addition to the above, Order Express must be able to establish/maintain an ongoing connection to a remote SQL Server.
While the initial handshake only requires port <code>1433:TCP</code> to be open, additional ports must be available to complete the handshake process.

Refer to the following link for more information: https://support.microsoft.com/kb/287932/en-us

== Major Version History ==

=== Version 2.0 ===
This was the first version of the desktop version of Order Express. Previous versions were implemented as web applications.

=== Version 2.1 ===
This version of Order Express introduced the concept of installing multiple catalogs alongside each other. Previously users were only able to install a single catalog at a time, and were required to uninstall the application prior to installing one from another manufacturer.

=== Version 2.2 ===
<ul>
<li>Completely revised back-end architecture for saving and loading projects. Projects that were stored in the legacy format are automatically converted to the new format when they are opened. Projects stored in the new format are 1/10th the size of those stored in the previous format, substantially reducing the time needed to save and load projects.</li>
<li>Setup & Admin is no longer built into the application. Instead, it has been replaced with a more robust version as a web application.</li>
</ul>

=== Version 2.3 ===
With this release, Order Express becomes substantially more reliable for users with slow or unstable internet connections. Many features within Order Express now leverage our powerful "Web API" for the offloading of various tasks to a central server. Our decision to use HTTP as our communications protocol allows us to consolidate numerous networking protocols into an industry-standard connection method that is almost universally allowed through corporate intranets, all without requiring complex configurations to the end-user network.

== See Also ==
* [[Order Express FAQ]]
* [[Uninstalling Order Express]]
* [[Troubleshooting Order Express]]

[[Category:Order Express]]

Order Express - Advanced Troubleshooting

2014-11-10T16:46:48Z

Jshearer: Adding instructions for unblocking files that have been downloaded from the internet.

File:OrderExpress Standalone Unblock2.png

2014-11-10T16:24:11Z

Jshearer: Unblocking a file that has been downloaded from the internet.

Unblocking a file that has been downloaded from the internet.

File:OrderExpress Standalone Unblock1.png

2014-11-10T16:23:34Z

Jshearer: Opening the "properties" window of a downloaded file.

Opening the "properties" window of a downloaded file.

Order Express

2014-10-24T15:46:56Z

Jshearer: /* Hosts And Ports */ Wrapped ports in code tags.

{{Infobox software
| name = Order Express
| logo = OrderExpressLogo.png
| logo_size = 150
| logo caption = Order Express Logo
| screenshot = OrderExpressScreenshot.png
| caption = Order Express running on Windows 8.1
| website = {{URL|http://orderexpress.evisionservices.com}}
}}
'''Order Express''' is an ordering application developed by [[eVision Services]]. It primarily services manufacturers and dealers in the kitchen and bath industry by allowing them to obtain price quotes using up-to-the-minute pricing data directly from the manufacturers.

== Features ==

* Advanced Quoting and Ordering Solution
* Full Specials Manager
* Secure User Login and Catalog Selection
* Cloud Storage of all Quotes and Orders
* Offline Creation and Editing of Projects
* Integrate to ERP, Biz, or Manufacturing System
* Extremely Low Cost Per User
* Automatic Updating of Application
* Automatic Updating of Product Catalog

== System Requirements ==

=== Minimum ===
* 1.3GHz or faster processor
* Microsoft® Windows® XP with Service Pack 3 (32-bit)/ Microsoft® Windows® XP with Service Pack 2 (64-bit)
* 2GB of RAM
* 320MB of available hard-disk space
* 1024x768 screen resolution
* Internet Explorer 8, 9, or 10; Firefox Extended Support Release; Chrome 36.0.1985.125

=== Recommended ===
* 2.0GHz or faster dual-core processor
* Microsoft® Windows® 8.1
* 4GB of RAM
* 10GB of available hard-disk space
* 1920x1080 screen resolution
* Internet Explorer 11; Firefox 30; Chrome 36.0.1985.125

== Network Requirements ==

=== Overview ===

Order Express is deployed to end users as a ClickOnce application requiring a "Full Trust" security zone. Because the Order Express binaries are not digitally signed, it is unfortunately not possible to set a deployment policy to allow Order Express to be installed independently of other ClickOnce applications. Subsequently, it is suggested (although not ''currently'' required) that end-users of Order Express have administrative access of their local machine.

Additional information regarding ClickOnce can be found at the following link: http://msdn.microsoft.com/en-us/library/t71a733d.aspx

In addition to the requirements of the security policy of the local machine, Order Express also has a number of requirements in terms of network connectivity. At its very core, Order Express is an internet application, relying on its ability to synchronize data to and from remote systems to keep both manufacturers and dealers informed throughout the ordering process.

Order Express must be able to access the following ports on remote machines. In the interest of helping network administrators maintain network security during the deployment of Order Express, the information in the list below is granular enough to reliably identify network traffic from Order Express so that it can be allowed.

=== Hosts And Ports ===
* Feature: Status Notifications
** Host: <code>smtp.gmail.com</code>
** Ports: <code>25:TCP</code>, <code>465:TCP</code>, <code>587:TCP</code>

* Feature: ClickOnce Install/Update, Setup & Admin (Accessed via Web-Browser), Database Synchronization
** Host: <code>*.evisionservices.com</code>
** Ports: <code>80:TCP</code>, <code>80:UDP</code>, <code>443:TCP</code>, <code>443:UDP</code>, <code>1433:TCP</code>

* Feature: Catalog Install/Update, Image Install/Update
** Host: <code>s3.amazonaws.com</code>
** Ports: <code>80:TCP</code>, <code>443:TCP</code>

In addition to the above, Order Express must be able to establish/maintain an ongoing connection to a remote SQL Server.
While the initial handshake only requires port <code>1433:TCP</code> to be open, additional ports must be available to complete the handshake process.

Refer to the following link for more information: https://support.microsoft.com/kb/287932/en-us

== See Also ==
* [[Order Express FAQ]]
* [[Uninstalling Order Express]]
* [[Troubleshooting Order Express]]

[[Category:Order Express]]

Order Express

2014-10-24T15:38:09Z

Jshearer: /* Overview */

Order Express Improvements

2014-09-30T16:22:04Z

Jshearer:

The purpose of this page is to allow the developers to offer ideas for functional improvements to the underlying framework behind Order Express.

These suggestions are ''technically'' visible publicly, but this should be a suitable area for us to collaborate in this regard.

= Notes =
* Always sign your name after your comments. Use the four tildes "<code><nowiki>~~~~</nowiki></code>" wiki syntax (or the signature button [[File:Insert-signature.png|text-bottom|link=|signature button]] in the toolbar above the editing textbox).
* Start a new discussion with a <code><nowiki>== level 2 heading ==</nowiki></code> at the bottom of the page (or use the “{{lcfirst:{{int:addsection}}}}” tab).
* Indent replies with colons (<code>:</code>) at the beginning of the line.
* Refer to the [https://www.mediawiki.org/w/index.php?title=Help:Talk_pages MediaWiki Help Page] for examples.

= Ideas =
Place new discussions in this section.


== User Type Indicator - Associated with every Account ==
We need a more robust way to indicate those <code>UserType</code> records that are implicitly attached to all <code>Accounts</code>. This wouldn't waive any of the existing requirements, such as requiring all users to have exactly 1 <code>AccountUser</code> record marked as the default. Perhaps this is best implemented in the form of a <code>UserTypeOEConfiguration</code> record? [[User:Jshearer|Joshua Shearer]] ([[User talk:Jshearer|talk]]) 12:21, 30 September 2014 (EDT)

Order Express Improvements

2014-09-30T16:21:50Z

Jshearer:

The purpose of this page is to allow the developers to offer ideas for functional improvements to the underlying framework behind Order Express.

These suggestions are ''technically'' visible publicly, but this should be a suitable area for us to collaborate in this regard.

= Notes =
* Always sign your name after your comments. Use the four tildes "<code><nowiki>~~~~</nowiki></code>" wiki syntax (or the signature button [[File:Insert-signature.png|text-bottom|link=|signature button]] in the toolbar above the editing textbox).
* Start a new discussion with a <code><nowiki>== level 2 heading ==</nowiki></code> at the bottom of the page (or use the “{{lcfirst:{{int:addsection}}}}” tab).
* Indent replies with colons (<code>:</code>) at the beginning of the line.
* Refer to the [https://www.mediawiki.org/w/index.php?title=Help:Talk_pages MediaWiki Help Page] for examples.

= Ideas =
Place new discussions in this section.


== User Type Indicator - Associated with every Account ==
We need a more robust way to indicate those <code>UserType</code> records that are implicitly attached to all <code>Accounts</code>. This wouldn't waive any of the existing requirements, such as requiring all users to have exactly 1 <code>AccountUser</code> record marked as the default. Perhaps this is best implemented in the form of a <code>UserTypeOEConfigurations</code> record? [[User:Jshearer|Joshua Shearer]] ([[User talk:Jshearer|talk]]) 12:21, 30 September 2014 (EDT)

Order Express Improvements

2014-09-30T16:21:04Z

Jshearer:

The purpose of this page is to allow the developers to offer ideas for functional improvements to the underlying framework behind Order Express.

These suggestions are *technically* visible publicly, but this should be a suitable area for us to collaborate in this regard.

= Notes =
* Always sign your name after your comments. Use the four tildes "<code><nowiki>~~~~</nowiki></code>" wiki syntax (or the signature button [[File:Insert-signature.png|text-bottom|link=|signature button]] in the toolbar above the editing textbox).
* Start a new discussion with a <code><nowiki>== level 2 heading ==</nowiki></code> at the bottom of the page (or use the “{{lcfirst:{{int:addsection}}}}” tab).
* Indent replies with colons (<code>:</code>) at the beginning of the line.
* Refer to the [https://www.mediawiki.org/w/index.php?title=Help:Talk_pages MediaWiki Help Page] for examples.

= Ideas =
Place new discussions in this section.


== User Type Indicator - Associated with every Account ==
We need a more robust way to indicate those <code>UserType</code> records that are implicitly attached to all <code>Accounts</code>. This wouldn't waive any of the existing requirements, such as requiring all users to have exactly 1 <code>AccountUser</code> record marked as the default. Perhaps this is best implemented in the form of a <code>UserTypeOEConfigurations</code> record? [[User:Jshearer|Joshua Shearer]] ([[User talk:Jshearer|talk]]) 12:21, 30 September 2014 (EDT)

Order Express Improvements

2014-09-30T16:19:19Z

Jshearer: Added example.

Order Express Improvements

2014-09-30T16:18:02Z

Jshearer: Created the page with instructions.

Nuget Package Repository

2014-09-29T18:59:12Z

Jshearer: corrected spelling.

eVision hosts an assortment of code libraries on our locally-hosted nuget repository. While the packages within our repository were not specifically designed to be consumed by third-parties, we have purposely left them publicly-accessible so that our clients can leverage some of our internal tools in order to interact with the various systems that store and process their data.

It is worth noting that these resources are the exact packages that we use within our internal projects, so these packages get tested fairly thoroughly and are well supported by our internal applications. While most of the packages don't have any documentation, there are some that include some degree of documentation in the format of VS-compatible "xmlcomments", which provide some level of documentation by way of Intellisense within Visual Studio.

== Getting Started With Nuget ==

In order to consume our nuget packages within Visual Studio, you'll need to ensure that you have nuget installed. The nuget website is a great resource for getting started; we've provided some links below:

* http://docs.nuget.org/docs/start-here/installing-nuget
* http://docs.nuget.org/docs/start-here/managing-nuget-packages-using-the-dialog

== Adding the eVision Repository ==
After installing nuget, it will need to be configured to use the eVision package repository in addition to the default. This will allow the eVision packages to show up in search results so that they can be added to your projects. The source for the package repository is <code><nowiki>http://nuget.evisionservices.com/nuget/Ensemble</nowiki></code>. The repository is also accessible via the web, at http://nuget.evisionservices.com/feeds/Ensemble

Order Express - Advanced Troubleshooting

2014-09-11T19:33:01Z

Jshearer:

Machine.config

2014-09-11T19:30:00Z

Jshearer:

==Overview==
The <code>machine.config</code> contains settings that apply to an entire computer. Editing this file is usually discouraged for users who do not fully understand the implications of doing so.

==Location==
Locating this file can be difficult, as multiple versions of it exist for the various versions of the .NET Framework installed on the local machine.

The root directory where a user should begin their search is <code>C:\Windows\Microsoft.NET\</code>.

Within this directory there's a directory named <code>Framework</code> and another one named <code>Framework64</code>. These directories contain the 32-bit and 64-bit versions of the .NET framework (respectively). Beneath these folders, the structure should be identical, so if you make a change under one of these and it doesn't fix it, try making the same change under the other first.

<code>C:\Windows\Microsoft.NET\Framework

C:\Windows\Microsoft.NET\Framework64</code>

These two directories contain a number of folders (disregard any files in this directory, as they aren't relevant for the purposes of this article). Each folder refers to a specific version of the .NET framework. The number of folders can vary based on the operating system as well as the installed applications. Most applications from eVision Services are currently using the .NET 4.0 framework, which should be contained in a folder named <code>v4.0.30319</code>.

Inside the folder for a particular version, there should be a directory named <code>Config</code>. In this folder there's a file named <code>machine.config</code>, which is the file that can be edited. (It is important to note that there are multiple files with very similar names, so double-check the name of the file before making any modifications to it)

Here are some examples of the full paths to the relevant files:

32-bit: <code>C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config\machine.config</code>

64-bit: <code>C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config\machine.config</code>

== Related Issues ==

[[Troubleshooting_Order_Express#Duplicate DbProviderFactories|The 'DbProviderFactories' section can only appear once per config file.]]

Order Express - Advanced Troubleshooting

2014-09-11T19:29:15Z

Jshearer:

Order Express - Advanced Troubleshooting

2014-09-11T19:21:26Z

Jshearer:

Order Express - Advanced Troubleshooting

2014-09-11T19:19:14Z

Jshearer: Added fix for dbproviderfactories

Machine.config

2014-09-11T19:02:43Z

Jshearer: Added link to issue.

==Overview==
The <code>machine.config</code> contains settings that apply to an entire computer. Changing this file is usually discouraged for users who do not fully understand the implications of doing so.

==Location==
Locating this file can be difficult, as multiple versions of it exist for the various versions of the .NET Framework installed on the local machine.

The root directory where a user should begin their search is <code>C:\Windows\Microsoft.NET\</code>.

Within this directory there's a directory named <code>Framework</code> and another one named <code>Framework64</code>. These directories contain the 32-bit and 64-bit versions of the .NET framework (respectively). Beneath these folders, the structure should be identical, so if you make a change under one of these and it doesn't fix it, try making the same change under the other first.

<code>C:\Windows\Microsoft.NET\Framework

C:\Windows\Microsoft.NET\Framework64</code>

These two directories contain a number of folders (disregard any files in this directory, as they aren't relevant for the purposes of this article). Each folder refers to a specific version of the .NET framework. The number of folders can vary based on the operating system as well as the installed applications. Most applications from eVision Services are currently using the .NET 4.0 framework, which should be contained in a folder named <code>v4.0.30319</code>.

Inside the folder for a particular version, there should be a directory named <code>Config</code>. In this folder there's a file named <code>machine.config</code>, which is the file that can be edited. (It is important to note that there are multiple files with very similar names, so double-check the name of the file before making any modifications to it)

Here are some examples of the full paths to the relevant files:

32-bit: <code>C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config\machine.config</code>

64-bit: <code>C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config\machine.config</code>

== Related Issues ==

[[Troubleshooting_Order_Express#Duplicate DbProviderFactories|The 'DbProviderFactories' section can only appear once per config file.]]

Main Page

2014-08-29T15:06:26Z

Jshearer: Added link to Machine.config

== Software Applications ==
* [[Order Express]] - Ordering Software
* [[Smart Spec]] - Spec Book Software

== Developer Resources ==
* [[Nuget Package Repository]]
* [[Order Express Pricing Rules]]
* [[Machine.config]]

Order Express Pricing Rules

2014-08-14T17:38:07Z

Jshearer: added links to other pages.

== Overview ==

[[Order Express]] utilizes a robust expression system designed by [[eVision Services]] which allows for the conditional pricing of items. These ''pricing rules'' are stored within the database in the <code>PricingRules</code> table. Rules are written in [[wikipedia:Reverse Polish Notation|postfix notation]], but includes a number of keywords that can be used to retrieve information about the item being priced (such as how a product can be priced differently based on which styles are applied to it.

== Unimplemented Keywords ==

These keywords are considered to be "valid" keywords/tokens within the ''Rules Engine'' but currently have no implementation for pricing rules, and are thus not available for usage in pricing rules.

* <code>C:</code> - Category
* <code>E:</code> - Finished End Option Group
* <code>H:</code> - Hinging Option Group
* <code>N:</code> - Style Option Selections Count
* <code>P:</code> - Product
* <code>L:</code> - Product Line
* <code>Q:</code> - Style Option Selection
* <code>S:</code> - Style Category
* <code>W:</code> - Modification Variable

== Implemented Keywords ==

The following keywords have a defined meaning within pricing rules and can be used. Each of the keyboards are shown as links which will take you to their usage instructions.

* <code>F:</code> - [[#Nested_Formulas|Formula]]
* <code>I:</code>, <code>=></code>, and <code>,</code> - [[#Conditional_Expressions|Conditional]]
* <code>O:</code> - [[#Style_Options|Style Option]]
* <code>M:</code> - [[#Variable_Price_Codes|Variable Price Code]]
* <code>R:</code> - [[#Prices|Price]]
* <code>T:</code> - [[#Tags|Tag]]
* <code>U:</code> - [[#Upcharges|Upcharge]]
* <code>V:</code> - [[#Variables|Variable]]
* <code>X:</code> - [[#Constants|Constant]]

== Usage ==

=== Nested Formulas ===

Format: <code>F:[parameter]</code>

Executes the pricing rule with a name of <code>[parameter]</code>. This is primarily used in conjunction with the conditional operators, or to split expressions into shorter pieces.

=== Conditional Expressions ===

Tokens: <code>I:</code>, <code>=></code>, <code>,</code>

Format: <code>I:[conditional]=>[expression_if_true],[expression_if_false]</code>

Conditional expressions are defined using the above tokens. When these tokens are found within the expression, the expression is split into multiple ''parts''. The <code>[conditional]</code> parameter is ''always'' executed to determine if it evaluates to a <code>true</code> or <code>false</code> value. If this evaluates to <code>true</code>, the <code>[expression_if_true]</code> parameter is executed. If it evaluates to <code>false</code>, the <code>[expression_if_false]</code> parameter is executed.

=== Style Options ===

Tokens: <code>O:</code>

Format: <code>O:[style_option_display_id]</code>

The value for the <code>[style_option_display_id]</code> parameter should match the StyleOptionDisplayID in the <code>StyleOptions</code> table.

=== Variable Price Codes ===

Tokens: <code>M:</code>

Format: <code>M:[variable_code]</code>

Used to obtain the price for the current item. The value specified for the <code>[variable_code]</code> parameter is used, alongside the current price group, to obtain the price for the current item. The value for the <code>[variable_code]</code> parameter must match the <code>Code</code> column in the <code>OEVariablePriceCodes</code> table.

=== Prices ===

Tokens: <code>R:</code>

Format: <code>R:[price_type]</code>

Only two values are valid for the <code>[price_type]</code> parameter. These values are <code>BOOK</code> and <code>LIST</code>.

=== Tags ===

Tokens: <code>T:</code>

Format: <code>T:[tag_name]</code>

Used to determine if the current item is tagged as the value specified in the <code>[tag_name]</code> parameter.

=== Upcharges ===

Tokens: <code>U:</code>

Format: <code>U:[style_option_category_short_name]</code>

Used to obtain the price of an upcharge for the style option category that matches the <code>[style_option_category_short_name]</code> parameter for the current item. The value for the <code>[style_option_category_short_name]</code> must match the <code>ShortName</code> column in the <code>StyleOptionCategories</code> table.

=== Variables ===

Tokens: <code>V:</code>

Format: <code>V:[variable_code]</code>

Used to obtain the value of a variable for the current item. The value for the <code>[variable_code]</code> parameter must match the <code>VariableCode</code> column in the <code>OEVariables</code> table.

=== Constants ===

Tokens: <code>X:</code>

Format: <code>X:[constant_name]</code>

Used to obtain the value of constant. The value for the <code>[constant_name]</code> parameter must match the <code>ShortName</code> column in the <code>Constants</code> table.

Main Page

2014-08-14T17:37:16Z

Jshearer: added link to order express pricing rules.

== Software Applications ==
* [[Order Express]] - Ordering Software
* [[Smart Spec]] - Spec Book Software

== Developer Resources ==
* [[Nuget Package Repository]]
* [[Order Express Pricing Rules]]

Order Express Pricing Rules

2014-08-14T17:11:43Z

Jshearer:

== Overview ==

Order Express utilizes a robust expression system designed by eVision Services which allows for the conditional pricing of items. These ''pricing rules'' are stored within the database in the <code>PricingRules</code> table. Rules are written in [[wikipedia:Reverse Polish Notation|postfix notation]], but includes a number of keywords that can be used to retrieve information about the item being priced (such as how a product can be priced differently based on which styles are applied to it.

== Unimplemented Keywords ==

These keywords are considered to be "valid" keywords/tokens within the ''Rules Engine'' but currently have no implementation for pricing rules, and are thus not available for usage in pricing rules.

* <code>C:</code> - Category
* <code>E:</code> - Finished End Option Group
* <code>H:</code> - Hinging Option Group
* <code>N:</code> - Style Option Selections Count
* <code>P:</code> - Product
* <code>L:</code> - Product Line
* <code>Q:</code> - Style Option Selection
* <code>S:</code> - Style Category
* <code>W:</code> - Modification Variable

== Implemented Keywords ==

The following keywords have a defined meaning within pricing rules and can be used. Each of the keyboards are shown as links which will take you to their usage instructions.

* <code>F:</code> - [[#Nested_Formulas|Formula]]
* <code>I:</code>, <code>=></code>, and <code>,</code> - [[#Conditional_Expressions|Conditional]]
* <code>O:</code> - [[#Style_Options|Style Option]]
* <code>M:</code> - [[#Variable_Price_Codes|Variable Price Code]]
* <code>R:</code> - [[#Prices|Price]]
* <code>T:</code> - [[#Tags|Tag]]
* <code>U:</code> - [[#Upcharges|Upcharge]]
* <code>V:</code> - [[#Variables|Variable]]
* <code>X:</code> - [[#Constants|Constant]]

== Usage ==

=== Nested Formulas ===

Format: <code>F:[parameter]</code>

Executes the pricing rule with a name of <code>[parameter]</code>. This is primarily used in conjunction with the conditional operators, or to split expressions into shorter pieces.

=== Conditional Expressions ===

Tokens: <code>I:</code>, <code>=></code>, <code>,</code>

Format: <code>I:[conditional]=>[expression_if_true],[expression_if_false]</code>

Conditional expressions are defined using the above tokens. When these tokens are found within the expression, the expression is split into multiple ''parts''. The <code>[conditional]</code> parameter is ''always'' executed to determine if it evaluates to a <code>true</code> or <code>false</code> value. If this evaluates to <code>true</code>, the <code>[expression_if_true]</code> parameter is executed. If it evaluates to <code>false</code>, the <code>[expression_if_false]</code> parameter is executed.

=== Style Options ===

Tokens: <code>O:</code>

Format: <code>O:[style_option_display_id]</code>

The value for the <code>[style_option_display_id]</code> parameter should match the StyleOptionDisplayID in the <code>StyleOptions</code> table.

=== Variable Price Codes ===

Tokens: <code>M:</code>

Format: <code>M:[variable_code]</code>

Used to obtain the price for the current item. The value specified for the <code>[variable_code]</code> parameter is used, alongside the current price group, to obtain the price for the current item. The value for the <code>[variable_code]</code> parameter must match the <code>Code</code> column in the <code>OEVariablePriceCodes</code> table.

=== Prices ===

Tokens: <code>R:</code>

Format: <code>R:[price_type]</code>

Only two values are valid for the <code>[price_type]</code> parameter. These values are <code>BOOK</code> and <code>LIST</code>.

=== Tags ===

Tokens: <code>T:</code>

Format: <code>T:[tag_name]</code>

Used to determine if the current item is tagged as the value specified in the <code>[tag_name]</code> parameter.

=== Upcharges ===

Tokens: <code>U:</code>

Format: <code>U:[style_option_category_short_name]</code>

Used to obtain the price of an upcharge for the style option category that matches the <code>[style_option_category_short_name]</code> parameter for the current item. The value for the <code>[style_option_category_short_name]</code> must match the <code>ShortName</code> column in the <code>StyleOptionCategories</code> table.

=== Variables ===

Tokens: <code>V:</code>

Format: <code>V:[variable_code]</code>

Used to obtain the value of a variable for the current item. The value for the <code>[variable_code]</code> parameter must match the <code>VariableCode</code> column in the <code>OEVariables</code> table.

=== Constants ===

Tokens: <code>X:</code>

Format: <code>X:[constant_name]</code>

Used to obtain the value of constant. The value for the <code>[constant_name]</code> parameter must match the <code>ShortName</code> column in the <code>Constants</code> table.

Order Express Pricing Rules

2014-08-14T17:09:06Z

Jshearer: Added missing variable price code description.

== Overview ==

Order Express utilizes a robust expression system designed by eVision Services which allows for the conditional pricing of items. These ''pricing rules'' are stored within the database in the <code>PricingRules</code> table. Rules are written in [[wikipedia:Reverse Polish Notation|postfix notation]], but includes a number of keywords that can be used to retrieve information about the item being priced (such as how a product can be priced differently based on which styles are applied to it.

== Unimplemented Keywords ==

These keywords are considered to be "valid" keywords/tokens within the ''Rules Engine'' but currently have no implementation for pricing rules, and are thus considered to be invalid.

* <code>C:</code> - Category
* <code>E:</code> - Finished End Option Group
* <code>H:</code> - Hinging Option Group
* <code>N:</code> - Style Option Selections Count
* <code>P:</code> - Product
* <code>L:</code> - Product Line
* <code>Q:</code> - Style Option Selection
* <code>S:</code> - Style Category
* <code>W:</code> - Modification Variable

== Implemented Keywords ==

* <code>F:</code> - [[#Nested_Formulas|Formula]]
* <code>I:</code>, <code>=></code>, and <code>,</code> - [[#Conditional_Expressions|Conditional]]
* <code>O:</code> - [[#Style_Options|Style Option]]
* <code>M:</code> - [[#Variable_Price_Codes|Variable Price Code]]
* <code>R:</code> - [[#Prices|Price]]
* <code>T:</code> - [[#Tags|Tag]]
* <code>U:</code> - [[#Upcharges|Upcharge]]
* <code>V:</code> - [[#Variables|Variable]]
* <code>X:</code> - [[#Constants|Constant]]

== Usage ==

=== Nested Formulas ===

Format: <code>F:[parameter]</code>

Executes the pricing rule with a name of <code>[parameter]</code>. This is primarily used in conjunction with the conditional operators, or to split expressions into shorter pieces.

=== Conditional Expressions ===

Tokens: <code>I:</code>, <code>=></code>, <code>,</code>

Format: <code>I:[conditional]=>[expression_if_true],[expression_if_false]</code>

Conditional expressions are defined using the above tokens. When these tokens are found within the expression, the expression is split into multiple ''parts''. The <code>[conditional]</code> parameter is ''always'' executed to determine if it evaluates to a <code>true</code> or <code>false</code> value. If this evaluates to <code>true</code>, the <code>[expression_if_true]</code> parameter is executed. If it evaluates to <code>false</code>, the <code>[expression_if_false]</code> parameter is executed.

=== Style Options ===

Tokens: <code>O:</code>

Format: <code>O:[style_option_display_id]</code>

The value for the <code>[style_option_display_id]</code> parameter should match the StyleOptionDisplayID in the <code>StyleOptions</code> table.

=== Variable Price Codes ===

Tokens: <code>M:</code>

Format: <code>M:[variable_code]</code>

Used to obtain the price for the current item. The value specified for the <code>[variable_code]</code> parameter is used, alongside the current price group, to obtain the price for the current item. The value for the <code>[variable_code]</code> parameter must match the <code>Code</code> column in the <code>OEVariablePriceCodes</code> table.

=== Prices ===

Tokens: <code>R:</code>

Format: <code>R:[price_type]</code>

Only two values are valid for the <code>[price_type]</code> parameter. These values are <code>BOOK</code> and <code>LIST</code>.

=== Tags ===

Tokens: <code>T:</code>

Format: <code>T:[tag_name]</code>

Used to determine if the current item is tagged as the value specified in the <code>[tag_name]</code> parameter.

=== Upcharges ===

Tokens: <code>U:</code>

Format: <code>U:[style_option_category_short_name]</code>

Used to obtain the price of an upcharge for the style option category that matches the <code>[style_option_category_short_name]</code> parameter for the current item. The value for the <code>[style_option_category_short_name]</code> must match the <code>ShortName</code> column in the <code>StyleOptionCategories</code> table.

=== Variables ===

Tokens: <code>V:</code>

Format: <code>V:[variable_code]</code>

Used to obtain the value of a variable for the current item. The value for the <code>[variable_code]</code> parameter must match the <code>VariableCode</code> column in the <code>OEVariables</code> table.

=== Constants ===

Tokens: <code>X:</code>

Format: <code>X:[constant_name]</code>

Used to obtain the value of constant. The value for the <code>[constant_name]</code> parameter must match the <code>ShortName</code> column in the <code>Constants</code> table.

Order Express Pricing Rules

2014-08-14T17:02:06Z

Jshearer: Fixed Headings again.

== Overview ==

Order Express utilizes a robust expression system designed by eVision Services which allows for the conditional pricing of items. These ''pricing rules'' are stored within the database in the <code>PricingRules</code> table. Rules are written in [[wikipedia:Reverse Polish Notation|postfix notation]], but includes a number of keywords that can be used to retrieve information about the item being priced (such as how a product can be priced differently based on which styles are applied to it.

== Unimplemented Keywords ==

These keywords are considered to be "valid" keywords/tokens within the ''Rules Engine'' but currently have no implementation for pricing rules, and are thus considered to be invalid.

* <code>C:</code> - Category
* <code>E:</code> - Finished End Option Group
* <code>H:</code> - Hinging Option Group
* <code>N:</code> - Style Option Selections Count
* <code>P:</code> - Product
* <code>L:</code> - Product Line
* <code>Q:</code> - Style Option Selection
* <code>S:</code> - Style Category
* <code>W:</code> - Modification Variable

== Implemented Keywords ==

* <code>F:</code> - [[#Nested_Formulas|Formula]]
* <code>I:</code>, <code>=></code>, and <code>,</code> - [[#Conditional_Expressions|Conditional]]
* <code>O:</code> - [[#Style_Options|Style Option]]
* <code>M:</code> - [[#Variable_Price_Codes|Variable Price Code]]
* <code>R:</code> - [[#Prices|Price]]
* <code>T:</code> - [[#Tags|Tag]]
* <code>U:</code> - [[#Upcharges|Upcharge]]
* <code>V:</code> - [[#Variables|Variable]]
* <code>X:</code> - [[#Constants|Constant]]

== Usage ==

=== Nested Formulas ===

Format: <code>F:[parameter]</code>

Executes the pricing rule with a name of <code>[parameter]</code>. This is primarily used in conjunction with the conditional operators, or to split expressions into shorter pieces.

=== Conditional Expressions ===

Tokens: <code>I:</code>, <code>=></code>, <code>,</code>

Format: <code>I:[conditional]=>[expression_if_true],[expression_if_false]</code>

Conditional expressions are defined using the above tokens. When these tokens are found within the expression, the expression is split into multiple ''parts''. The <code>[conditional]</code> parameter is ''always'' executed to determine if it evaluates to a <code>true</code> or <code>false</code> value. If this evaluates to <code>true</code>, the <code>[expression_if_true]</code> parameter is executed. If it evaluates to <code>false</code>, the <code>[expression_if_false]</code> parameter is executed.

=== Style Options ===

Tokens: <code>O:</code>

Format: <code>O:[style_option_display_id]</code>

The value for the <code>[style_option_display_id]</code> parameter should match the StyleOptionDisplayID in the <code>StyleOptions</code> table.

=== Variable Price Codes ===

Tokens: <code>M:</code>

Format: <code>M:[]</code>

Stored in the table <code>OEVariablePriceCodes</code>

=== Prices ===

Tokens: <code>R:</code>

Format: <code>R:[price_type]</code>

Only two values are valid for the <code>[price_type]</code> parameter. These values are <code>BOOK</code> and <code>LIST</code>.

=== Tags ===

Tokens: <code>T:</code>

Format: <code>T:[tag_name]</code>

Used to determine if the current item is tagged as the value specified in the <code>[tag_name]</code> parameter.

=== Upcharges ===

Tokens: <code>U:</code>

Format: <code>U:[style_option_category_short_name]</code>

Used to obtain the price of an upcharge for the style option category that matches the <code>[style_option_category_short_name]</code> parameter for the current item. The value for the <code>[style_option_category_short_name]</code> must match the <code>ShortName</code> column in the <code>StyleOptionCategories</code> table.

=== Variables ===

Tokens: <code>V:</code>

Format: <code>V:[variable_code]</code>

Used to obtain the value of a variable for the current item. The value for the <code>[variable_code]</code> parameter must match the <code>VariableCode</code> column in the <code>OEVariables</code> table.

=== Constants ===

Tokens: <code>X:</code>

Format: <code>X:[constant_name]</code>

Used to obtain the value of constant. The value for the <code>[constant_name]</code> parameter must match the <code>ShortName</code> column in the <code>Constants</code> table.

Order Express Pricing Rules

2014-08-14T16:58:50Z

Jshearer: Fixed headings.

== Overview ==

Order Express utilizes a robust expression system designed by eVision Services which allows for the conditional pricing of items. These ''pricing rules'' are stored within the database in the <code>PricingRules</code> table. Rules are written in [[wikipedia:Reverse Polish Notation|postfix notation]], but includes a number of keywords that can be used to retrieve information about the item being priced (such as how a product can be priced differently based on which styles are applied to it.

== Keywords ==

=== Unimplemented Keywords ===

These keywords are considered to be "valid" keywords/tokens within the ''Rules Engine'' but currently have no implementation for pricing rules, and are thus considered to be invalid.

* <code>C:</code> - Category
* <code>E:</code> - Finished End Option Group
* <code>H:</code> - Hinging Option Group
* <code>N:</code> - Style Option Selections Count
* <code>P:</code> - Product
* <code>L:</code> - Product Line
* <code>Q:</code> - Style Option Selection
* <code>S:</code> - Style Category
* <code>W:</code> - Modification Variable

=== Implemented Keywords ===

* <code>F:</code> - [[#Nested_Formulas|Formula]]
* <code>I:</code>, <code>=></code>, and <code>,</code> - [[#Conditional_Expressions|Conditional]]
* <code>O:</code> - [[#Style_Options|Style Option]]
* <code>M:</code> - [[#Variable_Price_Codes|Variable Price Code]]
* <code>R:</code> - [[#Prices|Price]]
* <code>T:</code> - [[#Tags|Tag]]
* <code>U:</code> - [[#Upcharges|Upcharge]]
* <code>V:</code> - [[#Variables|Variable]]
* <code>X:</code> - [[#Constants|Constant]]

=== Usage ===

==== Nested Formulas ====

Format: <code>F:[parameter]</code>

Executes the pricing rule with a name of <code>[parameter]</code>. This is primarily used in conjunction with the conditional operators, or to split expressions into shorter pieces.

==== Conditional Expressions ====

Tokens: <code>I:</code>, <code>=></code>, <code>,</code>

Format: <code>I:[conditional]=>[expression_if_true],[expression_if_false]</code>

Conditional expressions are defined using the above tokens. When these tokens are found within the expression, the expression is split into multiple ''parts''. The <code>[conditional]</code> parameter is ''always'' executed to determine if it evaluates to a <code>true</code> or <code>false</code> value. If this evaluates to <code>true</code>, the <code>[expression_if_true]</code> parameter is executed. If it evaluates to <code>false</code>, the <code>[expression_if_false]</code> parameter is executed.

==== Style Options ====

Tokens: <code>O:</code>

Format: <code>O:[style_option_display_id]</code>

The value for the <code>[style_option_display_id]</code> parameter should match the StyleOptionDisplayID in the <code>StyleOptions</code> table.

==== Variable Price Codes ====

Tokens: <code>M:</code>

Format: <code>M:[]</code>

Stored in the table <code>OEVariablePriceCodes</code>

==== Prices ====

Tokens: <code>R:</code>

Format: <code>R:[price_type]</code>

Only two values are valid for the <code>[price_type]</code> parameter. These values are <code>BOOK</code> and <code>LIST</code>.

==== Tags ====

Tokens: <code>T:</code>

Format: <code>T:[tag_name]</code>

Used to determine if the current item is tagged as the value specified in the <code>[tag_name]</code> parameter.

==== Upcharges ====

Tokens: <code>U:</code>

Format: <code>U:[style_option_category_short_name]</code>

Used to obtain the price of an upcharge for the style option category that matches the <code>[style_option_category_short_name]</code> parameter for the current item. The value for the <code>[style_option_category_short_name]</code> must match the <code>ShortName</code> column in the <code>StyleOptionCategories</code> table.

==== Variables ====

Tokens: <code>V:</code>

Format: <code>V:[variable_code]</code>

Used to obtain the value of a variable for the current item. The value for the <code>[variable_code]</code> parameter must match the <code>VariableCode</code> column in the <code>OEVariables</code> table.

==== Constants ====

Tokens: <code>X:</code>

Format: <code>X:[constant_name]</code>

Used to obtain the value of constant. The value for the <code>[constant_name]</code> parameter must match the <code>ShortName</code> column in the <code>Constants</code> table.

Order Express Pricing Rules

2014-08-14T16:54:36Z

Jshearer: Added links and headings for all keywords.

== Overview ==

Order Express utilizes a robust expression system designed by eVision Services which allows for the conditional pricing of items. These ''pricing rules'' are stored within the database in the <code>PricingRules</code> table. Rules are written in [[wikipedia:Reverse Polish Notation|postfix notation]], but includes a number of keywords that can be used to retrieve information about the item being priced (such as how a product can be priced differently based on which styles are applied to it.

=== Keywords Not Used For Pricing Rules ===

These keywords are considered to be "valid" keywords/tokens within the ''Rules Engine'' but currently have no implementation for pricing rules, and are thus considered to be invalid.

* <code>C:</code> - Category
* <code>E:</code> - Finished End Option Group
* <code>H:</code> - Hinging Option Group
* <code>N:</code> - Style Option Selections Count
* <code>P:</code> - Product
* <code>L:</code> - Product Line
* <code>Q:</code> - Style Option Selection
* <code>S:</code> - Style Category
* <code>W:</code> - Modification Variable

=== Keywords Used For Pricing Rules ===

* <code>F:</code> - [[#Nested_Formulas|Formula]]
* <code>I:</code>, <code>=></code>, and <code>,</code> - [[#Conditional_Expressions|Conditional]]
* <code>O:</code> - [[#Style_Options|Style Option]]
* <code>M:</code> - [[#Variable_Price_Codes|Variable Price Code]]
* <code>R:</code> - [[#Prices|Price]]
* <code>T:</code> - [[#Tags|Tag]]
* <code>U:</code> - [[#Upcharges|Upcharge]]
* <code>V:</code> - [[#Variables|Variable]]
* <code>X:</code> - [[#Constants|Constant]]

=== Nested Formulas ===

Format: <code>F:[parameter]</code>

Executes the pricing rule with a name of <code>[parameter]</code>. This is primarily used in conjunction with the conditional operators, or to split expressions into shorter pieces.

=== Conditional Expressions ===

Tokens: <code>I:</code>, <code>=></code>, <code>,</code>

Format: <code>I:[conditional]=>[expression_if_true],[expression_if_false]</code>

Conditional expressions are defined using the above tokens. When these tokens are found within the expression, the expression is split into multiple ''parts''. The <code>[conditional]</code> parameter is ''always'' executed to determine if it evaluates to a <code>true</code> or <code>false</code> value. If this evaluates to <code>true</code>, the <code>[expression_if_true]</code> parameter is executed. If it evaluates to <code>false</code>, the <code>[expression_if_false]</code> parameter is executed.

=== Style Options ===

Tokens: <code>O:</code>

Format: <code>O:[style_option_display_id]</code>

The value for the <code>[style_option_display_id]</code> parameter should match the StyleOptionDisplayID in the <code>StyleOptions</code> table.

=== Variable Price Codes ===

Tokens: <code>M:</code>

Format: <code>M:[]</code>

Stored in the table <code>OEVariablePriceCodes</code>

=== Prices ===

Tokens: <code>R:</code>

Format: <code>R:[price_type]</code>

Only two values are valid for the <code>[price_type]</code> parameter. These values are <code>BOOK</code> and <code>LIST</code>.

=== Tags ===

Tokens: <code>T:</code>

Format: <code>T:[tag_name]</code>

Used to determine if the current item is tagged as the value specified in the <code>[tag_name]</code> parameter.

=== Upcharges ===

Tokens: <code>U:</code>

Format: <code>U:[style_option_category_short_name]</code>

Used to obtain the price of an upcharge for the style option category that matches the <code>[style_option_category_short_name]</code> parameter for the current item. The value for the <code>[style_option_category_short_name]</code> must match the <code>ShortName</code> column in the <code>StyleOptionCategories</code> table.

=== Variables ===

Tokens: <code>V:</code>

Format: <code>V:[variable_code]</code>

Used to obtain the value of a variable for the current item. The value for the <code>[variable_code]</code> parameter must match the <code>VariableCode</code> column in the <code>OEVariables</code> table.

=== Constants ===

Tokens: <code>X:</code>

Format: <code>X:[constant_name]</code>

Used to obtain the value of constant. The value for the <code>[constant_name]</code> parameter must match the <code>ShortName</code> column in the <code>Constants</code> table.

Order Express Pricing Rules

2014-08-14T16:12:43Z

Jshearer:

Order Express Pricing Rules

2014-08-14T16:09:41Z

Jshearer:

Order Express Pricing Rules

2014-08-14T16:07:01Z

Jshearer: Creating the page with useful data, even though it isn't finished yet.

Machine.config

2014-08-13T21:21:32Z

Jshearer: Created page with "==Overview== The <code>machine.config</code> contains settings that apply to an entire computer. Changing this file is usually discouraged for users who do not fully understa..."

Nuget Package Repository

2014-07-30T14:03:39Z

Jshearer: Added information regarding out package repository.

eVision hosts an assortment of code libraries on our locally-hosted nuget repository. While the packages within our repository were not specifically designed to be consumed by third-parties, we have purposely left them publicly-accessible so that our clients can leverage some of our internal tools in order to interacting with the various systems that store and process their data.

It is worth noting that these resources are the exact packages that we use within our internal projects, so these packages get tested fairly thoroughly and are well supported by our internal applications. While most of the packages don't have any documentation, there are some that include some degree of documentation in the format of VS-compatible "xmlcomments", which provide some level of documentation by way of Intellisense within Visual Studio.

== Getting Started With Nuget ==

In order to consume our nuget packages within Visual Studio, you'll need to ensure that you have nuget installed. The nuget website is a great resource for getting started; we've provided some links below:

* http://docs.nuget.org/docs/start-here/installing-nuget
* http://docs.nuget.org/docs/start-here/managing-nuget-packages-using-the-dialog

== Adding the eVision Repository ==
After installing nuget, it will need to be configured to use the eVision package repository in addition to the default. This will allow the eVision packages to show up in search results so that they can be added to your projects. The source for the package repository is <code><nowiki>http://nuget.evisionservices.com/nuget/Ensemble</nowiki></code>. The repository is also accessible via the web, at http://nuget.evisionservices.com/feeds/Ensemble

Main Page

2014-07-30T13:49:36Z

Jshearer: Added link to nuget page.

== Software Applications ==
* [[Order Express]] - Ordering Software
* [[Smart Spec]] - Spec Book Software

== Additional Resources ==
[[Nuget Package Repository]]

Order Express - Frequently Asked Questions

2014-07-22T18:28:40Z

Jshearer:

This page contains answers to a variety of common questions and issues regarding Order Express. Please review the table of contents below to see if your question has been answered.

__FORCETOC__ 

=== When starting Order Express, the splash screen appears briefly and then disappears ===
[[File:OrderExpressSplashScreen.png|thumbnail|Order Express Splash Screen]]
This issue can occur under the following circumstances:
* A previous instance of Order Express did not fully close.
* Required files are missing from the installation directory.
* The installation directory contains files that are not the correct version.

In most cases, this issue can be resolved by performing an [[Uninstalling Order Express|''Extended (Full) Uninstall'']].

=== My question isn't on the list, what do I do? ===
If your question is not listed above, have the Manufacturer contact us and we'll do our best to answer your questions.

[[Category:Order Express]]

Order Express

2014-07-22T18:27:19Z

Jshearer: /* See Also */