Simple BPM Blank Title 124792

Yahoo Archive
1

Thanks for all the help, I ended up moving it to a post processing and it seems to be working fine.

 

Tyler Tisdale l IT Systems Administrator
ULTRAX Aerospace l 4200 NE Sun Court, Lee's Summit, MO 64064
t: 816-214-9999 l f: 816-214-9998 l e: ttisdale@...

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Miguel Santillan
Sent: Monday, September 23, 2013 11:50 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Simple BPM

 

 

Shouldnt the query in there be a NOT ProdCode?

From: vantage@yahoogroups.com [vantage@yahoogroups.com] on behalf of ultrax_tyler [ttisdale@...]
Sent: Friday, September 20, 2013 12:59 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Simple BPM

 

We have had a problem with people changing the default product group on a part when they create a new job. So I was trying to setup a warning when they go to save a job and the part group on the job is different from the part group on the part record. So I created a pre-processing bpm with the following code:

"for each ttjobhead , each Part where ttjobhead.PartNum=Part.PartNum and ttjobhead.ProdCode=Part.ProdCode no-lock"

So when they create a job and hit save, they are able to change the product code one time without it firing, if they try and save it a second time then the warning fires. Am I missing something simple causing them to be able to save the job the 1st time?

2
We have had a problem with people changing the default product group on a part when they create a new job. So I was trying to setup a warning when they go to save a job and the part group on the job is different from the part group on the part record. So I created a pre-processing bpm with the following code:

"for each ttjobhead , each Part where ttjobhead.PartNum=Part.PartNum and ttjobhead.ProdCode=Part.ProdCode no-lock"

So when they create a job and hit save, they are able to change the product code one time without it firing, if they try and save it a second time then the warning fires. Am I missing something simple causing them to be able to save the job the 1st time?
3
If you on are E9, many of the BO have both an update and masterupdate method that can be used to save the record, if JobEntry does you may need to put your BPM on both of these.

Jim Kinneman
Encompass Solutions, Inc.


--- In vantage@yahoogroups.com, <vantage@yahoogroups.com> wrote:

We have had a problem with people changing the default product group on a part when they create a new job. So I was trying to setup a warning when they go to save a job and the part group on the job is different from the part group on the part record. So I created a pre-processing bpm with the following code:

"for each ttjobhead , each Part where ttjobhead.PartNum=Part.PartNum and ttjobhead.ProdCode=Part.ProdCode no-lock"

So when they create a job and hit save, they are able to change the product code one time without it firing, if they try and save it a second time then the warning fires. Am I missing something simple causing them to be able to save the job the 1st time?
4
Shouldnt the query in there be a NOT ProdCode?
From: vantage@yahoogroups.com [vantage@yahoogroups.com] on behalf of ultrax_tyler [ttisdale@...]
Sent: Friday, September 20, 2013 12:59 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Simple BPM

 

We have had a problem with people changing the default product group on a part when they create a new job. So I was trying to setup a warning when they go to save a job and the part group on the job is different from the part group on the part record. So I created a pre-processing bpm with the following code:

"for each ttjobhead , each Part where ttjobhead.PartNum=Part.PartNum and ttjobhead.ProdCode=Part.ProdCode no-lock"

So when they create a job and hit save, they are able to change the product code one time without it firing, if they try and save it a second time then the warning fires. Am I missing something simple causing them to be able to save the job the 1st time?