Pre-Process or Post-Process for Part.Update BPM ? (V 8.03.409C)

Yahoo Archive
1
You can limit it on what form is calling update. This is how you could setup your condition to test if Part.Update is being called from Part Entry.


the ttCallContextClient.AssemblyName field is equal to the "Epicor.Mfg.UI.PartEntry" expression  Â





________________________________
From: c.krusen1 <ckrusen1@...>
To: vantage@yahoogroups.com
Sent: Friday, October 12, 2012 9:45 AM
Subject: [Vantage] Re: Pre-Process or Post-Process for Part.Update BPM ? (V 8.03.409C)

Thanks.

Now how do I keep other processes that that update the Part table from being constrained?

For example, say I create a SalesOrder.Update.Pre-Process directive to keep the line items from having a blank ProdGroup. New or changed order lines will be checked - which is what I want. But when a SalesOrder object (created before implementing this BPM) gets updated (like when a shipment is made against it), won't the BPM prevent the update of the shipping related fields?

Calvin

--- In vantage@yahoogroups.com, Jose Gomez <jose@...> wrote:
>
> Pre
>
> *Jose C Gomez*
> *Software Engineer*
> *
> *
> *
> *T: 904.469.1524 mobile
> E: jose@...
> http://www.josecgomez.com
>Â <http://www.linkedin.com/in/josecgomez> <http://www.facebook.com/josegomez>
>Â <http://www.google.com/profiles/jose.gomez> <http://www.twitter.com/joc85>
>Â <http://www.josecgomez.com/professional-resume/>
> <http://www.josecgomez.com/feed/>
>Â <http://www.usdoingstuff.com>
>
> *Quis custodiet ipsos custodes?*
>
>
>
> On Fri, Oct 12, 2012 at 9:09 AM, c.krusen1 <ckrusen1@...> wrote:
>
> > **
> >
> >
> > I need to make the ProdGroup manditory field when either creating a new
> > part, or updating an existing part.
> >
> > Should the "Raise an exception" action be done during Pre-Processing or
> > Post-Processing?
> >
> > Using Post-Processing seems to work. But isn't the Part table already
> > updated by the time the Post-Processing action takes place?
> >
> > And can I limit the action to only occur if the event occurs during while
> > in Part Maint? I don't want other system actions to get hung up if they
> > update a part record that doesn't have the ProdGroup field set.
> >
> >Â
> >
>
>
> [Non-text portions of this message have been removed]
>




------------------------------------

Useful links for the Yahoo!Groups Vantage Board are: ( Note:Â You must have already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder and Crystal Reports and other 'goodies', please goto: http://groups.yahoo.com/group/vantage/files/.%c2%a0
(2) To search through old msg's goto: http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto: http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links



[Non-text portions of this message have been removed]
2
I need to make the ProdGroup manditory field when either creating a new part, or updating an existing part.

Should the "Raise an exception" action be done during Pre-Processing or Post-Processing?

Using Post-Processing seems to work. But isn't the Part table already updated by the time the Post-Processing action takes place?

And can I limit the action to only occur if the event occurs during while in Part Maint? I don't want other system actions to get hung up if they update a part record that doesn't have the ProdGroup field set.
3
Pre

*Jose C Gomez*
*Software Engineer*
*
*
*
*T: 904.469.1524 mobile
E: jose@...
http://www.josecgomez.com
<http://www.linkedin.com/in/josecgomez> <http://www.facebook.com/josegomez>
<http://www.google.com/profiles/jose.gomez> <http://www.twitter.com/joc85>
<http://www.josecgomez.com/professional-resume/>
<http://www.josecgomez.com/feed/>
<http://www.usdoingstuff.com>

*Quis custodiet ipsos custodes?*



On Fri, Oct 12, 2012 at 9:09 AM, c.krusen1 <ckrusen1@...> wrote:

> **
>
>
> I need to make the ProdGroup manditory field when either creating a new
> part, or updating an existing part.
>
> Should the "Raise an exception" action be done during Pre-Processing or
> Post-Processing?
>
> Using Post-Processing seems to work. But isn't the Part table already
> updated by the time the Post-Processing action takes place?
>
> And can I limit the action to only occur if the event occurs during while
> in Part Maint? I don't want other system actions to get hung up if they
> update a part record that doesn't have the ProdGroup field set.
>
>
>


[Non-text portions of this message have been removed]
4
Thanks.

Now how do I keep other processes that that update the Part table from being constrained?

For example, say I create a SalesOrder.Update.Pre-Process directive to keep the line items from having a blank ProdGroup. New or changed order lines will be checked - which is what I want. But when a SalesOrder object (created before implementing this BPM) gets updated (like when a shipment is made against it), won't the BPM prevent the update of the shipping related fields?

Calvin

--- In vantage@yahoogroups.com, Jose Gomez <jose@...> wrote:
>
> Pre
>
> *Jose C Gomez*
> *Software Engineer*
> *
> *
> *
> *T: 904.469.1524 mobile
> E: jose@...
> http://www.josecgomez.com
> <http://www.linkedin.com/in/josecgomez> <http://www.facebook.com/josegomez>
> <http://www.google.com/profiles/jose.gomez> <http://www.twitter.com/joc85>
> <http://www.josecgomez.com/professional-resume/>
> <http://www.josecgomez.com/feed/>
> <http://www.usdoingstuff.com>
>
> *Quis custodiet ipsos custodes?*
>
>
>
> On Fri, Oct 12, 2012 at 9:09 AM, c.krusen1 <ckrusen1@...> wrote:
>
> > **
> >
> >
> > I need to make the ProdGroup manditory field when either creating a new
> > part, or updating an existing part.
> >
> > Should the "Raise an exception" action be done during Pre-Processing or
> > Post-Processing?
> >
> > Using Post-Processing seems to work. But isn't the Part table already
> > updated by the time the Post-Processing action takes place?
> >
> > And can I limit the action to only occur if the event occurs during while
> > in Part Maint? I don't want other system actions to get hung up if they
> > update a part record that doesn't have the ProdGroup field set.
> >
> >
> >
>
>
> [Non-text portions of this message have been removed]
>
5
What version are you on? Not sure when it was implemented but the required extended property should take care of this for you.

Should be able to go to extended properties maint, load up the part table, find the group field and check the Required checkbox.

May have to restart appserver for the change to take effect, but when it does, Epicor will natively throw a wobbly if you try to save the record without that field filled.

--- In vantage@yahoogroups.com, "c.krusen1" <ckrusen1@...> wrote:
>
> Thanks.
>
> Now how do I keep other processes that that update the Part table from being constrained?
>
> For example, say I create a SalesOrder.Update.Pre-Process directive to keep the line items from having a blank ProdGroup. New or changed order lines will be checked - which is what I want. But when a SalesOrder object (created before implementing this BPM) gets updated (like when a shipment is made against it), won't the BPM prevent the update of the shipping related fields?
>
> Calvin
>
> --- In vantage@yahoogroups.com, Jose Gomez <jose@> wrote:
> >
> > Pre
> >
> > *Jose C Gomez*
> > *Software Engineer*
> > *
> > *
> > *
> > *T: 904.469.1524 mobile
> > E: jose@
> > http://www.josecgomez.com
> > <http://www.linkedin.com/in/josecgomez> <http://www.facebook.com/josegomez>
> > <http://www.google.com/profiles/jose.gomez> <http://www.twitter.com/joc85>
> > <http://www.josecgomez.com/professional-resume/>
> > <http://www.josecgomez.com/feed/>
> > <http://www.usdoingstuff.com>
> >
> > *Quis custodiet ipsos custodes?*
> >
> >
> >
> > On Fri, Oct 12, 2012 at 9:09 AM, c.krusen1 <ckrusen1@> wrote:
> >
> > > **
> > >
> > >
> > > I need to make the ProdGroup manditory field when either creating a new
> > > part, or updating an existing part.
> > >
> > > Should the "Raise an exception" action be done during Pre-Processing or
> > > Post-Processing?
> > >
> > > Using Post-Processing seems to work. But isn't the Part table already
> > > updated by the time the Post-Processing action takes place?
> > >
> > > And can I limit the action to only occur if the event occurs during while
> > > in Part Maint? I don't want other system actions to get hung up if they
> > > update a part record that doesn't have the ProdGroup field set.
> > >
> > >
> > >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
6
Only if you put the BPM in the Shipping Methods...
BPM's are limited to their Business Object specifically.


*Jose C Gomez*
*Software Engineer*
*
*
*
*T: 904.469.1524 mobile
E: jose@...
http://www.josecgomez.com
<http://www.linkedin.com/in/josecgomez> <http://www.facebook.com/josegomez>
<http://www.google.com/profiles/jose.gomez> <http://www.twitter.com/joc85>
<http://www.josecgomez.com/professional-resume/>
<http://www.josecgomez.com/feed/>
<http://www.usdoingstuff.com>

*Quis custodiet ipsos custodes?*



On Fri, Oct 12, 2012 at 9:45 AM, c.krusen1 <ckrusen1@...> wrote:

> **
>
>
> Thanks.
>
> Now how do I keep other processes that that update the Part table from
> being constrained?
>
> For example, say I create a SalesOrder.Update.Pre-Process directive to
> keep the line items from having a blank ProdGroup. New or changed order
> lines will be checked - which is what I want. But when a SalesOrder object
> (created before implementing this BPM) gets updated (like when a shipment
> is made against it), won't the BPM prevent the update of the shipping
> related fields?
>
> Calvin
>
> --- In vantage@yahoogroups.com, Jose Gomez <jose@...> wrote:
> >
> > Pre
> >
> > *Jose C Gomez*
> > *Software Engineer*
> > *
> > *
> > *
> > *T: 904.469.1524 mobile
> > E: jose@...
> > http://www.josecgomez.com
> > <http://www.linkedin.com/in/josecgomez> <
> http://www.facebook.com/josegomez>
> > <http://www.google.com/profiles/jose.gomez> <
> http://www.twitter.com/joc85>
> > <http://www.josecgomez.com/professional-resume/>
> > <http://www.josecgomez.com/feed/>
> > <http://www.usdoingstuff.com>
> >
> > *Quis custodiet ipsos custodes?*
> >
> >
> >
> > On Fri, Oct 12, 2012 at 9:09 AM, c.krusen1 <ckrusen1@...> wrote:
> >
> > > **
>
> > >
> > >
> > > I need to make the ProdGroup manditory field when either creating a new
> > > part, or updating an existing part.
> > >
> > > Should the "Raise an exception" action be done during Pre-Processing or
> > > Post-Processing?
> > >
> > > Using Post-Processing seems to work. But isn't the Part table already
> > > updated by the time the Post-Processing action takes place?
> > >
> > > And can I limit the action to only occur if the event occurs during
> while
> > > in Part Maint? I don't want other system actions to get hung up if they
> > > update a part record that doesn't have the ProdGroup field set.
> > >
> > >
> > >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>


[Non-text portions of this message have been removed]