|
|
|
| Quote: | | It's not that I think your code sucks or you're dumb.. I just believe the permissions system is quite complex and hard to replicate and/or simplify much at this time. |
I agree with you 100% (probably on all counts). If we did an actual bridge we would use whatever API hooks are available for sure. I definitely don't want to spend any time trying to figure out the permissions system from a code perspective. We take enough time figuring it out from the UI.
The initial thought was to keep the task ID from w2P in a customer reference table, then only allow the customer to see some task information and some task log information where the task_log_task was the task ID and the billing code was either BILLABLE or FTC (our two codes for what clients can see). I don't like doing things this way because we always run the risk of an upgrade messing up our end of things, but that is why we use a dev, staging, and production installation. The benefit, though, is we can absolutely control which tasks we want the customer to see (sometimes we have supporting tasks or keep track of work that needs to be done on a customer's behalf that they don't need to know about).
If we went the non-API route I wouldn't release anything into the wild because that would create support nightmares that no one needs. _________________ Chuck Topinka
Sr. Partner, IPG
Ensuring Visibility, Productivity, Profitability through the Internet Performance Group |
|