diff --git a/docs/8.0/ayanova/docs/ay-start-changes-from-v7.md b/docs/8.0/ayanova/docs/ay-start-changes-from-v7.md index 1239264f..ae0e1770 100644 --- a/docs/8.0/ayanova/docs/ay-start-changes-from-v7.md +++ b/docs/8.0/ayanova/docs/ay-start-changes-from-v7.md @@ -95,7 +95,7 @@ Similar to how Tax Codes worked in AyaNova 7, rates will now have their price af User interface: The user interface for the work order has been designed to reduce the clutter on screen as much as possible while still using the fewest possible clicks to navigate around from section to section. In addition we've ensured that a work order can be fully completed using a device as narrow as a 360 pixel wide smart phone if necessary. -Decoupling of sections to reduce conflict: In v7 an entire work order was updated at once in the database meaning only one person at a time could edit **any part** of that work order and save without conflict. In v8 we have broken out the work order save process into each individual section so the work order Header is one section, a work order Item is another, a work order item part it's own section etc. This means if two (or more) people are working separately in the same work order, as long as what they are not working in the same section there is no conflict. For example two people could be working with two different work order items at the same time and save independantly of each other or two or more people could be entering parts separately in the same work order item without conflict. Note that there are still circumstances where a conflict can occur and we still recommend people take steps to avoid working in the same areas at the same time, but conflicts will be greatly reduced. V8 still uses the first save wins method of conflict resolution so that no one can save and lose their changes without knowing it. +Decoupling of sections to reduce conflict: In v7 an entire work order was updated at once in the database meaning only one person at a time could edit **any part** of that work order and save without conflict. In v8 we have broken out the work order save process into each individual section so the work order Header is one section, a work order Item is another, a work order item part it's own section etc. This means if two (or more) people are working separately in the same work order, as long as what they are not working in the same section there is no conflict. For example two people could be working with two different work order items at the same time and save independently of each other or two or more people could be entering parts separately in the same work order item without conflict. Note that there are still circumstances where a conflict can occur and we still recommend people take steps to avoid working in the same areas at the same time, but conflicts will be greatly reduced. V8 still uses the first save wins method of conflict resolution so that no one can save and lose their changes without knowing it. Decoupling of Client: In v7 a Client was tightly connected to a work order and needed to be selected prior to creation of a work order and could not be changed. We've made many behind the scenes structural changes to remove this limitation. In v8 the Customer can be changed at any time for the work order as a whole. diff --git a/docs/8.0/ayanova/docs/ay-start-form-data-tables.md b/docs/8.0/ayanova/docs/ay-start-form-data-tables.md index 51ae1fd6..d17c62f7 100644 --- a/docs/8.0/ayanova/docs/ay-start-form-data-tables.md +++ b/docs/8.0/ayanova/docs/ay-start-form-data-tables.md @@ -91,9 +91,13 @@ Use the column selector button ![data table column selector button](img/form-dat ![data table column selector](img/form-data-table-column-selector.png) -Here you can select which columns will be displayed in the data table and in which order. +Here you can select which columns will be included for display in the data table and the order they are displayed by moving them to the desired location and saving the form. -There is a `reset to default` option available from the menu in this form to reset the selections back to the default for this form. +There is a `reset to default` menu option to reset the selections back to their default locations and visibility. + +Some columns do not have an `include` checkbox option because they are the primary identifier for a record and need to be visible to be able to open the record and identify it. + +Column settings are independent of filters. ##### Filtered hidden columns indicator diff --git a/docs/8.0/ayanova/docs/home-schedule.md b/docs/8.0/ayanova/docs/home-schedule.md index 25b62c33..9eacd0c9 100644 --- a/docs/8.0/ayanova/docs/home-schedule.md +++ b/docs/8.0/ayanova/docs/home-schedule.md @@ -13,7 +13,7 @@ The personal schedule menu provides quick access to the currently logged in User ## Settings ![Settings](img/home-schedule-settings.png) -The settings dialog (access by clicking on gear icon at top) controls what is displayed in the schedule. Schedule settings are device independant and saved to the server so that any device used will take these same settings. +The settings dialog (access by clicking on gear icon at top) controls what is displayed in the schedule. Schedule settings are device independent and saved to the server so that any device used will take these same settings. ### First time in day view This controls the starting hour to display in day views. Use it to hide unused hours to reduce the need to scroll down. diff --git a/docs/8.0/ayanova/docs/img/form-data-table-column-selector-button.png b/docs/8.0/ayanova/docs/img/form-data-table-column-selector-button.png index eb3709ec..7a054dd8 100644 Binary files a/docs/8.0/ayanova/docs/img/form-data-table-column-selector-button.png and b/docs/8.0/ayanova/docs/img/form-data-table-column-selector-button.png differ diff --git a/docs/8.0/ayanova/docs/svc-contracts.md b/docs/8.0/ayanova/docs/svc-contracts.md index 35cf870d..c85541ec 100644 --- a/docs/8.0/ayanova/docs/svc-contracts.md +++ b/docs/8.0/ayanova/docs/svc-contracts.md @@ -26,7 +26,7 @@ AyaNova does not automatically apply Unit Contracts as there are too many scenar When a Unit is selected on a work order and that Unit has an **Active and un-expired** Contract **and** that Contract is different from the currently selected Contract in the work order header, AyaNova will prompt the user if they want to use that Contract for the entire work order. If the user chooses to accept it the work order header Contract field will be set to the Unit's Contract. -Multiple Units with Contracts on the same work order are permitted and not prevented so it's up to the user to ensure the validity of chosen Units / Contract. To avoid a conflicting contract situation only select one Contract holding Unit per work order, use a Customer or HeadOffice Contract instead of a Unit Contract or manually select independant contracts not associated with any other object instead of using automatic Contract selection if you want full control over what Contract is in effect in order to apply to multiple Units on the same work order. +Multiple Units with Contracts on the same work order are permitted and not prevented so it's up to the user to ensure the validity of chosen Units / Contract. To avoid a conflicting contract situation only select one Contract holding Unit per work order, use a Customer or HeadOffice Contract instead of a Unit Contract or manually select independent contracts not associated with any other object instead of using automatic Contract selection if you want full control over what Contract is in effect in order to apply to multiple Units on the same work order. ### Contract expiry diff --git a/server/AyaNova/DataList/DataListSqlFilterCriteriaBuilder.cs b/server/AyaNova/DataList/DataListSqlFilterCriteriaBuilder.cs index 6963c5c9..b62d2ce0 100644 --- a/server/AyaNova/DataList/DataListSqlFilterCriteriaBuilder.cs +++ b/server/AyaNova/DataList/DataListSqlFilterCriteriaBuilder.cs @@ -826,7 +826,7 @@ namespace AyaNova.DataList case UiFieldDataType.InternalId: case UiFieldDataType.Integer: //whole numbers, not only integer { - //case 1795 - it's numeric, convert to translation independant format + //case 1795 - it's numeric, convert to translation independent format //RAVEN NOTE: no numbers are coming from the client in any culture format other than xx,xxx.00 but this is just insurance for api users NumberFormatInfo nfi = System.Globalization.CultureInfo.CurrentCulture.NumberFormat; switch (DataType) diff --git a/server/AyaNova/PickList/PickListOptions.cs b/server/AyaNova/PickList/PickListOptions.cs index afcda0cc..ecf9149a 100644 --- a/server/AyaNova/PickList/PickListOptions.cs +++ b/server/AyaNova/PickList/PickListOptions.cs @@ -8,7 +8,7 @@ namespace AyaNova.PickList /* /// The AyaType object type to select from /// The query to filter the returned list by. Query text as provided will be case sensitively matched to all templated fields. - /// Independantely of this, if an addition space separated string that begins with two consecutive periods is encountered that will be considered a separate match to the TAGS collection of each object + /// independentely of this, if an addition space separated string that begins with two consecutive periods is encountered that will be considered a separate match to the TAGS collection of each object /// So a tag query might be entered as "..zon some" which would match all tags LIKE 'zon' and template fields LIKE 'some' /// Include inactive objects in the returned list /// Return only specific items (for pre-selected items on forms)