Chaining does not always work
I have an initial action that chains to another action. Sometimes it works and sometimes it doesn't. The error in the error log just says "Failed to chain action:" and then gives the action name. It's just weird that sometimes it opens the next form and sometimes not, with the same data entered on the first form.
On the form load of the action it's chaining to, there are some server side scripts that are being called. I need these there to update some data in the SQL tables.
Has anyone else had this issue? Does anyone know how to fix it?
Thanks.
Bette
Comments
-
This tends to happen when the engine is unable to update the alert list before the next action is called. As the user has no alert in the list the action fails. I have experienced this quite a bit on development/demo environments where all Metastorm components are installed on the same machine and the browser too is run from this machine. I have only rarely seen this in test and production systems when there tends to be a little more latency in the system.
0 -
If the roles for the chained action are based on the To Do or Watch list, this can easily happen, tes. The workaround is to use roles based on Folder data, or Static Roles. We have a 'hidden action' role in > our library < that allows any user (in fact the current user) to perfoirm an action. If no other roles are selected, the action is 'hidden'. We find this useful for chained loopback actions where we do not want all optiona available, or admin forms we only want to use from a button.
We have also found that if you add it to any Chained Action, these problems will tend to go away.
0 -
Thanks for getting back to me.
We have our development server set up the same as we have the production server. That is the engine and web server together and the DB on another server. So I doubt my chaining will work any better in production.
I see that Jerome posted something so I think I will see what he has to say.
Thanks again.
0 -
I did have the roles at the chained actions set to TO-DO list so I changed these to be the same static roles that are on the stages. I only had time to do a couple of tests to make sure the chaining still worked and it does. We will do more testing just to make sure this fixes the problem for us.
Thanks very much for your suggestion. It sounds like the solution to me.
0
Categories
- All Categories
- 123 Developer Announcements
- 54 Articles
- 155 General Questions
- 149 Thrust Services
- 57 Developer Hackathon
- 37 Thrust Studio
- 20.6K Analytics
- 4.2K AppWorks
- 9K Extended ECM
- 918 Core Messaging
- 84 Digital Asset Management
- 9.4K Documentum
- 33 eDOCS
- 190 Exstream
- 39.8K TeamSite
- 1.7K Web Experience Management
- 10 XM Fax
- Follow Categories