Release Notes - 3.4.1

Intended audience: ALL USERS

AO Platform: 3.4.1

Release Date

Release 3.4.1 builds on previous 3.x releases of the AO Platform. The underlying infrastructure of 3.x is very similar to 2.3.2. Most apps developed in 2.3.x work in 3.x with very few modifications. We continue to introduce many new features that will make the development and management of solutions much more effortless and be done mainly from the browser as a low-code environment.
The 3.4.1 release continues to have a strong focus on UI and functional enhancements to the Easy Answers solution as well as the composers supporting Easy Answers directly, including Ontology/MSO Composer, and Model Composer.
This topic includes a high-level introduction to the enhancements made during this release.

New Cue Cards showing Totals and/or Percentage of Total for requested data. For Categorical Data Cue Cards, add the Overview Categorical Field and associate the Categorical Trait with a given MSO. See Trait - Categorical.
Simpler Total and Total with Percentage Cue Cards are shown by default in Easy Answers.
New buttons in the Easy Answers Review screen make it easier to Add (or Remove) Synonyms based on the user’s suggested Synonyms.
Additional Filter options when selecting Feedback/Annotations/Issues to review on the Easy Answers Review screen.

Ontology Composer page - new option to add an Ontology with a complete hierarchy of associated MSOs to Transport, including a checkbox to allow “property value synonyms” to be added. See Ontology Page.
MSO pages.
- MSO General page - new Plural Name added and a new option to Clear the MSO Icon (on hover).
- MSO Curation page:
  - Enhancements to the Data Styles tab when selecting an MSO Field Property - new Color Palette and Color Ranges options. See Curation - Field Properties - Data Styles.
  - A number of MicroApps have been removed from the complete list of MicroApps in the dropdown. See the updated list on Curation - Micro Application Properties.
- MSO Traits pages - many new and updated properties in most Traits, and three new Traits that were added to 3.4 release, but missed in the 3.4 Release Notes:
  - Comparable Trait - see Trait - Comparable.
  - Graph Sourced Trait - see Trait - Graph Sourced.
  - Lookup Trait - see Trait - Lookup.
- MSO Statistics page - additional statistics are being generated for data types - mainly Number data types. See MSO - Statistics.
- MSO Settings page - 15 new Easy Answers properties on the MSO Settings page. See MSO - Settings > Easy Answers.

Added new Transformation Recommendations option on the Data Transformations page. This option is only available when MSO is selected as Data Source on the Training Data page. See Configuration > Data Transformations.
Added new Feature Engineering Recommendations option on the Feature Engineering page. This option is only available when MSO is selected as Data Source on the Training Data page. See Configuration > Feature Engineering.
New Manual option on the Test Model page. See Testing a Model.
Removed Pipeline option on the Test Model page.

Added a new Page for Schema on Read > Refresh Schema. See Admin > Schema on Read.
Added new Pages for Color Palettes and Color Palette Types. See Admin > UI.

15+ new documentation topics were added in this release supporting the feature enhancements and UI updates described above.
The AO Platform documentation can be accessed from https://docs.apporchid.com - or from options in the User menu in the AO Platform UI. This main user documentation is not publicly available, a token is required to access it unless accessed from within the AO Platform UI in the User menu.

It’s currently not possible to create the assembly of a final Solution directly from the existing Composers. A new Solution Composer will be introduced in a future release.
When creating an Annotation in Annotation Composer, it’s possible to divide a Layout cell into multiple rows. However, if such a cell in a row has an adjacent cell that isn’t divided, then the multiple rows in the first cell won’t be rendered correctly at runtime. The workaround is to create the same amount of divisions in all cells in the row and for instance use the Spacer control to ensure the Layout renders correctly, eg: