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

Question

Question

cannot copy subprocess with timer or catch event in 10.3.1.690

asked on April 26, 2019
  1. Happens in Chrome, Firefox and IE.
  2. This issue occurs on all processes both in production and development. In other words everyone here has the same issue and is system wide. It can easily and quickly be reproduced.
  3. The issue occurs in newly created processes as well as previously existing.
  4. Within the subprocess, if there are any timers or catch events the process will not fully copy.
  5. What I mean above by ‘not fully copy’:
    1. The icon appears but the subprocess name does not appear on the bottom list or the list on the left:
    2. You cannot delete the icon

 

Thanks

0 0

Answer

SELECTED ANSWER
replied on April 29, 2019

Investigated the issue [169071]. This was a regression issue that was introduced in 10.3.1 and fixed already in 10.4. The issue we found was that if you had a boundary event in a sub-process, that sub-process could not be successfully copied. Specifically, if you had a timer or signal boundary event inside the sub-process that had an outflow, the copy wouldn't work. We couldn't reproduce the issue with a normal timer catch event, just boundary events with an outflow. 

The issue is already fixed in 10.4, so an upgrade would solve the problem.

As a workaround in your current version, you can try to delete the outflow from the boundary event and then copy the sub-process. That copy worked successfully for us, and then remember to add the outflow back to both the original sub-process and the copied one. 

1 0
replied on April 30, 2019 Show version history

Ok. That is about what we came up with too. I guess I am the lucky one to be the first to first post about this.

I needed to confirm that an upgrade was necessary since it involves multiple public sector employees working from home over a weekend and a few months of running 10.4 in our development environment.

Thanks for taking the time out to investigate and for confirming, sir!

0 0

Replies

replied on April 27, 2019

Thanks for the detailed info Chris, we'll take a look. I'll follow up with questions if we have them after investigating. 

1 0
replied on April 29, 2019

Update: our VAR could also reproduce on their 10.3.1 system.

Thank you Jared :)

1 0
replied on April 29, 2019

We didn't get a chance to test this yesterday, but we'll investigate and file a bug for the issue. We will try to make a fix available as soon as possible. 

1 0
replied on May 15, 2019 Show version history

Here is another indication that your process is malfunctioning. If you suddenly show a subprocess with the end of an arrow just floating, then you are in trouble:

From what I can tell, this is an arrow that points back to itself and you can't edit it. It DOES show in the step as a path:

I tried putting some ridiculous logic in there so the process would not go down that path, but it had no effect. When I sent the form through this subprocess, it essentially split my path and froze the form:

It doesn't throw an error. I am going to assume my instructions are to upgrade to 10.4 which is not an option for quite a while. I am going to attempt to recreate the subprocess. 

Hope this keeps someone from going crazy one day. Total bummer.

0 0
replied on May 15, 2019

Unfortunately you are correct. The arrow issue is actually a different issue that we fixed in 10.4. If you find a stable way to reproduce it, please let us know. In 10.4 we added the ability to delete that arrow and included it as an error when you validate your process. 

https://answers.laserfiche.com/questions/143550/Feature-Request--Prevent-Form-Task-Connecting-to-Itself

0 0
replied on May 16, 2019

Thanks Jared. I spent some time trying to reproduce it but could not. I'll keep an eye out for it from here on though.

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

Sign in to reply to this post.