logging and typos

imixs · Nov 28, 2024 · 535ffe3 · 535ffe3
1 parent 6f5cafd
commit 535ffe3
Show file tree

Hide file tree

Showing 4 changed files with 25 additions and 17 deletions.
diff --git a/imixs-workflow-core/src/main/java/org/imixs/workflow/ModelManager.java b/imixs-workflow-core/src/main/java/org/imixs/workflow/ModelManager.java
@@ -345,7 +345,7 @@ public BPMNModel findModelByWorkitem(ItemCollection workitem) throws ModelExcept
                     if (result != null) {
                         // match
                         // update $modelVersion
-                        logger.info("Update $modelversion by regex " + version + " ▷ " + matchingVersion);
+                        logger.fine("Update $modelversion by regex " + version + " ▷ " + matchingVersion);
                         workitem.model(matchingVersion);
                         return result;
                     }

diff --git a/imixs-workflow-core/src/main/java/org/imixs/workflow/WorkflowKernel.java b/imixs-workflow-core/src/main/java/org/imixs/workflow/WorkflowKernel.java
@@ -439,6 +439,9 @@ private ItemCollection processEvent(ItemCollection workitem, ItemCollection even
 
         // test if a new model version was assigned by the last event
         if (updateModelVersionByEvent(workitem, event)) {
+            logger.log(Level.INFO, "\u2699 set new model : {0} ({1})",
+                    new Object[] { workitem.getItemValueString(UNIQUEID),
+                            workitem.getItemValueString(MODELVERSION) });
             // write event log
             logEvent(workitem.getTaskID(), workitem.getEventID(), workitem.getTaskID(), workitem);
             // load new Event and start new processing life cycle...
@@ -703,6 +706,8 @@ public List<ItemCollection> getSplitWorkitems() {
      * 
      * @param workitem
      * @param event
+     * @param log      - indicates if the procedure should be logged into the server
+     *                 log
      * @return true if the model version was updated by this method
      * @throws ModelException
      * @throws PluginException
@@ -745,10 +750,6 @@ private boolean updateModelVersionByEvent(final ItemCollection workitem, final I
                 updateWorkflowStatus(workitem, itemColNextTask);
             }
         }
-
-        logger.log(Level.INFO, "\u2699 set new model : {0} ({1})",
-                new Object[] { workitem.getItemValueString(UNIQUEID),
-                        workitem.getItemValueString(MODELVERSION) });
         return true;
 
     }

diff --git a/src/site/markdown/engine/plugins/analysisplugin.md b/src/site/markdown/engine/plugins/analysisplugin.md
@@ -2,19 +2,23 @@
 
 To analyze different phases of a workflow process the ImixsAnalysis PlugIn can be added into a process model:
 
+```java
+org.imixs.workflow.plugins.AnalysisPlugin
+```    
 
-    org.imixs.workflow.plugins.AnalysisPlugin
-
 The plugin is used to measure the processing time of the different phases during the life cycle of a process instance. Several individual measuring points can be configured in the workflow result of a BPMN event:
 
 
-###Example:
+### Example:
 
+```xml
     <item name='measurepoint' type='start'>p1</item> 
-
+```
 defines a start point named 'p1'
 
+```xml
     <item name='measurepoint' type='stop'>p1</item> 
+```
 
 defines an end point named 'p1'. 
 

diff --git a/src/site/markdown/engine/plugins/taxonomyplugin.md b/src/site/markdown/engine/plugins/taxonomyplugin.md
@@ -2,27 +2,30 @@
 
 The Imixs Taxonomy plugin can be used to collect taxonomy data at specific stages of a business process.
 
+```java
+org.imixs.workflow.plugins.TaxonomyPlugin
+```
 
-    org.imixs.workflow.plugins.TaxonomyPlugin
-
 The plugin can be used to collect data about the processing time of a certain phase within the life cycle of a process instance. Several individual taxonomy definitions can be configured in the workflow result of a BPMN event:
 
 
-###Example:
+### Example:
 
+```xml
     <taxonomy name="approval">
     	<type>start</type>
     	<anonymised>true</anonymised>
     </taxonomy>
-    
+```   
 
 defines a start point named 'approval'
 
+```xml
     <taxonomy name="approval">
     	<type>stop</type>
     	<anonymised>true</anonymised>
     </taxonomy>
-
+```    
 
 defines the end point named 'approval'. 
 
@@ -53,14 +56,14 @@ The first taxonomy definition 'P1' will measure the total processing time for a
 
 Per default the taxonomy plugin generates anomymised data entries. This means there is no reference to the user who started or stopped specific stages of a business process.
 
-You can disable this GDPR feature by setting the tag 'anonymised' to 'false:
-
+You can disable this GDPR feature by setting the tag `anonymised` to `false`:
 
+```xml
     <taxonomy name="approval">
     	<type>stop</type>
     	<anonymised>false</anonymised>
     </taxonomy>
-
+```