This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
Hi experts,
We are having issue with our Comms Template for PR being used for WFASSIGNMENT. The TO field is meant to be blank and picks up person's email address based on the workflow groups. However, for unknown reason the said Communications Template seems like being updated on the fly. It has now value on the TO field. I've deleted the list of users listed in the TO field from front-end (Recipients tab of the Comms Template application), but after several hours it has updated itself again. Now all PR email notifications are being received by the users listed on the TO field of the comms template. No recent change for our PR workflow, comms, escalations that could lead to this. Anyone encountered same issue? We're on 7116. Thanks heaps
Best regards,
Janice
I have encountered that one before it's a bug. In my case, I had a wait node before it
for some reason that seemed to set it off. I had to re-write workflow to get rid of it. That was 7.1.1.6 as well.
I did open a ticket, so Support should have something in the system.
Shannon Rotz
--- In MAXIMO@yahoogroups.com, "janice c" <carrillo_janice@...> wrote:
>
> Hi experts,
>
> We are having issue with our Comms Template for PR being used for WFASSIGNMENT. The TO field is meant to be blank and picks up person's email address based on the workflow groups. However, for unknown reason the said Communications Template seems like being updated on the fly. It has now value on the TO field. I've deleted the list of users listed in the TO field from front-end (Recipients tab of the Comms Template application), but after several hours it has updated itself again. Now all PR email notifications are being received by the users listed on the TO field of the comms template. No recent change for our PR workflow, comms, escalations that could lead to this. Anyone encountered same issue? We're on 7116. Thanks heaps
>
>
> Best regards,
> Janice
>
Thanks Shannon!
I've done further test on this issue and confirmed that the comms template being updated on the fly when reassigning a record in WF Admin is no longer an issue - http://www-01.ibm.com/support/docview.wss?uid=swg1IZ62752. I reckon having a value in the TO field of the comms template is not the real issue. The issue now is that it takes a while before it clears the TO field of the comms template, some sort of process being stucked or overlapping process.
I've replicated the issue by reassigning a record from the WORKFLOW ADMINISTRATION application. My test confirms that the TO field of the comms template gets populated every time a record enters the node of the workflow that uses the said comms template. In the Comms Template application (I have two Maximo opened to quickly switch to COMMS TEMPLATE and WF ADMIN applications), system insert a value to the TO field of the comms template so it could send the notification then clears the said field as well after the process. However, it seems like there are some transactions that overlap each other. One transaction isn't finished yet then it will process another transaction and insert the USERNAMES in the TO field of the comms template to send the notification. With this, user will receive notification for a record that is not assigned to him. Our temporarily solution is to delete the list of users from the RECIPIENTS tab of the COMMUNICATION TEMPLATES application. Not sure if it's a bug or we just need to review the Escalation related to the workflow? We are using AUTOACCEPT in the workflow. I've raised a ticket to IBM already.
Best regards,
Janice
--- In MAXIMO@yahoogroups.com, "shannonrotz" <shannonrotz@...> wrote:
>
> I have encountered that one before it's a bug. In my case, I had a wait node before it
for some reason that seemed to set it off. I had to re-write workflow to get rid of it. That was 7.1.1.6 as well.
>
> I did open a ticket, so Support should have something in the system.
>
>
>
> Shannon Rotz
>
> --- In MAXIMO@yahoogroups.com, "janice c" <carrillo_janice@> wrote:
> >
> > Hi experts,
> >
> > We are having issue with our Comms Template for PR being used for WFASSIGNMENT. The TO field is meant to be blank and picks up person's email address based on the workflow groups. However, for unknown reason the said Communications Template seems like being updated on the fly. It has now value on the TO field. I've deleted the list of users listed in the TO field from front-end (Recipients tab of the Comms Template application), but after several hours it has updated itself again. Now all PR email notifications are being received by the users listed on the TO field of the comms template. No recent change for our PR workflow, comms, escalations that could lead to this. Anyone encountered same issue? We're on 7116. Thanks heaps
> >
> >
> > Best regards,
> > Janice
> >
>
We've encountered another bug relative to Comm Templates and Workflow in v7.1.1.6. Upon reassigning a specific workflow assignment from the Workflow Admin application, the "reassignee" also gets added to the Comm Template TO field. This is a real problem for us because that Comm Template is used for all workflow assignments. So, after I reassign a workflow I have to go to the Comm Template and remove that person from the TO field.
Bill Murphy
--- In MAXIMO@yahoogroups.com, "shannonrotz" <shannonrotz@...> wrote:
>
> I have encountered that one before it's a bug. In my case, I had a wait node before it
for some reason that seemed to set it off. I had to re-write workflow to get rid of it. That was 7.1.1.6 as well.
>
> I did open a ticket, so Support should have something in the system.
>
>
>
> Shannon Rotz
>
> --- In MAXIMO@yahoogroups.com, "janice c" <carrillo_janice@> wrote:
> >
> > Hi experts,
> >
> > We are having issue with our Comms Template for PR being used for WFASSIGNMENT. The TO field is meant to be blank and picks up person's email address based on the workflow groups. However, for unknown reason the said Communications Template seems like being updated on the fly. It has now value on the TO field. I've deleted the list of users listed in the TO field from front-end (Recipients tab of the Comms Template application), but after several hours it has updated itself again. Now all PR email notifications are being received by the users listed on the TO field of the comms template. No recent change for our PR workflow, comms, escalations that could lead to this. Anyone encountered same issue? We're on 7116. Thanks heaps
> >
> >
> > Best regards,
> > Janice
> >
>
Hi Bill,
Did you raise a PMR to IBM? That is exactly what we are experiencing at the momment. First, we thougt that the template was corrupted. But after conducting further test (see my previous post for more details), it seems like it is a bug - sort of some transactions overlap another transaction.
Thank you.
Best regards,
Janice
--- In MAXIMO@yahoogroups.com, "Bill" <bill.e.murphy@...> wrote:
>
> We've encountered another bug relative to Comm Templates and Workflow in v7.1.1.6. Upon reassigning a specific workflow assignment from the Workflow Admin application, the "reassignee" also gets added to the Comm Template TO field. This is a real problem for us because that Comm Template is used for all workflow assignments. So, after I reassign a workflow I have to go to the Comm Template and remove that person from the TO field.
>
> Bill Murphy
>
> --- In MAXIMO@yahoogroups.com, "shannonrotz" <shannonrotz@> wrote:
> >
> > I have encountered that one before it's a bug. In my case, I had a wait node before it
for some reason that seemed to set it off. I had to re-write workflow to get rid of it. That was 7.1.1.6 as well.
> >
> > I did open a ticket, so Support should have something in the system.
> >
> >
> >
> > Shannon Rotz
> >
> > --- In MAXIMO@yahoogroups.com, "janice c" <carrillo_janice@> wrote:
> > >
> > > Hi experts,
> > >
> > > We are having issue with our Comms Template for PR being used for WFASSIGNMENT. The TO field is meant to be blank and picks up person's email address based on the workflow groups. However, for unknown reason the said Communications Template seems like being updated on the fly. It has now value on the TO field. I've deleted the list of users listed in the TO field from front-end (Recipients tab of the Comms Template application), but after several hours it has updated itself again. Now all PR email notifications are being received by the users listed on the TO field of the comms template. No recent change for our PR workflow, comms, escalations that could lead to this. Anyone encountered same issue? We're on 7116. Thanks heaps
> > >
> > >
> > > Best regards,
> > > Janice
> > >
> >
>
Yes, that sounds like a related problem - and I might have had that as well
sometimes (it sounds familiar). It's definitely a bug .
Shannon Rotz
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of
Bill
Sent: October-10-12 11:05 AM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Re: WF Comms Template update itself
We've encountered another bug relative to Comm Templates and Workflow in
v7.1.1.6. Upon reassigning a specific workflow assignment from the Workflow
Admin application, the "reassignee" also gets added to the Comm Template TO
field. This is a real problem for us because that Comm Template is used for
all workflow assignments. So, after I reassign a workflow I have to go to
the Comm Template and remove that person from the TO field.
Bill Murphy
--- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> ,
"shannonrotz" <shannonrotz@...> wrote:
>
> I have encountered that one before - it's a bug. In my case, I had a wait
node before it . for some reason that seemed to set it off. I had to
re-write workflow to get rid of it. That was 7.1.1.6 as well.
>
> I did open a ticket, so Support should have something in the system.
>
>
>
> Shannon Rotz
>
> --- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> , "janice
c" <carrillo_janice@> wrote:
> >
> > Hi experts,
> >
> > We are having issue with our Comms Template for PR being used for
WFASSIGNMENT. The TO field is meant to be blank and picks up person's email
address based on the workflow groups. However, for unknown reason the said
Communications Template seems like being updated on the fly. It has now
value on the TO field. I've deleted the list of users listed in the TO field
from front-end (Recipients tab of the Comms Template application), but after
several hours it has updated itself again. Now all PR email notifications
are being received by the users listed on the TO field of the comms
template. No recent change for our PR workflow, comms, escalations that
could lead to this. Anyone encountered same issue? We're on 7116. Thanks
heaps
> >
> >
> > Best regards,
> > Janice
> >
>
This was a bug in my view. Over time, it accumulated more and more
"additional" recipients, until the list got quite long. I believe they
fixed it in 7.1.1.6, but I honestly don't remember now.
Shannon Rotz
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of
janice c
Sent: October-09-12 11:44 PM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Re: WF Comms Template update itself
Thanks Shannon!
I've done further test on this issue and confirmed that the comms template
being updated on the fly when reassigning a record in WF Admin is no longer
an issue - http://www-01.ibm.com/support/docview.wss?uid=swg1IZ62752. I
reckon having a value in the TO field of the comms template is not the real
issue. The issue now is that it takes a while before it clears the TO field
of the comms template, some sort of process being stucked or overlapping
process.
I've replicated the issue by reassigning a record from the WORKFLOW
ADMINISTRATION application. My test confirms that the TO field of the comms
template gets populated every time a record enters the node of the workflow
that uses the said comms template. In the Comms Template application (I have
two Maximo opened to quickly switch to COMMS TEMPLATE and WF ADMIN
applications), system insert a value to the TO field of the comms template
so it could send the notification then clears the said field as well after
the process. However, it seems like there are some transactions that overlap
each other. One transaction isn't finished yet then it will process another
transaction and insert the USERNAMES in the TO field of the comms template
to send the notification. With this, user will receive notification for a
record that is not assigned to him. Our temporarily solution is to delete
the list of users from the RECIPIENTS tab of the COMMUNICATION TEMPLATES
application. Not sure if it's a bug or we just need to review the Escalation
related to the workflow? We are using AUTOACCEPT in the workflow. I've
raised a ticket to IBM already.
Best regards,
Janice
--- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> ,
"shannonrotz" <shannonrotz@...> wrote:
>
> I have encountered that one before - it's a bug. In my case, I had a wait
node before it . for some reason that seemed to set it off. I had to
re-write workflow to get rid of it. That was 7.1.1.6 as well.
>
> I did open a ticket, so Support should have something in the system.
>
>
>
> Shannon Rotz
>
> --- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> , "janice
c" <carrillo_janice@> wrote:
> >
> > Hi experts,
> >
> > We are having issue with our Comms Template for PR being used for
WFASSIGNMENT. The TO field is meant to be blank and picks up person's email
address based on the workflow groups. However, for unknown reason the said
Communications Template seems like being updated on the fly. It has now
value on the TO field. I've deleted the list of users listed in the TO field
from front-end (Recipients tab of the Comms Template application), but after
several hours it has updated itself again. Now all PR email notifications
are being received by the users listed on the TO field of the comms
template. No recent change for our PR workflow, comms, escalations that
could lead to this. Anyone encountered same issue? We're on 7116. Thanks
heaps
> >
> >
> > Best regards,
> > Janice
> >
>
Yes, we raised it. Reference this APAR - APAR/Defect IZ77693/ 10-15350 WF ADMIN SAYS YOU CAN'T REASSIGN TO A USER WITHOUT A VALID EMAIL AND THEN ADDS THEM TO THE ASSIGNEE LIST ANYWAY
The description seems a little off but it's the same issue. I understand that it's corrected in 7.1.1.8.
We're planning on installing a workaround that our crack IS group developed soon.
Bill Murphy
7.1.1.6
--- In MAXIMO@yahoogroups.com, "janice c" <carrillo_janice@...> wrote:
>
> Hi Bill,
>
> Did you raise a PMR to IBM? That is exactly what we are experiencing at the momment. First, we thougt that the template was corrupted. But after conducting further test (see my previous post for more details), it seems like it is a bug - sort of some transactions overlap another transaction.
> Thank you.
>
>
> Best regards,
> Janice
>
> --- In MAXIMO@yahoogroups.com, "Bill" <bill.e.murphy@> wrote:
> >
> > We've encountered another bug relative to Comm Templates and Workflow in v7.1.1.6. Upon reassigning a specific workflow assignment from the Workflow Admin application, the "reassignee" also gets added to the Comm Template TO field. This is a real problem for us because that Comm Template is used for all workflow assignments. So, after I reassign a workflow I have to go to the Comm Template and remove that person from the TO field.
> >
> > Bill Murphy
> >
> > --- In MAXIMO@yahoogroups.com, "shannonrotz" <shannonrotz@> wrote:
> > >
> > > I have encountered that one before it's a bug. In my case, I had a wait node before it
for some reason that seemed to set it off. I had to re-write workflow to get rid of it. That was 7.1.1.6 as well.
> > >
> > > I did open a ticket, so Support should have something in the system.
> > >
> > >
> > >
> > > Shannon Rotz
> > >
> > > --- In MAXIMO@yahoogroups.com, "janice c" <carrillo_janice@> wrote:
> > > >
> > > > Hi experts,
> > > >
> > > > We are having issue with our Comms Template for PR being used for WFASSIGNMENT. The TO field is meant to be blank and picks up person's email address based on the workflow groups. However, for unknown reason the said Communications Template seems like being updated on the fly. It has now value on the TO field. I've deleted the list of users listed in the TO field from front-end (Recipients tab of the Comms Template application), but after several hours it has updated itself again. Now all PR email notifications are being received by the users listed on the TO field of the comms template. No recent change for our PR workflow, comms, escalations that could lead to this. Anyone encountered same issue? We're on 7116. Thanks heaps
> > > >
> > > >
> > > > Best regards,
> > > > Janice
> > > >
> > >
> >
>
Thanks Billy. I was able to do a test in a 7118 environment and it seems like it was fixed already. All the best!
Best regards,
Janice
--- In MAXIMO@yahoogroups.com, "Bill" <bill.e.murphy@...> wrote:
>
> Yes, we raised it. Reference this APAR - APAR/Defect IZ77693/ 10-15350 WF ADMIN SAYS YOU CAN'T REASSIGN TO A USER WITHOUT A VALID EMAIL AND THEN ADDS THEM TO THE ASSIGNEE LIST ANYWAY
>
> The description seems a little off but it's the same issue. I understand that it's corrected in 7.1.1.8.
>
> We're planning on installing a workaround that our crack IS group developed soon.
>
> Bill Murphy
> 7.1.1.6
>
>
> --- In MAXIMO@yahoogroups.com, "janice c" <carrillo_janice@> wrote:
> >
> > Hi Bill,
> >
> > Did you raise a PMR to IBM? That is exactly what we are experiencing at the momment. First, we thougt that the template was corrupted. But after conducting further test (see my previous post for more details), it seems like it is a bug - sort of some transactions overlap another transaction.
> > Thank you.
> >
> >
> > Best regards,
> > Janice
> >
> > --- In MAXIMO@yahoogroups.com, "Bill" <bill.e.murphy@> wrote:
> > >
> > > We've encountered another bug relative to Comm Templates and Workflow in v7.1.1.6. Upon reassigning a specific workflow assignment from the Workflow Admin application, the "reassignee" also gets added to the Comm Template TO field. This is a real problem for us because that Comm Template is used for all workflow assignments. So, after I reassign a workflow I have to go to the Comm Template and remove that person from the TO field.
> > >
> > > Bill Murphy
> > >
> > > --- In MAXIMO@yahoogroups.com, "shannonrotz" <shannonrotz@> wrote:
> > > >
> > > > I have encountered that one before it's a bug. In my case, I had a wait node before it
for some reason that seemed to set it off. I had to re-write workflow to get rid of it. That was 7.1.1.6 as well.
> > > >
> > > > I did open a ticket, so Support should have something in the system.
> > > >
> > > >
> > > >
> > > > Shannon Rotz
> > > >
> > > > --- In MAXIMO@yahoogroups.com, "janice c" <carrillo_janice@> wrote:
> > > > >
> > > > > Hi experts,
> > > > >
> > > > > We are having issue with our Comms Template for PR being used for WFASSIGNMENT. The TO field is meant to be blank and picks up person's email address based on the workflow groups. However, for unknown reason the said Communications Template seems like being updated on the fly. It has now value on the TO field. I've deleted the list of users listed in the TO field from front-end (Recipients tab of the Comms Template application), but after several hours it has updated itself again. Now all PR email notifications are being received by the users listed on the TO field of the comms template. No recent change for our PR workflow, comms, escalations that could lead to this. Anyone encountered same issue? We're on 7116. Thanks heaps
> > > > >
> > > > >
> > > > > Best regards,
> > > > > Janice
> > > > >
> > > >
> > >
> >
>
Thanks for the feedback, Janice. I'll update my tracker that we keep here for developing biz case to upgrade.
Bill Murphy
v7.1.1.6 / Cal v7.1
--- In MAXIMO@yahoogroups.com, "janice c" <carrillo_janice@...> wrote:
>
> Thanks Billy. I was able to do a test in a 7118 environment and it seems like it was fixed already. All the best!
>
>
> Best regards,
> Janice
>
> --- In MAXIMO@yahoogroups.com, "Bill" <bill.e.murphy@> wrote:
> >
> > Yes, we raised it. Reference this APAR - APAR/Defect IZ77693/ 10-15350 WF ADMIN SAYS YOU CAN'T REASSIGN TO A USER WITHOUT A VALID EMAIL AND THEN ADDS THEM TO THE ASSIGNEE LIST ANYWAY
> >
> > The description seems a little off but it's the same issue. I understand that it's corrected in 7.1.1.8.
> >
> > We're planning on installing a workaround that our crack IS group developed soon.
> >
> > Bill Murphy
> > 7.1.1.6
> >
> >
> > --- In MAXIMO@yahoogroups.com, "janice c" <carrillo_janice@> wrote:
> > >
> > > Hi Bill,
> > >
> > > Did you raise a PMR to IBM? That is exactly what we are experiencing at the momment. First, we thougt that the template was corrupted. But after conducting further test (see my previous post for more details), it seems like it is a bug - sort of some transactions overlap another transaction.
> > > Thank you.
> > >
> > >
> > > Best regards,
> > > Janice
> > >
> > > --- In MAXIMO@yahoogroups.com, "Bill" <bill.e.murphy@> wrote:
> > > >
> > > > We've encountered another bug relative to Comm Templates and Workflow in v7.1.1.6. Upon reassigning a specific workflow assignment from the Workflow Admin application, the "reassignee" also gets added to the Comm Template TO field. This is a real problem for us because that Comm Template is used for all workflow assignments. So, after I reassign a workflow I have to go to the Comm Template and remove that person from the TO field.
> > > >
> > > > Bill Murphy
> > > >
> > > > --- In MAXIMO@yahoogroups.com, "shannonrotz" <shannonrotz@> wrote:
> > > > >
> > > > > I have encountered that one before it's a bug. In my case, I had a wait node before it
for some reason that seemed to set it off. I had to re-write workflow to get rid of it. That was 7.1.1.6 as well.
> > > > >
> > > > > I did open a ticket, so Support should have something in the system.
> > > > >
> > > > >
> > > > >
> > > > > Shannon Rotz
> > > > >
> > > > > --- In MAXIMO@yahoogroups.com, "janice c" <carrillo_janice@> wrote:
> > > > > >
> > > > > > Hi experts,
> > > > > >
> > > > > > We are having issue with our Comms Template for PR being used for WFASSIGNMENT. The TO field is meant to be blank and picks up person's email address based on the workflow groups. However, for unknown reason the said Communications Template seems like being updated on the fly. It has now value on the TO field. I've deleted the list of users listed in the TO field from front-end (Recipients tab of the Comms Template application), but after several hours it has updated itself again. Now all PR email notifications are being received by the users listed on the TO field of the comms template. No recent change for our PR workflow, comms, escalations that could lead to this. Anyone encountered same issue? We're on 7116. Thanks heaps
> > > > > >
> > > > > >
> > > > > > Best regards,
> > > > > > Janice
> > > > > >
> > > > >
> > > >
> > >
> >
>