Another thing you could do, since the first release is created by the
method, is do a post-processing message. Granted, the update would already
have occurred, so it would be more informational than stopping the action.
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
NigelK
Sent: Thursday, May 06, 2010 7:26 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: PO Line Due Date Customization
Hi Sean,
Once you get your BPM installation sorted....
We have a BPM for this in place. Like Sean suggested, I had problems with
the first PO Release being created automatically so I took a slightly
different route.
I created a Pre-Processing directive on the PO.ChangeApproveSwitch BO.
The condition is: "number of rows in the <query> is not less than 1".
The query is: for each ttPOHeader where (ttPOHeader.RowMod='A' or
ttPOHeader.RowMod='U') and ttPOHeader.ApprovalStatus = 'U' , each PORel
where PORel.Company = ttPOHeader.Company and PORel.PONum = ttPOHeader.PONum
and PORel.DueDate = ?"
The Action is: raise an Exception.
Now, when the user finishes entering a new PO and tries to click the
Approval tickbox, the BPM won't let it if any line is missing the DueDate.
HTH,
Nigel.
--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> , "Sean
McDaniel" <smcdaniel@...> wrote:
Behalf
method, is do a post-processing message. Granted, the update would already
have occurred, so it would be more informational than stopping the action.
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
NigelK
Sent: Thursday, May 06, 2010 7:26 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: PO Line Due Date Customization
Hi Sean,
Once you get your BPM installation sorted....
We have a BPM for this in place. Like Sean suggested, I had problems with
the first PO Release being created automatically so I took a slightly
different route.
I created a Pre-Processing directive on the PO.ChangeApproveSwitch BO.
The condition is: "number of rows in the <query> is not less than 1".
The query is: for each ttPOHeader where (ttPOHeader.RowMod='A' or
ttPOHeader.RowMod='U') and ttPOHeader.ApprovalStatus = 'U' , each PORel
where PORel.Company = ttPOHeader.Company and PORel.PONum = ttPOHeader.PONum
and PORel.DueDate = ?"
The Action is: raise an Exception.
Now, when the user finishes entering a new PO and tries to click the
Approval tickbox, the BPM won't let it if any line is missing the DueDate.
HTH,
Nigel.
--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> , "Sean
McDaniel" <smcdaniel@...> wrote:
>[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
> This might be a bit tricky with the first release as it doesn't follow
> the creation methods for the 2nd through n releases. The first release
> is created when you save the line for the first time so my guess is that
> you can require the due date be populated pre-save on an add of a po
> line and then require the due date on the update of a release from there
> on.
>
> Open to other ideas :o)
>
>
>
> From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Behalf
> Of Sean Toler[Non-text portions of this message have been removed]
> Sent: Thursday, May 06, 2010 12:20 PM
> To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> Subject: [Vantage] PO Line Due Date Customization
>
>
>
>
>
> Hello.
> I would like to make it so that the "Due Date" field in the PO Entry
> Line Item tab is a required field. We have an employee who is having a
> hard time remembering to give our vendors a due date, so I am hoping
> that I can remove human error from the equation.
>
> Does anyone know how or if this can be done?
>
>
>
>
>
> [Non-text portions of this message have been removed]
>