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

Question

Question

Suspend Save to Laserfiche Tasks after upgrading from Ver 9.2 to 10.2

Forms Version 10
Updated July 12, 2017
asked on July 10, 2017 • Show version history

We have upgraded Forms in our TEST system and have numerous suspended tasks ... all with the Save to Laserfiche task. Anyone have any insight as to why these forms would work perfectly in Ver. 9.2 but fail in Ver. 10.2?

UPDATE: By process of elimination, I have figured out the following:

Where I am saving the form using the initiator's displayname:

If I change it to the initiator's email:

it now works. I am going through and changing all my forms, but can this be explained?

0 0

Answer

SELECTED ANSWER
replied on July 11, 2017

According to the error "Bad field value ('Created by'): The parameter is out of range or too long. [9020]", it seems your initiator display name was too long for this "Created by" field. Can you check the width of the field "Created by" and the length of the initiator display name?

0 0

Replies

replied on July 10, 2017

Hi Gloria,

Can you check the instance error for the suspended instance and post it here? {/dataset/_initiator_displayname} works in my environment.

0 0
View 1 previous reply
replied on July 11, 2017

Error 7/10/2017 4:10:41 PM

An unexpected error has occurred. [LFF502-UnexpectedError]

 

Details:

URL:

Error: UnexpectedError

Date: 7/10/2017 4:10:41 PM (Eastern Standard Time)

HTTP Status Code: 500

Business Process ID: 183

Instance ID: 1189

Business Process Name: Reserve a Document Number

 

Other:

Bad field value ('Document Date'): Another operation on which this operation depends failed. [9054]

Bad field value ('Originator'): Another operation on which this operation depends failed. [9054]

Bad field value ('Subject'): Another operation on which this operation depends failed. [9054]

Bad field value ('Certificate #'): Another operation on which this operation depends failed. [9054]

Bad field value ('Project/Charge #'): Another operation on which this operation depends failed. [9054]

Bad field value ('Receiver'): Another operation on which this operation depends failed. [9054]

Bad field value ('Created by'): The parameter is out of range or too long. [9020]

 

Stack Trace:

Caught exception: Laserfiche.Forms.CommonUtils.Exceptions.LFFormsException

Message: An unexpected error has occurred. [LFF502-UnexpectedError]

   at Laserfiche.Forms.Routing.SaveToLaserficheService.Execute(Int32 instanceId, IRoutingContext routingContext, RoutingInstanceStatus OriginalStatus)

   at Laserfiche.Forms.Routing.ServiceTask.Execute(Int32 instanceId, IRoutingContext routingContext)

 

Inner exception: Laserfiche.RepositoryAccess.MultiStatusException

Message: Multistatus response. [9039]

The parameter is out of range or too long. [9020]

Another operation on which this operation depends failed. [9054]

Another operation on which this operation depends failed. [9054]

Another operation on which this operation depends failed. [9054]

Another operation on which this operation depends failed. [9054]

Another operation on which this operation depends failed. [9054]

Another operation on which this operation depends failed. [9054]

The parameter is out of range or too long. [9020]

   at Laserfiche.RepositoryAccess.EntryInfo.Save()

   at Laserfiche.Forms.CommonUtils.LFHelper.SetValueToTemplateField(EntryInfo lfDoc, String template, FieldValueCollection fvs)

0 0
SELECTED ANSWER
replied on July 11, 2017

According to the error "Bad field value ('Created by'): The parameter is out of range or too long. [9020]", it seems your initiator display name was too long for this "Created by" field. Can you check the width of the field "Created by" and the length of the initiator display name?

0 0
replied on July 12, 2017 • Show version history

I bumped it from 25 to 35. That appears to have fixed it. Funny that Ver. 9 didn't care as much as Ver. 10 does. UPDATE: Figured out why!

This is how my Display Name has shown in Outlook since November 2016:

I processed two records today ... one in the test system (Forms Ver. 10) and one in production (Forms Ver. 9). Turns out, the "display name" grabbed from Ver. 10 vs. Ver. 9 is different!

So, now I have to accommodate the number of characters in this field to support the extraneous info being brought in.

0 0
replied on July 12, 2017 • Show version history

Actually that's a known and expected change. Before Forms 10.0, Forms uses Name attribute in AD for display name for Windows user; since 10.0, we changed to use Display Name attribute to be consistent with LFDS and Workflow.

Sorry for the inconvenience. 

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

Sign in to reply to this post.

Details
Related Posts
Loading ...