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

Question

Question

Forms Team Javascript filter no longer working with Forms 11 update 5

asked on February 23, 2024

We updated to Forms 11 update 5 on 2/21/24 and we have a Team javascript filter that errors out with the following error:

Filter returned a script error: Cannot read property 'toLowerCase' of null [LFF6010-FilterReturnedScriptError]

Details:
URL: 
Error: FilterReturnedScriptError
Date: 2/22/2024 4:11:50 PM (Mountain Standard Time)
HTTP Status Code: 500
Business Process ID: 4
Instance ID: 76793
Business Process Name: Medicaid Appeal Workflow

Other:
TeamFilter: 6

Stack Trace:
Caught exception: Laserfiche.Forms.CommonUtils.Exceptions.LFFormsException
Message: Filter returned a script error: Cannot read property 'toLowerCase' of null [LFF6010-FilterReturnedScriptError]
   at Laserfiche.Forms.CommonUtils.RuleExecutionService.ExecuteTeamScriptFilter(IEntityContext appContext, team team, business_rule rule, cf_bp_main_instances mainInstance, cf_bp_processes process, XmlDocument routingXml, String& TestValue)
   at Laserfiche.Forms.Routing.UserTask.ResolveAndAssignTeamMemberToTask(cf_bp_worker_instnc_to_resume wr, IRoutingContext routingContext)

Here is the filter that has been working for years:

 

So testing the script with a blank value for 'Appeals_Coordinator' should return all team members which it does.  But when the script runs in the business process, the instance suspends with the error.  

I don't know where the property 'toLowerCase' is coming from or if the script is now evaluating the blank variable as NULL.

 

0 0

Answer

SELECTED ANSWER
replied on February 26, 2024

It should work for instances newly created or updated (like user task approved) after applying the hotfix.

For the running instances, please restart the user task, or run the following sql script to fix the data before retry:

delete from main_instance_extended_data where bp_instance_id = {your_instance_id}

 

2 0

Replies

replied on February 23, 2024

I wonder if this is the same issue that was reported on this post.  If so, @████████stated that a hotfix was being worked on.

0 0
replied on February 25, 2024

It should be same issue.

The individual hotfix has been provided to support so you may need to contact support for the fix.

And we are considering providing a public KB for it.

0 0
replied on February 26, 2024

We got and applied the hotfix and it did not fix the issue

 

0 0
SELECTED ANSWER
replied on February 26, 2024

It should work for instances newly created or updated (like user task approved) after applying the hotfix.

For the running instances, please restart the user task, or run the following sql script to fix the data before retry:

delete from main_instance_extended_data where bp_instance_id = {your_instance_id}

 

2 0
replied on November 10, 2024

Hi, we have fixed this issue on Forms 12 (Bug 510207).

You can see other changes from: Laserfiche 12 Changelog

Get Laserfiche Forms 12 package from: Laserfiche 12 - Downloads

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

Sign in to reply to this post.