Serialized Form

Package pl.net.bluesoft.rnd.pt.ext.emailcapture.model

Class pl.net.bluesoft.rnd.pt.ext.emailcapture.model.EmailCheckerConfiguration extends pl.net.bluesoft.rnd.processtool.model.PersistentEntity implements Serializable

Serialized Fields

mailSessionProperties

String mailSessionProperties

automaticUser

String automaticUser

rules

Set<E> rules

Class pl.net.bluesoft.rnd.pt.ext.emailcapture.model.EmailCheckerRuleConfiguration extends pl.net.bluesoft.rnd.processtool.model.PersistentEntity implements Serializable

Serialized Fields

subjectRegexp

String subjectRegexp

Regular expression that matches email subject. If the subject does not match, email is ignored for this rule. Empty field means that subject is not validated.

senderRegexp

String senderRegexp

Regular expression that matches email sender (name and email address). If the sender does not match, email is ignored for this rule. Empty field means that sender is not validated.

recipientRegexp

String recipientRegexp

Regular expression that matches email recipient (name and email address). If the recipient does not match, email is ignored for this rule. Empty field means that recipient is not validated.

processCode

String processCode

Process code to start. Must match ProcessDefinitionConfig.bpmDefinitionKey value.

omitTextAttachments

Boolean omitTextAttachments

should attachments of unknown or text/* content-type be added published do CMIS

lookupRunningProcesses

Boolean lookupRunningProcesses

Lookup running processes. The running process is looked up using email subject (with removed tokens provided by subjectRemovables attribute, removed whitespaces and uppercased) matched to ProcessInstance.keyword. When the process is initiated by email, ProcessInstance.keyword is filled with email subject using the algorithm presented above. What may be interesting is the fact, that one rule can start process, and another rule can lookup matching instance later on and publish attachments to another cmis folder.

startNewProcesses

Boolean startNewProcesses

When no running process has been matched, should a new process be started?

subjectRemovables

String subjectRemovables

Tokens removed from subject. Used for matching of processes using lookupRunningProcess mechanism.

repositoryAtomUrl

String repositoryAtomUrl

CMIS repository Atom url. If not provided, email attachments are ignored and not stored in CMIS.

repositoryId

String repositoryId

CMIS repository ID.

repositoryUser

String repositoryUser

CMIS repository username

repositoryPassword

String repositoryPassword

CMIS repository password

rootFolderPath

String rootFolderPath

CMIS repository root folder path. In this root folder, a folder with process name and prefixed with newFolderPrefix is created. In this folder, a sub-folder with a name subFolder is created and email attachments are stored there. If the folders on the path do not exist, the mechanism attempts to create them.

subFolder

String subFolder

Subfolder name. Documents are stored in ${rootFolderPath}/${newFolderPrefix}${processCode}/${subFolder}/

newFolderPrefix

String newFolderPrefix

Prefix used when creating a folder dedicated to a process instance on CMIS. Documents are stored in ${rootFolderPath}/${newFolderPrefix}${processCode}/${subFolder}/

folderAttributeName

String folderAttributeName

Under which process attribute a cmis folder ID for the documents is stored. Use of this attribute is suggested only when process uses a single CMIS folder (without subfolders).

configuration

EmailCheckerConfiguration configuration

runningProcessActionName

String runningProcessActionName

When processIdSubjectLookupRegexp is defined and matched and also matching process has been found and matches field processStepName. This action will be performed on the process, propagating further its execution. The process to be propagated further has to be waiting in a task in a special task. It is worth mentioning, that different combinations of runningProcessActionName and processIdSubjectLookupRegexp can provide simple decisions for a process. Email's sender address will be marked as a decision source, so there should exist some kind of regexp on sender's email and some verification of sender (e.g. SMTP AUTH) should be used.

processIdSubjectLookupRegexp

String processIdSubjectLookupRegexp

When processIdSubjectLookupRegexp is defined and matched and also matching process has been found and matches field processStepName. This action will be performed on the process, propagating further its execution. \ The regexp should contain one grouping, which will allow the engine to extract ProcessInstance.externalKey The process to be propagated further has to be waiting in a task in a special task. It is worth mentioning, that different combinations of runningProcessActionName and processIdSubjectLookupRegexp can provide simple decisions for a process. Email's sender address will be marked as a decision source, so there should exist some kind of regexp on sender's email and some verification of sender (e.g. SMTP AUTH) should be used.

processTaskName

String processTaskName

When processIdSubjectLookupRegexp is defined and matched and also matching process has been found and matches field processStepName. This action will be performed on the process, propagating further its execution. The process to be propagated further has to be waiting in a task in a special task. It is worth mentioning, that different combinations of runningProcessActionName and processIdSubjectLookupRegexp can provide simple decisions for a process. Email's sender address will be marked as a decision source, so there should exist some kind of regexp on sender's email and some verification of sender (e.g. SMTP AUTH) should be used.