You are viewing limited content. For full access, please sign in.

Question

Question

Start Forms Process from workflow

asked on June 9, 2016

I'm working on a custom process and I'm trying to use the Invoke Business Process activity in workflow to trigger a Forms process. If I'm using this activity is it limited to after the invokes the forms  process that it needs to be sent to a User task? When I setup a gateway as the first step, I receive an error 'Object not set to an instance of an object and it will not evaluate the gateway (terminating the Forms Process). If I setup a user task to be the first task it allows for me to have an approval for the form and continue on the process. 

 

Thanks in advance,

Steven

0 0

Replies

replied on June 9, 2016

Could you post the complete error message from the Forms Event log, please?

0 0
replied on June 10, 2016

Error6/9/2016 5:02:49 PM

An unexpected error has occurred. [LFF502-UnexpectedError] Details: URL: Error: UnexpectedError Date: 6/9/2016 5:02:49 PM (Central Standard Time) HTTP Status Code: 500 Business Process ID: 42 Instance ID: 20 Business Process Name: Work_Item_Form Stack Trace: Caught exception: Laserfiche.Forms.CommonUtils.Exceptions.LFFormsException Message: An unexpected error has occurred. [LFF502-UnexpectedError] Inner exception: System.NullReferenceException Message: Object reference not set to an instance of an object. at Laserfiche.Forms.Routing.StartEvent.InitializeDataForNewMainProcessInstance(Int32 instanceId, IRoutingContext routingContext) at Laserfiche.Forms.Routing.StartEvent.Execute(Int32 instanceId, IRoutingContext routingContext) at Laserfiche.Forms.Routing.RoutingDispatcher.ExecuteSteps()

0 0
replied on June 12, 2016

Any information on this? Do I need to setup a support case on this? The forms process does not have any issue with not triggered by workflow and started from a user in Forms. Anytime that I have the first activity in the business process after the submission as a gateway the process terminates. 

 

Thanks in advance.

 

0 0
replied on June 12, 2016

Hi Steven, can you open an support case with exported process that can reproduce this issue? We can't reproduce it with a gateway after a start event then start the process using workflow. Thanks.

0 0
replied on June 14, 2016

Working on getting this information sent to a support case. I do however have some additional information as we were able to do additional testing.

Scenario that works:

1. Message Start Event

2. Exclusive Gateway

     a. User Task (Route taken when WF fills out field in Form)

Scenario that causes the error message

1. Message Start Event 

2. Exclusive Gateway

    b. SubProcess (Route taken when WF does not fill out field in Form)

Thanks

 

 

 

0 0
replied on June 14, 2016

Hi Steven, based on the error message and the scenario you provided, the issue is related to a sub process is after the gateway. It's a known issue for 10.1 that will get error when start process using workflow follows by a sub process, we have fixed it in the coming update 1 for 10.1(will be released within 2 weeks).

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.