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

Discussion

Posted to Empower Conference

Discussion

Empower Conference

Empower 2015 - What have you applied already?

Ideas
Updated February 3, 2015
posted on January 20, 2015

Hello everyone!  Most of us are probably already home and back to work, so let's talk application of what we have learned...

 

What did you learn from Empower that you have already applied to your Laserfiche life?

 

Is there something particularly exciting you discovered that you have not yet used, but can't wait to get started?

 

For me, I learned a lot this year about Form - and since we just upgraded to Rio I can't wait to get started!

2 0
replied on January 23, 2015

I gained a better understanding of how to approach updating and testing existing workflows, and so am now in the process of successfully making some changes without worrying that I might break something else.  I also corrected a big misunderstanding I had about how cutoff works in Records Management, a feature I'm planning to use in my next project. 

3 0
replied on January 31, 2015

Barry - Workflow is a powerful tool.  As long as you give it some limits you can play all day without causing mass destruction!  : )

 

Of course, be sure your starting rules or the advanced server configuration exclude the user in the connection profile, or you may look down to see your server cooking away at 80% CPU for no apparent reason. 

1 0
replied on January 21, 2015

I happen to wander into an "Optimizing Workflow" class held by Ed Heaney.

He had several suggestions to make Workflow more robust. I could not wait to increase the number of threads that Workflow handles simultaneously. If you have not done this yet, your Workflow server is only functioning at half or 1/3 capacity!

Here is where it is:

Workflow Admin Console -> Server Configuration ->Rt Click: Adv Server options -> Properties -> Monitored Repositories tab -> Increase "Starting Rule Threads" to a 2 or a 3.

This increases the throughput of Workflow. I couldn't wait to get back to change this setting!

 

2 0
View 1 previous reply
replied on January 31, 2015

Chris - I just applied this to our installation as well.  :)

 

Thjanks for the tip!

 

I was in there excluding my workflow user.  I'm not to proud to say I had created a runaway workflow by not excluding the actions of the workflow user.  AGain.  :)

 

1 0
replied on February 2, 2015

Ooof. Been there. One terrible, terrible thing I did once was create a Workflow that was deleting entries based on entry ID. I ended up deleting some innocent bystanders during beta testing angry but learned a valuable lesson: avoid Workflows that make decisions based on entry ID's!!!

0 0
replied on February 2, 2015

In this case, the workflow was moving entries to their proper locations.  The problem was that starting rules applied to moves as well, and didn't exclude the workflow user.

 

So the documents were being moved over and over again to the same location.

 

Non destructive, but the cpu cores all went up to 80%.  I'm glad I noticed it.

 

You can set up the starting rules for "user != workflowuser" and/or there is a setting in the advanced server options for "User Exclusion Filter."  Or both.  :)  Can't be too careful.

 

I got the User Exclusion Filter from one of Empower14's Advanced Workflow classes.

 

(In this case, I had been trying to fix another issue and had set up a Windows account for my workflow user temporarily.  Oops.)

0 0
replied on February 3, 2015

That is a good one! I have a case where I actually need the workflow user to trigger other workflows. That rule would be good if you had to delegate Worklfow privileges to a new user that was just 'learning the ropes'. Thanks Michael!

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

Sign in to reply to this post.

Details
Related Posts
Loading ...