Field Service Management - Signature Pad

[Jamie Fraser]

Afternoon all,

I've been tasked with implementing Field Service Management (FSM) for my organisation, the documentation for FSM requires some reading between the lines to get anywhere, so far progress is good. We are running London Patch 5.

There is one thing that I'm currently looking into and thought I would throw it out there to see if anyone else has encountered it, we want to use signatures once a work order is complete and have enabled to OOTB signature pad plugin. The signature pad pop up appears when you click "Sign & Confirm" and can be filled in.

However, it seems that once it's inserted into the table signature_image it has none of the references populated, as you can see below. Although if I do it as myself (admin) it populates fine. I've tried doing that with different users with the roles, wm_dispatcher, wm_qualifier, wm_initiator_qualifier_dispather and wm_agent none of them seem to work. The record does have the correct signature image attached though.

I've done some reading and looked at the ACL's on the signature_image table and it looks like there aren't any specific roles required but clearly there's an issue somewhere.

If anyone has any ideas and would be willing to share that'd be fab and if I find the solution in the mean time I will make sure to post it.

Thanks,
Jamie

[Jamie Fraser · Accepted solution]

I have figured out this issue - it was the read ACL for the signature images table. As we want to be able to generate a HTML based order history form for the customers we have made it so the read attributes isn't locked to only allow signatures that where added by the current user.

We are looking into how we want to lock down access to signatures so only customers based at the same site have access to signatures for that site - probably do that via a business rule however I'm waiting on a management decision before I proceed with that.