eVision - User contributions [en]

Order Express - Release Notes

2016-08-15T18:04:05Z

Sowens:

2.3.33.0 - August 9, 2016 - minor fix<br />
[[2.3.32.0|2.3.32.0 - August 8, 2016]]<br />
[[2.3.31.0|2.3.31.0 - July 28, 2016]]

Back To [[Main Page]]

Order Express - Release Notes

2016-08-11T21:11:55Z

Sowens:

[[2.3.32.0|2.3.32.0 - August 8, 2016]]<br />
[[2.3.31.0|2.3.31.0 - July 28, 2016]]

Back To [[Main Page]]

2.3.31.0

2016-08-11T20:54:19Z

Sowens: Replaced content with "file:2.3.31.0.jpg Back to Release Notes"

[[file:2.3.31.0.jpg]]

Back to [[Order Express - Release Notes|Release Notes]]

File:2.3.31.0.jpg

2016-08-11T20:53:29Z

Sowens:

2.3.32.0

2016-08-11T20:51:44Z

Sowens:

[[file:2.3.32.0page1.jpg]]
[[file:2.3.32.0page2.jpg]]

Back To [[Order Express - Release Notes|Release Notes]]

2.3.32.0

2016-08-11T20:50:43Z

Sowens:

[[file:2.3.32.0page1.jpg]]
[[file:2.3.32.0page2.jpg]]

Back To [[Order Express - Release Notes]]

2.3.32.0

2016-08-11T20:49:12Z

Sowens: Replaced content with "file:2.3.32.0page1.jpg file:2.3.32.0page2.jpg"

[[file:2.3.32.0page1.jpg]]
[[file:2.3.32.0page2.jpg]]

Order Express - Release Notes

2016-08-11T20:48:26Z

Sowens:

[[2.3.32.0|2.3.32.0 - August 8, 2016]]

[[2.3.31.0|2.3.31.0 - July 28, 2016]]

Back To [[Main Page]]

Order Express - Release Notes

2016-08-11T20:47:51Z

Sowens:

[[file:2.3.32.0page1.jpg|2.3.32.0 - August 8, 2016]]

[[2.3.31.0|2.3.31.0 - July 28, 2016]]

Back To [[Main Page]]

File:2.3.32.0page2.jpg

2016-08-11T20:46:29Z

Sowens:

File:2.3.32.0page1.jpg

2016-08-11T20:46:05Z

Sowens:

2.3.32.0

2016-08-11T20:45:14Z

Sowens: Created page with "'''Global Updates''' 1. Changed the Project Manager Current Account box to say "All Selected Accounts" instead of "All Accounts" when the user doesn't have access to all acc..."

'''Global Updates'''

1. Changed the Project Manager Current Account box to say "All Selected Accounts" instead of "All Accounts" when the user doesn't have access to all accounts.

[[File:2.3.32.0 - All Selected Accounts.jpg]]

2. Added the ability for Manufacturers to edit the Details section of Specials
[[File:2.3.32.0 - Specials Details.jpg]]

3. Added the Specials Reference Number to special products on Product Entry & Project Review screens
[[File:]]

'''Bug Fixes'''

1.

2.

Back to [[Order Express - Release Notes|Release Notes]]

Order Express - Release Notes

2016-08-11T20:38:35Z

Sowens:

[[2.3.32.0|2.3.32.0 - August 8, 2016]]

[[2.3.31.0|2.3.31.0 - July 28, 2016]]

Back To [[Main Page]]

Order Express - Release Notes

2016-08-11T20:38:27Z

Sowens:

[[2.3.32.0|2.3.32.0 - August 8, 2016]]

[[2.3.31.0|2.3.31.0 - July 28, 2016]]

Back To [[Main Page]]

Order Express - Release Notes

2016-08-11T20:38:18Z

Sowens:

[[2.3.32.0|2.3.32.0 - August 8, 2016]]
[[2.3.31.0|2.3.31.0 - July 28, 2016]]

Back To [[Main Page]]

File:2.3.32.0 - All Selected Accounts.JPG

2016-08-11T20:33:31Z

Sowens:

File:2.3.32.0 - Post a message.JPG

2016-08-11T20:32:59Z

Sowens:

File:2.3.32.0 - Specials Details.JPG

2016-08-11T20:28:35Z

Sowens:

File:2.3.32.0 - Special Reference Number - Project Review.JPG

2016-08-11T20:28:19Z

Sowens:

File:2.3.32.0 - Special Reference Number - Product Entry.JPG

2016-08-11T20:28:08Z

Sowens:

File:Post a message.JPG

2016-08-11T20:26:08Z

Sowens:

File:All Selected Accounts.JPG

2016-08-11T20:25:45Z

Sowens:

2.3.31.0

2016-08-11T20:19:53Z

Sowens:

'''Global Updates'''

1. New Attachments section added on Project Review – Added the ability to view and download attachments from the Project Review screen

[[File:2.3.31.0 - Attachments.jpg]]

2. Added a “Hide Attachments” option at the top of the Project Review screen to be able to hide the Attachments section.
[[File:2.3.31.0 - Hide Attachments.jpg]]

3. Removed Apply Style Upcharges “Estimate” and “Actual” box inside of a special. Replaced with a single Apply Style Upcharges checkbox.
[[File:2.3.31.0 ApplyStyleUpcharges.jpg]]

'''Bug Fixes'''

1. Corrected a 20/20 import issue with minimum and maximum width data.

2. Manufacturer Adjustment box on Project Info screen (if applicable) now accepts negative values

Back to [[Order Express - Release Notes|Release Notes]]

Order Express - Release Notes

2016-08-11T20:19:26Z

Sowens:

[[2.3.31.0|2.3.31.0 - July 28, 2016]]

Back To [[Main Page]]

2.3.31.0

2016-08-11T20:17:19Z

Sowens:

''Released on July 28, 2016''

'''Global Updates'''

1. New Attachments section added on Project Review – Added the ability to view and download attachments from the Project Review screen

[[File:2.3.31.0 - Attachments.jpg]]

2. Added a “Hide Attachments” option at the top of the Project Review screen to be able to hide the Attachments section.
[[File:2.3.31.0 - Hide Attachments.jpg]]

3. Removed Apply Style Upcharges “Estimate” and “Actual” box inside of a special. Replaced with a single Apply Style Upcharges checkbox.
[[File:2.3.31.0 ApplyStyleUpcharges.jpg]]

'''Bug Fixes'''

1. Corrected a 20/20 import issue with minimum and maximum width data.

2. Manufacturer Adjustment box on Project Info screen (if applicable) now accepts negative values

Back to [[Order Express - Release Notes|Release Notes]]

2.3.31.0

2016-08-11T20:16:54Z

Sowens:

Order Express

2016-08-01T19:10:49Z

Sowens:

{{Infobox software
| name = Order Express
| logo = Order express logo.png
| logo_size = 150
| logo caption = Order Express logo
| screenshot = Demo opening.JPG
| caption = Order Express running on Windows 10
| 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

== 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 - Frequently Asked Questions|Frequently Asked Questions]]
* [[Order Express - Advanced Troubleshooting|Advanced Troubleshooting]]
* [[Order Express - Release Notes|Release Notes]]

Back to [[Main Page]]

EVision Services

2016-08-01T19:10:20Z

Sowens:

{{DISPLAYTITLE:eVision Services}}

'''eVision Services''' is a web solutions and services company located in Lexington, Kentucky. The company was established in 2003 to provide web and catalog services to the Kitchen and Bath Industry, but has since grown to provide software applications and services that address the challenges of any business. eVision's offerings target industry-specific problems by using rich internet-enabled software applications to provide a large return on investment.

Back to [[Main Page]]

Developer Page

2016-08-01T19:10:01Z

Sowens:

* [[Order_Express_Formulas|Formulas]]
* [[Order_Express_Improvements|Improvements]]
* [[JSON Permission Editing]]
* [[Nuget_Package_Repository|Nuget Package Repository]]

Back to [[Main Page]]

Order Express Formulas

2016-08-01T19:09:39Z

Sowens:

== Overview ==

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

== Valid Tokens ==

These keywords are considered to be "valid" keywords/tokens within the ''Rules Engine''. Each of the keywords are shown as links which will take you to their usage instructions.

* <code>A:</code> - [[#Specials|Special]]
* <code>ACCOUNT:</code> - [[#Accounts|Account]]
* <code>ACCOUNTVARIABLE:</code> - [[#Account_Variables|Account Variable]]
* <code>C:</code> - [[#Product_and_Modification_Categories|Category]]
* <code>COLLECTION:</code> - [[#Collections|Collection]]
* <code>COUNT:</code> - [[#Count|Count]]
* <code>D:</code> - [[#Modifications|Modification]]
* <code>DATETIME:</code> - [[#Dates|Date]]
* <code>E:</code> - [[#Finished_End_Option_Groups|Finished End Option Group]]
* <code>EVERY:</code> - [[#Every_Condition|Every]]
* <code>F:</code> - [[#Nested_Formulas|Formula]]
* <code>H:</code> - [[#Hinging_Option_Groups|Hinging Option Group]]
* <code>I:</code>, <code>=></code>, and <code>,</code> - [[#Conditional_Expressions|Conditional]]
* <code>IF:</code> and <code>=></code> - [[#Infix_Conditional_Expressions|Infix Conditional]]
* <code>INFIX:</code> - [[#Infix_Expressions|Infix]]
* <code>L:</code> - [[#Product_Lines|Product Line]]
* <code>LIMIT:</code> - [[#Limits|Limit]]
* <code>M:</code> - [[#Variable_Price_Codes|Variable Price Code]]
* <code>MAX:</code> - [[#Maximum_Value|Max]]
* <code>MIN:</code> - [[#Minimum_Value|Min]]
* <code>N:</code> - [[#Style_Option_Selection_Count|Style Option Selection Count]]
* <code>O:</code> - [[#Style_Options|Style Option]]
* <code>P:</code> - [[#Products|Product]]
* <code>Q:</code> - [[#Style_Option_Selections|Style Option Selection]]
* <code>QUOTE:</code> - [[#Quotes|Quote]]
* <code>QUOTEVARIABLE:</code> - [[#Quote_Variables|Quote Variable]]
* <code>R:</code> - [[#Prices|Price]]
* <code>S:</code> - [[#Style_Option_Categories|Style Option Category]]
* <code>SOME:</code> - [[#Some_Conditions|Some]]
* <code>SUM:</code> - [[#Summation|Sum]]
* <code>T:</code> - [[#Tags|Tag]]
* <code>TIMESPAN:</code> - [[#Time_Spans|Time Span]]
* <code>U:</code> - [[#Upcharges|Upcharge]]
* <code>V:</code> - [[#Product_Variables|Variable]]
* <code>VAR:</code> - [[#Context_Variables|Context Variable]]
* <code>W:</code> - [[#Modification_Variables|Modification Variable]]
* <code>X:</code> - [[#Constants|Constant]]
* <code>Z:</code> - Evaluation

== Usage ==

=== Accounts ===

Tokens: <code>ACCOUNT:</code>

Format: <code>ACCOUNT:[property_or_variable_code]</code>

Used to obtain the value of a account variable or property for the account the current item is associated with. The value for the <code>[property_or_variable_code]</code> parameter must match either the <code>VariableCode</code> column in the <code>OEVariables</code> table or a property on the <code>Account</code> object.

=== Aggregation ===

Tokens: <code>COUNT:()</code>, <code>MAX:()</code>, <code>MIN:()</code>, <code>SUM:()</code>

==== Count ====

Tokens: <code>COUNT:</code>, <code>(</code>, <code>,</code>, <code>)</code>

Format: <code>COUNT:([atoms])</code> or <code>COUNT:[count_greater_or_equal_to]([atoms])</code>

The value for <code>[atoms]</code> is a comma separated list of atoms to test against. Returns the number <code>[atoms]</code> that return true. The value of <code>[count_greater_or_equal_to]</code> changes the return type of this atom into a boolean, where the result is true if the number of <code>[atoms]</code> is greater or equal to the value supplied. Atoms that use the <code>TOKEN:(,)</code> format are not supported in the list of atoms.

==== Maximum Value ====

Tokens: <code>MAX:</code>, <code>(</code>, <code>,</code>, <code>)</code>

Format: <code>MAX:([atoms])</code>

The value for <code>[atoms]</code> is a comma separated list of atoms of which to find the largest value.

==== Minimum Value ====

Tokens: <code>MIN:</code>, <code>(</code>, <code>,</code>, <code>)</code>

Format: <code>MIN:([atoms])</code>

The value for <code>[atoms]</code> is a comma separated list of atoms of which to find the smallest value.

==== Summation ====

Tokens: <code>SUM:</code>, <code>(</code>, <code>,</code>, <code>)</code>

Format: <code>SUM:([atoms])</code>

The value for <code>[atoms]</code> is a comma separated list of atoms to add together.

=== Categories ===

Tokens: <code>C:</code>, <code>S:</code>

==== Product and Modification Categories ====

Tokens: <code>C:</code> or <code>Category:</code>

Format: <code>C:[product_category_display_id]</code> or <code>C:[modification_category_display_id]</code>

The value for the <code>[product_category_display_id]</code> parameter should match the <code>ProductCategoryDisplayID</code> in the <code>ProductCategories</code> table. The value for the <code>[modification_category_display_id]</code> parameter should match the <code>ModificationCategoryDisplayID</code> in the <code>ModificationCategories</code> table.

==== Style Option Categories ====

Tokens: <code>S:</code> or <code>StyleOptionCategory:</code>

Format: <code>S:[style_option_category_display_id]</code> or <code>S:[style_option_category_name]</code>

The value for the <code>[style_option_category_display_id]</code> parameter should match the <code>StyleOptionCategoryDisplayID</code> in the <code>StyleOptionCategories</code> table. The value of <code>[style_option_category_name]</code> should match the <code>ShortName</code> in the <code>StyleOptionCategories</code> table. The boolean value indicating whether there is a selected style option category excludes special style options.

=== Collections ===

Tokens: <code>COLLECTION:</code>, <code>(</code>, <code>,</code>, <code>)</code>

Format: <code>COLLECTION:([atoms])</code> or <code><nowiki>[[atoms]]</nowiki></code>

Used to return a collection of atom values. The value for <code>[atoms]</code> is a comma separated list of atoms to evaluate.

=== Conditionals ===

Tokens: <code>EVERY:</code>, <code>I:</code>, <code>LIMIT:</code>, <code>SOME:</code>

==== Every Condition ====

Tokens: <code>EVERY:</code> or <code>ALL:</code>, <code>(</code>, <code>,</code>, <code>)</code>

Format: <code>EVERY:([atoms])</code>

The value for <code>[atoms]</code> is a comma separated list of atoms to test against. Returns true if all of the atoms test true. Atoms that use the <code>TOKEN:(,)</code> format are not supported in the list of atoms.

==== Conditional Expressions ====

Tokens: <code>I:</code> or <code>Conditional:</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. Atoms that use the <code>TOKEN:(,)</code> format are not supported in the true or false expressions; they are however, supported in [[#Infix_Conditional_Expressions|infix conditionals]].

==== Limits ====

Tokens: <code>LIMIT:</code>, <code>(</code>, <code>,</code>, <code>)</code>

Format: <code>LIMIT:([atoms])</code> or <code>LIMIT:[maximum]([atoms])</code>

The value for <code>[atoms]</code> is a comma separated list of atoms to test against. The value of <code>[maximum]</code> indicates the threshold at which the result will be true (greater than <code>[maximum]</code>). If no <code>[maximum]</code> is supplied, it is assumed <code>0</code>. Atoms that use the <code>TOKEN:(,)</code> format are not supported in the list of atoms.

==== Some Conditions ====

Tokens: <code>SOME:</code> or <code>ANY:</code>, <code>(</code>, <code>,</code>, <code>)</code>

Format: <code>SOME:([atoms])</code>

The value for <code>[atoms]</code> is a comma separated list of atoms to test against. Returns true if any of the atoms test true. Atoms that use the <code>TOKEN:(,)</code> format are not supported in the list of atoms.

=== Constants ===

Tokens: <code>X:</code> or <code>Constant:</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.

==== Boolean ====

Tokens: None

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

The value must be a string representation of a boolean. Valid values are <code>true</code> or <code>false</code> (case-insensitive).

==== Decimal ====

Tokens: <code>X:</code>, <code>Constant:</code> or None

Format: <code>X:[decimal]</code> or <code>[decimal]</code>

The value must be a string representation of a number.

==== String ====

Tokens: <code>X:</code>, <code>Constant:</code> or None

Format: <code>X:"[string]"</code> or <code>"[string]"</code>

The value can be any string (enclosed in double quotes).

=== Dates and Time Spans ===

Tokens: <code>DATETIME:</code>, <code>TIMESPAN:</code>

==== Dates ====

Tokens: <code>DATETIME:</code>

Format: <code>DATETIME:[datetime]</code>, <code>DATETIME:"[datetime]"</code>, <code>DATETIME:Now</code>, or <code>DATETIME:UtcNow</code>

The value for <code>[datetime]</code> is a string representation of a date, or one of two keywords: <code>Now</code> or <code>UtcNow</code>. <code>Now</code> will return the users local time, where as <code>UtcNow</code> will return the users local time with the UTC offset applied. When writing infix expressions, enclose the <code>[datetime]</code> in double quotes, in order to distinguish operators such as <code>/</code> or <code>-</code> from date delimiters. See [https://msdn.microsoft.com/en-us/library/system.datetime.parse(v=vs.110).aspx#StringToParse here] for valid formats.

==== Time Spans ====

Tokens: <code>TIMESPAN:</code>

Format: <code>TIMESPAN:[timespan]</code> or <code>TIMESPAN:"[timespan]"</code>

The value for <code>[timespan]</code> is a string representation of a time span. When writing infix expressions and wishing to provide a negative time span, enclose the <code>[timespan]</code> in double quotes, in order to distinguish the <code>-</code> which indicates a negative. See [https://msdn.microsoft.com/en-us/library/se73z7b9(v=vs.110).aspx#Anchor_2 here] for valid formats.

=== Infix Notation ===

Tokens: <code>INFIX:</code>, <code>IF:</code>

==== Infix Expressions ====

Tokens: <code>INFIX:</code> or <code>MATH:</code> or <code>=</code>

Format: <code>INFIX:[expression]</code>

The value for <code>[expression]</code> is an expression/formula written in [[wikipedia:Infix notation|infix notation]]. Uses a subset of the [[#Valid_Operators|available operators]]: <code>*</code>, <code>/</code>, <code>+</code>, <code>-</code>, <code><</code>, <code>></code>, <code><=</code>, <code>>=</code>, <code>/U</code>, <code>*U</code>, <code>&&</code>, <code>||</code>, <code>!=</code>, <code>^</code>, <code>%</code>, <code>==</code>, <code>??</code>. When using the <code>=</code> token to denote an infix expression, it must be the first character in the formula.

==== Infix Conditional Expressions ====

Tokens: <code>IF:</code> or <code>InfixConditional:</code> or <code>ELSEIF:</code>, <code>=></code> or <code>THEN:</code> or <code>ELSE:</code>

Format: <code>IF:[conditional]</code> or <code>IF:[conditional]=>[expression_if_true]</code> or <code>IF:[conditional]=>[expression_if_true]=>[expression_if_false]</code> or

<code>IF:[conditional]THEN:[expression_if_true]ELSEIF:[second_conditional]THEN:[expression_if_second_is_true]ELSE:[expression_if_all_are_false]</code>

Infix conditional expressions are defined using the above tokens, and as the name suggests, uses [[wikipedia:Infix notation|infix notation]] throughout. 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 (or if <code>[expression_if_true]</code> is omitted, <code>1</code> when pricing, otherwise <code>true</code>). If it evaluates to <code>false</code> and <code>[expression_if_false]</code> is omitted, <code>0</code> is returned when pricing, otherwise <code>false</code>; the <code>[expression_if_false]</code> parameter is executed if supplied. The conditionals can be chained by using an <code>ELSEIF:</code> in the false expression.

=== Modifications ===

Tokens: <code>D:</code> or <code>Modification:</code>

Format: <code>D:[modification_display_id]</code> or <code>D:?</code>

The value for the <code>[modification_display_id]</code> parameter should match the <code>ModificationDisplayID</code> in the <code>Modifications</code> table. If the current item being evaluated is a modification, the value returned will be true if the modification's display id matches. If the current item being evaluated is a product, the value returned will be true if the product has a modification attached to it where the modification's display id matches. The format <code>D:?</code> is the equivalent of asking if the current item being evaluated is a modification. To check for special modifications, use <code>A:D:?</code>.

==== Modification Product ====

Tokens: <code>D:P:</code>, <code>D:P:D:</code>, <code>Modification:Product:</code> or <code>Modification:Product:Modification</code>

Format: <code>D:P:[product_display_id]</code> or <code>D:P:D:[modification_display_id]</code>

The value for the <code>[product_display_id]</code> parameter should match the <code>ProductDisplayID</code> in the <code>Products</code> table. The value returned will be true if the modification being evaluated is attached to a product with a matching display id. The format <code>D:P:D:[modification_display_id]</code> is the equivalent of asking if the modification that is being evaluated is attached to a product that with a matching modification display id.

==== Modification Product Tags ====

Tokens: <code>D:P:T:</code> or <code>Modification:Product:Tag:</code>

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

Used to determine if the modification is attached to a product that is tagged as the value specified in the <code>[tag_name]</code> parameter.

==== Modification Product Categories ====

Tokens: <code>D:P:C:</code> or <code>Modification:Product:Category:</code>

Format: <code>D:P:C:[product_category_display_id]</code>

Used to determine if the modification is attached to a product that is included in the category as specified by the value of the <code>[product_category_display_id]</code> parameter.

=== Nested Formulas ===

Tokens: <code>F:</code> or <code>Formula:</code>

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.

The value for <code>[parameter]</code> should match <code>PricingRuleLabel</code>.

=== Pricing and Upcharges ===

Tokens: <code>R:</code>, <code>U:</code>, <code>M:</code>

==== Prices ====

Tokens: <code>R:</code> or <code>Price:</code>

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

Used to obtain the price for the current item. Only four values are valid for the <code>[price_type]</code> parameter. These values are <code>BOOK</code>, <code>LIST</code>, <code>PREMIUM</code> or <code>BASE</code>. <code>BOOK</code> is the calculation of the first summary group in the sequence (<code>ProductLineSummaryGroups</code>), where as <code>LIST</code> is the price with no formula applied. If <code>[pricing_rule_label]</code> is supplied, it executes the pricing rule with a name of <code>[pricing_rule_label]</code>. The value for <code>[pricing_rule_label]</code> should match <code>PricingRuleLabel</code>.

==== Upcharges ====

Tokens: <code>U:</code> or <code>Upcharge:</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.

==== Variable Price Codes ====

Tokens: <code>M:</code> or <code>VariablePriceCode:</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.

=== Products ===

Tokens: <code>P:</code> or <code>Product:</code>

Format: <code>P:[product_display_id]</code> or <code>P:?</code>

The value for the <code>[product_display_id]</code> parameter should match the <code>ProductDisplayID</code> in the <code>Products</code> table. The format <code>P:?</code> is the equivalent of asking if the current item being evaluated is a product. To check for special products, use <code>A:P:?</code>.

==== Product Modifications ====

Tokens: <code>P:D:</code> or <code>Product:Modification:</code>

Format: <code>P:D:[modification_display_id]</code> or <code>P:D:?</code>

The value for the <code>[modification_display_id]</code> parameter should match the <code>ModificationDisplayID</code> in the <code>Modifications</code> table. The value returned will be true if the product being evaluated has a modification attached to it where the modification's display id matches. The format <code>P:D:?</code> is the equivalent of asking if the current product has any modifications attached to it.

==== Product Modification Categories ====

Tokens: <code>P:D:C:</code> or <code>Product:Modification:Category:</code>

Format: <code>P:D:C:[modification_category_display_id]</code>

The value for the <code>[modification_category_display_id]</code> parameter should match the <code>ModificationCategoryDisplayID</code> in the <code>ModificationCategories</code> table. Returns true of the product being evaluated has any modifications attached to it which match the specified modification category.

=== Product Lines and Options ===

Tokens: <code>E:</code>, <code>H:</code>, <code>L:</code>

==== Finished End Option Groups ====

Tokens: <code>E:</code> or <code>FinishedEndOptionGroup:</code>

Format: <code>E:[finished_end_group_option_code]</code>

The value for the <code>[finished_end_group_option_code]</code> parameter should match the <code>FinishedEndOptionGroupCode</code> in the <code>FinishedEndOptionGroups</code> table.

==== Hinging Option Groups ====

Tokens: <code>H:</code> or <code>HingingOptionGroup:</code>

Format: <code>H:[hinging_option_group_code]</code>

The value for the <code>[hinging_option_group_code]</code> parameter should match the <code>HingingOptionGroupCode</code> in the <code>HingingOptionGroups</code> table.

==== Product Lines ====

Tokens: <code>L:</code> or <code>ProductLine:</code>

Format: <code>L:[product_line_name]</code>

The value for the <code>[product_line_name]</code> parameter should match the <code>LineName</code> in the <code>ProductLines</code> table.

=== Quotes ===

Tokens: <code>QUOTE:</code>

Format: <code>QUOTE:[property_or_variable_code]</code>

Used to obtain the value of a quote variable or property for the quote the current item is associated with. The value for the <code>[property_or_variable_code]</code> parameter must match either the <code>VariableCode</code> column in the <code>OEVariables</code> table or a property on the <code>Quote</code> object.

=== Specials ===

Tokens: <code>A:</code> or <code>Special:</code>

Format: <code>A:?</code>

The format <code>A:?</code> is the equivalent of asking if the current item being evaluated is a special. This includes special products and special modifications (and styles). When evaluating <code>StyleOptionRules</code>, will return true if any of the currently selected style options is a special.

==== Special Product ====

Tokens: <code>A:P:</code> or <code>Special:Product:</code>

Format: <code>A:P:?</code>

The format <code>A:P:?</code> is the equivalent of asking if the current item being evaluated is a special product.

==== Special Modification ====

Tokens: <code>A:P:</code> or <code>Special:Modification:</code>

Format: <code>A:D:?</code>

The format <code>A:D:?</code> is the equivalent of asking if the current item being evaluated is a special modification.

==== Special Style Options for a Given Category ====

Tokens: <code>S: and A:</code> or <code>StyleOption: and Special:</code>

Format: <code>S:[style_option_category_display_id]:A:?</code> or <code>S:[style_option_category_name]:A:?</code>

To check if a special style option is selected for a given category, use the format <code>S:[style_option_category_display_id]:A:?</code> or <code>S:[style_option_category_name]:A:?</code>.

=== Style Options and Selections ===

Tokens: <code>O:</code>, <code>Q:</code>, <code>N:</code>

==== Style Options ====

Tokens: <code>O:</code> or <code>StyleOption:</code>

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

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

==== Style Option Selections ====

Tokens: <code>Q:</code> or <code>StyleOptionSelection:</code>

Format: <code>Q:[style_option_display_id]</code> or <code>Q:[style_option_tag_name]</code>

The value for the <code>[style_option_display_id]</code> parameter should match the <code>StyleOptionDisplayID</code> in the <code>StyleOptions</code> table. The value of <code>[style_option_tag_name]</code> should match the <code>StyleOptionTag</code> in the <code>StyleOptionTags</code> table. Functionally equivalent to the <code>O:</code> token, with the exception of when evaluating Style Option Rules, will check all products on the quote for the selected style.

==== Style Option Selection Count ====

Tokens: <code>N:</code> or <code>StyleOptionSelectionCount:</code>

Format: <code>N:[style_option_category_display_id]</code> or <code>N:[style_option_category_name]</code>

The value for the <code>[style_option_category_display_id]</code> parameter should match the <code>StyleOptionCategoryDisplayID</code> in the <code>StyleOptionCategories</code> table. The value of <code>[style_option_category_name]</code> should match the <code>Name</code> in the <code>StyleOptionCategories</code> table.

=== Tags ===

Tokens: <code>T:</code> or <code>Tag:</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. When the formula is being used as a price rule for a modification, the check is made on the product the modification is attached to (the equivalent of <code>D:P:T:[tag_name]</code>).

=== Variables ===

Tokens: <code>ACCOUNTVARIABLE:</code>, <code>VAR:</code>, <code>V:</code>, <code>W:</code>, <code>QUOTEVARIABLE:</code>

==== Account Variables ====

Tokens: <code>ACCOUNTVARIABLE:</code>

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

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

==== Context Variables ====

Tokens: <code>VAR:</code> or <code>ContextVariable:</code>

Format: <code>VAR:[variable_name]</code> or <code>[variable_name]</code> or <code>VAR:[variable_name]=[variable_value];[expression]</code> or

<code>VAR:[variable_name]=[variable_value];[second_variable_name]=[second_variable_value];[expression]</code>

Used to get or set the value of a variable during formula evaluation. The value for the <code>[variable_name]</code> can be any valid variable name (a-zA-Z0-9). The value for <code>[variable_value]</code> can be any valid formula. If a variable has not first been set, when evaluating a quote product this functions the same as [[#Product_Variables|product variables]]; similarly, when evaluating a quote product modification, this functions the same as [[#Modification_Variables|modification variables]].

==== Product Variables ====

Tokens: <code>V:</code> or <code>Variable:</code>

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

Used to obtain the value of a product 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.

==== Modification Variables ====

Tokens: <code>W:</code> or <code>ModificationVariable:</code>

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

Used to obtain the value of a modification 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. When pricing a quote product modification, the value is first checked against any <code>ModificationPrompts</code> with a matching <code>OEVariable</code>.

==== Quote Variables ====

Tokens: <code>QUOTEVARIABLE:</code>

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

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

== Rules and Formulas ==

=== Formulas ===

Located in the <code>Formulas</code> table. Used to validate the availability of modifications, finished ends, hinging, and so on. The <code>F:</code> token uses the <code>Formulas</code> table. In the case of validating modification availability, return true if the modification is available.

=== Final Validation Rules ===

Located in the <code>FinalValidationRules</code> table. Used to validate a quote before its status is changed to ''submitted''. The <code>F:</code> token uses the <code>Formulas</code> table. The rule should return false if the validation fails and a message needs to be presented to the user.

=== Pricing Rules ===

Located in the <code>PricingRules</code> table. Used to calculate pricing. The <code>F:</code> token uses the <code>PricingRules</code> table.

=== Style Option Rules ===

Located in the <code>StyleOptionRules</code> table. Used in evaluating the availability of style options.

==== Excludes ====

Tokens: <code><X></code>

Format: <code>[atoms]~<X>~[excluded_atoms]</code>

If any <code>[atoms]</code> are selected, <code>[excluded_atoms]</code> are excluded. The inverse is also true, if any <code>[excluded_atoms]</code> are matched, <code>[atoms]</code> are excluded. Valid atoms start with <code>T:</code>, <code>O:</code>, <code>S:</code> or <code>Q:</code>.

==== Excludes X of Y ====

Tokens: <code>< ></code>

Format: <code>[atoms]~<[count]>~[additional_atoms]</code>

If <code>[count]</code> or more <code>[atoms]</code> and or <code>[additional_atoms]</code> are selected, <code>[atoms]</code> and <code>[additional_atoms]</code> are excluded. Valid atoms start with <code>T:</code>.

==== Formula ====

Tokens: <code><F></code>

Format: <code>[style_selection_atoms]~<F>~[formula]</code>

If <code>[formula]</code> evaluates to true, <code>[style_selection_atoms]</code> are excluded. Valid style selection atoms start with <code>T:</code>, <code>O:</code>, <code>S:</code> or <code>Q:</code>. The <code>[formula]</code> can use all tokens. The <code>F:</code> token uses the <code>Formulas</code> table.

=== Values (Min, Max, Effect Conditions) ===

Usable in <code>OEPromptItems</code> and <code>ModificationPrompts</code>: <code>MinValue</code>, <code>MaxValue</code>, <code>MinFractionalValue</code>; <code>ModificationVariableEffects</code>: <code>Value</code>, <code>EffectConditionFormulaID</code>, <code>EffectType</code>. If the <code>EffectType</code> is a modification (e.x.: <code>D:123</code>), and the user is on advanced product entry with auto-mods enabled, the specified modification will automatically be selected. The <code>F:</code> token uses the <code>Formulas</code> table.

== Result Negation ==

To negate the result of an ''operation'' append a <code>!</code> after the token and before the token value. This works for both boolean and decimal results. In the case of a decimal, this is the equivalent of multiplying by <code>-1</code>.

== Valid Operators ==

=== String ===

<code>+</code> - Concatenate

<code>=</code> - Case Insensitive Equality

<code>==</code> - Case Sensitive Equality

<code>!</code> - Case Insensitive Inequality

<code>!=</code> - Case Sensitive Inequality

<code><</code> - Ordinal Less Than

<code>></code> - Ordinal Greater Than

<code><=</code> - Ordinal Less Than or Equal To

<code>>=</code> - Ordinal Greater Than or Equal To

<code>??</code> - Second Value if First is Null

=== Number (Decimal) ===

<code>+</code> - Add

<code>-</code> - Subtract

<code>*</code> - Multiply

<code>/</code> - Divide

<code>^</code> - Exponential

<code>%</code> - Modulo

<code>*U</code> - Multiply and Apply Ceiling on the Product

<code>/U</code> - Divide and apply Ceiling on the Quotient

<code><</code> - Less Than

<code>></code> - Greater Than

<code><=</code> - Less than or Equal To

<code>>=</code> - Greater Than or Equal To

<code>=</code> or <code>==</code> - Equality

<code>!</code> or <code>!=</code> - Inequality

<code>|</code> or <code>||</code> - Either Value is Greater Than Zero

<code>&</code> or <code>&&</code> - Both Values are Greater Than Zero

<code>??</code> - Second Value if First is Less Than or Equal To Zero

=== Boolean ===

<code>|</code>, <code>||</code>, <code>-</code>, <code>/</code>, <code>%</code> or <code>??</code> - Either Value is True

<code>&</code>, <code>&&</code>, <code>+</code>, <code>*</code> or <code>^</code> - Both Values are True

<code>=</code> or <code>==</code> - Equality

<code>!</code> or <code>!=</code> - Inequality

<code>#</code> - Logical Not (One True Value and One False Value)

=== Collection ===

<code>+</code> - Add

<code>-</code> - Remove

<code>|</code> or <code>||</code> - Returns the first collection with the elements from the second collection that do not exist in the first added

<code>&</code> or <code>&&</code> - Returns the elements that existing in both collections

<code>=</code> or <code>==</code> - Returns true if the values in the two collections match in value and sequence

<code>!</code> or <code>!=</code> - Returns true if the values in the two collections do not match match in value and or sequence

<code>??</code> - Second Value if First is Null

== Examples ==

=== Aggregate Atoms ===

<code>COUNT:(O:12,O:34,O:56)</code> - Returns the number of style options that match

<code>COUNT:2(O:78,O:99,O:100)</code> - Returns true if two or more of the style options match

<code>MAX:(V:MIN_CHARGE,F:PRICE_PER_SQ_FEET_WxD)</code> - Returns <code>F:PRICE_PER_SQ_FEET_WxD</code> if it is greater than <code>V:MIN_CHARGE</code>, otherwise returns <code>V:MIN_CHARGE</code>

<code>SUM:(R:LIST,F:FINISHED_END_UPCHARGE)</code> - Returns the sum of list price and <code>F:FINISHED_END_UPCHARGE</code>. Same as <code>R:LIST~F:FINISHED_END_UPCHARGE~+</code>

<code>SUM:(R:LIST,F:!DISCOUNT)</code> - Returns the list price minus the discount (adds the negated result of the DISCOUNT formula)

=== Conditional Atoms ===

<code>LIMIT:1(O:123,O:456,O:789)</code> - Returns true if more than one style option matches

<code>ANY:(T:IsTall,T:IsTallCorner)</code> - Returns true if an item is tagged with IsTall or IsTallCorner. Same as <code>SOME:(T:IsTall,T:IsTallCorner)</code> or <code>T:IsTall~T:IsTallCorner~|</code>

<code>ALL:(T:IsBase,O:Framed,O:Cherry)</code> - Returns true if the product is tagged IsBase and it has style option selections that are tagged Framed and Cherry

=== Math and Infix Atoms ===

<code>MATH:1+2*3/(4+5)</code> - Returns the numeric value <code>1.666...</code>

<code>=2+4*8/(10+22)</code> - Returns the numeric value <code>3</code>

<code>=-2+4-2*-2</code> - Returns the numeric value <code>6</code>

<code>INFIX:R:LIST+F:FINISHED_END_UPCHARGE</code> - Same as <code>R:LIST~F:FINISHED_END_UPCHARGE~+</code>

<code>IF: V:ROS_H <= 9.6875 => R:BOOK => R:BOOK * 2</code> - Same as <code>I:V:ROS_H~X:NINE_DOT_SIXEIGHTSEVENFIVE~<==>R:BOOK,R:BOOK~X:TWO~*</code>

<code>IF: V:ROS_H <= 9.6875 THEN: R:BOOK ELSEIF: V:ROS_H > 20 THEN: R:BOOK * 3 ELSE: R:BOOK * 2</code> -
:Logically the same as <code>if (V:ROS_H <= 9.6875) { return R:BOOK; } if (V:ROS_H > 20) { return R:BOOK * 3; } return R:BOOK * 2;</code>

<code>IF: (P:? && V:WS_UPCHARGE) || (D:? && W:WS_UPCHARGE) || A:? => F:UPCHARGE</code> -
:Same as <code>I:P:?~V:FINISH_UPCHARGE~&~D:?~W:FINISH_UPCHARGE~&~A:?~|~|=>F:UPCHARGE,X:ZERO</code>

<code>=F:LIST_PREMIUM * SUM:(U:CarriageHouseVintage,U:WornEdgeTreatmentVintage,U:FlyspeckSplitsVintage,U:DistressingWormholesVintage,U:KnifeOutsVintage,U:JointCutsVintage)</code> -
:Same as <code>U:CarriageHouseVintage~U:WornEdgeTreatmentVintage~+~U:FlyspeckSplitsVintage~+~U:DistressingWormholesVintage~+~U:KnifeOutsVintage~+~U:JointCutsVintage~+~F:LIST_PREMIUM~*</code>

=== Context Variable Atom ===

<code>var: x = 10; y = 5; z = x * y; x + y + z</code> - Returns the numeric value <code>65</code>

<code>IF: ANY:(VAR:WS_UPCHARGE,A:?) => F:UPCHARGE</code> - Same as <code>IF: (P:? && V:WS_UPCHARGE) || (D:? && W:WS_UPCHARGE) || A:? => F:UPCHARGE</code>

<code>var: u = U:FINISH; IF: u < .1 THEN: 173 ELSEIF: u < .2 THEN: 217 ELSEIF: u < .3 THEN: 269 ELSEIF: u < .4 THEN: 329 ELSEIF: u < .5 THEN: 398 ELSEIF: u < .6 THEN: 476 ELSE: 563</code> -
:Same as <code>IF: U:FINISH < .1 THEN: 173 ELSEIF: U:FINISH < .2 THEN: 217 ELSEIF: U:FINISH < .3 THEN: 269 ELSEIF: U:FINISH < .4 THEN: 329 ELSEIF: U:FINISH < .5 THEN: 398 ELSEIF: U:FINISH < .6 THEN: 476 ELSE: 563</code>

=== Collection Atom ===

<code>INFIX: [1,2,3,4] + 5</code> - Returns a collection with the elements 1, 2, 3, 4, and 5

<code>INFIX: [1,2,3,4] - 4</code> - Returns a collection with the elements 1, 2, and 3

<code>INFIX: [1,2] + [2,3]</code> - Returns a collection with the elements 1, 2, 2, and 3

<code>INFIX: ([1,2,3,4] + 5) == ([1,2,3,4,5,6] - 6)</code> - Returns true

<code>INFIX: [1,2] || [1,4]</code> - Returns a collection with the elements from the first collection, and the elements from the second collection no included in the first: 1, 2, and 4

<code>INFIX: [1,2] && [1,4]</code> - Returns a collection with the elements that exist in both collections: 1

=== Date Time and Time Span Atoms ===

<code>Quote:DateModified > (DateTime:UtcNow - TimeSpan:30)</code> - Returns true if the quote was modified withing the last 30 days.

<code>DateTime:"4/27/2016" + TimeSpan:1</code> - Returns the date 4/28/2016

=== Negation ===

<code>I:P:7206=>F:!PRODBSD6FinalValidationRule,TRUE</code> - Same as <code>I:P:7206=>F:PRODBSD6FinalValidationRule~X:TRUE~#,X:TRUE</code>

<code>T:!IsMolding</code> - Returns true if an item is not tagged with IsMolding

<code>=! true</code> - Returns false

=== Style Option Formulas ===

<code>T:KK~<F>~AccountVariable:NOT_FOR_KK</code> - Exclude KK if the account has a true value for the variable NOT_FOR_KK

<code>T:Cabinet Order~<F>~IF: Quote:ProjectUrgency.ProjectUrgencyLabel != "Cabinet Order"</code> -
:Exclude style options tagged Cabinet Order if the order type Cabinet Order is not selected.

=== Tokenless Constants ===

<code>I:V:EXTENDED_STILE_R~3~<==>92,114</code> - Same as <code>I:V:EXTENDED_STILE_R~X:THREE~<==>X:NINETYTWO,X:ONEHUNDREDFOURTEEN</code>

Back To [[Developer Page]]

Order Express Improvements

2016-08-01T19:08:38Z

Sowens:

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)

Back to [[Developer Page]]

JSON Permission Editing

2016-08-01T19:07:30Z

Sowens:

Find the JSON permissions file in the manufacturers OE app data folder, edit it how you want, save, right click the file, & set it to Read-Only so OE won't overwrite that file upon login.

For each permission section based on usertypes, there should be a ContextType 1 & ContextType 2 followed by the individual permissions. "ContextType": 1 stands for the UserType. To edit the usertype, change the ContextIdentifier number to one of these

00000000-0000-0000-0000-000000000001 Master Admin

00000000-0000-0000-0000-000000000002 Manufacturer Admin

00000000-0000-0000-0000-000000000003 Designer

00000000-0000-0000-0000-000000000004 Dealer Admin

00000000-0000-0000-0000-000000000005 Sales Reps

00000000-0000-0000-0000-000000000006 Engineering

00000000-0000-0000-0000-000000000007 Customer Support

181ffdf9-e7a0-40e7-8bee-1984d03eba8a Tester

9d7bd37c-4d8b-4aa1-b7d5-4b0816a64d1b Manufacturer

----------------------------------
"ContextType": 2 is for the status of the project. Here is what you can change the ContextIdentifier to

00000000-0000-0000-0000-000000000001 Quoted

00000000-0000-0000-0000-000000000002 Submitted

00000000-0000-0000-0000-000000000003 Under Manufacturer Review

00000000-0000-0000-0000-000000000004 Under Dealer Review

00000000-0000-0000-0000-000000000005 Acknowledgement Approved

00000000-0000-0000-0000-000000000006 In Production

00000000-0000-0000-0000-000000000007 Cancelled

00000000-0000-0000-0000-000000000008 Assistance Needed

00000000-0000-0000-0000-000000000009 Shipped

00000000-0000-0000-0000-000000000010 Acknowledged

00000000-0000-0000-0000-000000000011 Question Hold

00000000-0000-0000-0000-000000000012 Open for Revision

00000000-0000-0000-0000-000000000013 Re-Submitted

-----------------------------------------------

Here is a sample where the user type is a Master Admin & the status of the project is Submitted. This sample shows that the permission "Can Edit Under Review Projects" has a default value of True, but is currently set to False which means the user can not edit under review projects. It also shows the permission "Can Change Status" that has a default value of False, but is currently set to True which means that the user can change the status of the project. Also to note is that with the exception of the last permission, each permission has a comma after the closed bracket.

"Context": [
{
"ContextType": 1,
"ContextIdentifier": "00000000-0000-0000-0000-000000000001"
},
{
"ContextType": 2,
"ContextIdentifier": "00000000-0000-0000-0000-000000000002"
}
],
"Permissions": [
{
"Token": "CAN_EDIT_UNDERREVIEW_PROJECTS",
"DefaultValue": "TRUE",
"CurrentValue": "false",
"ValueType": "bool"
},
{
"Token": "CAN_CHANGE_STATUS",
"DefaultValue": "FALSE",
"CurrentValue": "TRUE",
"ValueType": "bool"
}
]

Back to [[Developer Page]]

Nuget Package Repository

2016-08-01T19:07:07Z

Sowens:

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

Back to [[Developer Page]]

Smart Spec - Tips & Tricks

2016-08-01T19:05:27Z

Sowens:

== Remember Password ==

By default, Smart Spec doesn't allow users to save their password. However, this functionality ''does'' exist in the released version.

To access it:

<ol>
<li>Open Smart Spec</li>
<li>On the bottom of the login screen, click the link for "'Show Advanced Options'"</li>
<li>Click the link that says "'Open Data Folder'"</li>
<li>Close SmartSpec at this time to prevent it from overwriting our changes.</li>
<li>Open the file named "'LoginPreferences.xml'" in notepad. (the "'.xml'" portion may not be visible on all computers)</li>
<li>Edit the file as follows: (sample file shown below)

Locate the line highlighted below:
<syntaxhighlight lang="xml" highlight="6">
<?xml version="1.0" encoding="utf-16"?>
<LoginPreferences xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<ManufacturerID>00000000-0000-0000-0000-000000000000</ManufacturerID>
<RememberUsername>true</RememberUsername>
<Username>joe.user@evisionservices.com</Username>
<Password />
</LoginPreferences>
</syntaxhighlight>

And change it to this:

<syntaxhighlight lang="xml" highlight="6">
<?xml version="1.0" encoding="utf-16"?>
<LoginPreferences xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<ManufacturerID>00000000-0000-0000-0000-000000000000</ManufacturerID>
<RememberUsername>true</RememberUsername>
<Username>joe.user@evisionservices.com</Username>
<Password>MySuperSecretPassword</Password>
</LoginPreferences>
</syntaxhighlight>
</li>

<li>Save the file and open SmartSpec.</li>

Back to [[Main Page]]

Smart Spec

2016-08-01T19:04:58Z

Sowens:

{{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]]

Back to [[Main Page]]

Order Express - Advanced Troubleshooting

2016-08-01T19:04:05Z

Sowens:

__FORCETOC__

== 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. Machine.config 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.

==== Machine.config file 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>

==== Instructions ====
<ol>
<li>Locate the machine.config file and make a backup of the file. Put the backup in a safe location in case something goes wrong with it. </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 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>

== 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>

Back to [[Main Page]]

Order Express - Frequently Asked Questions

2016-08-01T19:03:10Z

Sowens:

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__ 

== What are the system requirements? ==

==== Minimum ====
These requirements are the minimum requirements for the program to run. Only having the minimum system requirements may cause the program to run at a slower speed & display as unintended.
* 1.3GHz or faster processor
* Microsoft Windows 7
* 2GB of RAM
* 320MB of available hard-disk space
* 1024x768 screen resolution
* Google Chrome, Mozilla Firefox, or Microsoft Internet Explorer 8, 9, or 10

==== Recommended ====
* 2.0GHz or faster dual-core processor
* Microsoft Windows 10
* 4GB of RAM
* 10GB of available hard-disk space
* 1920x1080 screen resolution
* Google Chrome, Mozilla Firefox or Microsoft Edge browser

== What are the 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

== How do I uninstall the program? ==
[[File:Win8 ControlPanelUninstall.png|thumb|125px|Uninstall Programs]]
[[File:Win8 ControlPanelUninstall2.png|thumb|125px|Uninstalling Order Express]]

Like other applications [[Order Express]] can be uninstalled from a computer using the '''Add/Remove Programs''' entry in the control panel. This is usually sufficient to solve any problems that arise as a result of a failed installation, but this method does leave a few minor files behind on the local system. These files rarely cause issues, but removing these files is an effective way to guarantee that an installation of Order Express is brand new.

===Standard Uninstall===
# Open the ''Control Panel''
# Under ''Programs'', click ''Uninstall a program''
# Select ''Order Express 2.3'' in the list, and click ''Uninstall/Change''
# Confirm the uninstall on the dialog that appears.

=== Extended (Full) Uninstall ===
<ol>
<li>Perform the steps outlined above in ''Standard Uninstall''</li>
<li>Navigate to the following directory on the target computer:
<code>%appdata%\..\Local\Apps\2.0\</code>
</li>
<li>Open the folder that is '''not''' named ''Data''.</li>
<li>Open the only folder in this directory. </li>
<li>In this directory, the amount of folders is dependent upon the number of ClickOnce applications installed on the local machine. </li>
<li>Ensure that the folders are sorted by name, and locate any folders that '''begin''' with the text <code>orde...exe</code> '''or''' <code>orde..tion</code></li>
<li>After locating those folders, back them up (copy them to the desktop) and then delete them.</li>
<li>At this point Order Express has been completely removed from your system.</li>
</ol>

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

=== See Also ===
* [[Order Express - Advanced Troubleshooting|Advanced Troubleshooting]]
* [[Order Express]]

Back to [[Main Page]]

Order Express - Features

2016-08-01T19:02:42Z

Sowens:

Order Express - Features

2016-08-01T19:02:12Z

Sowens:

Order Express - Features

2016-08-01T19:02:03Z

Sowens:

Order Express

2016-08-01T15:01:04Z

Sowens:

2.3.31.0

2016-07-29T20:49:42Z

Sowens:

2.3.31.0

2016-07-29T20:49:13Z

Sowens:

Here is a brief look at the recent updates to Order Express.

'''Global Updates'''

1. New Attachments section added on Project Review – Added the ability to view and download attachments from the Project Review screen

[[File:2.3.31.0 - Attachments.jpg]]

2. Added a “Hide Attachments” option at the top of the Project Review screen to be able to hide the Attachments section.
[[File:2.3.31.0 - Hide Attachments.jpg]]

3. Removed Apply Style Upcharges “Estimate” and “Actual” box inside of a special. Replaced with a single Apply Style Upcharges checkbox.
[[File:2.3.31.0 ApplyStyleUpcharges.jpg]]

'''Bug Fixes'''

1. Corrected a 20/20 import issue with minimum and maximum width data.

2. Manufacturer Adjustment box on Project Info screen (if applicable) now accepts negative values

Back to [[Order Express - Release Notes|Release Notes]]

2.3.31.0

2016-07-29T20:47:09Z

Sowens:

Here is a brief look at the recent updates to Order Express.

'''Global Updates'''

1. New Attachments section added on Project Review – Added the ability to view and download attachments from the Project Review screen

[[File:2.3.31.0_Attachments.jpg]]

2. Added a “Hide Attachments” option at the top of the Project Review screen to be able to hide the Attachments section.

3. Removed Apply Style Upcharges “Estimate” and “Actual” box inside of a special. Replaced with a single Apply Style Upcharges checkbox.

'''Bug Fixes'''

1. Corrected a 20/20 import issue with minimum and maximum width data.

2. Manufacturer Adjustment box on Project Info screen (if applicable) now accepts negative values

Back to [[Order Express - Release Notes|Release Notes]]

File:2.3.31.0 ApplyStyleUpcharges.jpg

2016-07-29T20:39:42Z

Sowens:

File:2.3.31.0 - Hide Attachments.jpg

2016-07-29T20:38:33Z

Sowens:

File:2.3.31.0 - Attachments.jpg

2016-07-29T20:38:05Z

Sowens:

Order Express

2016-07-29T20:35:27Z

Sowens: /* See Also */

Order Express - Release Notes

2016-07-29T20:33:35Z

Sowens:

[[2.3.31.0]]

Back To [[Main Page]]

2.3.31.0

2016-07-29T20:32:55Z

Sowens:

Here is a brief look at the recent updates to Order Express.

'''Global Updates'''

1. New Attachments section added on Project Review – Added the ability to view and download attachments from the Project Review screen

2. Added a “Hide Attachments” option at the top of the Project Review screen to be able to hide the Attachments section.

3. Removed Apply Style Upcharges “Estimate” and “Actual” box inside of a special. Replaced with a single Apply Style Upcharges checkbox.

'''Bug Fixes'''

1. Corrected a 20/20 import issue with minimum and maximum width data.

2. Manufacturer Adjustment box on Project Info screen (if applicable) now accepts negative values

Back to [[Order Express - Release Notes|Release Notes]]