I'll have to remember this trick. What I usually do is have a status field
where one of the values is "Error". When the Error Handler filter fires it
sets the status to Error. All of the other worlflow has 'Status' != "Error"
in the Run If so it won't fire once the error has been handled.
The nice
Throw everything into a guide. When your error handler triggers, do your data
push and then jump to the label at the end of the guide and exit, bypassing all
the rest of the workflow in the guide. I use this setup all the time.
I have seen BMC code that also uses the go to execution order 1000,
Hi
Should not be an issue, but I would confirmed that upgrade from 7.1 to V9
is supported, you may go via v7.6.04.
The only option for Email Engine is if you want to run it in 32-bit mode or
not. Email Engine is installed default, same with flashboard.
-J BMC_JAVA_EMAIL_ENGINE_SELECTED_FOR_32BIT
Hi,
Ok, do you suggest that we should do it on Remedy data from 7.1 env.
Also how shall I install Email engine also with this install ?
What entry we should make for installing email engine ?
Thanks,
Vivek
On Tue, Jan 5, 2016 at 2:56 PM, Jarl Grøneng wrote:
> **
> Hei
>
> We did copy the datab
Hi,
So you want to log the error event in a form, and then continue to throw the
actual error?
After your error handler has caught the error, you can do a new Message Action
with the ERROR, ERRMSG and ERRAPPENDMSG keywords to get it to the end user.
The problem is getting the Push to commit to t
Hei
We did copy the database (this was a 7.6.04 installation) to a new
database-server, then did the installation/upgrade v901 on a new Linux
server.
In earlier versions of the installer you must specify
install/upgrade/server-group, but with v 9 (and maybe also v8) the
installer detects if ther
6 matches
Mail list logo
