Hi Nathan,
Nathan Gray schrieb:
I’m looking at extending Tracker and using it as part of a new
Warranty application for projectERP. It has pretty much everything
needed from a tracking point of view (I didn’t know about the
escalations until I started poking. Very nice.), I “just” need to add
the inventory parts and tie it together with a UI. Warranty users
would primarily work through the Warranty app, but there’s too much
good stuff in Tracker not to re-use.
I just want to confirm if I use the link system, are there update
hooks that I can use to have the tracker and warranty claim update
each other, in case users notice the Warranty queue and comment, post
pictures, withdraw the claim, etc. there?
The following is implemented in the link class:
An application A can register a notification hook, which get’s called
whenever an other application B create a link to an entry from A, or
changes something an already linked entry of B with A.
I’d also like to add some ACL to the comments. Consider the following
comment exchange:
Description:
Had problem with pump, please credit our account.
Warranty:
Before this claim can be processed, we require the serial number of
the damaged product
Client:
S/N 123456-78 pleas credit accont
Warranty:
S/N indicates the pump is still covered under warranty. We have
issued an RMA, please return for evaluation.
Client:
Ok sent it off ples credit acct
Warranty:
Pump showed up, looks like somebody drove over it with a truck,
there’s pieces missing and a tread pattern on the bottom. How did
they get it on the bottom?
Warranty Admin:
Check the packaging for damage first, but these guys have a history of
trying to rip us off with warranty claims. If it’s obviously misuse,
their warranty is void. Also, double check that serial number, make
sure it wasn’t pulled off a different pump.
Warranty:
Packaging looks OK. They bubble-wrapped it, but the mounting
bracket’s still missing.
Warranty:
It appears that your product was damaged by something that is not
covered by our warranty, which is limited to defects in materials and
craftsmanship. Your claim has been denied, we regret we are unable to
credit your account at this time.
It’s great that updates are automatically emailed, but we need to be
able to hide some internal commentary, so Warranty and Warranty Admin
can decide what to do about this without Client getting emails.
It looks like it would be fairly simple to add a Public / Owner /
Technicians selectbox to the Add comment tab. Some config and per-
queue preferences would be needed. Maybe some colors on the Comments
tab to indicate who sees what.
Would it be OK to add that in to tracker?
I’ve no problem with that.
Maybe we can hide the flag, if one has no write perm to the flag and
giving noone that permission by default. Then nothing changes (and gets
more complicated) for all installs not setting (and needing) that
permission.
I know it won’t make it until 1.7+ because it will probably need a table
column in egw_tracker_replies, tinyint ‘visibility’.
Until I create the 1.6 release branch, probably this weekend, pleas dont
commit it to trunk, as it’s still feature frozen.
Any other tips or thoughts as I plan?
Nope, currently.
Ralf
Ralf Becker
Director Software Development
Stylite GmbH
[open style of IT]
Morschheimer Strasse 15
67292 Kirchheimbolanden
fon +49 (0) 6352 70629-0
fax +49 (0) 6352 70629-30
cell +49 (0) 170 7815917
mailto: rb@stylite.de
www.stylite.de
www.egroupware.org
Geschäftsführer Andre Keller, Nigel John Vickers,
Gudrun K. Müller und Ralf Becker
Registergericht Kaiserslautern HRB 12087
This SF.Net email is sponsored by the Moblin Your Move Developer’s challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
eGroupWare-developers mailing list
eGroupWare-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-developers
