Form Template changing submission mechanism from default to SQL storage

[dhavalbakhda]

Hi,

We have so many workflow initiated and storage mechanism is Content sever workflow

Now i want to know if i change the storage mechanism to SQL Table, will the initiated workflow will get impacted??



Thanks
Dhaval

 

[appnair]

That really depends on your business requirement.work flow table data is something that you cannot control.If you generate a workflow from a map it is stored in livelink
schema you cannot do anything about it.You are also loosely confusing Forms /form templates with workflow.Forms can write its values as version files or you can put it to a table in the schema so its values can be shown thru a sql tool.And on top of it it has versions and submissions .When you make a form initiate a workflow all it is doing is take the user from the form to the first step(maybe not the start step) of the real workflow.The mechanism of the form is still what you set.the form travels with the workflow at different steps.Many people will replace the standard workflow step with form steps so it can be made more pleasing with java script validations et al.

At the core Form Templates/Forms are in no way connected to workflow.The designer makes the call to use forms in a workflow or not.


Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008,Livelink ECM Champion 2010

http://www.tek-tips.com/faqs.cfm?fid=2884

http://www.linkedin.com/in/appunair

http://www.livelink.in

 

[dhavalbakhda]

Thanks Appnair for your quick reply.

Actually our client wants live report of all the workflow data, so i thought to change the storage mechanism to SQL data.We have used Form template and it is associated with the Workflow. In Form Template Manage Relational Table i have change it to Create sql table and from Workflow map Map->Forms i have change Storage Mechanism to SQL Table. My main concern as there are so many initiated workflow pending, by changing it to SQL table this initiated Workflow should not get impacted.


Thanks
Dhaval

 

[appnair]

What was initiate form a map(old stuff) does not have any bearing.Only maps going forwards will see your change

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008,Livelink ECM Champion 2010

http://www.tek-tips.com/faqs.cfm?fid=2884

http://www.linkedin.com/in/appunair

http://www.livelink.in

 

[ggriffit]

I believe that ALL changes to the WF template, such as adding a new step, changing config etc will only apply to WFs started after the change.

To be sure, I would create a simple dummy WF using the "old" mechanism, run a few WFs and then change it to the "new" mechanism to confirm.

Greg Griffiths
Livelink Certified Developer & ECM Global Star Champion 2005 & 2006

http://www.greggriffiths.org/livelink/

 

[dhavalbakhda]

Thanks Appnair..

@ggriffit Thanks for replying. I have tested, its not affecting the old initiated workflow.
Have you tested??

 

[ggriffit]

that is as I expected, each WF instance is a standalone entity once initiated and any changes to the template only affect future instances.

Greg Griffiths
Livelink Certified Developer & ECM Global Star Champion 2005 & 2006

http://www.greggriffiths.org/livelink/