BPM - Make a Date field Mandatory

Yahoo Archive
1
Can you try making the exception for the date being less than something like the day you went live or Jan 1, 1970?

--- In vantage@yahoogroups.com, "Rashid Mahmood" <emailrashidforum@...> wrote:
>
> It seems like it wont work in this version, Apart from BPM is there any other way of making a date field mandatory?
>
> Thanks a lot for your help.
>
>
>
> --- In vantage@yahoogroups.com, Mike Carter <mcarter@> wrote:
> >
> > 8.03.409C is the latest patch for Vantage 8.
> >
> > From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Randall Weber
> > Sent: Thursday, November 04, 2010 12:42 PM
> > To: vantage@yahoogroups.com
> > Subject: [Vantage] Re: BPM - Make a Date field Mandatory
> >
> >
> >
> > I tested it in 803.409A, which is the latest 803 patch and has been reported
> > to be more stable.
> >
> > --
> > Randy Weber
> > weber.randy@<mailto:weber.randy%40gmail.com>
> > (651) 263-1811
> >
> > http://randallweber.com/
> >
> > [Non-text portions of this message have been removed]
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
2
I would like to set the promise date field (PO release) as a mandatory field through BPM, as we are in a situation where buyers are not putting the promise date regularly. I have tried to create pre Processing method directive, where condition is

the PORel.PromiseDt field of the changed row is equal to the "" value

and action is

raise exception based on the Mandatory Field template


when it try to save this it gives me an error message that the promise date is a date field and value should be dd/mm/yy. Could any one help that how I can put the condition to check if it is a blank field.
Thanks in advance for your help.

Rashid
3
What version of Epicor?
If you are in 9 you can use the Extended Properties Module



*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> <http://www.josecgomez.com/feed/>

*Quis custodiet ipsos custodes?*



On Thu, Nov 4, 2010 at 7:58 AM, Rashid Mahmood
<emailrashidforum@...>wrote:

>
>
> I would like to set the promise date field (PO release) as a mandatory
> field through BPM, as we are in a situation where buyers are not putting the
> promise date regularly. I have tried to create pre Processing method
> directive, where condition is
>
> the PORel.PromiseDt field of the changed row is equal to the "" value
>
> and action is
>
> raise exception based on the Mandatory Field template
>
> when it try to save this it gives me an error message that the promise date
> is a date field and value should be dd/mm/yy. Could any one help that how I
> can put the condition to check if it is a blank field.
> Thanks in advance for your help.
>
> Rashid
>
>
>


[Non-text portions of this message have been removed]
4
Check the Null box in the Specify a Value for the changed to field.

the ttPORel.DueDate field has been changed from any to ?

--
Randy Weber
weber.randy@...
(651) 263-1811

http://randallweber.com/


[Non-text portions of this message have been removed]
5
We are on 8.03.407

I have tried to check the null check box as specified value, it does let me save the BPM but it when I test the BPM it didnot give any message for the empty promise date field. Also I remember that during the BPM course they said that this null check box doesnt work properly so you need to use the "" for null values.
Any other idea please


--- In vantage@yahoogroups.com, Randall Weber <weber.randy@...> wrote:
>
> Check the Null box in the Specify a Value for the changed to field.
>
> the ttPORel.DueDate field has been changed from any to ?
>
> --
> Randy Weber
> weber.randy@...
> (651) 263-1811
>
> http://randallweber.com/
>
>
> [Non-text portions of this message have been removed]
>
6
I Checked this again, and I noticed that eventhough I am selecting the ttPORel Table and PromiseDt field but when it become a condition it becomes PORel.PromiseDt rather than ttPORel.PromiseDt

Rashid

--- In vantage@yahoogroups.com, Randall Weber <weber.randy@...> wrote:
>
> Check the Null box in the Specify a Value for the changed to field.
>
> the ttPORel.DueDate field has been changed from any to ?
>
> --
> Randy Weber
> weber.randy@...
> (651) 263-1811
>
> http://randallweber.com/
>
>
> [Non-text portions of this message have been removed]
>
7
Hi Rashid,

I was putting in a similar BPM (using DueDate instead of PromiseDate) and found that the because the release is automatically created when a new line is added, the BPM wasn't being called at all.

Eventually I came up with:
* add a Pre-Processing BPM onto the PO.ChangeApproveSwitch BO
* condition: number of rows in the <query> is not less than 1
* query: 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 = ?
* action: raise an exception


Now, the user can add lines/releases without the required date, but whenever s/he tries to change the PO to Pending or Approved the BPM is triggered and catches the missing date.

BTW, we're on v8.03.406a

HTH,
Nigel.


--- In vantage@yahoogroups.com, "Rashid Mahmood" <emailrashidforum@...> wrote:
>
>
> I Checked this again, and I noticed that eventhough I am selecting the ttPORel Table and PromiseDt field but when it become a condition it becomes PORel.PromiseDt rather than ttPORel.PromiseDt
>
> Rashid
>
> --- In vantage@yahoogroups.com, Randall Weber <weber.randy@> wrote:
> >
> > Check the Null box in the Specify a Value for the changed to field.
> >
> > the ttPORel.DueDate field has been changed from any to ?
> >
> > --
> > Randy Weber
> > weber.randy@
> > (651) 263-1811
> >
> > http://randallweber.com/
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
8
Hi Nigel,
I have tried this by copy pasting the query and then test by leaveing the due date blank but still this bpm is not firing when I approve the PO.
Any other suggestion please, or any other way to make fields mandatory especially date fields.

Thanks

--- In vantage@yahoogroups.com, "NigelK" <nigel.kerley@...> wrote:
>
> Hi Rashid,
>
> I was putting in a similar BPM (using DueDate instead of PromiseDate) and found that the because the release is automatically created when a new line is added, the BPM wasn't being called at all.
>
> Eventually I came up with:
> * add a Pre-Processing BPM onto the PO.ChangeApproveSwitch BO
> * condition: number of rows in the <query> is not less than 1
> * query: 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 = ?
> * action: raise an exception
>
>
> Now, the user can add lines/releases without the required date, but whenever s/he tries to change the PO to Pending or Approved the BPM is triggered and catches the missing date.
>
> BTW, we're on v8.03.406a
>
> HTH,
> Nigel.
>
>
> --- In vantage@yahoogroups.com, "Rashid Mahmood" <emailrashidforum@> wrote:
> >
> >
> > I Checked this again, and I noticed that eventhough I am selecting the ttPORel Table and PromiseDt field but when it become a condition it becomes PORel.PromiseDt rather than ttPORel.PromiseDt
> >
> > Rashid
> >
> > --- In vantage@yahoogroups.com, Randall Weber <weber.randy@> wrote:
> > >
> > > Check the Null box in the Specify a Value for the changed to field.
> > >
> > > the ttPORel.DueDate field has been changed from any to ?
> > >
> > > --
> > > Randy Weber
> > > weber.randy@
> > > (651) 263-1811
> > >
> > > http://randallweber.com/
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
>
9
Hi Rashid,

Do you have other BPMs that you know *are* running?

Take out the condition and try authorising a PO. Without the condition this should automatically trigger the BPM. If that doesn't work, then there's an issue with your BPM setup.


Nigel.

--- In vantage@yahoogroups.com, "Rashid Mahmood" <emailrashidforum@...> wrote:
>
> Hi Nigel,
> I have tried this by copy pasting the query and then test by leaveing the due date blank but still this bpm is not firing when I approve the PO.
> Any other suggestion please, or any other way to make fields mandatory especially date fields.
>
> Thanks
>
10
Hi Nigel,
Yes it is working, I have removed the condition and try to approve a purchase order and it give me an error message. but some how it is not working with the condition.

any other ideas please.

Rashid

--- In vantage@yahoogroups.com, "NigelK" <nigel.kerley@...> wrote:
>
> Hi Rashid,
>
> Do you have other BPMs that you know *are* running?
>
> Take out the condition and try authorising a PO. Without the condition this should automatically trigger the BPM. If that doesn't work, then there's an issue with your BPM setup.
>
>
> Nigel.
>
> --- In vantage@yahoogroups.com, "Rashid Mahmood" <emailrashidforum@> wrote:
> >
> > Hi Nigel,
> > I have tried this by copy pasting the query and then test by leaveing the due date blank but still this bpm is not firing when I approve the PO.
> > Any other suggestion please, or any other way to make fields mandatory especially date fields.
> >
> > Thanks
> >
>
11
I think it should be:
Â
 the PORel.PromiseDt field of the added row is equal to the ? value
Â
When I first started working with BPMs, I noticed that when you select a tt
field, it changes it in the condition statement. I just chalked it up to one of
those Epicor inconsistencies. It still works.



________________________________
From: Rashid Mahmood <emailrashidforum@...>
To: vantage@yahoogroups.com
Sent: Thu, November 4, 2010 1:26:33 PM
Subject: [Vantage] Re: BPM - Make a Date field Mandatory

Â
Hi Nigel,
Yes it is working, I have removed the condition and try to approve a purchase
order and it give me an error message. but some how it is not working with the
condition.


any other ideas please.

Rashid

--- In vantage@yahoogroups.com, "NigelK" <nigel.kerley@...> wrote:
>
> Hi Rashid,
>
> Do you have other BPMs that you know *are* running?
>
> Take out the condition and try authorising a PO. Without the condition this
>should automatically trigger the BPM. If that doesn't work, then there's an
>issue with your BPM setup.
>
>
> Nigel.
>
> --- In vantage@yahoogroups.com, "Rashid Mahmood" <emailrashidforum@> wrote:
> >
> > Hi Nigel,
> > I have tried this by copy pasting the query and then test by leaveing the due
>date blank but still this bpm is not firing when I approve the PO.
>
> > Any other suggestion please, or any other way to make fields mandatory
>especially date fields.
> >
> > Thanks
> >
>







[Non-text portions of this message have been removed]
12
I tested it in 803.409A, which is the latest 803 patch and has been reported
to be more stable.

--
Randy Weber
weber.randy@...
(651) 263-1811

http://randallweber.com/


[Non-text portions of this message have been removed]
13
8.03.409C is the latest patch for Vantage 8.

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Randall Weber
Sent: Thursday, November 04, 2010 12:42 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: BPM - Make a Date field Mandatory



I tested it in 803.409A, which is the latest 803 patch and has been reported
to be more stable.

--
Randy Weber
weber.randy@...<mailto:weber.randy%40gmail.com>
(651) 263-1811

http://randallweber.com/

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



[Non-text portions of this message have been removed]
14
It seems like it wont work in this version, Apart from BPM is there any other way of making a date field mandatory?

Thanks a lot for your help.



--- In vantage@yahoogroups.com, Mike Carter <mcarter@...> wrote:
>
> 8.03.409C is the latest patch for Vantage 8.
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Randall Weber
> Sent: Thursday, November 04, 2010 12:42 PM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: BPM - Make a Date field Mandatory
>
>
>
> I tested it in 803.409A, which is the latest 803 patch and has been reported
> to be more stable.
>
> --
> Randy Weber
> weber.randy@...<mailto:weber.randy%40gmail.com>
> (651) 263-1811
>
> http://randallweber.com/
>
> [Non-text portions of this message have been removed]
>
>
>
> [Non-text portions of this message have been removed]
>
15
I have tried with the added row
"the PORel.PromiseDt field of the added row is equal to the ? value"
but still no success.
I have other BPMs where I make fields mandatory but those are not date fields and I used "" instead of ticking the Null check box as specified value, May it is because of the format of the field.

Can we do it through customisation? and if yes how?

Thanks for your help.

--- In vantage@yahoogroups.com, Steven Gotschall <sgotschall@...> wrote:
>
> I think it should be:
> ÂÂ
>  the PORel.PromiseDt field of the added row is equal to the ? value
> ÂÂ
> When I first started working with BPMs, I noticed that when you select a tt
> field, it changes it in the condition statement. I just chalked it up to one of
> those Epicor inconsistencies. It still works.
>
>
>
> ________________________________
> From: Rashid Mahmood <emailrashidforum@...>
> To: vantage@yahoogroups.com
> Sent: Thu, November 4, 2010 1:26:33 PM
> Subject: [Vantage] Re: BPM - Make a Date field Mandatory
>
> ÂÂ
> Hi Nigel,
> Yes it is working, I have removed the condition and try to approve a purchase
> order and it give me an error message. but some how it is not working with the
> condition.
>
>
> any other ideas please.
>
> Rashid
>
> --- In vantage@yahoogroups.com, "NigelK" <nigel.kerley@> wrote:
> >
> > Hi Rashid,
> >
> > Do you have other BPMs that you know *are* running?
> >
> > Take out the condition and try authorising a PO. Without the condition this
> >should automatically trigger the BPM. If that doesn't work, then there's an
> >issue with your BPM setup.
> >
> >
> > Nigel.
> >
> > --- In vantage@yahoogroups.com, "Rashid Mahmood" <emailrashidforum@> wrote:
> > >
> > > Hi Nigel,
> > > I have tried this by copy pasting the query and then test by leaveing the due
> >date blank but still this bpm is not firing when I approve the PO.
> >
> > > Any other suggestion please, or any other way to make fields mandatory
> >especially date fields.
> > >
> > > Thanks
> > >
> >
>
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
16
Hi Rashid,

Did you change PORel.DueDate in my query to PORel.PromiseDt? I just copied/pasted my code.

Sorry, I can't think of anything else. This BPM works for us.

Try starting with a much reduced query - say, looking at the PODetail.PartNum - and then building it up gradually. Sometimes works for me.

Nigel.

--- In vantage@yahoogroups.com, "Rashid Mahmood" <emailrashidforum@...> wrote:
>
> Hi Nigel,
> Yes it is working, I have removed the condition and try to approve a purchase order and it give me an error message. but some how it is not working with the condition.
>
> any other ideas please.
>
> Rashid
>
> --- In vantage@yahoogroups.com, "NigelK" <nigel.kerley@> wrote:
> >
> > Hi Rashid,
> >
> > Do you have other BPMs that you know *are* running?
> >
> > Take out the condition and try authorising a PO. Without the condition this should automatically trigger the BPM. If that doesn't work, then there's an issue with your BPM setup.
> >
> >
> > Nigel.
> >
> > --- In vantage@yahoogroups.com, "Rashid Mahmood" <emailrashidforum@> wrote:
> > >
> > > Hi Nigel,
> > > I have tried this by copy pasting the query and then test by leaveing the due date blank but still this bpm is not firing when I approve the PO.
> > > Any other suggestion please, or any other way to make fields mandatory especially date fields.
> > >
> > > Thanks
> > >
> >
>
17
I tried with both POREl.DueDate and leaving the due date empty but nothing happen and then with PORel.PromiseDt same result. Now I have tried to make this mandatory through Customisation (RowRuleWizard), It worked in training company by changing the rule as warning rather than mandatory and it started giving me warning message if promise date is Null, but when I rewrite it to the live company it didnt work, it only changed the colour of the promise date field. so I am still stuck with this seems like a simple thing.


--- In vantage@yahoogroups.com, "NigelK" <nigel.kerley@...> wrote:
>
> Hi Rashid,
>
> Did you change PORel.DueDate in my query to PORel.PromiseDt? I just copied/pasted my code.
>
> Sorry, I can't think of anything else. This BPM works for us.
>
> Try starting with a much reduced query - say, looking at the PODetail.PartNum - and then building it up gradually. Sometimes works for me.
>
> Nigel.
>
> --- In vantage@yahoogroups.com, "Rashid Mahmood" <emailrashidforum@> wrote:
> >
> > Hi Nigel,
> > Yes it is working, I have removed the condition and try to approve a purchase order and it give me an error message. but some how it is not working with the condition.
> >
> > any other ideas please.
> >
> > Rashid
> >
> > --- In vantage@yahoogroups.com, "NigelK" <nigel.kerley@> wrote:
> > >
> > > Hi Rashid,
> > >
> > > Do you have other BPMs that you know *are* running?
> > >
> > > Take out the condition and try authorising a PO. Without the condition this should automatically trigger the BPM. If that doesn't work, then there's an issue with your BPM setup.
> > >
> > >
> > > Nigel.
> > >
> > > --- In vantage@yahoogroups.com, "Rashid Mahmood" <emailrashidforum@> wrote:
> > > >
> > > > Hi Nigel,
> > > > I have tried this by copy pasting the query and then test by leaveing the due date blank but still this bpm is not firing when I approve the PO.
> > > > Any other suggestion please, or any other way to make fields mandatory especially date fields.
> > > >
> > > > Thanks
> > > >
> > >
> >
>
18
Have you tried comparing the date field to the Date01, Date02 or any of
the user date fields that you are not using? I seem to remember getting
that to work in one of my BPMs. It is worth a shot anyway.



Linda

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Rashid Mahmood
Sent: Friday, November 05, 2010 6:48 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: BPM - Make a Date field Mandatory





I tried with both POREl.DueDate and leaving the due date empty but
nothing happen and then with PORel.PromiseDt same result. Now I have
tried to make this mandatory through Customisation (RowRuleWizard), It
worked in training company by changing the rule as warning rather than
mandatory and it started giving me warning message if promise date is
Null, but when I rewrite it to the live company it didnt work, it only
changed the colour of the promise date field. so I am still stuck with
this seems like a simple thing.

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"NigelK" <nigel.kerley@...> wrote:
>
> Hi Rashid,
>
> Did you change PORel.DueDate in my query to PORel.PromiseDt? I just
copied/pasted my code.
>
> Sorry, I can't think of anything else. This BPM works for us.
>
> Try starting with a much reduced query - say, looking at the
PODetail.PartNum - and then building it up gradually. Sometimes works
for me.
>
> Nigel.
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"Rashid Mahmood" <emailrashidforum@> wrote:
> >
> > Hi Nigel,
> > Yes it is working, I have removed the condition and try to approve a
purchase order and it give me an error message. but some how it is not
working with the condition.
> >
> > any other ideas please.
> >
> > Rashid
> >
> > --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"NigelK" <nigel.kerley@> wrote:
> > >
> > > Hi Rashid,
> > >
> > > Do you have other BPMs that you know *are* running?
> > >
> > > Take out the condition and try authorising a PO. Without the
condition this should automatically trigger the BPM. If that doesn't
work, then there's an issue with your BPM setup.
> > >
> > >
> > > Nigel.
> > >
> > > --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
, "Rashid Mahmood" <emailrashidforum@> wrote:
> > > >
> > > > Hi Nigel,
> > > > I have tried this by copy pasting the query and then test by
leaveing the due date blank but still this bpm is not firing when I
approve the PO.
> > > > Any other suggestion please, or any other way to make fields
mandatory especially date fields.
> > > >
> > > > Thanks
> > > >
> > >
> >
>





[Non-text portions of this message have been removed]
19
Yes - threaten to fire the buyer who does not enter dates.

Okay maybe that's a bit rough. We created dashboards for this kind of stuff
- called them 'Exception Reports' or 'Whoops Reports'. For us, it was sales
that missed some important data entry elements; such as weekend ship dates,
zero unit price, etc. The dashboard would identify these things and the
sales manager reviewed it every morning. After getting emails from their
boss saying, "Why is the price zero on SO#12345?" they magically began
making less mistakes.

Randy Weber

On Fri, Nov 5, 2010 at 4:40 AM, Rashid Mahmood
<emailrashidforum@...>wrote:

>
>
> It seems like it wont work in this version, Apart from BPM is there any
> other way of making a date field mandatory?
>
> Thanks a lot for your help.
>
>
> --- In vantage@yahoogroups.com <vantage%40yahoogroups.com>, Mike Carter
> <mcarter@...> wrote:
> >
> > 8.03.409C is the latest patch for Vantage 8.
> >
> > From: vantage@yahoogroups.com <vantage%40yahoogroups.com> [mailto:
> vantage@yahoogroups.com <vantage%40yahoogroups.com>] On Behalf Of Randall
> Weber
> > Sent: Thursday, November 04, 2010 12:42 PM
> > To: vantage@yahoogroups.com <vantage%40yahoogroups.com>
> > Subject: [Vantage] Re: BPM - Make a Date field Mandatory
> >
> >
> >
> > I tested it in 803.409A, which is the latest 803 patch and has been
> reported
> > to be more stable.
> >
> > --
> > Randy Weber
> > weber.randy@...<mailto:weber.randy%40gmail.com<weber.randy%2540gmail.com>
> >
>
> > (651) 263-1811
> >
> > http://randallweber.com/
> >
> > [Non-text portions of this message have been removed]
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>



--
Randy Weber
weber.randy@...
(651) 263-1811

http://randallweber.com/


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