Process with no documents general question.

I have a task to create a process that is fairly complex. This process will have no documents attached to it but is tracking the flow of a process that has documents that need to be created. These documents will be stored outside of documentum and taskspace. I am looking for help on how to do this process that will track from inbox to inbox with no real data being added other then checkboxes for pass, fail and very few dropdown list boxes.

This process needs to be able to be tracked in the BAM and have reports against it. These reports need to pull from historical data as well, meaning if the process completes all the way thru there is a disposition box that stated its end status (pursue, non-compete, third party) they are anticipating about 50 of these being completed each week and want history for the last 6 months.

thank you in advance!

Find more posts tagged with

Comments

msroth

You shouldn't have any trouble building processes without packages or documents attached; I do it all the time. To track the data you are interested in you can use process variables and structured data types as appropriate.

michaeljmeza

I thought that when the process completed the process variables were lost for history purposes.

msroth

I believe that is true. If you move them into SDTs should stay around until the dm_Clean job is run (one of the new params on the job is to clean up SDTs). I’m not sure of the exact sync mechanism with BAM but it seems to me that once they are in the BAM database they should be available for historic reporting.

Cheers,

--Scott

M. Scott Roth, EMCPA

Content Technology Solution Architect

C | +1 (703) 408-1187

F | +1 (571) 482-5551

Scott.Roth@FlatironsSolutions.com

http://www.flatironssolutions.com<http://www.flatironssolutions.com/

DCTM_Guru

"I thought that when the process completed the process variables were lost for history purposes."

- If you want process values to persist, you need to map them to your object model. I typcially do this for some process variables at the end of the workflow.

DimaL

If you'll use SDT or process variables and mark them as reportable they will be persisted in BAM database

After that, they cannot be deleted, unless you did it yourself, which allows you to report on last 6 months.