WorkflowSettings

From GeoMedia Smart Client
Jump to: navigation, search
Settings WorkflowSetting FormSetting CommonSetting



Contents

1 WorkflowRoot
2 Version
3 WorkflowLinkGroup/WorkflowLink
4 WorkflowNode
5 WorkflowTrigger & Parameters

5.1 SQL Trigger

5.2 SQL Iterator Trigger

5.3 SQL File Iterator Trigger

5.4 Mail Trigger

5.5 Session/Remove Session Trigger

5.6 Log Trigger



The workflow enables the user to implement the hierarchical logic of the application in the form of a tree structure. This chapter will describe the necessary and optional Workflow-Elements used in the WorkflowSettings.xml file.

The definition of all workflows can be written in a XML-File, which should be stored at the following path:

  • Intergraph\GeoMedia SmartClient\Program\Workflows\WorkflowSettings\


Example:

  • MyNewProject.xml


Blue.pngThe filename does not distinguish between the FormSettings-XML and the (optionally) employed resource file(s).



Hierachical structure of the Workflow-Elements:

XSD Workflow settings


Relation between the distinct hierarchical layers:

  • WorkflowRoot: Root element for the Workflow-Settings structure, appears exactly once per document.
Parentelement Cardinality Childelement Cardinality
WorkflowRoot 1
WorkflowLinkGroup 0 .. n
WorkflowNode 1 .. n
Version 0 .. 1


  • WorkflowLinkGroup: Container element for embedding Workflow-Links in the panel navigation.
Parentelement Cardinality Childelement Cardinality
WorkflowLinkGroup 1 WorkflowLink 1 .. n


  • WorkflowLink: Element for embedding Workflow-Nodes in the panel navigation.
  • Version: Element for saving the Workflow specific software version.
  • WorkflowNode: navigation-element in the HTML-Workflow.
Parentelement Cardinality Childelement Cardinality
WorkflowNode 1 WorkflowNode 0 .. n
WorkflowTrigger 0 .. n


  • WorkflowTrigger: Element for trigger-interaction with the database.
Parentelement Cardinality Childelement Cardinality
WorkflowTrigger 1 Param 0 .. n


  • Param: Element for defining the trigger-parameter.


Example:

General structure of a Workflow-XML

  1.  <?xml version="1.0" encoding="utf-8"?>
  2.  <WorkflowRoot>
  3.   <Version major="1" minor="0" hotfix="0" annex="" />
  4.   <WorkflowLinkGroup name="Organizationgroup" label="Organizations">
  5.     <WorkflowLink nodeid="110"/>
  6.     <WorkflowLink nodeid="120"/>                 
  7.   </WorkflowLinkGroup>
  8.   <WorkflowNode id="0" label="Emergency operation center">
  9.     <WorkflowNode id="200" label="Localization">
  10.       <WorkflowNode id="210" label="Register Location" controller="Form" form="OPERATION" emptyform="true" condition="true" follownode="2240">
  11.         <WorkflowTrigger name="Template" type="SqlTrigger" method="after" 
  12. condition="SQL[SELECT CASE COUNT(*) WHEN 0 THEN 1 ELSE 0 END FROM PR_OPERATION_UNIT WHERE OPERATION_ID={FORM.OPERATION_ID} AND {FORM.TEMPLATE_GUID} IS NULL]">
  13.           <Param name="Sql" value="INSERT INTO PR_OPERATION_UNIT(OPERATION_ID,NAME,BEGINDATE) VALUES (NEW_GUID,'OPERATION VIENNA',SYSDATE)" />
  14.         </WorkflowTrigger>
  15.         ...
  16.       </WorkflowNode>
  17.     </WorkflowNode>
  18.   </WorkflowNode>
  19.   ...
  20.  </WorkflowRoot>



Pfeil new.png To the top Pfeil new.png

WorkflowRoot

The base node of the Workflow.xml is always the node called Workflow-Root; it contains no attributes.

You can add subentries of the types WorkflowLinkGroup - WorkflowLink, WorkflowNode, and one subentry of the type Version.


WorkflowRoot-Attributes

GMSC 2014

Attribute Mandatory Description
theme no Name of theme.


 <WorkflowRoot theme="FlatTheme">
 ...
 </WorkflowRoot>



Language: English