It is true that we use, and want to use, the CustRequest entity for
more than just requests from customers. One way to think of it is as a
"custom" request instead of a "customer" request, but it is a little
bit silly.
Either way I don't think it is really worth changing the name of the
Well,
I don't know.
Hans, what you are suggesting is good in general, but in this specific
situation I am not sure.
The reason is that CustRequest is a bad name for the entity (Request
would be more appropriate) because a Request could come from a party
that is not a customer.
Before we com
Hans,
Thanks for looking into the issue. This seems to be a good idea to me.
It will bring things inline with best practices.
Regards
Anil Patel
On Jul 16, 2009, at 9:13 AM, Hans Bakker wrote:
I would like to ask the community about the following change.
Currently the screens and forms fil
I would like to ask the community about the following change.
Currently the screens and forms files in the system for the Entity
CustRequest are called RequestForms.xml and RequestScreens.xml
if you work pretty often in this area it still happens pretty frequently
that i cannot find them because
