Forms [LFF380-ValidateNoStep] Error

asked on May 15, 2017 • Show version history

Hi All,

I'm working on Forms process and am having trouble configuring a Timer Catch Event to send an email reminder to the employee that needs to provide a signature.

Here's a screenshot of the process:

After a supervisor reviews and signs the form, the relevant employee receives an email that their signature is required. For testing purposes, if they do not sign within 1 minute of receiving the first email, another email should be sent reminding them to sign the form. This reminder email should be sent every minute until the form is signed.

I created the following Timer Catch Event on the Employee Signature task:

Here are the properties for the reminder email:

However, after initiating the process, providing the supervisor signature, and receiving the first employee notification email, nothing happens--the Instance Monitor just shows everything as suspended. The Timer Catch Events are triggering, but no emails are being sent. Here's an example (all items with "Terminated" status has a status of "Suspended" before I killed the process):

When I checked the Error Log for this process, I received an error with a code that I couldn't search out on Support or Answers:

The process step configured within task name "Employee Signature Deadline Reminder" is not valid or has not occurred. [LFF380-ValidateNoStep]

Details: URL: Error: ValidateNoStep Date: 5/15/2017 8:09:47 AM (Central Standard Time) HTTP Status Code: 400 Business Process ID: 6 Instance ID: 215 Business Process Name: REDACTED Process

Stack Trace: Caught exception: Laserfiche.Forms.CommonUtils.Exceptions.LFFormsException Message: The process step configured within task name "Employee Signature Deadline Reminder" is not valid or has not occurred. [LFF380-ValidateNoStep] at FormsModel.RoutingModels.AssignPreviousStep.GetFormIdAndSubmissionId(cf_bp_worker_instances processInstance, cf_bp_main_instances instance, AssignedTypes at, String AssignedStepId, Int32 LastSubmissionId, RoutingInstanceStatus OriginalStatus, Int32& SubmissionId, Int32& FormId) at Laserfiche.Forms.Routing.EmailService.GetFormToAddToAttachment(cf_bp_worker_instances processInstance, RoutingInstanceStatus OriginalStatus, cf_forms& form, Int32& submissionId) at Laserfiche.Forms.Routing.EmailService.Execute(Int32 instanceId, IRoutingContext routingContext, RoutingInstanceStatus OriginalStatus) at Laserfiche.Forms.Routing.ServiceTask.Execute(Int32 instanceId, IRoutingContext routingContext)

I imagine I probably have the Timer/Email event configured incorrectly, but all my attempts at reconfiguration have failed. It's worth noting that I _do_ receive an email reminder, but only at the end of the process, once it's completed.

All help appreciated!

Thank you,

Rob

0 0

SELECTED ANSWER

replied on May 15, 2017

The timer seems to just be sitting there without a direction of where to go if the form is not submitted within time. You can write the email message within the process itself and use the Timer to re-route to itself if it's not submitted (see screenshot). Or if you want to keep it the way you have it, then simply drag the arrow from the Timer to the reminder email task and then from the email task back to the Employee Signature.

Right now it seems that you are simply sending the employee from the Employee Signature stage, to the Email Reminder and then Terminate.

So, try removing the "Employee Signature Deadline Reminder" task and adding the email message right into the "Employee Signature" task. Then use the Timer arrow to re-route to itself each minute. Remove the "Employee Signature Acquired" terminate event too.

Also, isn't the time between reminders too close? A person stepping out for 15 minutes will come back to 15 email reminders.

timer.png (6.67 KB)

| Download

1 0

replied on May 15, 2017

Hi Raul,

Thanks for the reply--that was indeed the answer!

The short (minute long) duration between reminders was for testing purposes only--I didn't want to have to wait very long before initiating another run.

Interesting note: that 1 minute duration between reminders does seem to be too short to ensure that the emails go out. Before I switched the duration to 10 minutes, I would not receive a single reminder email until the process completed, at which point I'd receive 1 reminder email (regardless of how many reminder cycles transpired during the test). After setting the duration to 10 minutes, I received the reminders as expected.

Thank you,

Rob

1 0

replied on May 15, 2017

I should have figured out that the time duration was for testing purposes.

Hey, thanks for sharing your findings on the emails not being sent when set to 1 minute. Now I know not to use that setting, even when testing.

Glad you made it work.

Thanks,

Raul

1 0

Question

Question

Forms [LFF380-ValidateNoStep] Error

Answer

Replies

Sign in to reply to this post.