M-Files Process Maps 2.0.4.12

---

#2002 Enhancement – The properties shown in the Object Smartnode can now be selected and therefore reduced as desired.

#2006 Bugfix – Labels show #NA instead of value when addressing associated object
Under certain circumstances addressing metadata from ‘associated object’ resulted in #NA instead of showing the corresponding value. Also using the dynamic value dialog box lead to exceptions when using boolean meta data. Fixed.

#2005 Enhancement – The object smart node now displays files which are carried by the object. The files are displayed with their icon. The default action can be set as desired i.e. view or or edit.

You can configure the default action in the properties:

#2004 Enhancement – With version 2.0.4.12, the filters and content areas of the SmartNodes have been extended/adapted. Filters and content areas are available both on the Object SmartNodes and on the View SmartNodes.

ObjSN

• Relations ( Filter&Content )
• Files ( Content )

ViewSN

• Content ( Filter&Content )

Extensions/changes for the content area:

Single objects If only a single object falls into one of the categories of a content area, this is now treated as a special case.

Hide the 'Counter' The counter above the relation can be hidden. It can be automatically hidden, if then count results in a single object.

This can be configured in the properties section:

Both Object Smart Nodes and View Smart Nodes now have an optimized section for the content. The command for a single object can be set up. For OBJECTS it will launch the metacard. For DOCUMENTS it will launch the default viewer.

Grouping-Level set to OBJID: When you set the grouping Level to OBJID the result is a list of all related object or documents. In the past you often had a “#” symbol as the icon. This as been optimized to display the corresponding object or class icon.

Optimized Filters – automatically reduced Filters: In the past the list of filters had to be manually reduced to the desired outcome. This was a lengthy configuration process.

The lists in the filter area are reduced automatically, at least as far as possible. This works excellently in the relations area of the Object SmartNodes, as the result set ( relations ) is fixed here and the lists can be adapted to the values that actually exist:

To enable or disable this behavior use the properties pane:

Unfortunately, this automatic reduction does not work so well with the View SmartNodes. Here, the relevant information can only be obtained from the corresponding search queries in the view. However, the views/search queries must really be configured accordingly for the same effect to occur.

Automatic hiding of lists If lists are redundant, they can now be hidden. This means that they only appear when it makes sense. Lists are 'redundant', for example

• if they are empty
• if they only contain one value

Due to the automatic reduction of lists, this now occurs more frequently. This behavior can also be configured in the properties:

#2007 Enhancement – Optimizations to dynamically display content based on associated objects (selected in shell listing) A. The object type of the associated object can be applied to corresponding properties in the filter conditions.

The following example shows a selected 'Department' as an associated object. The associated object is displayed by the Object SmartNode on the left-hand side. At the same time, the related persons and processes are displayed on the right-hand side. A View SmartNode is used for this purpose, which has a corresponding view as its basis. In this view, the object type of the associated object is now applied to the corresponding filter conditions ( here 'Department' ):

The two separate SmartNodes on the right-hand side therefore show direct relations of the associated object. These are only the relationships (from the point of view of the associated object). However, these can now be processed differently. E.g. different filter conditions or corresponding charts. This behavior must of course be configured (default is off). This is done in the filter options of the SmartNode:

Strict filtering means that the list of filter values is shortened. Not strict shows the entire list and selects the given values.

B. Other properties of the associated object Other properties of the associated object can also be applied to filter conditions.

The following example shows the same as before. However, there is a different View SmartNode on the right-hand side. This now shows the processes that have a relationship with the objects from the 'Managers' property of the associated object. This is therefore an indirect relationship. These objects cannot be found directly in the relations of the associated object, as the relationship 'goes around a corner'.

Of course, this behavior must also be configured. It must also be defined specifically for certain properties: