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

Question

Question

Unable to delete pages from specific area of repository after upgrade

asked on March 18, 2019

Hello, we upgraded from 10.3 to 10.4 Forms and Repository. Prior to the upgrade our users were able to delete pages from documents in their area of the repository. After the upgrade they are no longer able to do so. When they try to delete the entry refreshes like it is going to delete but nothing happens. When we (admins) try to delete we get an error "This document has changed on the server, and must be reloaded before it may be modified. Do you wish to get latest version now?". We select Yes, document refreshes, we attempt to delete the page again and get the same message.

 

We've verified all users have the correct access rights to this area of the repository. Any new folders/documents created in this area of the repository have the same issue so it's not limited to existing entries prior to update. We can copy the entry to another area of the repository and delete pages with no issues and then copy back to their original location.

 

We've also rebooted the repository/db server and rebuilt the db indexes.

 

Has anyone else bumped into this issue before or have any ideas?

0 0

Replies

replied on June 4, 2019

Have you had any response on this?  We just upgraded to 10.4 over the weekend and are experiencing the same thing.

0 0
replied on June 10, 2019

Hi @████████, yes we were able to resolve this with advice from our VAR. (I don't know why this worked in 10.3 but broke in 10.4) What happened was we had multiple workflow starting rules being evaluated as true (figured out which ones by using the Subscriber) and kicking off workflows so the entry would get temporarily locked while one workflow was running and so wouldn't let us delete pages while locked. We adjusted our starting rules for the appropriate workflows to ONLY evaluate true if Entry Changes include Template Assigned, Template Field Deleted, or Template Field Set.

0 0
replied on June 18, 2019

Hi Cassandra, just thought I would share that we did do the update to 10.4.1 which did resolve this issue for us without changing any starting rules. 

1 0
replied on June 18, 2019

I will test it again once we update to 10.4.1 - Thank you!!

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

Sign in to reply to this post.