Credit Hold? Blank Title 93354

Yahoo Archive
1
We encountered the same (or similar - ours may have been unapproving vendors) issue before prepping for going live a few years ago.

I'm out of the development code now but recall the quickfix was to customize the client app:

Detect session's dcduser id on app load.

I don't recall if (knowing it was poor practice & would eventually be changed after the mad rush to go live & work thru the initial rash of problems was thru) if I just hardcoded the 2-3 users we wanted to allow to put customers on hold (unapprove vendors??) OR if I poked into empbasic (FKV, subtable view or coded search by ID or BAQ search) to check status of a highjacked checkbox## field (indicating rights to take the action).

You tie all this to whether the control is active or inactive.

...Thinking it was a emp ID hardcode (and assuming IT has long since circled back around & done it a maintainable way).

Seems to me a combo of process & field security should allow you to isolate the users you are after.

Wish I could help more but the memory has faded.

Rob

--- Original Message ---
From:"johngeh" <johngeh@...>
Sent:Thu 9/9/10 12:30 pm
To:vantage@yahoogroups.com
Subj:[Vantage] Credit Hold?

We needed to be able to restrict who had the ability to change the credit hold status of a customer.

I went into process security and updated CheckCreditHold in bo.Customer to only give specific users access to this functionality. In a sense it worked since only there users have access to changing the credit hold status. The problem is that it had unintended behaviors as well. It also restricts access to changing a customers price list access and the ability to add new customers.

Does anyone know how to make this work so that I only restrict access to credit hold and allow other users to create new users and have access to other customer parameters (i.e. price lists).

Please let me know.

Thanks.

John
2
We needed to be able to restrict who had the ability to change the credit hold status of a customer.

I went into process security and updated CheckCreditHold in bo.Customer to only give specific users access to this functionality. In a sense it worked since only there users have access to changing the credit hold status. The problem is that it had unintended behaviors as well. It also restricts access to changing a customers price list access and the ability to add new customers.

Does anyone know how to make this work so that I only restrict access to credit hold and allow other users to create new users and have access to other customer parameters (i.e. price lists).

Please let me know.

Thanks.

John
3
Hi John,

You can restrict access to the credit hold field (or any other field) for specific users or groups by using Field Security instead of Process Security.

David

--- In vantage@yahoogroups.com, "johngeh" <johngeh@...> wrote:
>
> We needed to be able to restrict who had the ability to change the credit hold status of a customer.
>
> I went into process security and updated CheckCreditHold in bo.Customer to only give specific users access to this functionality. In a sense it worked since only there users have access to changing the credit hold status. The problem is that it had unintended behaviors as well. It also restricts access to changing a customers price list access and the ability to add new customers.
>
> Does anyone know how to make this work so that I only restrict access to credit hold and allow other users to create new users and have access to other customer parameters (i.e. price lists).
>
> Please let me know.
>
> Thanks.
>
> John
>