FIXME **This page is not fully translated, yet. Please help completing the translation.**\\ //(remove this paragraph once the translation is finished)// ====== StartSoftlinksFromProcessVariablesHandler ====== ==== Description ==== This handler starts softlinks and fills it with variables from the main process.\\ Thereby, the handler acts in accordance with the following schema:\\ It searches for all variables containing the mainDataSuffix. Afterwards, it searches for all variables containing the softLinkSuffix, whereupon it counts up from 0 to the small softLinkCount.\\ After every increment, a softlink instance of the given definition is started.\\ In the softlink instances, the softLinkSuffix is removed in order to make the representation in the Smartform easier. ------ ==== Action Class ==== com.dooris.bpm.actionhandler.StartSoftlinksFromProcessVariablesHandler \\ ---- ==== Event Type ==== any ==== Action Name ==== any ==== Mandatory Fields ==== none ---- ==== Parameter ==== == softLinkDefinition == Tells from which process definitions the softlinks should be started. \\ == mainSuffix == Tells which process variables of the main process should be taken for all of the Softlinks.\\ Example: if the suffix is set to '_daten', the all process variables ending in '_daten' will be taken (firstname_daten, lastname_daten, email_daten,...) \\ Mandatory field. If not required, please enter an ending that is not in existence, i.e. _end \\ \\ == softLinkCount == Tells how many softlinks should be started.\\ \\ == softLinkSuffix == Tells which variables should be assigned to the individual softlinks.\\ This is where the parameter "softLinkCount" is employed.\\ The handler counts to "i", counting up from **0** to **i < softLinkCount** and thereby collects all variables that are built based on the following schema:\\ At least one variable with the appropriate ending must be found, otherwise a sub-process will not be started. \\ \\ variablenname_softLinkSuffix[i]\\ \\ After every run-though, an new instance of the softlinkdefinition is started and provided with all of the variables found through the "mainSuffix" and the "softLinkSuffix". \\ In the newly-started softlink instance, the softLinkSuffix is removed in order to assure a standardized representation in the Smartform.\\ \\ == archiveWithMainInstance == Tells whether the softlink instances should be archived when the main process instances are archived.\\ Possible values:\\ archiveWithMainInstance=true -> The softlink instances are archived with the main process instance.\\ archiveWithMainInstance=false -> The softlink instances are not archived with the main process instance. ---- ==== Example ==== {{ :software:tim:actionhandler:startsoftlinksfromprocessvariableshandler.png }} === Example 1 === Variable in the process: \\ user_email_sl[0]=Hans.Mueller@tim.com \\ user_email_sl[1]=Marta.Meier@tim.com \\ user_email_sl[2]=Max.Muster@tim.com \\ user_name_sl[0]=Hans \\ user_name_sl[1]=Marta \\ user_name_sl[2]=Max \\ user_nachname_sl[0]=Mueller \\ user_nachname_sl[1]=Meier \\ user_nachname_sl[2]=Muster \\ \\ softLinkSuffix=_sl; \\ softLinkCount=3; \\ \\ => 3 Sub-processes with variables: \\ 1. \\ user_email=Hans.Mueller@tim.com \\ user_name=Hans \\ user_nachname=Mueller \\ 2. \\ user_email=Marta...\\ === Beispiel 2 === datum_start_hp=01.01.2014 \\ starter_hp=pm \\ anforderer_hp=user123 \\ username=Mueller \\ useremail_sl[0]=mueller@tim.de \\ uservorname=Hans \\ \\ mainSuffix=_hp \\ softLinkSuffix=_sl; \\ softLinkCount=1; \\ \\ =>Subprozess mit folgenden Variablen \\ datum_start=01.01.2014 \\ starter=pm \\ anforderer=user123 \\ ----