Dear Aware IM users,
the beta version of Aware IM 8.6 has now been released. If you want to take it for a spin please send email to [email protected]
Please check the video about 8.6 here:
https://youtu.be/9mv03fbTMgg
Video tutorials referenced in the video:
A new tutorial about multi-step processes:
https://youtu.be/5Rq_3GF1CrI
Updated video about custom queries with the section about template builder at the end:
https://youtu.be/ttBHOH2-V-E
Updated video about visual perspectives with the VP editor section at the end:
https://youtu.be/RctLYK40NmM
Full list of features:
1. Support for multi-column comboboxes (see video)
2. Ability to build an HTML template used for custom queries (desktop and mobile) - see new Custom Queries video tutorial
3. Calendar/Scheduler - search for appointments. New checkbox in the Calendar Pane.
4. Ability to show steps for wizard forms (Stepper widget) - see video
5. Support for the Timeline widget - see video
6. Support for image cropping and resizing - see video
7. Visual Perspectives improvements (see new Visual Perspectives video tutorial):
- Support for "modern" style of display - when a header of a panel is displayed using Kendo Cards. There is a new property of a content panel called "Display Settings" which specifies whether to display using "modern" or "classic (same as before)" style.
- When a new content panel is being created the system asks about the contents straight away
- New property of the tab - "Default panel display settings". These are default display properties of the new ContentPanel
- When a new tab is added the dialog displays that allows selecting layout and other properties of the tab straight away
- Layout editor for visual perspectives:
- Synchronization of panel selection in the tree and preview
- Double click on a panel in preview brings up Contents property
- It is possible to drag around panels in preview and change their location (all layouts except Border and Accordion)
- Preview on Desktop, Tablet and Phone for Responsive layouts
- Make panel wider/narrower for Responsive Grid Nested layout
- Maximize preview button that hides the tree and displays preview "full screen"
- Redesign of Content Panel Contents dialog
- Allow editing of all predefined elements
- Allow specifying Calendar, Google Map as separate components (as well as embed them into HTML)
- Date Range Picker component that allows specifying date range
8. "Phone" and "Tablet" view for forms - extra buttons on the forms toolbar
9. IN_CONTEXT function - check if the specified object is in Context
10.Multi-step processes to implement complex wizards - see video
11. It is possible to specify an expression when defining badges, rather than using an attribute of an object - see Badge in CRM
12. Button-type cell in the Form Designser can be used to display multiple buttons
13. It is now possible to add combo-boxes and text fields to toolbars of a form or query. When Editing a Toolbar in the Config. Tool there is a new option “Add Input” (under “Add Text”). This works similar to the current Input Control command in a visual perspective menu item (except that it runs an operation rather than command after data is saved. This feature allows creating complex filters for all types of parsers (currently we allow attribute filters in a toolbar for charts and custom queries only). For example, you can have a combo that filters by a particular period (First Quarter, Second Quarter etc). The process can then be called after a selection is made to check the selected value and run the corresponding query.
14. Grid grouping improvements - see video
a) Allow grouping by multiple columns
b) Allow specifying group header template
c) Allow end users to group data
15. Support for Mac Big Sur
16. Using the latest Java
17. Tomcat 9.0
18. Improvements to the display of the list of active processes
19. On/Off strings for switches and "do not display colon after label" settings added to form styles
20. CSS class and style added to form and grid styles
Bugs:
- Inserting a row into a form and then moving it up making it first lost column properties
- Viewing a document which name has spaces or #, didn't work
- Undefined documents stored in file system could not be "read"
Version 8.6 beta
-
- Posts: 7525
- Joined: Sun Apr 24, 2005 12:36 am
- Contact:
Version 8.6 beta
Aware IM Support Team
Re: Version 8.6 beta
Astonishing!
From,
Himanshu Jain
AwareIM Consultant (since version 4.0)
OS: Windows 10.0, Mac
DB: MYSQL, MSSQL
Himanshu Jain
AwareIM Consultant (since version 4.0)
OS: Windows 10.0, Mac
DB: MYSQL, MSSQL
Re: Version 8.6 beta
IN_CONTEXT ?
Unsure why this is needed?
@support Please give use case. Thx
Unsure why this is needed?
@support Please give use case. Thx
Click Here to see a collection of my tips & hacks on this forum. Or search for "JaymerTip" in the search bar at the top.
Jaymer
Aware Programming & Consulting - Tampa FL
Jaymer
Aware Programming & Consulting - Tampa FL
Re: Version 8.6 beta
This looks promising
-
- Posts: 7525
- Joined: Sun Apr 24, 2005 12:36 am
- Contact:
Re: Version 8.6 beta
Regarding IN_CONTEXT.
The usage is IF IN_CONTEXT('Name of BO') = 'Yes'
The use case for this is somewhat esoteric. We have found a need for it in one of the apps we developed. In this app the same process was called from forms of different objects. These objects were naturally passed as a context for the process call. The process had only one object declared as input and it used to work assuming that only this object is in the context. So if the process was called from a form of a different object it didn't work. Of course, it was possible to create a duplicate of the process and declare a different object as the input and then another duplicate for yet another object. The objects in question, by the way, were related through some reference attribute - object B could be derived from object A as A.B etc.
But creating multiple processes with different input made the app very messy, so we ended up with the following solution - declare only one object as process input, for example A. Then the code of the process looked like this:
IF IN_CONTEXT ('B') = 'Yes' Then
FIND A WHERE A.B = B
IF IN_CONTEXT ('C') = 'Yes' Then
FIND A WHERE A.C = C
...
// Then do all the work as usual assuming that object A is context (if it wasn't the rules above made sure it was)
The usage is IF IN_CONTEXT('Name of BO') = 'Yes'
The use case for this is somewhat esoteric. We have found a need for it in one of the apps we developed. In this app the same process was called from forms of different objects. These objects were naturally passed as a context for the process call. The process had only one object declared as input and it used to work assuming that only this object is in the context. So if the process was called from a form of a different object it didn't work. Of course, it was possible to create a duplicate of the process and declare a different object as the input and then another duplicate for yet another object. The objects in question, by the way, were related through some reference attribute - object B could be derived from object A as A.B etc.
But creating multiple processes with different input made the app very messy, so we ended up with the following solution - declare only one object as process input, for example A. Then the code of the process looked like this:
IF IN_CONTEXT ('B') = 'Yes' Then
FIND A WHERE A.B = B
IF IN_CONTEXT ('C') = 'Yes' Then
FIND A WHERE A.C = C
...
// Then do all the work as usual assuming that object A is context (if it wasn't the rules above made sure it was)
Aware IM Support Team