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

Question

Question

Field issue in Workflow and Admin. Console

asked on January 19, 2016

Hello,

Workflow Designer keeps returning this error when I validate the workflow

I understand this to be an issue before a field is created, however the field was created in Admin. Console before attempting to add it to a workflow.

The other curious issue I have, which I believe is connected to the above, is that in Admin. Console this particular field seems to be in a constant state on needing to be saved.

Below is a image of the field properties window:

Each time I click the ‘security’ button I get the 'save' prompt:

Even when there have been no changes.

Closing/saving/restarting has no impact, the issue persists.

0 0

Replies

replied on January 19, 2016

Hello Darren, 

 

The field in the Workflow Designer seems to be misspelled with a 'w' instead of an 'e' in acknowledgement.

Hope that helps!

1 0
replied on January 19, 2016 Show version history

Winston,

Good eye! I thought I'd caught that type-0 yesterday.  After fixing the mistake I republished and received this error,  "The field definition has changed since it's value was last edited.  The value specified may not be valid anymore." which is the one I was receiving in the beginning.

 

That field, which is one of 10 in that work flow with all the same properties/settings, appears 'stuck' in the 'save loop' mentioned above.  

0 0
replied on January 19, 2016

That's just a warning, so you can ignore it. It usually comes up if the field type changed too so the user double-checks that values are correct for the new field type.

0 0
replied on March 22, 2017

Miruna, I have the same problem after upgrade to 10.2 - the field values haven't changed at all and I verified that the value is correct. I keep running into this warring and it actually Completes my workflow without completing the tasks under it.

0 0
replied on March 22, 2017

I also have the same problem after the  upgrade to 10.2.

No field changes were made.

0 0
replied on May 3, 2017

Any solution to this issue?  Thanks

0 0
replied on May 4, 2017

This issue has been addressed in hotfix 1013837 for Workflow 10.2.

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

Sign in to reply to this post.