Making Fields Mandatory (V8.00.10)

Yahoo Archive
1
There is a bug with mandatory field! If the user changes to a
different line (such as on p.o. entry) the system will let you save
even if the manditory field in not populated. I have had a call in
and support has duplicated this problem in both version 8.00.810b and
in the current version of 8.03, but an scr has not been created for
it yet.


--- In vantage@yahoogroups.com, "bw2868bond" <bwalker@...> wrote:
>
> In V8 it is described in the help as such:
>
> Purpose
> You can indicate that a field is required, or mandatory, by using
the
> Rule Wizard. You do this by first creating a mandatory rule and
then
> adding a mandatory rule action to it. Here's how:
>
> Within the Customization Tools Dialog, click on the Wizards tab and
> the Rule Wizard tab.
>
> Click the New Row Rule button.
>
> For the Rule Description field, enter a description that indicates
> this is a mandatory row rule. For example: MyMandatoryRule
>
> Now on the Select View list, choose the table, or dataView, that
> contains the field you want to make mandatory. For example: ShipVia
>
> Set up the rule condition so the Select Field is always equal to
> itself. To do this, select the same option for the Select Field and
> Rule Value lists and then select Equals for the rule condition.
>
> -bw
>
> --- In vantage@yahoogroups.com, "bchguessing" <bhepner@> wrote:
> >
> > In 6.1 it was very easy make a field mandatory for the users by
> simply
> > checking madatory box for the field. I'm told by support that I
> need
> > to write code to do this in V8.00.10. I have done a little
> > programming in Visual Basic but never in .Net. Has anyone found
an
> > easier way of making a field mandatory or a generic set of code
> that
> > can be manipulated for any field?
> >
>
2
In 6.1 it was very easy make a field mandatory for the users by simply
checking madatory box for the field. I'm told by support that I need
to write code to do this in V8.00.10. I have done a little
programming in Visual Basic but never in .Net. Has anyone found an
easier way of making a field mandatory or a generic set of code that
can be manipulated for any field?
3
In V8 it is described in the help as such:

Purpose
You can indicate that a field is required, or mandatory, by using the
Rule Wizard. You do this by first creating a mandatory rule and then
adding a mandatory rule action to it. Here's how:

Within the Customization Tools Dialog, click on the Wizards tab and
the Rule Wizard tab.

Click the New Row Rule button.

For the Rule Description field, enter a description that indicates
this is a mandatory row rule. For example: MyMandatoryRule

Now on the Select View list, choose the table, or dataView, that
contains the field you want to make mandatory. For example: ShipVia

Set up the rule condition so the Select Field is always equal to
itself. To do this, select the same option for the Select Field and
Rule Value lists and then select Equals for the rule condition.

-bw

--- In vantage@yahoogroups.com, "bchguessing" <bhepner@...> wrote:
>
> In 6.1 it was very easy make a field mandatory for the users by
simply
> checking madatory box for the field. I'm told by support that I
need
> to write code to do this in V8.00.10. I have done a little
> programming in Visual Basic but never in .Net. Has anyone found an
> easier way of making a field mandatory or a generic set of code
that
> can be manipulated for any field?
>
4
> In 6.1 it was very easy make a field mandatory for the users by simply
> checking madatory box for the field. I'm told by support that I need
> to write code to do this in V8.00.10.

I would agree that adding a "mandatory" field to the user interface would make
this easier but 8.0 is a different world. In pre-8, THE interface was the GUI
but in 8+ you now have business objects and web services that can modify your
data as well. If one wants to make a field mandatory everywhere and not just
the GUI, this requirement must be defined at a lower level.

Version 8.3 has a new feature (which I haven't tested yet) that let's you set
up "inhibitors" that prevent transactions from completing under certain
circumstances. The module is called BPM (for Business Process Manager I
believe) and this might be something to consider for all who want to make
fields mandatory everywhere and not just in the user interface.

Mark W.