Workflow Attachment vs Package

What is the difference between a workflow attachment and a workflow package? I was hoping to start a workflow using the attachment, and once I've validated that the attachment satisfies certains conditions, copy the attachment into the workflow package.

Background:

I have a process that is initiated with an "Email Inbound - Initiate" activity. This activity fetches the emails for a given user. The idea here is that the user has emails, each with one attachment, that need to be the package for a running workflow. But before placing the email attachment into the workflow package, I wanted to put it into the workflow attachment, then perform a few checks to ensure that the email/attachment meet certain requirements. Once the checks succeed, copy the attachment data into the package using a process data mapper.

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

Miller-zzMST

Hi!

Package is like a process variable - you define its type (and form optionally) on design phase, before running the process.

Attachment you got in runtime and you don't know what object you will get before you get it.

Package can be just one. You can bind to it different objects, but the package instance will be just one.

Number of attachments could be variable.

For package you must define the Type. For attachment you define nothing.

For package you can define the Form template, so you can get form's content (inside data container). You can do it for attachment, but you must bind the form template to certain index and you must be sure that in runtime you will get exactly what you have defined earlier.

~ Konstantin

All comments

Miller-zzMST

Hi!

Package is like a process variable - you define its type (and form optionally) on design phase, before running the process.

Attachment you got in runtime and you don't know what object you will get before you get it.

Package can be just one. You can bind to it different objects, but the package instance will be just one.

Number of attachments could be variable.

For package you must define the Type. For attachment you define nothing.

~ Konstantin

udeleng

Does each workflow that has a mandatory package always has at least one attachment as well? So in such a case, for each workflow, there would a dmi_package and a dmi_wf_attachment bound to the same object?

UPDATE:

I started a workflow with one mandatory package. I used DQL to see if both a dmi_package and dmi_wf_attachment existed for the workflow, but only a dmi_package was present.

Message was edited by: udeleng

Miller-zzMST

UPDATE:

I started a workflow with one mandatory package. I used DQL to see if both a dmi_package and dmi_wf_attachment existed for the workflow, but only a dmi_package was present.

Package and attachment are different objects and unrelated with each other.