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

Question

Question

assign field data activity not removing unassigned fields when assigning a template

Workflow
Updated January 12, 2015
asked on December 10, 2014

So we use a preprocessing template in a process where quick fields will take documents, and capture metadata that is required. The preprocessing template has some process aspects included, like a field Quick Fields uses for picking up ready documents. We do not need this field though when the processing is over. I actually use quick fields to assign fields but not the template, and then a workflow assigns the template. because it needs even more information based on database lookups. 

When workflow assigns a new template and I tell it to remove fields that are not in the new template, it still leaves the old fields in at the bottom. Am I doing something wrong?

0 0

Answer

APPROVED ANSWER SELECTED ANSWER
replied on January 12, 2015

This issue is resolved. The problem was that the Workflow user didn't have delete rights to some of the fields in the original template. That's why when Workflow assigned the new template and tried to drop the fields from the unassigned template, some fields remained on the document as independent fields. Once the field rights were corrected, Workflow was able to drop the fields from the unassigned template properly.

1 0

Replies

replied on December 10, 2014

What version of Workflow are you using?

0 0
replied on December 10, 2014

can you lend any information based on the version number i provided? Is this a known bug?

0 0
replied on December 10, 2014

9.1.1.365

Is this a known issue?

0 0
View 3 previous replies
replied on December 10, 2014

Yes, it is a known issue for 9.1.1.365 and has been patched. See KB 1013512 for the latest hotfix for Workflow 9.1.1.

As far as why the version is relevant, for issues reported through Answers, we can get you an answer faster if we can start with checking the appropriate hotfix list first, then if not found there, we can narrow it down based on the known issues for that version. If a workaround needs to be provided, the version may make a difference in the tools and features available.

1 0
replied on January 9, 2015 • Show version history

I am still having this issue with Workflow Designer 9.1.1.395

I have tried republishing my workflows and even remaking the Assign field values activity and it has not helped. 

0 0
replied on January 9, 2015

Is the Workflow Server installed on a different computer than the one that you're using the Designer from? When you applied the Workflow hotfix, did you only run it on the Workflow Designer computer? Please make sure that you've applied the hotfix on all servers that have Workflow 9.1.1 components (Server, Subscriber, Designer, etc.)

If that's been confirmed and this issue is still occurring, please open a case with Laserfiche Support and provide a copy of your workflow definition.

0 0
replied on January 9, 2015

Workflow designer and Workflow server are on the same machine. I have confirmed this is the case. I shall open a case shortly.

Should I add this question into the opening of the case to get us to the same page?

 

0 0
replied on January 9, 2015

Yes, please mention this Answers thread when you open a case. In addition to the workflow, please also provide a briefcase of sample documents along with the old and new templates.

0 0
APPROVED ANSWER SELECTED ANSWER
replied on January 12, 2015

This issue is resolved. The problem was that the Workflow user didn't have delete rights to some of the fields in the original template. That's why when Workflow assigned the new template and tried to drop the fields from the unassigned template, some fields remained on the document as independent fields. Once the field rights were corrected, Workflow was able to drop the fields from the unassigned template properly.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...